[1395] in linux-scsi channel archive
Re: ncr53c8xx problem with a CLARiiON disk array.
daemon@ATHENA.MIT.EDU (Gerard Roudier)
Thu Feb 6 15:07:32 1997
Date: Thu, 6 Feb 1997 20:51:31 +0000 (GMT)
From: Gerard Roudier <groudier@club-internet.fr>
To: Dario_Ballabio@milano.europe.dg.com
cc: linux-scsi@vger.rutgers.edu
In-Reply-To: <199702061118.MAA25406@milano.europe.dg.com>
The Linux scsi driver is probably configured with multi-luns support.
It detected 4 luns on the CLARiiON.
I donnot have info about such hardware, but in my opinion, lun 0
should be enough to access all the disks as a single one.
Other luns should probably allow to access each disk of the array
as a separate one. (Speculation only)
If the above is true, you should try, for the moment, to disable
multi-luns support.
No need to recompile the kernel, the following boot setup command
under LILO prompt should work:
max_scsi_luns=1
The hang of the insmod process is in my opinion not due to the ncr
driver.
Gerard.
On Thu, 6 Feb 1997 Dario_Ballabio@milano.europe.dg.com wrote:
> I'm trying to install linux on an AViiON 5900 (quad PPro 200Mhz, 1Gb memory)
> connected to a CLARiiON disk array by an NCR SYMBIOS diff card (rev. 3.07).
> Actually the ncr53c8xx driver hangs just after scanning the devices on
> the disk array. The behaviour is the same booting both stock 2.0.28
> and stock 2.1.25 (no SMP in both cases), with the ncr driver in the system
> or loaded as a module. Here the syslog output for 2.0.28 when the ncr
> driver is loaded as a module. After this the insmod process just hangs,
> but the system is still fully operational (except for the devices detected
> on the ncr scsi bus, which are not operational).
> Any suggestion from the ncr guys?
>
> PS: the same system works fine with both DG/UX and Netware 4.11.
>
> ncr53c8xx : at PCI bus 0, device 11, function 0
> ncr_attach: unit=0 chip=825 base=feaffc00, io_port=fc00, irq=11
> ncr53c825-0: using memory mapped IO at virtual address 0x484bc00
> ncr53c825-0: initial value of SCNTL3 = 03, final = 13
> ncr53c825-0: requesting shared irq 11 (dev_id=0x383c068)
> ncr53c825-0: restart (scsi reset).
> scsi2 : ncr53c8xx (rel 1.12d)
> scsi : 3 hosts.
> ncr53c825-0-<target 0, lun 0>: using tagged command queueing, up to 4 cmds/lun
> Vendor: DGC Model: DISK Rev: 0816
> Type: Direct-Access ANSI SCSI revision: 02
> Detected scsi disk sda at scsi2, channel 0, id 0, lun 0
> ncr53c825-0-<target 0, lun 0>: using tagged command queueing, up to 4 cmds/lun
> ncr53c825-0-<target 0, lun 1>: using tagged command queueing, up to 4 cmds/lun
> Vendor: DGC Model: DISK Rev: 0816
> Type: Direct-Access ANSI SCSI revision: 02
> Detected scsi disk sdb at scsi2, channel 0, id 0, lun 1
> ncr53c825-0-<target 0, lun 0>: using tagged command queueing, up to 4 cmds/lun
> ncr53c825-0-<target 0, lun 1>: using tagged command queueing, up to 4 cmds/lun
> ncr53c825-0-<target 0, lun 2>: using tagged command queueing, up to 4 cmds/lun
> Vendor: DGC Model: DISK Rev: 0816
> Type: Direct-Access ANSI SCSI revision: 02
> Detected scsi disk sdc at scsi2, channel 0, id 0, lun 2
> ncr53c825-0-<target 0, lun 0>: using tagged command queueing, up to 4 cmds/lun
> ncr53c825-0-<target 0, lun 1>: using tagged command queueing, up to 4 cmds/lun
> ncr53c825-0-<target 0, lun 2>: using tagged command queueing, up to 4 cmds/lun
> ncr53c825-0-<target 0, lun 3>: using tagged command queueing, up to 4 cmds/lun
> Vendor: DGC Model: DISK Rev: 0816
> Type: Direct-Access ANSI SCSI revision: 02
> Detected scsi disk sdd at scsi2, channel 0, id 0, lun 3
