Bug 2672

Summary: Numerous task_no_data_intr error messages during boot
Product: IO/Storage Reporter: Kam Leo (a1tmblwd)
Component: IDEAssignee: Bartlomiej Zolnierkiewicz (bzolnier)
Status: CLOSED PATCH_ALREADY_AVAILABLE    
Severity: normal CC: cesarb, sogerc1, yhlu
Priority: P2    
Hardware: i386   
OS: Linux   
Kernel Version: 2.6.6 Subsystem:
Regression: --- Bisected commit-id:
Attachments: dmesg
revert to previous (2.4) way of handling flush cache command
rollup patch from Rene Herman

Description Kam Leo 2004-05-11 00:23:53 UTC
Distribution: Fedora Core 1.92 Test 3
Hardware Environment: K6-2 450MHz cpu, 256MB RAM, Maxtor 80GB 7200 rpm IDE HD
Software Environment: 
Problem Description: 

The following error messages are displayed numerous times during boot:

hda: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error }
hda: task_no_data_intr: error=0x04 { DriveStatusError }
hda: Write Cache FAILED Flushing!

These messages did not appear with 2.6.6-rc3 or 2.6.6-rc3-mm2 versions.

Steps to reproduce:
1. Startup system. 
2. Error messages appear
Comment 1 Kam Leo 2004-05-11 00:27:00 UTC
Created attachment 2841 [details]
dmesg
Comment 2 Bartlomiej Zolnierkiewicz 2004-05-11 03:53:31 UTC
Created attachment 2842 [details]
revert to previous (2.4) way of handling flush cache command
Comment 3 Bartlomiej Zolnierkiewicz 2004-05-11 03:55:56 UTC
Please try this patch.
Comment 4 Kam Leo 2004-05-11 14:12:12 UTC
I applied the patch as specified.  gcc3.3.3 complained that cf was defined but
not used. The error messages no longer appear.  
Comment 5 dacal 2004-05-12 01:23:43 UTC
Same probem for me
Debian Sid 2.6.6 or 2.6.6-mm1
no problem with 2.6.6-rc3

This error message only appears for my maxtor hard drive (80 go), and not for
the IBM one.
Comment 6 Bartlomiej Zolnierkiewicz 2004-05-12 10:35:31 UTC
I'm working on this.  Recent flush cache fixes uncovered some more bugs in
ide-disk driver and firmware peculiarities of some Maxtor disks.  Proper fixes
should be available soon.  If you want to get rid of these warnings (they are
harmless - they mean that disk aborted unknown command - no threat to your data
etc.) in the meantime use previously posted patch (and ignore gcc warning about
unused variable).
Comment 7 Bartlomiej Zolnierkiewicz 2004-05-12 10:36:59 UTC
*** Bug 2677 has been marked as a duplicate of this bug. ***
Comment 8 Bartlomiej Zolnierkiewicz 2004-05-12 10:37:47 UTC
*** Bug 2678 has been marked as a duplicate of this bug. ***
Comment 9 Bartlomiej Zolnierkiewicz 2004-05-12 10:39:10 UTC
*** Bug 2687 has been marked as a duplicate of this bug. ***
Comment 10 Bartlomiej Zolnierkiewicz 2004-05-12 10:53:43 UTC
Created attachment 2846 [details]
rollup patch from Rene Herman

STANDBY on reboot should also be fixed soon.  It is needed only on
halt/shutdown to properly flush caches of some disks and prevent fs corruption
and there was no clean way to do it just for halt/shutdown.  You can apply 2nd
patch to fix it
(contains 1st patch + 'system_state' patch by Andrew Morton + 'no STANDBY on
reboot' patch by Rene Herman).
Comment 11 Bartlomiej Zolnierkiewicz 2004-05-12 10:56:13 UTC
oh by '1st patch' I really meant '1st fix' because patches are different
(but result is the same)
Comment 12 Karlan 2004-05-13 15:51:36 UTC
This happens to me with both of my maxtor drives, but the odd things is my
CRX-140E Sony CDRW drive(hdc).  At boot it tells me something about an
interpret(sorry for vaugeness), and my system NEVER boots, the message keeps
occurring.  I do not know if this is related, but this and the maxtor problem
only occur with 2.6.6