14 messages in org.freebsd.freebsd-currentRe: Removing USB keyboard after files...| From | Sent On | Attachments |
|---|---|---|
| Garrett Cooper | Mar 7, 2010 2:06 am | |
| Garrett Cooper | Mar 7, 2010 2:23 am | |
| Hans Petter Selasky | Mar 7, 2010 10:39 am | |
| Giovanni Trematerra | Mar 8, 2010 5:59 am | |
| Giovanni Trematerra | Mar 10, 2010 1:56 pm | |
| Tom Couch | Mar 10, 2010 2:07 pm | |
| Garrett Cooper | Mar 10, 2010 9:58 pm | |
| Giovanni Trematerra | Mar 11, 2010 12:08 am | |
| Garrett Cooper | Mar 12, 2010 7:33 pm | |
| Giovanni Trematerra | Mar 13, 2010 3:56 pm | |
| Giovanni Trematerra | Mar 25, 2010 1:17 am | |
| Attilio Rao | Apr 13, 2010 3:48 am | |
| Attilio Rao | Apr 13, 2010 3:50 am | |
| Garrett Cooper | Apr 13, 2010 7:44 am |
| Subject: | Re: Removing USB keyboard after filesystems synced causes panic with destroyed mutex twa(4)? | |
|---|---|---|
| From: | Garrett Cooper (yane...@gmail.com) | |
| Date: | Mar 7, 2010 2:23:50 am | |
| List: | org.freebsd.freebsd-current | |
On Sun, Mar 7, 2010 at 2:07 AM, Garrett Cooper <yane...@gmail.com> wrote:
Hi Alexander and Hans, I 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_intr.c:88
cpuid = 1 KDB: enter: panic [thread pid 12 tid 100025 ] Stopped at kdb_enter+0x3d: movq $0,0x40289c(%rip) db>
I 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
_______________________________________________ free...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "free...@freebsd.org"