yeah, it was hardware error, we can ship!

yeah, it was hardware error, we can ship!

[Hans Reiser]

I excerpt the evidence of it:

 kernel: hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
 kernel: hda: drive_cmd: error=0x04 { DriveStatusError }
 kernel: ide: failed opcode was: 0xef
 [powersave_proxy][2907]: WARNING: hdparm returned error 5
 kernel: hda: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error
}
 kernel: hda: task_no_data_intr: error=0x04 { DriveStatusError }
 kernel: ide: failed opcode was: 0xef
 [powersave_proxy][2907]: WARNING: hdparm returned error 5
 ifup: No configuration found for sit0
 kernel: hdb: drive_cmd: status=0x51 { DriveReady SeekComplete Error }

RE: yeah, it was hardware error, we can ship!

[David Dabbs]

> 
> I excerpt the evidence of it:
> 

Good for reiser4! Bad for me. Sigh. This is especially bad in that I have
not completed benchmarking the reiser4 key patch. Back to the hardware
store...

Sorry if my dodgy hardware stirred things up.

David

Re: yeah, it was hardware error, we can ship!

[Lamont R. Peterson]

[-- Attachment #1: Type: text/plain, Size: 1948 bytes --]

On Wed, 2004-08-04 at 12:30, Hans Reiser wrote:
> I excerpt the evidence of it:
> 
>  kernel: hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
>  kernel: hda: drive_cmd: error=0x04 { DriveStatusError }
>  kernel: ide: failed opcode was: 0xef
>  [powersave_proxy][2907]: WARNING: hdparm returned error 5
>  kernel: hda: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error
> }
>  kernel: hda: task_no_data_intr: error=0x04 { DriveStatusError }
>  kernel: ide: failed opcode was: 0xef
>  [powersave_proxy][2907]: WARNING: hdparm returned error 5
>  ifup: No configuration found for sit0
>  kernel: hdb: drive_cmd: status=0x51 { DriveReady SeekComplete Error }

David, what distribution were you using when he got these errors?  What
desktop environment was running on X at the time?

I ask because I started to see some similar errors on my notebook a
couple of months ago after I upgraded to FC2 (from FC1/FC2test hybrid). 
I thought that my hard drive was starting to turn on me.

After replacing it with a new drive and installing FC2 from scratch, I
still saw the same errors.  I was also experiencing massive DMA timeout
errors for hda that were causing hard lockups.

The really weird part was that it only happens after about two minutes
logged on using Red Hat's build of KDE.  Using Gnome (or any other
desktop) the problems disappeared entirely.  I know Red Hat cuts up and
rearranges KDE when they build it, but I do not know what they are doing
differently that would account for this error.  I also tried KDE's
packages for FC2; that worked perfectly and this problem did not appear.

BTW: I have ext3 and reiserfs (3.6) partitions on this notebook.  On the
old hard drive, I used plain old partitions.  On the new drive, I use
LVM for everything except /boot and swap.
-- 
Lamont R. Peterson <lamont@gurulabs.com>
Senior Instructor
Guru Labs, L.C. http://www.GuruLabs.com/

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

RE: yeah, it was hardware error, we can ship!

[David Dabbs]

>David, what distribution were you using when he got these errors?  What
>desktop environment was running on X at the time?

SuSE 9.1 kde


>BTW: I have ext3 and reiserfs (3.6) partitions on this notebook.  On the
>old hard drive, I used plain old partitions.  On the new drive, I use
>LVM for everything except /boot and swap.

Thanks for the info, Lamont.

David

RE: yeah, it was hardware error, we can ship!

[Nikita Danilov]

David Dabbs writes:
 > 
 > >David, what distribution were you using when he got these errors?  What
 > >desktop environment was running on X at the time?
 > 
 > SuSE 9.1 kde
 > 

Then you can ignore these messages. They are driver artefact. There
was lengthy thread on this subject on LKML recently.
 
 > 
 > >BTW: I have ext3 and reiserfs (3.6) partitions on this notebook.  On the
 > >old hard drive, I used plain old partitions.  On the new drive, I use
 > >LVM for everything except /boot and swap.
 > 
 > Thanks for the info, Lamont.
 > 
 > David
 > 

