From: "Henning P. Schmiedehausen" <hps@intermeta.de>
To: linux-kernel@vger.kernel.org
Subject: Re: [2.4.21-pre7-ac1] IDE Warning when booting
Date: Wed, 16 Apr 2003 11:16:57 +0000 (UTC) [thread overview]
Message-ID: <b7je39$cfp$1@tangens.hometree.net> (raw)
In-Reply-To: <20030416103105.GC7135@miggy.org>
Athanasius <link@gurus.tf> writes:
>--ALfTUftag+2gvp1h
>Content-Type: text/plain; charset=us-ascii
>Content-Disposition: inline
>Content-Transfer-Encoding: quoted-printable
>On Wed, Apr 16, 2003 at 10:16:12AM +0000, Henning P. Schmiedehausen wrote:
>> !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
>> vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
>> hda: task_no_data_intr: status=3D0x51 { DriveReady SeekComplete Error }
>> hda: task_no_data_intr: error=3D0x04 { DriveStatusError }
>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>> !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
> Not the exact, byte-for-byte, same, but, from Configure.help:
Alan did post an explanation for these (which I haven't read before
posting this) that these are harmless. And yes, the task_no_data_intr
vs. set_multmode makes all the difference. :-) Getting these quieted
down would be nice, though.
Regards
Henning
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
hps@intermeta.de +49 9131 50 654 0 http://www.intermeta.de/
Java, perl, Solaris, Linux, xSP Consulting, Web Services
freelance consultant -- Jakarta Turbine Development -- hero for hire
next prev parent reply other threads:[~2003-04-16 11:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-16 10:16 Henning P. Schmiedehausen
2003-04-16 10:31 ` Athanasius
2003-04-16 11:16 ` Henning P. Schmiedehausen [this message]
2003-04-16 15:32 Mudama, Eric
2003-04-16 21:02 ` Henning P. Schmiedehausen
2003-04-16 16:25 Mudama, Eric
2003-04-16 15:48 ` Alan Cox
2003-04-16 16:39 ` Pau Aliagas
2003-04-16 16:45 Mudama, Eric
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='b7je39$cfp$1@tangens.hometree.net' \
--to=hps@intermeta.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®