Can't boot 2.1.10[56] due to SCSI device detection failure

Dr. Michael Grimm (Michael.Grimm@Schering.DE)
Tue, 16 Jun 1998 11:00:10 +0000


Hi,

I'm unable to boot kernels 2.10[56] due to the following failure during
SCSI device scanning; kernel 2.102+io_apic behaves as expected.

Hardware: TYAN TC II, 2xP200, BusLogic-UW, AHA2940 (plain) as 2nd controller.

BusLogic's initialization is successful (time and kernel infos removed) :

scsi: ***** BusLogic SCSI Driver Version 2.1.13 of 17 April 1998 *****
scsi: Copyright 1995-1998 by Leonard N. Zubkoff <lnz@dandelion.com>
scsi0: Configuring BusLogic Model BT-950 PCI Wide Ultra SCSI Host Adapter
scsi0: Firmware Version: 5.02, I/O Address: 0x6100, IRQ Channel: 17/Level
scsi0: PCI Bus: 0, Device: 19, Address: 0xE0905000, Host Adapter SCSI ID: 7
[snip]

AHA's initialization is successful:

aic7xxx: Warning - detected auto-termination on controller:
aic7xxx: <Adaptec AHA-294X SCSI host adapter> at PCI 20/0
[ comment concerning device termination snipped ]
aic7xxx: Cables present (Int-50 YES, Ext-50 NO)
aic7xxx: Termination Enabled
(scsi1) <Adaptec AHA-294X SCSI host adapter> found at PCI 20/0
(scsi1) Narrow Channel, SCSI ID=7, 16/255 SCBs
(scsi1) BIOS enabled, IO Port 0x6200, IRQ 16
(scsi1) IO Memory at 0xe0906000, MMAP Memory at 0xc8802000
(scsi1) Downloading sequencer code... 406 instructions downloaded
scsi0 : BusLogic BT-950
scsi1 : Adaptec AHA274x/284x/294x (EISA/VLB/PCI-Fast SCSI) 5.0.13/3.2.4
<Adaptec AHA-294X SCSI host adapter>
scsi : 2 hosts.

BusLogic's device scan is successful:

Vendor: IBM Model: DORS-32160W Rev: WA6A
Type: Direct-Access ANSI SCSI revision: 02
Detected scsi disk sda at scsi0, channel 0, id 0, lun 0
Vendor: IBM Model: DCAS-34330W Rev: S65A
Type: Direct-Access ANSI SCSI revision: 02
Detected scsi disk sdb at scsi0, channel 0, id 2, lun 0
Vendor: TOSHIBA Model: CD-ROM XM-5701TA Rev: 0167
Type: CD-ROM ANSI SCSI revision: 02
scsi0: Target 0: Queue Depth 28, Wide Synchronous at 40.0 MB/sec, offset 15
scsi0: Target 2: Queue Depth 28, Wide Synchronous at 40.0 MB/sec, offset 15
scsi0: Target 5: Queue Depth 3, Synchronous at 10.0 MB/sec, offset 8

AHA's device scan fails miserably (and this has been written to paper):

(scsi1:0:-1:-1) Scanning channel for devices.
scsi: aborting command due to timeout: pid 20, scsi1, channel 0, id 1, lun0\
Inquiry 000000ff00
scsi host 1 abort (pid 20) timed out - resetting
scsi bus is being reset for host 1 channel 0
scsi host 1 channel 0 reset (pid 20) timed out - trying harder

The last three lines are repeated forever ... ;-(

2.1.102+io_apic scans at this stage like a charm:

(scsi1:0:1:0) Synchronous at 10.0MHz, offset 15.
Vendor: IBM Model: DORS-32160 Rev: WA0A
Type: Direct-Access ANSI SCSI revision: 02
Detected scsi disk sdc at scsi1, channel 0, id 1, lun 0
(scsi1:0:2:0) Synchronous at 10.0MHz, offset 15.
Vendor: IBM Model: DORS-32160 Rev: S84A
Type: Direct-Access ANSI SCSI revision: 02
Detected scsi disk sdd at scsi1, channel 0, id 2, lun 0
(scsi1:0:6:0) Synchronous at 5.0MHz, offset 8.
Vendor: HP Model: HP35480A Rev: 1109
Type: Sequential-Access ANSI SCSI revision: 02
scsi : detected 4 SCSI disks total.
SCSI device sda: hdwr sector= 512 bytes. Sectors= 4226725 [2063 MB] [2.1 GB]
SCSI device sdb: hdwr sector= 512 bytes. Sectors= 8467200 [4134 MB] [4.1 GB]
SCSI device sdc: hdwr sector= 512 bytes. Sectors= 4226725 [2063 MB] [2.1 GB]
SCSI device sdd: hdwr sector= 512 bytes. Sectors= 4226725 [2063 MB] [2.1 GB]

Any help is highly appreciated,

Michael

-- 
-- ============================================================
  The opinions expressed above are solely those of the author
          and are not necessarily those of Schering.
===============================================================
NAME:  Dr. Michael Grimm         ADDRESS: Schering AG
EMAIL: michael.grimm@schering.de          Research Laboratories
PHONE: +49-30-468-15477                   D-13342 Berlin
FAX:   +49-30-468-16741                   Germany
===============================================================

- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu