---------- Forwarded message ---------- Date: Thu, 19 Sep 2002 19:49:53 +0200 From: Csillag Tamas <[EMAIL PROTECTED]> To: Randy.Dunlap <[EMAIL PROTECTED]> Subject: Re: [Linux-usb-users] Bug: disconnect failure
Forward to the list if you want. "Randy.Dunlap" wrote: > On Thu, 19 Sep 2002, Csillag Tamas wrote: > > | Bug report: > | > | > ================ > | > COREFILE SUMMARY > | > ================ > | > > | > The system died due to a software failure. > | > > | > <4> bmAttributes = 03 (Interrupt) > | > <4> wMaxPacketSize = 0001 > | > <4> bInterval = 08 > | > <7>usb.c: kusbd: /sbin/hotplug add 3 > | > <7>usb.c: kusbd policy returned 0xfffffffe > | > <7>hub.c: port 1 connection change > | > <7>hub.c: port 1, portstatus 100, change 3, 12 Mb/s > | > <6>usb.c: USB disconnect on device 2 > | > <7>usb.c: kusbd: /sbin/hotplug remove 2 > | > <7>usb.c: kusbd policy returned 0xfffffffe > | > <6>SysRq : Emergency Sync > | > <6>SysRq : Emergency Remount R/O > | > <6>SysRq : Start a Crash Dump (If Configured) > | > <1>Dumping from interrupt handler ! > | > <1>Uncertain scenario - but will try my best > | > <4> > | > <4>dump: Dumping to device 0x30a [ide0(3,10)] on CPU 0 ... > | > <4>dump: Compression value is 0x0, Writing dump header > | > <4> > | > <4>dump: Pass 1: Saving Reserved Pages: > | > <4>dump: Memory Bank[0]: 0 ... ffeffff: \- > | > > | > =========================== > | > STACK TRACE OF FAILING TASK > | > =========================== > | > > | > ================================================================ > | > STACK TRACE FOR TASK: 0xc1bce000 (khubd) > > This is the interesting part. Where did it go? I am really sorry but I do not know. It used to produce this section but not anymore. I cannot do 'lcrash /boot/System.map dump' neither it says: 'NULL buffer pointer' and exits But I think it maybe a deadlock (Dumping from interrupt handler), Sysrq keys work..... _____________________________________________________________________________ The next time that it locks up, I suggest that you try alt-sysrq-P and alt-sysrq-T to see if there is any good information there about where it is locked up. If they don't work, try ctrl-scrolllock (same output as alt-sysrq-T). ~Randy ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
