Skip to contentSkip to conversation

2.6.1-rc1, scanner.ko, oops

DISCUSSION John M Flinchbaugh 2 participants 4 messages Jan 3, 2004 – Jan 4, 2004

lore
Share & tools
lore
#0 lore raw

i tried my canoscan 670u scanner with 2.6.1-rc1's scanner module, xsane 0.91, sane 1.0.13. (also, i'm using ohci-hcd on a tyan thunder s2462ung.)

i had some trouble with "funky results" when all my usb devices were connected with a hub and all, but i'll continue to research that myself.

with just the scanner and my apc ups plugged into separate ports, the scanner worked nicely, but when i tried to rmmod scanner, rmmod segfaulted and i got this error in dmesg:

drivers/usb/core/usb.c: deregistering driver usbscanner ohci_hcd 0000:00:07.4: shutdown urb dd9d07c0 pipe 40008280 ep1in-intr drivers/usb/core/file.c: removing 1 minor drivers/usb/core/file.c: release_usb_class_dev - scanner1 usb 1-1: hcd_unlink_urb dd9d07c0 fail -22

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

EIP is at disconnect_scanner+0x2c/0x5d [scanner]
eax: ffffffff ebx: dfd79bd4 ecx: e0d0d0a0 edx: 00000007
esi: 00000000 edi: dd9d086c ebp: de6c7e5c esp: de6c7e4c
ds: 007b es: 007b ss: 0068
Process rmmod (pid: 2989, threadinfo=de6c6000 task=c426ad20)

Stack: dfd79bc0 e0d11498 dfd79bc0 e0d11500 de6c7e78 e0c52167 dfd79bc0 dfd79bc0 
       dfd79c00 dfd79bd4 e0d11520 de6c7e90 c0230ed0 dfd79bd4 dfd79c00 dd9d0884 
       dd9d0840 de6c7eac e0d0c9f0 dfd79bd4 dfd79bc0 dd9d0884 e0d11430 00000000 
Call Trace:
 [<e0c52167>] usb_unbind_interface+0x77/0x80 [usbcore]
 [<c0230ed0>] device_release_driver+0x60/0x70
 [<e0d0c9f0>] destroy_scanner+0x50/0xb0 [scanner]
 [<c01dd61d>] kobject_cleanup+0x8d/0x90
 [<e0c52167>] usb_unbind_interface+0x77/0x80 [usbcore]
 [<c0230ed0>] device_release_driver+0x60/0x70
 [<c0230f02>] driver_detach+0x22/0x40
 [<c023113a>] bus_remove_driver+0x3a/0x70
 [<c0231534>] driver_unregister+0x14/0x28
 [<e0c52242>] usb_deregister+0x32/0x40 [usbcore]
 [<e0d0d222>] usb_scanner_exit+0x12/0x14 [scanner]
 [<c013a797>] sys_delete_module+0x147/0x1a0
 [<c0153604>] sys_munmap+0x44/0x70
 [<c010950f>] syscall_call+0x7/0xb

Code: 80 7e 1e 00 75 1e 85 f6 74 12 8d 46 44 8b 5d f8 8b 75 fc 89 
Signature · 3 lines
____________________}John Flinchbaugh{______________________
| [email protected]         http://www.hjsoft.com/~glynis/ |
~~Powered by Linux: Reboots are for hardware upgrades only~~
#1 lore raw
Quoted 3 lines · John M Flinchbaugh

i tried my canoscan 670u scanner with 2.6.1-rc1's scanner module, xsane 0.91, sane 1.0.13. (also, i'm using ohci-hcd on a tyan thunder s2462ung.)

Can you try not using the scanner module? xsane should work just fine using libusb, talking to the device from userspace with no kernel module.

thanks,

greg k-h

#2 lore raw
Quoted 7 lines · Greg KH
Quoted 3 lines · John M Flinchbaugh

i tried my canoscan 670u scanner with 2.6.1-rc1's scanner module, xsane 0.91, sane 1.0.13. (also, i'm using ohci-hcd on a tyan thunder s2462ung.)

Can you try not using the scanner module? xsane should work just fine using libusb, talking to the device from userspace with no kernel module.

it does indeed work using libusb. i had gotten the impression that the scanner module may not be the preferred path these days. is this correct?

Signature · 3 lines
____________________}John Flinchbaugh{______________________
| [email protected]         http://www.hjsoft.com/~glynis/ |
~~Powered by Linux: Reboots are for hardware upgrades only~~
#3 lore raw
Quoted 5 lines · John M Flinchbaugh
Quoted 4 lines · Greg KH
Quoted 3 lines · John M Flinchbaugh

i tried my canoscan 670u scanner with 2.6.1-rc1's scanner module, xsane 0.91, sane 1.0.13. (also, i'm using ohci-hcd on a tyan thunder s2462ung.)

Quoted 7 lines
Quoted 3 lines

Can you try not using the scanner module? xsane should work just fine using libusb, talking to the device from userspace with no kernel module.

it does indeed work using libusb. i had gotten the impression that the scanner module may not be the preferred path these days. is this correct?

See the help text for CONFIG_USB_SCANNER :)

thanks,

greg k-h