lkml.org 
[lkml]   [1999]   [Jul]   [2]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectProblems with SCSI raw-device under 2.2.x
Hello,
i have a ICP-Vortex SCSI-Hostadapter (GDT-3000B, EISA)
I try to reserve a Fujitsu MO-Device (M2513) at SCSI-ID 4
as a scsi-raw device.

The 'append-line' at '/etc/lilo.conf'
-------------------------------------
append="gdth=disable:N,rescan:Y,reserve_list:0,0,4,0,hdr_channel:0
-------------------------------------


Kernel 2.0.36/37 works well:

'cat /proc/scsi/scsi' (from 2.0.37):
-------------------------------------
Attached devices:
Host: scsi0 Channel: 00 Id: 00 Lun: 00
Vendor: ICP Model: Host Drive #00 Rev:
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi0 Channel: 00 Id: 01 Lun: 00
Vendor: ICP Model: Host Drive #01 Rev:
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi0 Channel: 01 Id: 04 Lun: 00
Vendor: FUJITSU Model: M2513E Rev: 0060
Type: Optical Device ANSI SCSI revision: 02


I do not change anything at my hardware.
I just boot kernel 2.2.10 with the same lilo-configuration.
'cat /proc/scsi/scsi' (from 2.2.10):
-------------------------------------
Attached devices:
Host: scsi0 Channel: 00 Id: 00 Lun: 00
Vendor: ICP Model: Host Drive #00 Rev:
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi0 Channel: 00 Id: 01 Lun: 00
Vendor: ICP Model: Host Drive #01 Rev:
Type: Direct-Access ANSI SCSI revision: 02
------------------------------------

The reserved MO-device from lilo-configuration is not present.
One aspect is importent, maybe:
The messages in '/proc/scsi/gdth/0' (directly from the controller)
are the same, whether kernel 2.0.36/37 or kernel 2.2.10 is running.
They shows the correct informations:

'cat /proc/scsi/gdth/0' (kernel 2.0.36/37 and kernel 2.2.10):
-------------------------------------------------------------
Driver Parameters:
reserve_mode: 1 reserve_list: 0,0,4,0
max_ids: 127 hdr_channel: 0

Disk Array Controller Information:
Number: 0 Name: GDT3000B
Driver Ver.: 1.14 Firmware Ver.: 1.17.01-N3E00
Serial No.: 0x3E000002 Cache RAM size: 16384 KB

Physical Devices:
Chn/ID/LUN: A/00/0 Name: IBM DORS-32160 WA6A
Capacity [MB]: 2063 To Log. Drive: 0
Grown Defects: 0

Chn/ID/LUN: A/04/0 Name: FUJITSU M2513E 0060
Capacity [MB]: 0 To Log. Drive: --

Chn/ID/LUN: A/02/0 Name: IBM DDRS-34560 S97B
Capacity [MB]: 4357 To Log. Drive: 1
Grown Defects: 0

Logical Drives:
Number: 0 Status: ok
Capacity [MB]: 2063 Type: Disk
To Array Drv.: --

Number: 1 Status: ok
Capacity [MB]: 4357 Type: Disk
To Array Drv.: --

Array Drives:
--

Host Drives:
Number: 0 Arr/Log. Drive: 0
Capacity [MB]: 2062 Start Sector: 0

Number: 1 Arr/Log. Drive: 1
Capacity [MB]: 4353 Start Sector: 0

Controller Events:
-------------------------------------------------------------

I have spoken to the support-team from ICP-Vortex many times.
They do not have any solutions for this problem.
It looks so, that it is not a problem of the gdth-driver.

So my question is, could this behavior belong to the SCSI-code at 2.2.x ?
Note: The Motherboard has EISA/PCI - bus and 2xpentium 200 (smp).

Do someone else have trouble with Kernels 2.2.x and EISA-Controllers,
especially from ICP-Vortex?


Note: This email to the kernel mailinglist is my last idea, to get
some help solving this problem.



Thank you in advance,
Andreas.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

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