Re: Booting loops (Downloading SCSI SCRIPTS)
*** linux-scsi:
Regarding master parity error. It seems that the moderboard was erring.
I put the same Tekram DC390U in another machine and there it worked with
pci parity checking on (see dmesg last in mail).
*** debian-boot and Adam Di Carlo:
Don't file a bug against the kernel.
It fix is almost already there
I suggest the following patch (and similar for other languages):
$ diff -u f6.txt.~1~ f6.txt
--- f6.txt.~1~ Thu Nov 23 07:37:20 2000
+++ f6.txt Thu Nov 23 07:43:29 2000
@@ -11,7 +11,7 @@
BusLogic SCSI Hosts 0fbuslogic=0biobase07
Certain DELL machines 0faic7xxx=no_probe07
Future Domain TMC-8xx/950 0ftmc8xx=0bmem_base0f,0birq07
-NCR-810 SCSI controller 0fsym53c8xx=safe:y07
+NCR-based SCSI controllers 0fsym53c8xx=safe:y07
Pro Audio Spectrum 0fpas16=0biobase0f,0birq07
PS/2 ESDI (MCA) 0fed=0bcyl0f,0bhead0f,0bsec07
Seagate ST-0x 0fst0x=0bmem_base0f,0birq07
And possible mention in the release-notes that we switched from the
ncr to the sym-driver which checks for parity errors on the pci bus.
Which results in driver loops during boot for some bad controller-
motherboard combinations. Fix as above.
Regards,
/Karl
-----------------------------------------------------------------------
Karl Hammar Aspö Data karl@kalle.csb.ki.se
Lilla Aspö 2340 +46 173 140 57 Networks
S-742 94 Östhammar +46 70 511 97 84 Computers
Sweden Consulting
-----------------------------------------------------------------------
From: Adam Di Carlo <adam@onshore.com>
Subject: Re: Booting loops (Downloading SCSI SCRIPTS)
Date: 22 Nov 2000 19:35:38 -0500
>
> Well, what is the upshot here for the purposes of boot-floppies?
>
> Document the argument to workaround?
>
> File a bug against the kernel to disable the one driver in favor of
> the other as Karl recommended?
>
> --
> .....Adam Di Carlo....adam@onShore.com.....<URL:http://www.onShore.com/>
----------------------------------
From: Karl Hammar <karl@kalle.csb.ki.se>
Subject: Re: Booting loops (Downloading SCSI SCRIPTS)
Date: Wed, 22 Nov 2000 21:52:50 +0100
>
> debian-boot and Frank:
> >From what I recognize what Gérard says, we could boot the Tekram
> DC390U with:
>
> boot: linux sym53c8xx=mpar:n
>
> to disable the pci master parity checking.
>
> I have tested this and it works (tested with boot floppies v2.2.17).
>
> Gérard:
> Thank you for your quick and kind help.
> (the url seems to be ftp://ftp.tux.org/roudier/drivers/portable/experimental/sym-2.0.4-20001112.tar.gz)
> ^^^^^^^
> Regards,
> /Karl
>
> -----------------------------------------------------------------------
> Karl Hammar Aspö Data karl@kalle.csb.ki.se
> Lilla Aspö 2340 +46 173 140 57 Networks
> S-742 94 Östhammar +46 70 511 97 84 Computers
> Sweden Consulting
> -----------------------------------------------------------------------
>
> From: Gérard Roudier <groudier@club-internet.fr>
> Subject: Re: Booting loops (Downloading SCSI SCRIPTS)
> Date: Wed, 22 Nov 2000 20:11:34 +0100 (CET)
>
> >
> > 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.
> >
...
----------------
sym53c8xx: at PCI bus 0, device 11, function 0
sym53c8xx: setting PCI_COMMAND_PARITY...(fix-up)
sym53c8xx: 53c875E detected with Tekram NVRAM
sym53c8xx: at PCI bus 0, device 9, function 1
sym53c8xx: setting PCI_COMMAND_PARITY...(fix-up)
sym53c8xx: 53c1010 detected with Symbios NVRAM
sym53c8xx: at PCI bus 0, device 9, function 0
sym53c8xx: setting PCI_COMMAND_PARITY...(fix-up)
sym53c8xx: 53c1010 detected with Symbios NVRAM
sym53c1010-0: rev 0x1 on pci bus 0 device 9 function 0 irq 11
sym53c1010-0: Symbios format NVRAM, ID 7, Fast-80, Parity Checking
sym53c1010-0: on-chip RAM at 0xefffa000
sym53c1010-0: restart (scsi reset).
sym53c1010-0: handling phase mismatch from SCRIPTS.
sym53c1010-0: Downloading SCSI SCRIPTS.
sym53c1010-1: rev 0x1 on pci bus 0 device 9 function 1 irq 11
sym53c1010-1: Symbios format NVRAM, ID 7, Fast-80, Parity Checking
sym53c1010-1: on-chip RAM at 0xefffc000
sym53c1010-1: restart (scsi reset).
sym53c1010-1: handling phase mismatch from SCRIPTS.
sym53c1010-1: Downloading SCSI SCRIPTS.
sym53c875E-2: rev 0x26 on pci bus 0 device 11 function 0 irq 9
sym53c875E-2: Tekram format NVRAM, ID 7, Fast-20, Parity Checking
scsi0 : sym53c8xx-1.7.1-20000726
scsi1 : sym53c8xx-1.7.1-20000726
scsi2 : sym53c8xx-1.7.1-20000726
scsi : 3 hosts.
sym53c1010-0-<0,*>: FAST-40 WIDE SCSI 80.0 MB/s (25 ns, offset 31)
Vendor: IBM Model: DMVS09D Rev: 0100
Type: Direct-Access ANSI SCSI revision: 03
Detected scsi disk sda at scsi0, channel 0, id 0, lun 0
Vendor: IBM Model: DDYS-T36950M Rev: S80D
Type: Direct-Access ANSI SCSI revision: 03
Detected scsi disk sdb at scsi0, channel 0, id 1, lun 0
sym53c1010-0-<2,*>: FAST-40 WIDE SCSI 80.0 MB/s (25 ns, offset 31)
Vendor: IBM Model: DMVS09V Rev: 0100
Type: Direct-Access ANSI SCSI revision: 03
Detected scsi disk sdc at scsi0, channel 0, id 2, lun 0
Vendor: IBM Model: DDYS-T36950M Rev: S80D
Type: Direct-Access ANSI SCSI revision: 03
Detected scsi disk sdd at scsi0, channel 0, id 4, lun 0
Vendor: TANDBERG Model: MLR3 Rev: 0404
Type: Sequential-Access ANSI SCSI revision: 02
sym53c1010-0-<0,0>: tagged command queue depth set to 32
sym53c1010-0-<1,0>: tagged command queue depth set to 32
sym53c1010-0-<2,0>: tagged command queue depth set to 32
sym53c1010-0-<4,0>: tagged command queue depth set to 32
Vendor: PLEXTOR Model: CD-R PX-W124TS Rev: 1.05
Type: CD-ROM ANSI SCSI revision: 02
Vendor: SEAGATE Model: ST34520N Rev: 1444
Type: Direct-Access ANSI SCSI revision: 02
Detected scsi disk sde at scsi2, channel 0, id 0, lun 0
scsi : detected 5 SCSI disks total.
sym53c1010-0-<0,*>: FAST-40 WIDE SCSI 80.0 MB/s (25 ns, offset 30)
SCSI device sda: hdwr sector= 512 bytes. Sectors= 17916240 [8748 MB] [8.7 GB]
sym53c1010-0-<1,*>: FAST-80 WIDE SCSI 160.0 MB/s (12 ns, offset 62)
SCSI device sdb: hdwr sector= 512 bytes. Sectors= 71687340 [35003 MB] [35.0 GB]
sym53c1010-0-<2,*>: FAST-40 WIDE SCSI 80.0 MB/s (25 ns, offset 30)
SCSI device sdc: hdwr sector= 512 bytes. Sectors= 17916240 [8748 MB] [8.7 GB]
sym53c1010-0-<4,*>: FAST-80 WIDE SCSI 160.0 MB/s (12 ns, offset 62)
SCSI device sdd: hdwr sector= 512 bytes. Sectors= 71687340 [35003 MB] [35.0 GB]
sym53c875E-2-<0,*>: FAST-20 SCSI 20.0 MB/s (50 ns, offset 15)
SCSI device sde: hdwr sector= 512 bytes. Sectors= 8888924 [4340 MB] [4.3 GB]
Partition check:
sda: sda1 sda2 sda3 sda4 < sda5 sda6 sda7 sda8 >
sdb: sdb1 sdb2
sdc: sdc1
sdd: sdd1 sdd2
sde: sde1 sde2 sde3 sde4 < sde5 sde6 sde7 >
Reply to: