The error indicates that the device, acting as a master, detected a PCI
parity error, either in data received, or the PCI target having signaled
such an error condition.
Historically, the FreeBSD ncr and the Linux ncr53c8xx drivers didn't care
about the Enable Parity Error Response bit in the PCI command register. By
the way, only a few PCI device drivers are caring about it, even nowadays.
Result is that most systems are running PCI devices with PCI parity error
just ignored.
I have changed that in sym53c8xx, since PCI parity checking is not a
option for this kind of device, but is mandatory. So, the driver is not
the cause of the problem you report but it is the hardware that is not PCI
compliant. Which part of the hardware ? is the question. I donnot know is
my response. :-)
I have implemented some work-around in the FreeBSD sym driver, and this
driver has muted to SYM-2 driver. SYM-2 also supports Linux and is
currently available for testing:
ftp://ftp.tux.org/drivers/portable/experimental/sym-2.0.4-20001112.tar.gz
Btw, the work-around consists in early detecting (in snooptest) the
hardware PCI parity breakage and disabling PCI parity checking by the
master. Nothing actually magic.:)
The change is small enough to be merged with sym53c8xx-1.7.x, but, in my
limited time, I do prefer to work on SYM-2, which is intended to replace
3 drivers by a single one.
Gérard.
On Wed, 22 Nov 2000, Karl Hammar wrote:
> Problem verified.
> The sym53c8xxx driver won't boot with a Tekram DC390U card installed.
> I have tested this with two different DC390U (53c875e) cards, and with
> a DC310 card.
>
> The ncr53c8xxx driver boots ok.
>
> Kernels 2.0.38, 2.2.{0,10,15,17-whith sym-driver 1.7.1} tested.
>
> debian-boot:
> The quick fix is to make another boot diskette, but replace the
> sym-driver with the ncr-driver.
>
> linux-scsi:
> Is this known? From the docs I get the impression that the 875 is
> supported by sym driver.
>
> Regards,
> /Karl
>
> -----------------------------------------------------------------------
> Karl Hammar Aspö Data [EMAIL PROTECTED]
> Lilla Aspö 2340 +46 173 140 57 Networks
> S-742 94 Östhammar +46 70 511 97 84 Computers
> Sweden Consulting
> -----------------------------------------------------------------------
>
>
> From: Frank Heckenbach <[EMAIL PROTECTED]>
> Subject: Booting loops (Downloading SCSI SCRIPTS)
> Date: Tue, 21 Nov 2000 18:13:43 +0100
>
> > I'm trying to install Debian GNU/Linux 2.2 (LinuxLand -- official
> > i386 Binary (20000814)), but booting (from CD or disk) hangs in an
> > endless loop of the following messages:
> >
> > sym53c875-0: restart (scsi reset)
> > sym53c875-0: Downloading SCSI SCRIPTS
> > sym53c875-0:1: ERROR (40:0) (e-ae-0) (0/5)e(script 68:1e000000)
> > sym53c875-0: script cmd=f31c0004
> > sym53c875-0: regdump: da 10 80 05 47 00 01 0f 71 0e 00 ae 80 00 0e 00
> >
> > (Modulo typos -- BTW, is there a better way than pencil and paper to
> > copy these messages?)
> >
> > My controller is a Tekram DC-390U.
> >
> > I've been using SuSE for some years with various (self-built) 2.0,
> > 2.2 and 2.4-test kernels and never seen this problem. These are the
> > syslog messages from my working system (2.4.0-test10):
> >
> > Nov 21 17:36:25 goedel kernel: SCSI subsystem driver Revision: 1.00
> > Nov 21 17:36:25 goedel kernel: ncr53c8xx: at PCI bus 0, device 8, function 0
> > Nov 21 17:36:25 goedel kernel: ncr53c8xx: 53c875 detected with Tekram NVRAM
> > Nov 21 17:36:25 goedel kernel: ncr53c875-0: rev 0x3 on pci bus 0 device 8 function
>0 irq 11
> > Nov 21 17:36:25 goedel kernel: ncr53c875-0: Tekram format NVRAM, ID 7, Fast-20,
>Parity Checking
> > Nov 21 17:36:25 goedel kernel: ncr53c875-0: on-chip RAM at 0xe1000000
> > Nov 21 17:36:25 goedel kernel: ncr53c875-0: restart (scsi reset).
> > Nov 21 17:36:25 goedel kernel: ncr53c875-0: Downloading SCSI SCRIPTS.
> > Nov 21 17:36:25 goedel kernel: scsi0 : ncr53c8xx - version 3.3b
> > Nov 21 17:36:25 goedel kernel: Vendor: SEAGATE Model: ST12400N SUN2.1G Rev:
>8720
> > Nov 21 17:36:25 goedel kernel: Type: Direct-Access ANSI
>SCSI revision: 02
> > Nov 21 17:36:25 goedel kernel: Vendor: SEAGATE Model: ST12400N SUN2.1G Rev:
>8720
> > Nov 21 17:36:25 goedel kernel: Type: Direct-Access ANSI
>SCSI revision: 02
> > Nov 21 17:36:25 goedel kernel: Vendor: SEAGATE Model: ST12400N SUN2.1G Rev:
>8720
> > Nov 21 17:36:25 goedel kernel: Type: Direct-Access ANSI
>SCSI revision: 02
> > Nov 21 17:36:25 goedel kernel: Vendor: SCSI-CD Model: ReWritable-2x2x6 Rev:
>2.00
> > Nov 21 17:36:25 goedel kernel: Type: CD-ROM ANSI
>SCSI revision: 02
> > Nov 21 17:36:25 goedel kernel: ncr53c875-0-<1,0>: tagged command queue depth set
>to 4
> > Nov 21 17:36:25 goedel kernel: ncr53c875-0-<2,0>: tagged command queue depth set
>to 4
> > Nov 21 17:36:25 goedel kernel: ncr53c875-0-<3,0>: tagged command queue depth set
>to 4
> > Nov 21 17:36:25 goedel kernel: Detected scsi disk sda at scsi0, channel 0, id 1,
>lun 0
> > Nov 21 17:36:25 goedel kernel: Detected scsi disk sdb at scsi0, channel 0, id 2,
>lun 0
> > Nov 21 17:36:25 goedel kernel: Detected scsi disk sdc at scsi0, channel 0, id 3,
>lun 0
> > Nov 21 17:36:25 goedel kernel: ncr53c875-0-<1,0>: sync_msgout: 1-3-1-c-10.
> > Nov 21 17:36:25 goedel kernel: ncr53c875-0-<1,0>: sync msgin: 1-3-1-19-f.
> > Nov 21 17:36:25 goedel kernel: ncr53c875-0-<1,0>: sync: per=25 scntl3=0x30 ofs=15
>fak=0 chg=0.
> > Nov 21 17:36:25 goedel kernel: ncr53c875-0-<1,*>: FAST-10 SCSI 10.0 MB/s (100 ns,
>offset 15)
> > Nov 21 17:36:25 goedel kernel: SCSI device sda: 4194685 512-byte hdwr sectors
>(2148 MB)
> > Nov 21 17:36:25 goedel kernel: /dev/scsi/host0/bus0/target1/lun0: p1 p2
> > Nov 21 17:36:25 goedel kernel: ncr53c875-0-<2,0>: sync_msgout: 1-3-1-c-10.
> > Nov 21 17:36:25 goedel kernel: ncr53c875-0-<2,0>: sync msgin: 1-3-1-19-f.
> > Nov 21 17:36:25 goedel kernel: ncr53c875-0-<2,0>: sync: per=25 scntl3=0x30 ofs=15
>fak=0 chg=0.
> > Nov 21 17:36:25 goedel kernel: ncr53c875-0-<2,*>: FAST-10 SCSI 10.0 MB/s (100 ns,
>offset 15)
> > Nov 21 17:36:25 goedel kernel: SCSI device sdb: 4194685 512-byte hdwr sectors
>(2148 MB)
> > Nov 21 17:36:25 goedel kernel: /dev/scsi/host0/bus0/target2/lun0: p1 p2
> > Nov 21 17:36:25 goedel kernel: ncr53c875-0-<3,0>: sync_msgout: 1-3-1-c-10.
> > Nov 21 17:36:25 goedel kernel: ncr53c875-0-<3,0>: sync msgin: 1-3-1-19-f.
> > Nov 21 17:36:25 goedel kernel: ncr53c875-0-<3,0>: sync: per=25 scntl3=0x30 ofs=15
>fak=0 chg=0.
> > Nov 21 17:36:25 goedel kernel: ncr53c875-0-<3,*>: FAST-10 SCSI 10.0 MB/s (100 ns,
>offset 15)
> > Nov 21 17:36:25 goedel kernel: SCSI device sdc: 4194685 512-byte hdwr sectors
>(2148 MB)
> > Nov 21 17:36:25 goedel kernel: /dev/scsi/host0/bus0/target3/lun0: p1 p2 p3
> > Nov 21 17:36:25 goedel kernel: Detected scsi CD-ROM sr0 at scsi0, channel 0, id 6,
>lun 0
> > Nov 21 17:36:25 goedel kernel: ncr53c875-0-<6,0>: sync_msgout: 1-3-1-c-10.
> > Nov 21 17:36:25 goedel kernel: ncr53c875-0-<6,0>: sync msgin: 1-3-1-19-f.
> > Nov 21 17:36:25 goedel kernel: ncr53c875-0-<6,0>: sync: per=25 scntl3=0x30 ofs=15
>fak=0 chg=0.
> > Nov 21 17:36:25 goedel kernel: ncr53c875-0-<6,*>: FAST-10 SCSI 10.0 MB/s (100 ns,
>offset 15)
> > Nov 21 17:36:25 goedel kernel: sr0: scsi3-mmc drive: 2x/6x writer cd/rw xa/form2
>cdda tray
> >
> > Does this mean that the Debian boot kernel mis-detects my controller
> > as a sym53c875?
> >
> > How to fix this? Should I try some kernel parameters? (BTW, I
> > wouldn't mind if it doesn't detect the SCSI controller at all since
> > I'll install on some IDE partitions, anyway.)
> >
> > Or can I use my working kernel to start the Debian installation
> > (how)?
> >
> > Frank
> >
> > --
> > Frank Heckenbach, [EMAIL PROTECTED]
> > http://fjf.gnu.de/
> > PGP and GPG keys: http://fjf.gnu.de/plan
> >
> >
> > --
> > To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
> -
> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
> the body of a message to [EMAIL PROTECTED]
>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
