On Fri, Oct 11, 2002 at 11:25:51AM -0700, Greg KH wrote: > > I'm currently testing multiple readers with SuSE 8.1 (linux 2.4.19). > > The computer does freeze often at the end of tests in the middle of > > testruns. The nun lock and caps lock LEDs did then blink. The text > > console did just freeze, but this text console was not in text mode, > > but in fbdev graphics mode. I will get the hardware the next days, > > so that I can test it here localy. Any idea where to look? > Sounds like the kernel paniced, so any oops message that you can get > (run in text mode or use a serial console cable) would be needed.
Ok. I did it test now with a 2.4.9 on Rotkaeppchen 7.2. The message is: ...[Don't see what's here.] Call Trace: [<c0215216>] copyrite [kernel] 0xaf6 [<c...>] uhci_clean_transfer [usb-uhci] 0x8c [<c...>] __down [kernel] 0x54 [<c...>] __down_failed [kernel] 0x8 [<c...>] __insmod_cyberjack_S.text_L3744 [cyberjack] 0xeeb [<c...>] process_urb [usb-uhci] 0x1c5 [<c...>] uhci_interrupt [usb-uhci] 0xdc [<c...>] handle_IRQ_event [kernel] 0x3a [<c...>] do_IRQ [kernel] 0x68 [<c...>] call_do_IRQ [kernel] 0x5 [<c...>] __insmod_cyberjack_S.text_L3744 [cyberjack] 0x5db [<c...>] ezusb_set_rest_R44ebaf6a [usbserial] 0x2c9 [<c...>] write_chan [kernel] 0x19f [<c...>] tty_write [kernel] 0x14e [<c...>] write_chan [kernel] 0x0 [<c...>] sys_write [kernel] 0x96 [<c...>] system_call [kernel] 0x33 Code: 0f 0b 5f 58 8d 65 f4 5b 5e 5f 5d c3 89 f6 8d bc 27 00 00 00 Kernel panic: Aiee, killing interrupt handler! I will try to get more output from newer kernels. Mahlzeit endergone Zwiebeltuete ------------------------------------------------------- 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-devel
