mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Erik Andersen <andersen@codepoet.org>
To: Georg Schwarz <geos@epost.de>
Cc: linux-kernel@vger.kernel.org, andre@linux-ide.org
Subject: Re: 2.4.21/2.4.22-rc1: IDE error message on startup
Date: Fri, 8 Aug 2003 16:42:10 -0600	[thread overview]
Message-ID: <20030808224210.GA26877@codepoet.org> (raw)
In-Reply-To: <1fze7ly.1v3ap5q173m695M@geos.net.eu.org>

On Fri Aug 08, 2003 at 10:05:08PM +0200, Georg Schwarz wrote:
> Dear Linux kernel maintainers,
> 
> the following problem (aka bug?) appeared in 2.4.21 and still exists in
> 2.4.22-rc1 (kernels prior to 2.4.21 work fine):
> 
> SETUP:
> various mostly older PCs (486, Pentium I) and various smaller IDE drives
> (can would be happy to more details if needed)
> 
> PROBLEM:
> With Linux 2.4.21 or 2.4.22-rc1 (not with prior versions using the same
> .config however) on startup I get the following error messages for any
> connected IDE disk (but not ATAPI CR-ROM):
> 
> hda: attached ide-disk driver.
> hda: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error }
> hda: task_no_data_intr: error=0x04 { DriveStatusError }

A change was made to ide-disk.c where it _always_ attempts to do
a READ_NATIVE_MAX call regardless of whether the drive supports
the host protected area feature set in the
init_idedisk_capacity() function.  I submitted a patch to address
this, which is currently being reworked a bit in the 2.6 kernel 
tree and will then be backported again to 2.4.

 -Erik

--
Erik B. Andersen             http://codepoet-consulting.com/
--This message was written using 73% post-consumer electrons--

  reply	other threads:[~2003-08-08 22:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-08 20:05 Georg Schwarz
2003-08-08 22:42 ` Erik Andersen [this message]
2003-08-10 20:27   ` Andre Hedrick

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=20030808224210.GA26877@codepoet.org \
    --to=andersen@codepoet.org \
    --cc=andre@linux-ide.org \
    --cc=geos@epost.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®