Antti P Miettinen <ananaza@xxxxxx> writes: > Anyone have a handy way of generating interrupt load? At least flood ping is not any better in provoking the disconnect than scp, dd'ing from disk with small packets, busylooping shell script with and without nice etc. It just seems to happen sometimes. Last was early morning today. Hmm.. seems to be about the time I woke up, but I did not even touch the machine :) To get an understanding about the situation I added some dump_stack() calls here and there. Is the below backtrace sane? Are people seeing USB disconnects without nvidia proprietary drivers? :-) ehci_hcd 0000:03:0c.2: devpath 1 ep3in 3strikes [pg0+944436239/1069159424] qtd_copy_status+0x25f/0x270 [ehci_hcd] [pg0+944436789/1069159424] qh_completions+0x115/0x390 [ehci_hcd] [pg0+944441047/1069159424] scan_async+0xa7/0x160 [ehci_hcd] [pg0+944453218/1069159424] ehci_work+0x52/0xf0 [ehci_hcd] [pg0+944455402/1069159424] ehci_irq+0x21a/0x360 [ehci_hcd] [try_to_wake_up+113/1072] try_to_wake_up+0x71/0x430 [pg0+952375303/1069159424] _nv001806rm+0x87/0xa8 [nvidia] [rebalance_tick+245/288] rebalance_tick+0xf5/0x120 [pg0+944243209/1069159424] usb_hcd_irq+0x39/0x70 [usbcore] [handle_IRQ_event+61/112] handle_IRQ_event+0x3d/0x70 [__do_IRQ+157/272] __do_IRQ+0x9d/0x110 [do_IRQ+25/48] do_IRQ+0x19/0x30 [common_interrupt+26/32] common_interrupt+0x1a/0x20 [default_idle+0/96] default_idle+0x0/0x60 [default_idle+44/96] default_idle+0x2c/0x60 [cpu_idle+111/192] cpu_idle+0x6f/0xc0 [start_kernel+415/512] start_kernel+0x19f/0x200 [unknown_bootoption+0/496] unknown_bootoption+0x0/0x1f0 I put the kernel log to http://www.hut.fi/~apm/kern.log -- http://www.iki.fi/~ananaza/ _______________________________________________ linux-dvb mailing list linux-dvb@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
