From: Florian Schuele <schuele@gmx.de>
To: linux-kernel@vger.kernel.org
Subject: 2.6.0 IDE drive_cmd error=0x04 - results in heavy freeze
Date: Sun, 28 Dec 2003 23:22:00 +0100 [thread overview]
Message-ID: <20031228222200.GA2225@spacken.de> (raw)
Hi,
i have a problem with the final release of kernel 2.6.0.
After a few minutes running and having a little traffic
on my harddisk, i get the following errors in my messages
log:
kernel: hdc: drive_cmd: status=0x51 { DriveReady\
SeekComplete Error }
kernel: hdc: drive_cmd: error=0x04 { DriveStatusError }
I get a few of these messages and then my machine freezes.
Nothing works anymore. The only thing i can do is switching off the
machine or pressing the reset switch...
Since i installed my machine with a
2.4.20-gentoo-r6 kernel SMP (i686), the 2.4.20 runs
without any problems!
Now i have the two kernels installed. The 2.4.20 from above and the
2.6.0 (gentoo development-sources).
- This error occurs with both 2 IDE disks in my machine.
- "Use multi-mode by default" is enabled in both kernels.
- A "fsck.ext3 -f" on my root partition (hdc3) had no errors.
- A drive fitness test from IBM (hitachi) didnt report any errors.
- Distribution is gentoo 1.4
Thanks a lot for hints...
Florian Schuele
reply other threads:[~2003-12-28 22:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20031228222200.GA2225@spacken.de \
--to=schuele@gmx.de \
--cc=linux-kernel@vger.kernel.org \
/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.