Skip to contentSkip to conversation

khubd crash on scanner disconnect

DISCUSSION Matthias Andree 3 participants 6 messages Jan 30, 2004 – Jan 31, 2004

lore
Share & tools
lore
#0 lore raw

Hi,

I have just caught this khubd NULL dereference simply by unplugging my scanner. Kernel is a current 2.6.2-rc2 from BK, PNP enabled:

usb 1-1: USB disconnect, address 2

Unable to handle kernel NULL pointer dereference at virtual address 0000001e
 printing eip:
c0299a9c
*pde = 00000000
Oops: 0000 [#1]
CPU:    0
EIP:    0060:[<c0299a9c>]    Not tainted
EFLAGS: 00010282

EIP is at disconnect_scanner+0x2c/0x5f
eax: ffffffff ebx: d3d25094 ecx: c03d76d8 edx: 00000030
esi: 00000000 edi: d3cb28c0 ebp: d3dc1e24 esp: d3dc1e14
ds: 007b es: 007b ss: 0068
Process khubd (pid: 5, threadinfo=d3dc0000 task=d3f8e040)

Stack: d3d25080 c03d76d8 d3d25080 c03d7740 d3dc1e40 c02824f6 d3d25080 d3d25080 
       d3d25094 d3d25094 c03d7760 d3dc1e58 c023b456 d3d25094 d3d250c0 d3cb28fc 
       d3cb28e8 d3dc1e74 c02993ec d3d25094 d3d25080 d3cb28fc c03d766c 00000000 
Call Trace:
 [<c02824f6>] usb_unbind_interface+0x76/0x80
 [<c023b456>] device_release_driver+0x66/0x70
 [<c02993ec>] destroy_scanner+0x7c/0xe0
 [<c01e3225>] kobject_cleanup+0x95/0xa0
 [<c02824f6>] usb_unbind_interface+0x76/0x80
 [<c023b456>] device_release_driver+0x66/0x70
 [<c023b5cd>] bus_remove_device+0x6d/0xb0
 [<c023a394>] device_del+0x74/0xd0
 [<c0288a20>] usb_disable_device+0x90/0xc0
 [<c0282fd4>] usb_disconnect+0xd4/0x120
 [<c028562f>] hub_port_connect_change+0x22f/0x350
 [<c0285041>] hub_port_status+0x41/0xb0
 [<c02859c6>] hub_events+0x276/0x330
 [<c0285ad3>] hub_thread+0x53/0x110
 [<c011f6c0>] default_wake_function+0x0/0x20
 [<c0285a80>] hub_thread+0x0/0x110
 [<c01092a9>] kernel_thread_helper+0x5/0xc

Code: 80 7e 1e 00 75 16 85 f6 74 21 8d 46 3c 8b 5d f8 8b 75 fc 89 
Signature · 3 lines
Matthias Andree

Encrypt your mail: my GnuPG key ID is 0x052E7D95
#1 lore raw
Quoted 4 lines · Matthias Andree

Hi,

I have just caught this khubd NULL dereference simply by unplugging my scanner. Kernel is a current 2.6.2-rc2 from BK, PNP enabled:

Known bug, don't use that module, it's OBSOLETED. Use xscane and libusb instead.

thanks,

greg k-h

#2 lore raw
Quoted 10 lines · Greg KH
Quoted 4 lines · Matthias Andree

Hi,

I have just caught this khubd NULL dereference simply by unplugging my scanner. Kernel is a current 2.6.2-rc2 from BK, PNP enabled:

Known bug, don't use that module, it's OBSOLETED. Use xscane and libusb instead.

Are you sure, it is "xscane" and not "xsane"? I thought you just did a typo in my post, but now you did it twice, so no typo?

Prakash

#3 lore raw
Quoted 9 lines · Prakash K. Cheemplavam
Quoted 8 lines · Greg KH
Quoted 4 lines · Matthias Andree

Hi,

I have just caught this khubd NULL dereference simply by unplugging my scanner. Kernel is a current 2.6.2-rc2 from BK, PNP enabled:

Quoted 5 lines
Quoted 2 lines

Known bug, don't use that module, it's OBSOLETED. Use xscane and libusb instead.

Are you sure, it is "xscane" and not "xsane"? I thought you just did a typo in my post, but now you did it twice, so no typo?

Sorry, I don't know what the program is called, as I've never used it...

greg k-h

#4 lore raw
In reply to Greg KH
Quoted 8 lines · Greg KH
Quoted 4 lines · Matthias Andree

Hi,

I have just caught this khubd NULL dereference simply by unplugging my scanner. Kernel is a current 2.6.2-rc2 from BK, PNP enabled:

Known bug, don't use that module, it's OBSOLETED. Use xscane and libusb instead.

Well, if it's "obsoleted" AND "broken", why not remove it from Kconfig altogether, just leaving a pointer "scanner has been replaced by libusb"?

Signature · 3 lines
Matthias Andree

Encrypt your mail: my GnuPG key ID is 0x052E7D95
#5 lore raw
In reply to Greg KH
Quoted 2 lines · Greg KH

Known bug, don't use that module, it's OBSOLETED. Use xscane and libusb instead.

You mean xsane, or any other stuff that uses original SANE backends, Epkowa's iscan doesn't appear to work yet (but seems to require the scanner module still), see sane-devel archives:
http://lists.alioth.debian.org/pipermail/sane-devel/2003-December/009803.html

JFTR, my /etc/sane.d/epson.conf (SANE 1.0.10 here) now has:

# /etc/sane.d/epson.conf
# I personally don't need this:
scsi EPSON
# adjust the hex numbers to vendor and product as printed
# by sane-find-scanner, this is for instance an Epson Perfection 1650:
usb libusb
usb 0x04b8 0x0110

KHK's "epson" backend seems to work fine though. scanimage -L, xsane.

Signature · 3 lines
Matthias Andree

Encrypt your mail: my GnuPG key ID is 0x052E7D95