I've seen this problem under stress, not normally during boot. Time
permitting I will have a look into this next week.
Probably a race condition somewhere.
Could you tell me whether the panic appears after a lengthy wait or is
it directly related to a an event like plugging in a device or starting
to talk to it (usbd, ugen, etc.)
Cheers,
Nick
> "me too" (but only if there is a device plugged in)
>
> > I get this same panic with both devices I've tried; a Kodak
DC265 and a
> > Sandisk CompactFlash reader. Its not obvious why this is
happening (at
> > least from where I'm sitting.)
> >
> > Any ideas?
> >
> > Should I report back with a kernel compiled with OHCI_DEBUG?
> >
> > Thanks.
> >
> > ...
> > ohci0: <OPTi 82C861 (FireLink) USB controller> irq 9 at device
11.0 on pci0
> > usb0: OHCI version 1.0, legacy support
> > usb0: <OPTi 82C861 (FireLink) USB controller> on ohci0
> > usb0: USB revision 1.0
> > uhub0: OPTi OHCI root hub, class 9/0, rev 1.00/1.00, addr 1
> > uhub0: 2 ports with 2 removable, self powered
> > panic: ohci_hash_find_td: addr 0x03e7c770 not found
> >
> > Debugger("panic")
> > Stopped at Debugger+0x37: movl $0,in_Debugger
> > db> t
> > Debugger(c0289aa3) at Debugger+0x37
> > panic(c029c0c0,3e7c770,c0373cbc,c0225142,c07a5800) at
panic+0x74
> > ohci_hash_find_td(c07a5800,3e7c770,6,c07a5800,2) at
ohci_hash_find_td+0x33
> > ohci_process_done(c07a5800,3e7c7d0,6b9457,c07a5800,c07a6e80) at
> ohci_process_done+0x1e
> > ohci_intr1(c07a5800) at ohci_intr1+0x10c
> > ohci_waitintr(c07a5800,c07a6e80,c07a6e80,c07a6e80,c0373d20) at
> ohci_waitintr+0x69
>
>
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
>
---------End of Included Message----------
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
