[sane-devel] Kernel-panic

[Bernd Porr]

Hi folks,

AGFA SNAPSCAN1236s, kernel 2.4.19, SANE 1.0.9, debian woody.

Following happens when I try to scan from xscanimage:

Nov  1 15:18:36 sauerkraut kernel: Attached scsi generic sg0 at scsi0, 
channel 0, id 0, lun 0,  type 6
Nov  1 15:22:08 sauerkraut kernel: Unable to handle kernel NULL pointer 
dereference at virtual address 0000001b
Nov  1 15:22:08 sauerkraut kernel:  printing eip:
Nov  1 15:22:08 sauerkraut kernel: d08481c9
Nov  1 15:22:08 sauerkraut kernel: *pde = 00000000
Nov  1 15:22:08 sauerkraut kernel: Oops: 0000
Nov  1 15:22:08 sauerkraut kernel: CPU:    0
Nov  1 15:22:08 sauerkraut kernel: EIP:    0010:[<d08481c9>]    Not tainted
Nov  1 15:22:08 sauerkraut kernel: EFLAGS: 00010002
Nov  1 15:22:08 sauerkraut kernel: eax: 00000000   ebx: cddd0a00   ecx: 
cd548000   edx: cea62cc0
Nov  1 15:22:08 sauerkraut kernel: esi: cf808800   edi: cddd0a00   ebp: 
cf808800   esp: c786be0c
Nov  1 15:22:08 sauerkraut kernel: ds: 0018   es: 0018   ss: 0018
Nov  1 15:22:08 sauerkraut kernel: Process xscanimage (pid: 25893, 
stackpage=c786b000)
Nov  1 15:22:08 sauerkraut kernel: Stack: 00000293 cf59bdd4 cddd0a00 
d08482d1 cddd0a00 00000000 00000000 00000000
Nov  1 15:22:08 sauerkraut kernel:        d0830db0 d083064d cddd0a00 
d0830db0 cddd0a00 cf59bdd4 cddd0ab8 cf59bdd4
Nov  1 15:22:08 sauerkraut kernel:        00000000 d0837daf cddd0a00 
cddd0a00 00000286 cff3a218 cf59bd80 c786bf1c
Nov  1 15:22:08 sauerkraut kernel: Call Trace:    [<d08482d1>] 
[<d0830db0>] [<d083064d>] [<d0830db0>] [<d0837daf>]
Nov  1 15:22:08 sauerkraut kernel:   [<d08372b6>] [<d08372fe>] 
[<d08309e3>] [<d09ba08b>] [<d09bb044>] [<d09b9e1b>]
Nov  1 15:22:08 sauerkraut kernel:   [<c0128fe3>] [<d09b99d3>] 
[<c013a6a2>] [<c012d826>] [<c010854b>]
Nov  1 15:22:08 sauerkraut kernel:
Nov  1 15:22:08 sauerkraut kernel: Code: 0f b6 50 1b 8b 14 95 3c c4 26 
c0 2b 82 a0 00 00 00 69 c0 a3
Nov  1 15:22:33 sauerkraut gnome-name-server[24226]: input condition is: 
0x11, exiting
Nov  1 15:23:01 sauerkraut /USR/SBIN/CRON[25903]: (mail) CMD (  if [ -x 
/usr/sbin/exim -a -f /etc/exim/exim.conf ]; then /usr/sbin/exim -q ; fi)
Nov  1 15:23:01 sauerkraut CRON[25902]: PAM pam_putenv: delete 
non-existent entry; PATH PS1 GDK_USE_XFT QT_XFT
Nov  1 15:24:08 sauerkraut kernel:  <3>(scsi0:0:0) cannot abort running 
or disconnected command
Nov  1 15:24:43 sauerkraut kernel: aha152x0: scsi reset in
Nov  1 15:24:48 sauerkraut kernel: Unable to handle kernel NULL pointer 
dereference at virtual address 0000001b
Nov  1 15:24:48 sauerkraut kernel:  printing eip:
Nov  1 15:24:48 sauerkraut kernel: d08481c9
Nov  1 15:24:48 sauerkraut kernel: *pde = 00000000
Nov  1 15:24:48 sauerkraut kernel: Oops: 0000
Nov  1 15:24:48 sauerkraut kernel: CPU:    0
Nov  1 15:24:48 sauerkraut kernel: EIP:    0010:[<d08481c9>]    Not tainted
Nov  1 15:24:48 sauerkraut kernel: EFLAGS: 00010002
Nov  1 15:24:48 sauerkraut kernel: eax: 00000000   ebx: cddd0a00   ecx: 
cd548000   edx: cc3cfc00
Nov  1 15:24:48 sauerkraut kernel: esi: cf808800   edi: cf837f74   ebp: 
cddd0a00   esp: cf837f04
Nov  1 15:24:48 sauerkraut kernel: ds: 0018   es: 0018   ss: 0018
Nov  1 15:24:48 sauerkraut kernel: Process scsi_eh_0 (pid: 51, 
stackpage=cf837000)
Nov  1 15:24:48 sauerkraut kernel: Stack: 00000292 cf837f60 cf837f74 
d08482d1 cddd0a00 00000000 00000000 00000000
Nov  1 15:24:48 sauerkraut kernel:        d0834d30 d083527f cddd0a00 
d0834d30 cddd0a00 cddd0a00 cff3a200 cddd0a00
Nov  1 15:24:48 sauerkraut kernel:        cf837f60 cf808800 00000000 
00000000 00000000 cf837f6c cf837f6c 00000000
Nov  1 15:24:48 sauerkraut kernel: Call Trace:    [<d08482d1>] 
[<d0834d30>] [<d083527f>] [<d0834d30>] [<d0834e6a>]
Nov  1 15:24:48 sauerkraut kernel:   [<d0835db6>] [<d08362d9>] [<c0106ec8>]
Nov  1 15:24:48 sauerkraut kernel:
Nov  1 15:24:48 sauerkraut kernel: Code: 0f b6 50 1b 8b 14 95 3c c4 26 
c0 2b 82 a0 00 00 00 69 c0 a3
Aiee, killing interrupt handler!

The thing is that the scanner worked fine with an older verion of SANE 
with a even more older version of a snapscan-patch. The problem is that 
I can no longer compile it and I've forgotten where I got this stuff 
from. What I remember is that the Scanner always transmitted too much 
data while scanning which was ignored by the aha152x-driver. Maybe this 
is problem now that a buffer-overflow happens...

/Bernd