[1330] in linux-scsi channel archive
Re: NCR53C8XX (BSD ported) 16e for 2.0.28, Hard error.
daemon@ATHENA.MIT.EDU (Gerard Roudier)
Mon Jan 27 14:52:32 1997
Date: Mon, 27 Jan 1997 20:48:30 +0000 (GMT)
From: Gerard Roudier <groudier@club-internet.fr>
To: "James W. Laferriere" <babydr@nwrain.net>
cc: linux-scsi@vger.rutgers.edu, ncr53c810@colorado.edu
In-Reply-To: <Pine.LNX.3.95q.970126202950.1711A-100000@filesrv1.baby-dragons.com>
James,
I have rewritten the Linux reset entry point of the driver.
I am currently testing error recovery stuff. I will release the 1.17
version as soon as possible.
Your chip is a 810A. Such chips seems to have problems with burst 16
_and_ PCI dma features enabled.
For now you can try the following boot setup command:
- ncr53c8xx=burst:3 (means burst 2^^3=8) or
- ncr53c8xx=burst:255 (means burst from BIOS settings) or
- ncr53c8xx=specf:n (means special features disabled)
On Sun, 26 Jan 1997, James W. Laferriere
wrote:
>
> +scsi: Aborting Command due to timeout : pid 15832 :
> Scsi 0 : Channel 0 : ID 0 : Lun 0 write (6) 05 2f cb f4 00
>
> Found the above on the -locked- console this morning
> I haven't attempted to run that kernel since. It's on
> floppy so that I had my stable kernel still available.
>
> To be very honest I am not sure if there isn't something
> else conflicting (in some manner) with the scsi controller
> or software.
>
> All I could do was -power off-, I tried the three
> finger salute & the reset button - the reset button
> restarted the system although the disk activity light
> stayed -on- IE: no flashing,.....
>
> /dev/sda1 was in very unstable state, on reboot the
> system came back with 'reboot emmediately', so I got
> out my ncr53c8xx/slackware boot & recovery disks.
>
Gerard.
