Who whould be responsible for the sd.c driver ?
gat
Uncle George wrote:
>
> on cpu(i386)/card hardware initialization via the scsi bios, I do not
> allow the scsi card to spin up my scsi drives.
> with 2.0.36 ( as from rh5.2 ) the drives are spun up by the
> initialization of the kernel/scsi drivers
>
> with 2.2.12pre12 the scsi drives do spin up. But apparently they get
> hosed. They give device timeouts for the drive. Hitting the reset
> button does nothing. I have to turn off the machine, and load the 2.0.36
> system
>
> If i load up 2.0.26 first ( to spin up the drives ), then I can reboot
> ( witout shutting down the system ) with the 2.2.12 kernel without
> incident. This happens fairly consistently.
>
> gat
> Are u the person loooking into the adaptec stuff ?
This sounds like a problem in the 2.2.12 sd.c driver code, not the aic7xxx
driver code (at least it shouldn't be in the aic7xxx driver code because it
doesn't spin the drives up).
--
Doug Ledford <[EMAIL PROTECTED]>
Alan Cox wrote:
> > downloaded glibc-2.1.2-17.i386.rpm. My SCSI controller is AIC-7890, on a ASUS
> > P2B-DS motherboard. The disc model is a Seagate ST34520W.
>
> The disk seems to have a problem
>
> > scsi0: MEDIUM ERROR on channel 0, id 1, lun 0, CDB: Read (10) 00 00 39 b0 40 00 00
>02 00
> > Info fld=0x39b041, Current sd08:05: sense key Medium Error
> > Additional sense indicates Unrecovered read error
>
> This is a failure from the disk itself. Medium error indicates the media (the
--
To unsubscribe:
mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
