we set udma mode for 40pin in original code. It's dangerous. Now we add code to choose correct dma mode for PATA. Patch ready and tested. sb600_ide_udma_mode.patch is the root cause for this bug. sb600_ide_one_channel.patch is to clean up the code for SB600 IDE controller Version-Release number of selected component (if applicable): kernel-2.6.9-42 How reproducible: Always Use IDE harddisk with 40-pin cable. Install OS onto it or just use it as data disk. Actual Results: 1. data on IDE disk will be lost when connected with 40-pin cable Expected Results: when connected to 40-pin cable, it should not use udma mode Additional info:
Created attachment 147194 [details] SB 600 IDE controller only has one channel
I am unable to duplicate case #1. The disk subsystem reports some errors caused by CRC failure and then changes down to UDMA33. This in turn only occurs if the drive side detect is also wrong. Also does not appear to correct handle suspend/resume which is probably not a concern for 4.x but may be for 5
Created attachment 147204 [details] fix udma mode issue These two patches have been accepted by kernel.org
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release.
*** Bug 234245 has been marked as a duplicate of this bug. ***
Upstream patch: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=b25168dfdc162b4198fa6395cd191a20dddc6d34
Created attachment 158604 [details] RHEL4.6: fix for this issue
*** Bug 228400 has been marked as a duplicate of this bug. ***
committed in stream U6 build 55.24. A test kernel with this patch is available from http://people.redhat.com/~jbaron/rhel4/
A fix for this issue should have been included in the packages contained in the RHEL4.6 Beta released on RHN (also available at partners.redhat.com). Requested action: Please verify that your issue is fixed to ensure that it is included in this update release. After you (Red Hat Partner) have verified that this issue has been addressed, please perform the following: 1) Change the *status* of this bug to VERIFIED. 2) Add *keyword* of PartnerVerified (leaving the existing keywords unmodified) If this issue is not fixed, please add a comment describing the most recent symptoms of the problem you are having and change the status of the bug to FAILS_QA. If you cannot access bugzilla, please reply with a message to Issue Tracker and I will change the status for you. If you need assistance accessing ftp://partners.redhat.com, please contact your Partner Manager.
A fix for this issue should have been included in the packages contained in the RHEL4.6-Snapshot1 on partners.redhat.com. Requested action: Please verify that your issue is fixed to ensure that it is included in this update release. After you (Red Hat Partner) have verified that this issue has been addressed, please perform the following: 1) Change the *status* of this bug to VERIFIED. 2) Add *keyword* of PartnerVerified (leaving the existing keywords unmodified) If this issue is not fixed, please add a comment describing the most recent symptoms of the problem you are having and change the status of the bug to FAILS_QA. If you cannot access bugzilla, please reply with a message about your test results to Issue Tracker. If you need assistance accessing ftp://partners.redhat.com, please contact your Partner Manager.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2007-0791.html