[5203] in linux-scsi channel archive

home help back first fref pref prev next nref lref last post

Re: NCR810 + HP SJ4C = bad?

daemon@ATHENA.MIT.EDU (Jon Lewis)
Wed Nov 25 03:05:38 1998

Date: 	Tue, 24 Nov 1998 18:57:19 -0500 (EST)
From: Jon Lewis <jlewis@inorganic5.fdt.net>
To: Gerard Roudier <groudier@club-internet.fr>
cc: ncr53c810@Colorado.EDU,
        Linux SCSI Mailing List <linux-scsi@vger.rutgers.edu>
In-Reply-To: <Pine.LNX.3.95.981124235521.563A-100000@localhost>

On Wed, 25 Nov 1998, Gerard Roudier wrote:

> DSTAT=0xa0 -> Bit 0x20 means PCI BUS fault.
> They seem to happen for several different locations in the SCRIPTS.

Ah...so its not really a SCSI problem at all.  I suppose that's probably
good.

> Anything that seems to work fine on win98 is suspicious. :-))

I guess win98 hides any errors, and as long as it gets through, its happy.

> 1 - Compile the driver for NORMAL IO.

Will do that tonight, and let you know what happens.  I love 4 minute
kernel builds. :)

> 2 - If it still fails, try another SCSI device type on this controller.

I'll try it with nothing at all connected to the card.

> Should not make differences in my opinion.

I moved it because I thought it was odd that the NCR driver was
complaining about timeouts probing SCSI IDs that weren't even in use.  It
didn't make any difference. 

> IMO, the cause of PCI BUS errors might be:
> 
> - Chipset crap or bad configured.

Motherboard is an Asus P2L97 AGP with an Intel PII-333.

> - Controller broken.

Unlikely...unless I just static zapped it.  The 810 was pulled from my
dual P120 where it had run 2 SCSI disks and a CD for 1-2 years without
trouble.  In fact, that was the system and setup where you found/fixed
some SMP problems in the ncr53c8xx driver long ago.  It is a _very_ old
NCR 810.  Is it possible that it's not quite up to the current PCI specs
and the new motherboard doesn't get along with it?

> - Mother-board problem.

I hope not.

> - Driver provided with some wrong memory address. 

How would that happen?

> - (Un)intentionnal overclocking.

I don't think so.  I'm pretty sure its all jumpered properly, and I did
not intend to overclock it.  I was upgrading from a 486-33...so 333 was
plenty fast enough.

----don't waste your cpu, crack rc5...www.distributed.net team enzo---
 Jon Lewis <jlewis@fdt.net>  |  Spammers will be winnuked or 
 Network Administrator       |  nestea'd...whatever it takes
 Florida Digital Turnpike    |  to get the job done.
______http://inorganic5.fdt.net/~jlewis/pgp for PGP public key________


-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.rutgers.edu

home help back first fref pref prev next nref lref last post