sata_nv regression, reboots system
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
High
|
Colin Ian King | ||
Hardy |
Fix Released
|
High
|
Colin Ian King | ||
Intrepid |
Fix Released
|
High
|
Colin Ian King |
Bug Description
Trying 2.6.24-13-server doesn't help. Since 2.6.23 somewhere, sata_nv has gotten improved exception handling, but there's a serious bug fixed in 2.6.25-pre6. On a server, to guarantee data integrity, I run # hdparm -W 0 /dev/sda ; hdparm -W 0 /dev/sdb. On Gutsy, this gives periodic kernel messages, but on Hardy it fails terribly. XFS filesystem shutdown due to error, and most times system reboots without any messages to serial console.
The fix is in the following commit in git linux-2.6-stable tree:
author Robert Hancock <email address hidden>
Wed, 30 Jan 2008 01:53:19 +0000 (19:53 -0600)
committer Jeff Garzik <email address hidden>
Fri, 1 Feb 2008 17:26:38 +0000 (12:26 -0500)
commit a1fe782414b7122
.....
This patch is based on an original patch from Kuan Luo of NVIDIA,
posted under subject "fixed a bug of adma in rhel4u5 with HDS7250SASUN500G".
His description follows. I've reworked it a bit to avoid some unnecessary
repeated checks but it should be functionally identical.
"The patch is to solve the error message "ata1: CPB flags CMD err,
flags=0x11" when testing HDS7250SASUN500G in rhel4u5.
I tested this hd in 2.6.24-rc7 which needed to remove the mask in
blacklist to run the ncq and the same error also showed up...
.....
Changed in linux: | |
assignee: | ubuntu-kernel-team → colin-king |
Changed in linux: | |
status: | Triaged → In Progress |
Changed in linux: | |
assignee: | nobody → colin-king |
importance: | Undecided → High |
status: | New → In Progress |
assignee: | colin-king → nobody |
milestone: | ubuntu-8.04.1 → none |
status: | In Progress → Fix Released |
Changed in linux: | |
status: | Fix Released → Fix Committed |
I tried 2.6.25-pre6 and it seems to work. I tried the Hardy kernel + the patch, it also works.
I'm attaching the required logs.