Bug #1101
ohci related panic
| Status: | New | Start date: | ||
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% |
|
| Category: | - | |||
| Target version: | - |
Description
panic: ohci_abort_xfer: not in process context
Trace beginning at frame 0xcc50ed1c
panic(cc50ed40, c1697f80, c1a65c80, c1ad6ec8,cc50ed60) at panic+0x8c
ohci_abort_xfer(c1697f80, cc50ed84, c045f6ab, c1ad6ec8, c0625364) at
ohci_abort_xfer+0xc2
ohci_timeout_task(c1ad6ec8, c0625364, ff800000, c0625364,0) at
ohci_timeout_task+0x29
usb_task_thread(c066400,0,0,0,0) at usb_task_thread+0x9b
kthread_exit at kthread_exit
Debugger("panic")
Stopped at Debugger+0x34 movb $0, in_Debugger.3949
2 usb devices connected: usb flash drive (umass0) and ucom0 (Motorola
phone), ppp up and running via ucom.
Related todos
History
Updated by hasso almost 5 years ago
I don't see any of these in the dmesg attached. And please provide dmesg
from verbose boot mode, please.
Updated by polachok almost 5 years ago
verbose dmesg attached with devices plugged in.
Updated by tuxillo over 3 years ago
Hi Polachok,
Matt did some changes to OHCI in the summer. Could you try to reproduce this again?
Cheers,
Antonio Huete