Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#11535 - sata_nv.patch gives dmesg errors for kernel26 2.6.26.5-1

Attached to Project: Arch Linux
Opened by Börje Holmberg (linfan) - Saturday, 20 September 2008, 14:05 GMT
Last edited by Tobias Powalowski (tpowa) - Saturday, 11 October 2008, 05:34 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To Tobias Powalowski (tpowa)
Thomas Bächler (brain0)
Architecture i686
Severity Low
Priority Normal
Reported Version None
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description: uppgrading to latest kernel26 2.6.26.5-1 gives dmesg errors apparently due to sata_nv.patch. For further reference, see Additional info below.
Downgrading to previous kernel26 2.6.26.3-1 fixes this issue.

Additional info: http://bbs.archlinux.org/viewtopic.php?id=55214
* package version(s)
* config and/or log files etc.


Steps to reproduce: pacman -Syu
This task depends upon

Closed by  Tobias Powalowski (tpowa)
Saturday, 11 October 2008, 05:34 GMT
Reason for closing:  Fixed
Comment by Filip Wojciechowski (fwojciec) - Saturday, 20 September 2008, 21:21 GMT
I can confirm this is a problem with the sata_nv patch included with Arch kernel -- removing the patch and rebuilding kernel26 package solves the issue.
Comment by Tobias Powalowski (tpowa) - Sunday, 21 September 2008, 11:59 GMT
the patch fixed a different problem and it is already included in upstream .27 series, seems we need to wait for another fix :/
Comment by Łukasz Fibinger (lucke) - Monday, 29 September 2008, 20:03 GMT
There's a patch posted: http://article.gmane.org/gmane.linux.ide/34750
Comment by Börje Holmberg (linfan) - Friday, 10 October 2008, 16:24 GMT
Is this thing fixed in 2.6.27 in testing as of today?
Comment by Łukasz Fibinger (lucke) - Friday, 10 October 2008, 16:27 GMT
Should be - it has been fixed upstream.
Comment by Pierre Schmitz (Pierre) - Friday, 10 October 2008, 21:02 GMT
The new kernel fixed the problem for me. So I think this can be closed now.

Loading...