Tom,
I had problems with 5.1.21 when I installed a new Ultra160 LVD drive.
The machine got into an infinite loop of SCSI bus resets.
The first time it happened I thought that the new disk is bad, so I
repleaced
it, but when the same thing happened with the replaced drive, I started to
search in the aic7xxx area.
Check http://people.redhat.com/dledford/
I upgraded to 5.1.28 and all my troubles went away.
HTH.
./adoram
Tom Sedge wrote:
>
> On Mon, 3 Apr 2000, Adoram Rogel wrote:
>
> > What version of the adaptec driver ?
>
> The one bundled with kernel 2.2.13 + ac3. I've since upgraded to 2.2.14
> but the problem remains.
>
> The aic7xxx.c source indicates:
> #define AIC7XXX_C_VERSION "5.1.21"
>
> Best Regards,
>
> Tom.
> --
> Cognality Ltd. [EMAIL PROTECTED] Where dreams become reality....
>
> >
> > ./adoram
> >
> > Tom Sedge wrote:
> > >
> > > Hi,
> > >
> > > We've installed a new Onstream ADR50 drive (SCSI Ultra 3 LVD bus). It is
> > > sitting in a machine with the following spec:
> > >
> > > ASUS P2DS motherboard
> > > 2 x Dual PII 400Mhz
> > > 384RAM
> > > Onboard Adaptec 2940U2W SCSI Ultra 3 LVD bus
> > > 1 x Seagate Cheeta 9.1Gb SCSI drive
> > > 3 x Seagate Cheeta 18.2Gb SCSI drives
> > > D-link DFE530TX 10/100 Ethernet PCI
> > > RedHat Linux 6.1 patched to kernel 2.2.13 + ac3 (SMP).
> > > Software raid 5 across the 3 18.2Gb drives (not the boot drive)
> > >
> > > The drive is properly recognised and reported on startup, and assigned to
> > > /dev/st0.
> > >
> > > All is well until we try reading or writing to a tape. The drive starts
> > > to show write/read behaviour and then nothing happens for a minute or so
> > > until a large number of SCSI write errors are reported by the kernel. At
> > > this point the SCSI bus seems to go bananas an the hard drive light goes
> > > fully on. The machine then stops responding and a reset is needed (to
> > > reset the SCSI bus). After coming back up the machine is fine, and no
> > > problems occur unless we try accessing the drive. Nothing is logged in
> > > the system logs and there are no 'oopses'.
> > >
> > > We've checked for SCSI Id conflicts and termination of the bus. Both seem
> > > to be ok. Could this be an SMP problem? The addition of the ADR drive is
> > > the only change to this machine recently.
> > >
> > > If anyone can help, I'd be most grateful.
> > >
> > > Best Regards,
> > >
> > > Tom.
> > > --
> > > Cognality Ltd. [EMAIL PROTECTED] Where dreams become reality....
> > >
> > > -
> > > Linux SMP list: FIRST see FAQ at http://www.irisa.fr/prive/dmentre/smp-howto/
> > > To Unsubscribe: send "unsubscribe linux-smp" to [EMAIL PROTECTED]
> >
> >
--
|----------------------------------------------------|
| Adoram Rogel email: [EMAIL PROTECTED] |
| OpenSource Inc. Tel: (650) 330-0652 |
| 1047, El Camino Real,#204 Fax: (650) 330-0205 |
| Menlo Park, CA 94025 Home: (650) 594-1010 |
|-* emailed using 100% Micro$oft-free linux machine *|
-
Linux SMP list: FIRST see FAQ at http://www.irisa.fr/prive/dmentre/smp-howto/
To Unsubscribe: send "unsubscribe linux-smp" to [EMAIL PROTECTED]
