Re: usb issues in sarge: scanner, multicard
I am going to add the following, which may be relevant:
tail -f /var/log/messages
Aug 13 23:16:56 localhost gconfd (trc-4692): Resolved address
"xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only
configuration source at position 2
Aug 13 23:17:00 localhost kernel: usb 2-1: control timeout on ep0in
Aug 13 23:17:03 localhost gconfd (trc-4692): Resolved address
"xml:readwrite:/home/trc/.gconf" to a writable configuration source at
position 0
Aug 13 23:17:05 localhost kernel: usb 2-1: control timeout on ep0in
Aug 13 23:17:10 localhost kernel: usb 2-1: control timeout on ep0in
Aug 13 23:17:11 localhost kernel: parport0: PC-style at 0x378 (0x778)
[PCSPP,TRISTATE]
Aug 13 23:17:11 localhost kernel: parport0: irq 7 detected
Aug 13 23:17:11 localhost kernel: parport0: Printer, hp deskjet 5550
Aug 13 23:17:11 localhost kernel: lp0: using parport0 (polling).
Aug 13 23:17:16 localhost kernel: usb 2-1: control timeout on ep0in
Message from syslogd@localhost at Sat Aug 13 23:17:46 2005 ...
localhost kernel: Disabling IRQ #193
Aug 13 23:17:46 localhost last message repeated 6 times
Aug 13 23:17:46 localhost kernel: [__report_bad_irq+42/144]
__report_bad_irq+0x2a/0x90
Aug 13 23:17:46 localhost kernel: [note_interrupt+112/176]
note_interrupt+0x70/0xb0
Aug 13 23:17:46 localhost kernel: [do_IRQ+352/416] do_IRQ+0x160/0x1a0
Aug 13 23:17:46 localhost kernel: [common_interrupt+24/32]
common_interrupt+0x18/0x20
Aug 13 23:17:46 localhost kernel: [default_idle+0/64]
default_idle+0x0/0x40
Aug 13 23:17:46 localhost kernel: [default_idle+44/64]
default_idle+0x2c/0x40
Aug 13 23:17:46 localhost kernel: [cpu_idle+59/80] cpu_idle+0x3b/0x50
Aug 13 23:17:46 localhost kernel: [printk+366/448] printk+0x16e/0x1c0
Aug 13 23:17:51 localhost kernel: usb 2-1: control timeout on ep0in
Aug 13 23:18:16 localhost last message repeated 5 times
Notice that the line
Message from syslogd@localhost at Sat Aug 13 23:17:46 2005 ...
and all after it appeared after conecting the multicard. I disconected
the multicard without response. Hmm, sounds not good.
Reply to: