Reproducable PPA/SCSI OOPS in 2.0.32

Hrafnkell Eiriksson (
Fri, 12 Dec 1997 11:50:04 +0000


I just discovered a reproducable PPA and/or SCSI
OOPS in 2.0.32

I have a aha1520 scsi card in my computer and
I have the driver for it compiled as a module.
I allso have the parallel port zip driver (ppa.o)
compiled as a module. I dont load these modules
during boot, I usually insmod them only when
needed. No device is connected to my aha1520

When doing
mount /dev/scd0 /mnt/cdrom
with no scsi device attached to my computer
(neither to the aha1520 or the zip drive connected
to my parallel port) and no SCSI modules loaded
I get an oops.

When doing
mount /dev/sda1 /mnt/cdrom
(no devices and no modules)
all I get is a complaint that I should specify
the filesystem type.

Here is the oops and the output from ksymoops
[root@kasmir /root]# lsmod
Module: #pages: Used by:
ppp 5 0
hisax 25 0
isdn 21 [hisax] 3
slhc 2 [ppp isdn] 2
smc-ultra 2 1 (autoclean)
8390 2 [smc-ultra] 0 (autoclean)
[root@kasmir /root]# mount /dev/scd0 /mnt/cdrom
PPA: unable to initialise controller at 0x378, error 2
scsi : 0 hosts.
Unable to handle kernel NULL pointer dereference at virtual address c0000000
current->tss.cr3 = 01391000, %cr3 = 01391000
*pde = 00102067
*pte = 00000000
Oops: 0000
CPU: 0
EIP: 0010:[<0018fe9d>]
EFLAGS: 00010246
eax: 00000000 ebx: 019018c4 ecx: 00000000 edx: 00000000
esi: 00000000 edi: 00000016 ebp: 0280eb38 esp: 01394f04
ds: 0018 es: 0018 fs: 002b gs: 002b ss: 0018
Process insmod (pid: 349, process nr: 33, stackpage=01394000)
Stack: 019018c4 01901808 00000016 01546098 00000016 001900c6 0280eb38 00190156
0280eb38 0280eaa2 00000001 0280eb38 00115b20 013d3c0c bffffce8 080557f8
bffffc58 0012029d c2c00000 00001000 000000bc 00000000 01901808 019018c4
Call Trace: [<001900c6>] [<0280eb38>] [<00190156>] [<0280eb38>] [<0280eaa2>] [<0280eb38>] [<00115b20>]
[<0012029d>] [<0280ea74>] [<0280eac4>] [<00111fe1>] [<00112018>] [<0011836b>] [<0010a879>]
Code: 0f b7 11 81 fa 25 01 00 00 7f 38 52 68 a8 ba 1a 00 e8 bd 59
mount: you must specify the filesystem type

>>EIP: 18fe9d <scsi_unregister_host+30d/380>
Trace: 1900c6 <scsi_register_module+36/90>
Trace: 280eb38
Trace: 190156 <scsi_unregister_module+36/50>
Trace: 280eb38
Trace: 280eaa2
Trace: 280eb38
Trace: 115b20 <sys_init_module+400/440>
Trace: 12029d <vmalloc+4d/80>
Trace: 280ea74
Trace: 280eac4
Trace: 111fe1 <timer_bh+c1/360>
Trace: 112018 <timer_bh+f8/360>
Trace: 11836b <do_bottom_half+3b/70>
Trace: 10a879 <system_call+55/7c>

Code: 18fe9d <scsi_unregister_host+30d/380> movzwl (%ecx),%edx
Code: 18fea0 <scsi_unregister_host+310/380> cmpl $0x125,%edx
Code: 18fea6 <scsi_unregister_host+316/380> jg 18fee0 <scsi_unregister_host+350/380>
Code: 18fea8 <scsi_unregister_host+318/380> pushl %edx
Code: 18fea9 <scsi_unregister_host+319/380> pushl $0x1abaa8
Code: 18feae <scsi_unregister_host+31e/380> call 900059d3 <_EIP+900059d3>
Code: 18feb3 <scsi_unregister_host+323/380> nop
Code: 18feb4 <scsi_unregister_host+324/380> nop

Hrafnkell -

PS. Are ther any updates to the ISDN drivers planned for 2.0.33?
It seems that it is quite unstable. I frequently
get oopses from it when using multilink PPP.