From: John Bradford <john@grabjohn.com>
To: gzp@myhost.mynet (Gabor Z. Papp)
Cc: alan@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: hda: task_no_data_intr
Date: Sat, 30 Nov 2002 13:45:50 +0000 (GMT) [thread overview]
Message-ID: <200211301345.gAUDjoiZ000163@darkstar.example.net> (raw)
In-Reply-To: <34e8.3de88c28.44a4f@gzp1.gzp.hu> from "Gabor Z. Papp" at Nov 30, 2002 10:00:08 AM
> What mean this message at boot time?
>
> hda: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error }
> hda: task_no_data_intr: error=0x04 { DriveStatusError }
I think that they are diagnostic messages that are a result of an old
disk not supporting some new commands that are being send to it. I
thought this was done silently in the 2.4.x series - I see it on some
really old, (100 MB) disks running 2.5.x
I _think_ you can safely ignore it, but I am CCing Alan, because he
will know for certain.
> Tried with 3 different hard disks, and got the same message
> every time.
Are they all of a similar age/capacity?
> Seems like I'm also unable to make ext3 fs on the disks.
What is the exact problem?
John.
next prev parent reply other threads:[~2002-11-30 13:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-30 10:00 hda: task_no_data_intr Gabor Z. Papp
2002-11-30 13:45 ` John Bradford [this message]
2002-11-30 13:42 ` Alan Cox
2002-11-30 15:26 ` Gabor Z. Papp
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=200211301345.gAUDjoiZ000163@darkstar.example.net \
--to=john@grabjohn.com \
--cc=alan@redhat.com \
--cc=gzp@myhost.mynet \
--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