Sounds like your bus isnt terminated. Not sure about that hard drive, but
if it's an LVD device, then even though there may be a jumper for said
termination, there isn't a single lvd drive in production that has builtin
termination, so you need to go drop $30 on a devent active LVD terminator.
good luck...
Kelsey Hudson khudson@ctica.com
Software Engineer
Compendium Technologies, Inc (619) 725-0771
---------------------------------------------------------------------------
On Mon, 8 May 2000, Mike McLagan wrote:
> Hello,
>
> I'm having a heck of a time with a system here and I'm wondering if anyone
> out there has any good suggestions. I am at my wit's end in trying to resolve
> this.
>
> I have an Amptron PM-9600 motherboard (Socket 7, VIA TX2 chipset, Pent
> 233MMX, 1M Cache) with 128M of RAM. In the system is an Intel EtherExpress
> Pro/100, cheapy Janco (?) PCI VGA card, Adaptec 2940 U2W and a PAS 16. The
> hard disk is a Seagate ST39140W on a 68 pin cable and there's a Toshiba 6401
> 40x CD and an Ecrix VXA-1 tape drive on a 50 pin cable.
>
> The system will not back up, restore, do large file copying or operate
> reliably for more than 2 or 3 days if I don't do those operations. Basically
> any heavy SCSI activity causes the kernel to go into a loop of resetting and
> timing out the SCSI bus. Once it starts that, it's adios because it never
> recovers.
>
> I've used kernels 2.2.5 -> 2.2.15 on this system, all without any help. I
> have systematically changed every piece of SCSI equipment -- used an AHA
> 2940UW, a new 68 pin cable, a new 50 pin cable, a new CD, a new tape as well as
> changing the CPU and the motherboard(s). Each one was changed and put into
> service, only to fail shortly thereafter.
>
> Is anyone else having a similar problem? Is it a card, drive, drive+card,
> card+driver, drive+driver or motherboard problem? I have some PIII systems
> with Adaptec chips and the same type HDD in them without this problem so I'm
> thinking motherboard chipset (I've tried other identical MBs with no success)
> or kernel is losing an interrupt maybe.
>
> Any suggestions would be greatly appreciated.
>
> Michael
>
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.rutgers.edu
> Please read the FAQ at http://www.tux.org/lkml/
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon May 15 2000 - 21:00:12 EST