Date: Sat, 28 Nov 2009 12:04:38 -0500 From: Glen Barber <glen.j.barber@gmail.com> To: Benjamin Kaduk <kaduk@mit.edu> Cc: freebsd-net@freebsd.org Subject: Re: kern/140036: [iwn] [lor] lock order reversal with iwn0_com_lock and iwn0 softc lock Message-ID: <4ad871310911280904h10b6ab16gc0d73057973ebf08@mail.gmail.com> In-Reply-To: <200911240230.nAO2U6Ak004167@freefall.freebsd.org> References: <200911240230.nAO2U6Ak004167@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, On Mon, Nov 23, 2009 at 9:30 PM, Benjamin Kaduk <kaduk@mit.edu> > =A0> On Sun, 22 Nov 2009, Bernhard Schmidt wrote: > =A0>> > =A0>> Can you verify that the LOR is gone with the latest checkout of my > =A0>> repository? > =A0>> Compile instructions: > =A0>> http://forums.freebsd.org/showpost.php?p=3D47627&postcount=3D16 > =A0> > =A0> I upgraded to today's current (which picked up a number of probably-= unrelated > =A0> changes), and then installed the driver from > =A0> your tree on top of it. > =A0> No LOR on boot, and I'll let you know if I see any lockups. I am seeing this LOR on 8-STABLE (with the latest iwn(4) patches from the site above). > > > =A0I got a "lockup" (no idea what actually was happening) while in X toni= ght; > =A0nothing useful is in the logs. Do you mean "lockup" as in the system becomes non-responsive? If so, I am experiencing this as well. I recently switched my filesystem to ZFS because of the time fsck_ufs takes, and added the following options to GENERIC to try to track this down: KDB DDB BREAK_TO_DEBUGGER ALT_BREAK_TO_DEBUGGER INVARIANTS INVARIANT_SUPPORT WITNESS WITNESS_SKIPSPIN SOCKBUF_DEBUG DIAGNOSTIC SW_WATCHDOG DEBUG_VFS_LOCKS > =A0I'm not even sure if I can blame iwn for it ... The last time the system locked, I wasn't in X. I saw the following on the console before it became unusable: firmware error log: error type =3D "SYSASSERT" (0x00000005) program counter =3D 0x0000C920 source line =3D 0x00000619 error data =3D 0x000000FE00000000 branch link =3D 0x0000C8420000C842 interrupt link =3D 0x0000090E00000000 time =3D 1182627 driver status: tx ring 0: qid=3D0 cur=3D1 queued=3D1 tx ring 1: qid=3D1 cur=3D0 queued=3D0 tx ring 2: qid=3D2 cur=3D0 queued=3D0 tx ring 3: qid=3D3 cur=3D0 queued=3D0 tx ring 4: qid=3D4 cur=3D12 queued=3D0 tx ring 5: qid=3D5 cur=3D0 queued=3D0 tx ring 6: qid=3D6 cur=3D0 queued=3D0 tx ring 7: qid=3D7 cur=3D0 queued=3D0 tx ring 8: qid=3D8 cur=3D0 queued=3D0 tx ring 9: qid=3D9 cur=3D0 queued=3D0 tx ring 10: qid=3D10 cur=3D0 queued=3D0 tx ring 11: qid=3D11 cur=3D0 queued=3D0 tx ring 12: qid=3D12 cur=3D0 queued=3D0 tx ring 13: qid=3D13 cur=3D0 queued=3D0 tx ring 14: qid=3D14 cur=3D0 queued=3D0 tx ring 15: qid=3D15 cur=3D0 queued=3D0 tx ring 16: qid=3D16 cur=3D0 queued=3D0 tx ring 17: qid=3D17 cur=3D0 queued=3D0 tx ring 18: qid=3D18 cur=3D0 queued=3D0 tx ring 19: qid=3D19 cur=3D0 queued=3D0 rx ring: cur=3D59 iwn0: iwn_apm_stop_master: timeout waiting for master If there is more information I can provide, please let me know. --=20 Glen Barber
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4ad871310911280904h10b6ab16gc0d73057973ebf08>