Nikita.

 > 
 > 

Re: yeah, it was hardware error, we can ship!

[Hans Reiser]

Nikita Danilov wrote:

>David Dabbs writes:
> > 
> > >David, what distribution were you using when he got these errors?  What
> > >desktop environment was running on X at the time?
> > 
> > SuSE 9.1 kde
> > 
>
>Then you can ignore these messages. They are driver artefact. There
>was lengthy thread on this subject on LKML recently.
> 
> > 
> > >BTW: I have ext3 and reiserfs (3.6) partitions on this notebook.  On the
> > >old hard drive, I used plain old partitions.  On the new drive, I use
> > >LVM for everything except /boot and swap.
> > 
> > Thanks for the info, Lamont.
> > 
> > David
> > 
>
>Nikita.
>
> > 
> > 
>
>
>  
>
Are your words intended to suggest that it is not a hardware bug, and 
thus might be software?

Re: yeah, it was hardware error, we can ship!

[Nikita Danilov]

Hans Reiser writes:
 > Nikita Danilov wrote:
 > 
 > >David Dabbs writes:
 > > > 
 > > > >David, what distribution were you using when he got these errors?  What
 > > > >desktop environment was running on X at the time?
 > > > 
 > > > SuSE 9.1 kde
 > > > 
 > >
 > >Then you can ignore these messages. They are driver artefact. There
 > >was lengthy thread on this subject on LKML recently.
 > > 
 > > > 
 > > > >BTW: I have ext3 and reiserfs (3.6) partitions on this notebook.  On the
 > > > >old hard drive, I used plain old partitions.  On the new drive, I use
 > > > >LVM for everything except /boot and swap.
 > > > 
 > > > Thanks for the info, Lamont.
 > > > 
 > > > David
 > > > 
 > >
 > >Nikita.
 > >
 > > > 
 > > > 
 > >
 > >
 > >  
 > >
 > Are your words intended to suggest that it is not a hardware bug, and 
 > thus might be software?

Yes, these messages are harmless. I am getting them also, on a brand-new
disk, SuSE9.1

Jul  3 10:44:04 tau kernel: hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
Jul  3 10:44:04 tau kernel: hda: drive_cmd: error=0x04 { DriveStatusError }
Jul  3 10:44:04 tau kernel: hda: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error }
Jul  3 10:44:04 tau kernel: hda: task_no_data_intr: error=0x04 { DriveStatusError }  

Search for SeekComplete in the LKML archive.

Nikita.

RE: yeah, it was hardware error, we can ship!

[David Dabbs]

> -----Original Message-----
> From: Nikita Danilov [mailto:nikita@clusterfs.com]
> Sent: Monday, August 02, 2004 6:46 PM
> To: Hans Reiser
> Cc: David Dabbs; 'ReiserFS List'
> Subject: Re: yeah, it was hardware error, we can ship!
> 
> Hans Reiser writes:
>  > Nikita Danilov wrote:
>  > >
>  > Are your words intended to suggest that it is not a hardware bug, and
>  > thus might be software?
> 
> Yes, these messages are harmless. I am getting them also, on a brand-new
> disk, SuSE9.1
> 
> Jul  3 10:44:04 tau kernel: hda: drive_cmd: status=0x51 { DriveReady
> SeekComplete Error }
> Jul  3 10:44:04 tau kernel: hda: drive_cmd: error=0x04 { DriveStatusError
> }
> Jul  3 10:44:04 tau kernel: hda: task_no_data_intr: status=0x51 {
> DriveReady SeekComplete Error }
> Jul  3 10:44:04 tau kernel: hda: task_no_data_intr: error=0x04 {
> DriveStatusError }
> 
> Search for SeekComplete in the LKML archive.
> 
> Nikita.

Well, whether or not the messages are innocuous, they are gone. I have a new
refurbished disk that provides more space and is faster. And I am rerunning
the mongo benchmarks whose failure started this thread.

David