These aren't really examples of a "deadlock", they're just oopses. Can you disassemble the qh_completions() code and find out what it's trying to execute when it oopses? Either GDB or "objdump" can be used.
This is a new one, but at least it looks like it's the same spot in the code each time ... so maybe it's simple. I've not done as much SMP testing with EHCI as I'd like.
- Dave
The deadlocks occur randomly, i.e. at no specific position during read or write operations.
----------------
with the following oopses:
Unable to handle kernel paging request at virtual address 00100104
printing eip:
f89d1617
*pde = 00000000
Oops: 0002 [#1]
SMP
CPU: 1
EIP: 0060:[<f89d1617>] Not tainted
EFLAGS: 00010046 (2.6.5)
EIP is at qh_completions+0x162/0x35d [ehci_hcd]
eax: 00100100 ebx: 80001c00 ecx: f6ce91b8 edx: 00200200
esi: f6ce9180 edi: f9d4244c ebp: f7f45ea4 esp: f7f45e60
ds: 007b es: 007b ss: 0068
Process swapper (pid: 0, threadinfo=f7f44000 task=f7f411f0)
Stack: f704ca9c f6d4244c 00001000 80001c00 f6ced14c 01000000 00000000 00000001
00000000 f6ce9218 f6ce9c60 00000000 c1a17660 f704cca4 f6ced14c f6ced100
f704ca9c f7f45ed0 f89d24bc f704ca9c f6ced100 00000000 00000001 00000000
Call Trace:
[<f89d24bc>] scan_async+0x7e/0x125 [ehci_hcd]
[<f89d441a>] ehci_watchdog+0x0/0xcd [ehci_hcd]
[<f89d4f47>] ehci_work+0x35/0xbb [ehci_hcd]
[<f89d4482>] ehci_watchdog+0x68/0xcd [ehci_hcd]
...
------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
