Re: USB umass panic

From: Anish Mistry <mistry.7_at_osu.edu>
Date: Tue, 7 Sep 2004 21:46:47 -0400
On Sunday 05 September 2004 08:16 pm, you wrote:
> On Sun, Sep 05, 2004 at 06:29:52PM -0400, Anish Mistry wrote:
> > I'm getting the following panic when I plugged/unplugged in my usb camera
> > for the first time.
> >
> > Repeat:
> > 1) plug in camera while on
> > 2) unplug a few seconds later
> > 3) panic (hand transcribed, must get firewire debugging equipment):
> >
> > umass0: at uhub0  port 1 (addr 2) disconnected
> >
> >
> > Fatal trap 12: page fault while in kernel mode
> > fault virtual address = 0xdeadc0de
> > fault code   = supervisor read, page not present
> > instruction pointer = 0x8:0xc072327b
> > stack pointer  = 0x10:0xcb2c0c0c
> > frame pointer  = 0x10:0xcb2c0c3c
> > code segment  = base 0x0, limit 0xfffff, type 0x1b
> >     = DPL 0, pres 1, def32 1, gran 1
> > processor eflags = interrupt enabled, resume, IOPL = 0
> > current process = 22 (irq11: ohci0)
> > [thread 100019]
> > Stopped at ohci_device_request+0xdf: movl 0(%edx),%ecx
> > db> trace
> > ohci_device_request(c16bd200,c16bd200,c16d8700,cb2c0c64,c071aa03) at 
> > ohci_device_request+0xdf
> > ohci_device_ctrl_start(c16bd200,c116b400,c16d8700,cb2c0c8c,c071a962) at 
> > ohci_device_ctrl_start+0x23
> > usbd_start_next(c16d8700,0,0,0,c116b43c) at usbd_start_next+0x37
> > usb_transfer_complete(c116b400,5,c16d8700,0,0) at
> > usb_transfer_complete+0x1c2 
> > ohci_softint(c1143000,c1143000,cb2c0ce8,c07227b6,c1143000) at 
> > ohci_softintr+0x238
> > usb_schedsoftintr(c1143000,c1143000,a651f30,c116ac00,c10b1780) at 
> > usb_schedsoftintr+0x2f
> > ohci_intr1(c1143000,cd2c0d1c,c049f1c6,c1143000,0) at ohci_intr1+0x1aa
> > ohci_intr(c1143000,0,1372,c10bde00,0) at ohci_intr+0x30
> > ithread_loop(c10b1780,cb2c0d48,c10b1780,c049f044,0) at othread_loop+0x182
> > fork_exit(c049f044,c10b1780,cb2c0d48) at fork_exit+0x7e
> > fork_trampoline() at fork_trampoline+0x8
> > --- trap 0x1, eip = 0, esp = 0xcb2c0d7c, ebp = 0 ---
>
> Hi,
>
> Just to give a better clue has to where the trap occurs,
> if you can find the kernel.debug file on your system,
> (usually under /usr/obj/usr/src/sys/[kernel config file
> name]/kernel.debug), what is the output of:
>
> gdb kernel.debug
>
> l *0xc072327b
>
This just gives me  "no source file for address 0xc072327b".
From DDB after the panic "print *0xc072327b" shows e1810a8b.
I can't get a dump, and when I manually try to dump (call doadump) from the 
debugger I get a bunch of ATA RESET errors and it doesn't dump.

Not sure how to get anymore debug info.


-- 
Anish Mistry

Received on Tue Sep 07 2004 - 23:44:53 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:11 UTC