Bug 101357 - (IDE PDC202XX) ata failure with Severn
(IDE PDC202XX) ata failure with Severn
Product: Red Hat Linux Beta
Classification: Retired
Component: kernel (Show other bugs)
i386 Linux
high Severity high
: ---
: ---
Assigned To: Dave Jones
Brian Brock
Depends On:
Blocks: CambridgeBlocker
  Show dependency treegraph
Reported: 2003-07-31 00:47 EDT by djh
Modified: 2015-01-04 17:02 EST (History)
4 users (show)

See Also:
Fixed In Version: 2.4.22-1.2086.nptl
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-10-09 21:04:08 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
lspci (978 bytes, text/plain)
2003-07-31 00:51 EDT, djh
no flags Details

  None (edit)
Description djh 2003-07-31 00:47:36 EDT
Description of problem:
An old Athlon system of mine is not liking Severn.  The ata code reports errors 
followed by severe fs corruption.  This occurs with and without acpi.

This particular system has run lots of 2.4 kernels with no major problems, and 
was successfully running RHL9 up until a few weeks ago.  The drive is healthy.

Here's an example of what happens when it fails:
hde: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error }
hde: task_no_data_intr: error=0x04 { DriveStatusError }
EXT3-fs error (...) in start_transaction: Journal has aborted

Version-Release number of selected component:
2.4.21-20.1.2024.2.1.nptl  (athlon rpm)

Hardware info:
A7V mobo (KT133 chipset, onboard VIA ata66 and Promise ata100 controllers)
hdc is an old Sony burner
(see attachments for more details)

How reproducible:
~10 mins of idling seems to reliably reproduce it.  I've also seen it occur 
during bootup, and occasionally during normal use.

I cannot reproduce it with RHL9 errata kernel (2.4.20-19.9) + Severn userland.

