Date: Sun, 7 Mar 2010 02:24:17 -0800 From: Garrett Cooper <yanefbsd@gmail.com> To: Alexander Motin <mav@freebsd.org>, Hans Petter Selasky <hselasky@c2i.net> Cc: FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: Removing USB keyboard after filesystems synced causes panic with destroyed mutex twa(4)? Message-ID: <7d6fde3d1003070224k3626a9b5y98c11a43eef1bed4@mail.gmail.com> In-Reply-To: <7d6fde3d1003070207q621e69ado2cb64e431feacd76@mail.gmail.com> References: <7d6fde3d1003070207q621e69ado2cb64e431feacd76@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Mar 7, 2010 at 2:07 AM, Garrett Cooper <yanefbsd@gmail.com> wrote: > Hi Alexander and Hans, > =A0 =A0I recently did the following which generated a panic on a > 9-CURRENT kernel compiled on the 26th: > > 1. Executed reboot > 2. Removed keyboard. > 3. Some time after `All buffers synced\nUptime: ...' was displayed, > the keyboard was registered disconnected. > 4. The interrupt was delivered to my twa(4) enabled card and the > kernel panicked, like so: > > ugen2.2: <Mitsumi Electric> at usbus2 (disconnected) > uhub8: at uhub2, port 1, addr 2 (disconnected) > ugen2.3: <Mitsumi Electric> at usbus2 (disconnected) > ukbd0: at uhub8, port 3, addr 3 (disconnected) > uhid0: at uhub8, port 3, addr 3 (disconnected) > panic: mtx_lock_spin() of destroyed mutex @ /usr/src/sys/dev/twa/tw_cl_in= tr.c:88 > > cpuid =3D 1 > KDB: enter: panic > [thread pid 12 tid 100025 ] > Stopped at =A0 =A0 =A0 =A0 kdb_enter+0x3d: movq =A0 =A0 $0,0x40289c(%rip) > db> > > =A0 =A0I wish I could provide you with more details, but unfortunately I > the USB bus isn't registering the fact that I'm reattaching the > keyboard right now and the box won't reboot automatically :( (didn't > set the right sysctl beforehand to panic automatically). I'll try and > reproduce the issue again, but I was just wondering whether or not you > guys had seen this problem before. Phew... it's reproducible with that kernel. Here's what I did exactly (because my original directions were incorrect): 1. Hit power button (for S5). 2. Disconnect keyboard RIGHT as `Uptime: ...' is displayed. Kernel panicked on my system again. Now to figure out if it still exists with a kernel compiled today, and also how to debug it if it still does exist :/... Thanks, -Garrett
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7d6fde3d1003070224k3626a9b5y98c11a43eef1bed4>