On Fri, 2005-07-08 at 09:46 +0200, Soeren Sonnenburg wrote:
> On Thu, 2005-07-07 at 12:43 +0400, Alexey Dobriyan wrote:
> > On Thursday 07 July 2005 12:04, Soeren Sonnenburg wrote:
> > > with hddtemp regularly polling for the temperature state together with
> > > libsata from kernel 2.6.12 on a promise tx2. The disk is set to go to
> > > sleep mode (hdparm -S 35 /dev/sda). And after a couple of hours the
> > > machine oopsed (the disk was sleeping/not mounted at that time - with
> > > high probability) :
> > >
> > > ata2: command timeout
> > > ata2: translated ATA stat/err 0xb0/00 to SCSI SK/ASC/ASCQ 0xb/47/00
> > > Assertion failed! qc->flags &
> > > ATA_QCFLAG_ACTIVE,drivers/scsi/libata-core.c,ata_qc_complete,line=3052
> > > ata2: translated ATA stat/err 0xb0/00 to SCSI SK/ASC/ASCQ 0xb/47/00
> > > ata2: status=0xb0 { Busy }
> > > Unable to handle kernel NULL pointer dereference at virtual address
> > > 00000000
> >
> > > EIP: 0060:[<c0118eac>] Tainted: P VLI
> >
> > > I am now trying w/o hddtemp, lets see how long it survives...
> >
> > With untainted kernel, please. To be sure it's our problem.
>
> Ok, I've found a way to reproduce it without loading any prop. stuff.
>
> 1. boot with init=/bin/sh
> 2. run hdparm -S 1 /dev/sda
> 3. run hddtemp /dev/sda
> 4. immediate oops
>
> another hang:
>
> 1. boot with init=/bin/sh
> 2. run hdparm -y /dev/sda
>
> Nevertheless, as promised I rand without hddtemp for about a day. I got
> this single error:
>
> ata2: translated ATA stat/err 0x25/00 to SCSI SK/ASC/ASCQ 0x4/00/00
> ata2: status=0x25 { DeviceFault CorrectedError Error }
> SCSI error : <1 0 0 0> return code = 0x8000002
> sda: Current: sense key: Hardware Error
> Additional sense: No additional sense information
> end_request: I/O error, dev sda, sector 240910336
>
> I will reverse apply the patch and proceed w/o hddtemp/hdparm... lets
> see whether it survives this night.
Ok, so I now ran the machine over the weekend w/o the patch so no
hddtemp/hddparm (and no smartd also). None of the problems above
appeared, but instead
ata2: status=0x51 { DriveReady SeekComplete Error }
ata2: error=0x0c { DriveStatusError }
occassionally (i.e. 9 times when transferring ~400 GB from/to the disk).
This is vanilla 2.6.12... Is this error problematic ? What is causing
this ?
Any ideas ?
Thanks,
Soeren.
--
Sometimes, there's a moment as you're waking, when you become aware of
the real world around you, but you're still dreaming.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
