Date: Mon, 12 Apr 2004 15:32:47 -0700 From: Steve Kargl <sgk@troutmask.apl.washington.edu> To: Chris Shenton <chris@shenton.org> Cc: current@freebsd.org Subject: Re: 5.2-CURRENT yesterday: GIANT-LOCKED, lock order reversal Message-ID: <20040412223247.GA59079@troutmask.apl.washington.edu> In-Reply-To: <86ekqtcemd.fsf@PECTOPAH.shenton.org> References: <86ekqtcemd.fsf@PECTOPAH.shenton.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Apr 12, 2004 at 01:03:54PM -0400, Chris Shenton wrote: > Built world and new kernel from yesterday's CVSup and noticed a bunch > of [GIANT-LOCKED] in the bootup. Then, after it came up, it spewed > errors about lock order reversal. I'm not clueful enough to understand > what it's trying to tell me :-( > > Here's a "uname -a" info, then the dmesg output with GIANT-LOCK and > lock order reversal. Should I be concerned? Any work-arounds? Thanks. > GIANT-LOCK is simply an anotation that a device driver is still under the GAINT lock. Until a few weeks ago, drivers were reporting [MPSAFE] to note the driver was now under a finer grain lock. The LOR you reported has been reported previous. -- Steve
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040412223247.GA59079>