USB scanner not working with 2.6.26-rc3

Hello everyone.

I switched to 2.6.25-rc3 today, and couldnt get the scanner working. It works in 2.6.25.3. All i did was to open up kooka (kde scanning program) and tried to do a preview scan. After nothing happend i tried to replug the scanner but it wont get detected now.

That is what dmesg says:

usb 1-3: new high speed USB device using ehci_hcd and address 4
usb 1-3: configuration #1 chosen from 1 choice
scsi7 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 4
usb-storage: waiting for device to settle before scanning
usblp0: USB Bidirectional printer dev 4 if 1 alt 0 proto 2 vid 0x6B10 pid 0x805F
usbcore: registered new interface driver usblp
scsi 7:0:0:0: Direct-Access Canon MP600Storage 0107 PQ: 0 ANSI: 2
sd 7:0:0:0: [sde] Attached SCSI removable disk
sd 7:0:0:0: Attached scsi generic sg6 type 0
usb-storage: device scan complete
usb 1-3: usbfs: interface 1 claimed by usblp while 'kooka' sets config #1 usb 1-3: usbfs: interface 1 claimed by usblp while 'kooka' sets config #1 usb 1-3: usbfs: interface 1 claimed by usblp while 'kooka' sets config #1 ehci_hcd 0000:00:02.1: HC died; cleaning up
usb 1-1: USB disconnect, address 2
usb 1-3: USB disconnect, address 4
usblp0: removed
irq 20: nobody cared (try booting with the "irqpoll" option)
Pid: 3598, comm: wcg_dddt_autodo Tainted: P 2.6.26-rc3 #1

Call Trace:
 <IRQ>  [<ffffffff802544c3>] __report_bad_irq+0x30/0x72
 [<ffffffff802546ff>] note_interrupt+0x1fa/0x25b
 [<ffffffff80254dcc>] handle_fasteoi_irq+0xb0/0xd8
 [<ffffffff8020dfff>] do_IRQ+0x6d/0xd4
 [<ffffffff8020b781>] ret_from_intr+0x0/0xa
 <EOI>

handlers:
[<ffffffff803d6734>] (usb_hcd_irq+0x0/0x58)
Disabling IRQ #20

Maybe someone will know what causes that. If any more informations are needed, feel free to ask. I am willing to test :)

Have a nice day everyone.

brot
--
To unsubscribe from this list: send the line "unsubscribe kernel-testers" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html

Does it also happen with a plain ftp.kernel.org kernel without any patches applied or other modules loaded?

cu
Adrian

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

--
To unsubscribe from this list: send the line "unsubscribe kernel-testers" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Well, the kernel is only tainted because of the nvidia driver. which i have in every kernel. It seems like my printer/scanner or usb controller is having problems atm, as it is causing problems on 2.6.25.3 where it should work.

Another question: http://lkml.org/lkml/2008/5/9/229 - it doesnt seem that anyone looked at this bug, or am i wrong ? maybe one should point ingo or peter at it.

Have a nice day.

brot
--
To unsubscribe from this list: send the line "unsubscribe kernel-testers" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html

It's not impossible that the nvidia driver messed with interrupts in a way causing your problem.

There have been too many problems in the kernel in the past that turned out to be caused by binary-only modules after developers had wasted much time on them.

A kernel module has the full power to break _everything_ and we cannot debug their blob.

Please try without this driver ever loaded since booting (you should even be able to reproduce this problem without running X).

If you still see it, please send the output of:
- dmesg -s 1000000
- cat /proc/interrupts

Rafael, did they ever answer?

cu
Adrian

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

--
To unsubscribe from this list: send the line "unsubscribe kernel-testers" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html