From: John Bradford <john@grabjohn.com>
To: inkognito.anonym@uni.de
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.5.50] IDE error messages appearing after upgrade
Date: Fri, 6 Dec 2002 21:09:16 +0000 (GMT) [thread overview]
Message-ID: <200212062109.gB6L9GWe000553@darkstar.example.net> (raw)
In-Reply-To: <10525789281.20021206212219@uni.de> from "Tobias Rittweiler" at Dec 06, 2002 09:22:19 PM
> Upgrading from 2.4.19 to 2.5.50 results in getting IDE error
> log-messages on startup:
>
> Dec 6 21:00:23 brood kernel: hda: task_no_data_intr: status=0x51 {
> DriveReady SeekComplete Error }
> Dec 6 21:00:23 brood kernel: hda: task_no_data_intr: error=0x04 {
> DriveStatusError }
> Dec 6 21:00:23 brood kernel: hda: 4128768 sectors (2114 MB)
> w/256KiB Cache, CHS=1024/64/63
> Dec 6 21:00:23 brood kernel: /dev/ide/host0/bus0/target0/lun0: p1 p2
> Dec 6 21:00:23 brood kernel: hdb: task_no_data_intr: status=0x51 {
> DriveReady SeekComplete Error }
> Dec 6 21:00:23 brood kernel: hdb: task_no_data_intr: error=0x04 {
> DriveStatusError }
Ignore these 'errors', they are really warnings - your drive doesn't
recognise some commands being sent to it.
2.4.20 will also show these messages.
> Dec 6 21:00:24 brood kernel: end_request: I/O error, dev hdc, sector 0
> Dec 6 21:00:24 brood kernel: hdc: ATAPI 40X DVD-ROM drive, 512kB Cache
> Dec 6 21:00:24 brood kernel: Uniform CD-ROM driver Revision: 3.12
> Dec 6 21:00:24 brood kernel: end_request: I/O error, dev hdc, sector 0
> Dec 6 21:00:24 brood kernel: end_request: I/O error, dev hdd, sector 0
> Dec 6 21:00:24 brood kernel: end_request: I/O error, dev hdd, sector 0
Not sure about these, though. I suspect that commands that only
relate to disk devices are being sent to your CD-ROM drives, but
somebody else will probably confirm/deny that.
John.
next prev parent reply other threads:[~2002-12-06 20:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-06 20:22 [2.5.50] IDE error messages appearing after upgrade Tobias Rittweiler
2002-12-06 21:09 ` John Bradford [this message]
2002-12-06 22:50 ` Andrew Morton
2002-12-06 23:17 ` Alan Cox
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=200212062109.gB6L9GWe000553@darkstar.example.net \
--to=john@grabjohn.com \
--cc=inkognito.anonym@uni.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.