Hi Duncan,
Duncan Sands wrote:
>please do sysctl-t (or whatever it is on your platform) to get a process
>backtrace.
>
I did a sysreq + t and got the following for the stuck process:
puppy D 8023249C 0 246 220 (NOTLB)
Stack : 00008000 8000b574 b804a940 000f422b b89d3fc0 000f422b 81dc68d4
001a286d
00000002 8119fcb8 00002af8 8119fe90 81cfac00 81cfac00 00002af8
813a2814
8119fc58 8023249c 8119fd18 812f8f48 802b7560 0000001e 00000001
81dc67b0
80027fc8 8119fcbc 8119fcbc 00000000 00000000 81dc67b0 80027fc8
00000000
00000000 8119ad40 00000000 8119ad40 386d4454 80193f6c 81026820
0000000f
...
Running the values manually through ksymoops, I get this:
Adhoc 8023249c <wait_for_completion+c4/154>
Adhoc 8000b574 <do_IRQ+24/34>
Adhoc 802b7560 <__per_cpu_start+4c0/f60>
Adhoc 80027fc8 <default_wake_function+0/20>
Adhoc 80193f6c <usb_start_wait_urb+bc/124>
I'm not sure if this information is what you were after. If not, can you
give me some tips on how to get better info? I can recompile the kernel
with different options if that will help.
>>00:06:55 (none) kern.err kernel: scheduling while atomic:
>>puppy/0x10000001/204
>>
>
>Was this all the information? No backtrace?
>
I think there may have been, but I did not have the System.map for that
kernel, so didn't pay much attention. My bad.
I haven't got much experience in collecting relevant details when it
comes to kernel issues, but am willing to learn. Pointers to any tools /
processes that will make it easier to track the source of these issues
down are very welcome.
Thanks,
Peter.
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
