From: "Lamont R. Peterson" <lamont@gurulabs.com>
To: ReiserFS List <reiserfs-list@namesys.com>
Subject: Re: yeah, it was hardware error, we can ship!
Date: Wed, 04 Aug 2004 12:56:20 -0600 [thread overview]
Message-ID: <1091645780.2391.15.camel@wraith.lrp.advansoft.us> (raw)
In-Reply-To: <41112B30.2050509@namesys.com>
[-- 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 --]
next prev parent reply other threads:[~2004-08-04 18:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-04 18:30 yeah, it was hardware error, we can ship! Hans Reiser
2004-08-04 18:40 ` David Dabbs
2004-08-04 18:56 ` Lamont R. Peterson [this message]
2004-08-04 19:13 ` David Dabbs
2004-08-04 20:48 ` Nikita Danilov
2004-08-04 21:36 ` Hans Reiser
2004-08-02 23:46 ` Nikita Danilov
2004-08-05 15:29 ` David Dabbs
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1091645780.2391.15.camel@wraith.lrp.advansoft.us \
--to=lamont@gurulabs.com \
--cc=reiserfs-list@namesys.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.