lkml.org 
[lkml]   [1997]   [Jan]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectKernel panics in 2.0.x - SCSI/AIC78xx problem
Date
  I've got the same problem that Tuomas Heino mentioned.  I experienced that
in 2.0.0 and 2.0.27. I tried only that two, but I'm sure all between those two
have same problem. Yesterday, I built 2.0.27 and rebooted. When booting proc-
ess reaches to '/sbin/swapon -a', system felt into one of the following two
cases.

Case 1: I got following rapidly scrolling message.

Aiee: Scheduling in interrupt 00122104
Aiee: Scheduling in interrupt 00122104
...

Case 2: System halted after following message. I also hand-copied the message

scsi0: Target 1, channel A, now synchronous at 10.0MHz, offset 15.
Vendor: CONNER Model: CFP1080S Rev: 4649
Type: Direct-Access ANSI SCSI revision: 02
Detected scsi disk sda at scsi0, channel 0, id 1, lun 0
scsi0: Target 2, channel A, now synchronous at 5.0MHz, offset 15.
Vendor: MATSHITA Model: CD-ROM CR-504 Rev: ST23
Type: CD-ROM ANSI SCSI revision: 02
scsi0: Target 3, channel A, now synchronous at 10.0MHz, offset 15.
Vendor: CONNER Model: CFP1080S Rev: 4649
Type: Direct-Access ANSI SCSI revision: 02
Detected scsi disk sdb at scsi0, channel 0, id 3, lun 0
scsi : detected 2 SCSI disks total.
SCSI device sda: hdwr sector= 512 bytes. Sectors= 2110812 [1030 MB] [1.0 GB]
SCSI device sdb: hdwr sector= 512 bytes. Sectors= 2110812 [1030 MB] [1.0 GB]

-- 4 lines about ethernet card --

Partition check:
sda: sda1 sda2 sda3 sda4 < sda5 sda6 >
sdb: sdb1 sdb2 sdb3 sdb4
VFS: Mounted root (ext2 filesystem) readonly. # now the crashing point. :(
scsi0: No active SCB for reconnecting target 1, channel A - Issuing ABORT. SAVED
_TCL(0x10).
Kernel panic: scsi0: Target 1, channel A, did not send an IDENTITY message. SAVE
D_TCL 0x10.

In swapper task - not syncing

-- End of kernel message --

My system has adaptec 'AIC-7850 Rev B.' on-board SCSI host adapter. I suc-
ceeded installing linux on my system with a patched slackware boot image. (the
version is 1.3.98. I found it from newsgroup) There was no such problem.
When I tried to upgrade to 2.0.0 kernel, the problem had begun. I'm using
slackware-3.1 now. I got same problem with 2.0.0 boot image of slack-3.1.

I wonder whether it caused by aic7xxx driver or by 7850 chip.

--
J. H. "Vajra" Yoo
kernel@mercury.isisnet.co.kr


\
 
 \ /
  Last update: 2005-03-22 13:38    [W:0.034 / U:0.624 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site