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 }
Whether I compile with CONFIG_IDEDISK_MULTI_MODE set or not does not
make a difference, by the way.
If there's any more info I can provide (kernel configs maybe?) or things
I could test please do not hesitste to let me know.
I'd appreciate your feedback.
Georg
--
Georg Schwarz http://home.pages.de/~schwarz/
[email protected] +49 177 8811442
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--
Given the early nature of the test, its design was to catch devices which
fail to issue an abort for unsupported command sets. This was to be a
means to flag the device as possible non-compliant. It is okay to remove
or delete all, as clearly early warnings about standard command sets not
being supported was a silly design on my part.
Making all error messages hide by far is superior than exposing a
potential problem with hardware. Maybe exposing the facts of media
forensics would clarify the issues; however, it is not that important.
Regards,
--a
On Fri, 8 Aug 2003, Erik Andersen wrote:
> 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--
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>