Red Hat Bugzilla – Bug 442906
libata: sata_nv - disable ADMA by default
Last modified: 2013-07-02 22:35:33 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9b4pre) Gecko/2008030315 Red Hat/3.0b4pre-0.beta3.4.el5 Minefield/3.0b4pre
Description of problem:
The sata_nv driver should disable ADMA by default due to
1. lockup during resume
2. lockup after hotplug
3. timeout of FLUSH after NCQ writes
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Possibly on suspend/resume, hotplug, or IO stress.
Possible system lockup or reset.
System should not lockup or reset.
Author: Jeff Garzik <email@example.com>
Commit from jgarzik/libata-dev.git#upstream
Date: Fri Apr 4 03:34:45 2008 -0400
[libata] sata_nv: disable ADMA by default
Continues to have open issues, and engineering support is extremely difficul
to come by, according to fellow NVIDIA engineers.
Signed-off-by: Jeff Garzik <firstname.lastname@example.org>
*** This bug has been marked as a duplicate of 441707 ***
Reopen, BZ 441707 is for RHEL4
This request was evaluated by Red Hat Product Management for
inclusion, but this component is not scheduled to be updated in
the current Red Hat Enterprise Linux release. If you would like
this request to be reviewed for the next minor release, ask your
support representative to set the next rhel-x.y flag to "?".
Unfortunately the previous automated notification about the
non-inclusion of this request in Red Hat Enterprise Linux 5.3 used
the wrong text template. It should have read: this request has been
reviewed by Product Management and is not planned for inclusion
in the current minor release of Red Hat Enterprise Linux.
If you would like this request to be reviewed for the next minor
release, ask your support representative to set the next rhel-x.y
flag to "?" or raise an exception.
You can download this test kernel from http://people.redhat.com/dzickus/el5
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 therefore 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.
*** Bug 427219 has been marked as a duplicate of this bug. ***