[5202] in linux-scsi channel archive
Re: NCR810 + HP SJ4C = bad?
daemon@ATHENA.MIT.EDU (Gerard Roudier)
Wed Nov 25 02:29:02 1998
Date: Wed, 25 Nov 1998 00:18:37 +0100 (MET)
From: Gerard Roudier <groudier@club-internet.fr>
To: Jon Lewis <jlewis@inorganic5.fdt.net>
cc: ncr53c810@Colorado.EDU,
Linux SCSI Mailing List <linux-scsi@vger.rutgers.edu>
In-Reply-To: <Pine.LNX.3.95.981124124836.310H-100000@tarkin.fdt.net>
On Tue, 24 Nov 1998, Jon Lewis wrote:
> On Mon, 23 Nov 1998, Jon Lewis wrote:
>
> > I just hooked up my HP ScanJet 4c to an NCR810. No other SCSI devices are
> > in use. Both the controller and scanner are terminated. The NCR driver
> > (stock from 2.0.36) seems pretty upset about something.
> >
> > ncr53c8xx: at PCI bus 0, device 12, function 0
> > ncr53c8xx: 53c810 detected
> > ncr53c810-0: rev=0x01, base=0xe0800000, io_port=0xb800, irq=11
> > ncr53c810-0: ID 7, Fast-10, Parity Checking
> > ncr53c810-0: restart (scsi reset).
> > scsi0 : ncr53c8xx - revision 2.5f.1
> > scsi : 1 host.
> > ncr53c810-0:0: ERROR (a0:0) (8-0-0) (0/3) @ (script 5ec:721a0000).
DSTAT=0xa0 -> Bit 0x20 means PCI BUS fault.
They seem to happen for several different locations in the SCRIPTS.
> > ncr53c810-0: script cmd = 800cbf40
> > ncr53c810-0: regdump: ca 00 00 03 47 00 00 1f 71 08 02 00 80 00 0f 02.
> > ncr53c810-0: have to clear fifos.
> > ncr53c810-0: restart (scsi reset).
> > ncr53c810-0: restart (scsi reset).
> > Vendor: HP Model: C2520A Rev: 3503
> > Type: Processor ANSI SCSI revision: 02
> > ncr53c810-0:2: ERROR (a0:0) (8-0-0) (0/3) @ (script 8:7810ff00).
> > ncr53c810-0: script cmd = 721a0000
> > ncr53c810-0: regdump: da 00 00 03 47 00 02 1f 75 08 02 00 80 00 0f 02.
> > ncr53c810-0: have to clear fifos.
> > ncr53c810-0: restart (scsi reset).
> > ncr53c810-0:0: ERROR (a0:0) (8-0-0) (0/3) @ (script 5ec:721a0000).
> > ncr53c810-0: script cmd = 800cbf40
> > ncr53c810-0: regdump: ca 00 00 03 47 00 00 1f 71 08 02 00 80 00 0f 02.
> > ncr53c810-0: have to clear fifos.
> > ncr53c810-0: restart (scsi reset).
> > ncr53c810-0:0: ERROR (a0:0) (8-0-0) (0/3) @ (script 5ec:721a0000).
> > ncr53c810-0: script cmd = 800cbf40
> > ncr53c810-0: regdump: ca 00 00 03 47 00 00 1f 71 08 02 00 80 00 0f 02.
> > ncr53c810-0: have to clear fifos.
> > ncr53c810-0: restart (scsi reset).
> > ncr53c810-0:0: ERROR (a0:0) (8-0-0) (0/3) @ (script 34:c0000004).
> > ncr53c810-0: script cmd = c0000004
> > ncr53c810-0: regdump: da 00 00 03 47 00 04 1f 31 08 02 00 80 00 0f 02.
> > ncr53c810-0: have to clear fifos.
> > ncr53c810-0: restart (scsi reset).
> > ncr53c810-0:0: ERROR (a0:0) (8-0-0) (0/3) @ (script 5ec:721a0000).
> > ncr53c810-0: script cmd = 800cbf40
> > ncr53c810-0: regdump: ca 00 00 03 47 00 00 1f 71 08 02 00 80 00 0f 02.
> > ncr53c810-0: have to clear fifos.
> > ncr53c810-0: restart (scsi reset).
> > ncr53c810-0:0: ERROR (a0:0) (8-0-0) (0/3) @ (script 40:c0000004).
> > ncr53c810-0: script cmd = 90080000
> > ncr53c810-0: regdump: da 00 00 03 47 00 05 1f 31 08 02 00 80 00 0f 02.
> > ncr53c810-0: have to clear fifos.
> > ncr53c810-0: restart (scsi reset).
> > ncr53c810-0:0: ERROR (a0:0) (8-0-0) (0/3) @ (script 5ec:721a0000).
> > ncr53c810-0: script cmd = 800cbf40
> > ncr53c810-0: regdump: ca 00 00 03 47 00 00 1f 71 08 02 00 80 00 0f 02.
> > ncr53c810-0: have to clear fifos.
> > ncr53c810-0: restart (scsi reset).
> > scsi : detected total.
> >
> > Is there a boot option that needs tweaking to make the NCR and HP play
> > nice? Here's my kernel config options:
[ ... ]
> > The scanner seems to work fine on the same PC when I boot win98...but I
> > prefer not to do that. I've not yet setup software to try scanning under
> > linux...so I don't know if it works here. All those resets worry me
> > though.
Anything that seems to work fine on win98 is suspicious. :-))
Could you try the following:
1 - Compile the driver for NORMAL IO.
2 - If it still fails, try another SCSI device type on this controller.
[ ... ]
> Is anyone using one of these successfuly under linux?
>
> Host: scsi0 Channel: 00 Id: 06 Lun: 00
> Vendor: HP Model: C2520A Rev: 3503
> Type: Processor ANSI SCSI revision: 02
> (btw...I moved it from id2 to id6 last night while messing with settings)
Should not make differences in my opinion.
IMO, the cause of PCI BUS errors might be:
- Chipset crap or bad configured.
- Controller broken.
- Mother-board problem.
- Driver provided with some wrong memory address.
- (Un)intentionnal overclocking.
Regards,
Gerard.
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.rutgers.edu