Additional info:
I also had a similar problem with the installer kernel, but it's much harder to 
reproduce.  It took a few reboots for anaconda to successfully mount the 
existing ext3 partition.  (IIRC it reported lost irq, disabled DMA, and PIO mode 
didn't work)

Also, I see similar 0x51/0x04 errors with hdc after smartd starts.
Comment 1 djh 2003-07-31 00:51:21 EDT
Created attachment 93286 [details]
Comment 2 Bill Nottingham 2003-07-31 01:21:56 EDT
What happens if you use the i686 kernel instead of the athlon kernel?
Comment 3 djh 2003-07-31 02:28:37 EDT
Same result with the i686 version. (acpi=off)

I'll try some recent vanilla and -ac kernels later.
Comment 4 djh 2003-08-01 01:54:43 EDT
I could not reproduce it with 2.4.21, 2.4.22-pre6-ac1, or with Arjans 2.6 RPMs
(2.6.0-0.test1.1.26 and 2.6.0-0.test2.1.28).
Comment 5 Peter van Egdom 2003-08-01 14:55:45 EDT
What happens if you turn of the loading of smartd ("chkconfig --level 35 smartd
off") and reboot the machine? On one of my machines smartd does a devicescan and
due to this my ide-tape drive does funny things.
Comment 6 djh 2003-08-06 09:49:07 EDT
It stops the errors about hdc.  No change with hde.
Comment 7 Alan Cox 2003-08-08 16:29:29 EDT
Its something in the severn stuff - I've seen multiple reports and even with
ACPI and "all the usual suspects" enabled it only happens with the RH tree. Its
really quite weird and I really don't know what severn is doing here.
Comment 8 djh 2003-08-12 08:57:34 EDT
I've just tried moving the drive from the Promise to the VIA controller - same

BTW here's another report - (the only hardware in common is the harddrive)
Comment 9 djh 2003-09-30 00:32:57 EDT
I tried the Severn2 kernel (2.4.22-1.2061.nptl) with the Severn1 installation
and the same errors occur.

I have just noticed what has changed - when using the Severn kernels the hard
drive spins down after 5-10 mins.  (I'd really like to know why)
Comment 10 djh 2003-10-02 00:21:41 EDT
Bugzilla has lost the last few comments, so here is a summary.

laptop_mode is disabled.  "HDD power down" is disabled in BIOS.

After a fresh install of Fedora 0.94 it still occurs.
(0x51/04 errors, ide and ext3 failures, reset, manually fsck if required)
Comment 11 Dave Jones 2003-10-02 11:19:59 EDT
We're starting to suspect DMA problems with fireball drives, as this is the
third report I've been able to find, which is the only common factor.
(Different chipsets each time).

If you feel motivated to investigate this, can you paste the boot messages
of both a RHL9 and a cambridge kernel so we can see how they differ ?

Additionally, booting with ide=nodma may prevent around the corruption if our
guesses are correct.
Comment 12 Alan Cox 2003-10-02 18:41:30 EDT
You might want to add that quantum drive to the local blacklist for the PDC202xx
- not sure why it should bite just the quantumn though
Comment 13 Dave Jones 2003-10-03 06:38:34 EDT
It'll need adding in multiple places if thats the case, as this has been seen on
at least 3 different controllers now.
Comment 14 Dave Jones 2003-10-03 06:46:17 EDT
Also #91932 looks very similar (same hardware, also seeing corruption).
disabling DMA didn't help in that case, so it's back to the drawing board.
Comment 15 Dave Jones 2003-10-03 10:08:26 EDT
Are you using LVM ?
Comment 16 Dave Jones 2003-10-03 10:52:36 EDT
I'm interested to hear if this fares any better...
Comment 17 djh 2003-10-03 11:57:07 EDT
No LVM, and ide=nodma didn't help much.

(btw I can't reproduce it with the Taroon kernel - 2.4.21-3.EL)
Comment 18 djh 2003-10-03 22:11:31 EDT
2.4.22-1.2086.nptl is looking good so far.
Comment 19 Dave Jones 2003-10-09 11:02:12 EDT
Any update on this ? Is it behaving now ?
Comment 20 djh 2003-10-09 21:04:08 EDT
With the limited amount of testing I've been able to do, 2.4.22-1.2086.nptl
seems to fix the problem.  2086 lasts for over 6 hours - previous Severn kernels
would fail within 20 mins.

I'll do some further tests, but I believe the problem is fixed.
Comment 21 Dave Jones 2003-10-11 08:51:00 EDT
Sounds promising. Looks like the acoustic management patch doesn't play well
with these drives.
Thanks for chasing this.
Comment 22 Dave Jones 2003-10-16 11:17:12 EDT
Can you paste the output of hdparm -I /dev/hd? from that Quantum Fireball please ?
Comment 23 djh 2003-10-16 23:44:52 EDT
ATA device, with non-removable media
        Model Number:       QUANTUM FIREBALLP AS40.0
        Serial Number:      194034230190
        Firmware Revision:  A1Y.1300
        Used: ATA/ATAPI-5 T13 1321D revision 1
        Supported: 5 4 3 2 & some of 6
        Logical         max     current
        cylinders       16383   16383
        heads           16      16
        sectors/track   63      63
        CHS current addressable sectors:   16514064
        LBA    user addressable sectors:   78177792
        device size with M = 1024*1024:       38172 MBytes
        device size with M = 1000*1000:       40027 MBytes (40 GB)
        LBA, IORDY(can be disabled)
        bytes avail on r/w long: 4      Queue depth: 1
        Standby timer values: spec'd by Vendor, no device specific minimum
        R/W multiple sector transfer: Max = 16  Current = 16
        Recommended acoustic management value: 254, current value: 254
        DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 *udma5
             Cycle time: min=120ns recommended=120ns
        PIO: pio0 pio1 pio2 pio3 pio4
             Cycle time: no flow control=120ns  IORDY flow control=120ns
        Enabled Supported:
           *    READ BUFFER cmd
           *    WRITE BUFFER cmd
           *    Host Protected Area feature set
           *    Look-ahead
           *    Write cache
           *    Power Management feature set
                Security Mode feature set
           *    SMART feature set
           *    Automatic Acoustic Management feature set
           *    DOWNLOAD MICROCODE cmd
        Master password revision code = 65534
        not     enabled
        not     locked
        not     frozen
        not     expired: security count
        not     supported: enhanced erase
HW reset results:
        CBLID- above Vih
        Device num = 0 determined by CSEL
Checksum: correct

Note You need to log in before you can comment on or make changes to this bug.