[Bugme-new] [Bug 4338] New: Scanner configuration freeze system

[bugme-daemon at osdl.org]

http://bugme.osdl.org/show_bug.cgi?id=4338

           Summary: Scanner configuration freeze system
    Kernel Version: 2.6.8
            Status: NEW
          Severity: blocking
             Owner: andmike at us.ibm.com
         Submitter: joerg.beschorner at t-online.de


Distribution: SuSE 9.2

Hardware Environment: AMD Athlon XP2000+; SCSI Controller Domex DMX3191 with
scanner Mustek A3  SP

Software Environment: SuSE-YAST;SANE 

Problem Description:
If I try to configure the scanner with YAST the system freeze.
Till SuSE 9.0 with Kernel 2.4.21 everything worked fine.
I get the following informations at /var/log/boot.msg 
> 
> <5>SCSI subsystem initialized
> <6>ACPI: PCI interrupt 0000:00:0c.0[A] -> GSI 11 (level, low) -> IRQ 11
> <6>scsi0 : Domex DMX3191D
> <5>  Vendor: SCANNER   Model:                   Rev: 1.01
> <5>  Type:   Scanner                            ANSI SCSI revision: 01 CCS

In /var/log/messages I finde the following entries
> 
> Mar  9 20:25:11 jblinux kernel: Domex DMX3191D did not call scsi_unregister
> Mar  9 20:25:11 jblinux kernel:  [<f883da2f>] exit_this_scsi_driver+0xaf/0xf5 
> [dmx3191d]
> Mar  9 20:25:11 jblinux kernel:  [<c012ea9a>] sys_delete_module+0x15a/0x170
> Mar  9 20:25:11 jblinux kernel:  [<c014648e>] unmap_vma_list+0xe/0x20
> Mar  9 20:25:11 jblinux kernel:  [<c0146788>] do_munmap+0xd8/0x120
> Mar  9 20:25:11 jblinux kernel:  [<c014680c>] sys_munmap+0x3c/0x60
> Mar  9 20:25:11 jblinux kernel:  [<c0105c69>] sysenter_past_esp+0x52/0x79
.
.
repeats until I kill the system

If I start sane-find-scanner at a terminal I get
Mar 14 20:41:37 jblinux sane-find-scanner: resmgr: server response code 502
Mar 14 20:41:37 jblinux last message repeated 2 times
Mar 14 20:41:37 jblinux sane-find-scanner: resmgr: server response code 501
Mar 14 20:41:37 jblinux sane-find-scanner: resmgr: server response code 502
Mar 14 20:43:37 jblinux kernel: scsi0 : aborting command
Mar 14 20:43:37 jblinux kernel: scsi0 : destination target 6, lun 0
Mar 14 20:43:37 jblinux kernel:         command = Inquiry 00 00 00 05 00 
Mar 14 20:43:37 jblinux kernel: 
Mar 14 20:43:37 jblinux kernel: NCR5380 core release=7.   
Mar 14 20:43:37 jblinux kernel: Base Addr: 0x00000    io_port: ec00      IRQ: 11.
Mar 14 20:43:37 jblinux kernel: scsi0: no currently connected command
Mar 14 20:43:37 jblinux kernel: scsi0: issue_queue
Mar 14 20:43:37 jblinux kernel: scsi0: disconnected_queue
Mar 14 20:43:37 jblinux kernel: 
Mar 14 20:43:37 jblinux kernel: scsi0 : aborting command
Mar 14 20:43:37 jblinux kernel: scsi0 : destination target 6, lun 0
Mar 14 20:43:37 jblinux kernel:         command = Inquiry 00 00 00 05 00 
.
repeating till [Ctrl+C]
.
Mar 14 20:44:17 jblinux kernel: 
Mar 14 20:44:17 jblinux kernel: scsi: Device offlined - not ready after error
recovery: host 0 channel 0 id 6 lun 0
Mar 14 20:44:17 jblinux kernel: Unable to handle kernel NULL pointer dereference
at virtual address 0000014c
Mar 14 20:44:17 jblinux kernel:  printing eip:
Mar 14 20:44:17 jblinux kernel: f8853a89
Mar 14 20:44:17 jblinux kernel: *pde = 00000000
Mar 14 20:44:17 jblinux kernel: Oops: 0000 [#1]

The maintainer of the SANE Mustek backend tool recommended to ask the kernel crow

Steps to reproduce:
see above

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.