Bug 91880 - (IDE HPT366)System hangs with HPT366 and IBM Deskstar with kernel-2.4.20-13.7
Summary: (IDE HPT366)System hangs with HPT366 and IBM Deskstar with kernel-2.4.20-13.7
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kernel
Version: 7.3
Hardware: i686
OS: Linux
high
high
Target Milestone: ---
Assignee: Arjan van de Ven
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-05-29 08:41 UTC by Marek Greško
Modified: 2005-10-31 22:00 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2003-06-21 11:31:35 UTC
Embargoed:

Attachments (Terms of Use)

Description Marek Greško 2003-05-29 08:41:33 UTC 
Description of problem:
System hangs with UDMA failure with HPT366 and IBM Deskstar

Version-Release number of selected component (if applicable):
2.4.20-13.7

How reproducible:
After every boot.

Steps to Reproduce:
1. Install kernel-2.4.20-13.7
2. Boot the new kernel
3. System hangs with UDMA failure during boot.
    
Actual results:
System hangs.

Expected results:
System boots.

Additional info:
Comment 1 Alan Cox 2003-06-08 12:34:55 UTC 
Which kernel were you using before that works ?
Also does booting with ide=nodma work (this will make it slow but mean we can
then do some
other tests)
Comment 2 Marek Greško 2003-06-09 11:25:27 UTC 
We were using kernel 2.4.18-27.7.x and it worked perfectly. 
 
I cannot test ide=nodma now, because it is our produsction machine situated at 
our hosting provider. I will provide this information later.
Comment 3 Alan Cox 2003-06-09 11:56:52 UTC 
Ok if 18.27 fixed it then I know what problem it was and I'll close the bug.
Comment 4 Marek Greško 2003-06-16 16:05:51 UTC 
If nobody else encounters this bug. It is probably not a bug. Only hardware
problem. The disk is out of order forever. The new disk is not IBM Deskstar so I
cannot test it any more.

Sorry for your time.
Comment 5 Alan Cox 2003-06-21 11:31:35 UTC 
Thanks for filing the bug. If someone else finds this bug and has the same
problem - please reopen it
Note You need to log in before you can comment on or make changes to this bug.