Bug 629315
| Summary: | libata-acpi errors on Gateway notebook (workaround: libata.noacpi=1) | ||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Sean Sheedy <redhat> | ||||||||||||||||||||
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||||||||||||||||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||||||||
| Severity: | high | Docs Contact: | |||||||||||||||||||||
| Priority: | low | ||||||||||||||||||||||
| Version: | 13 | CC: | anton, dougsland, gansalmon, itamar, jonathan, kernel-maint, kmcmartin, madhu.chinakonda | ||||||||||||||||||||
| Target Milestone: | --- | ||||||||||||||||||||||
| Target Release: | --- | ||||||||||||||||||||||
| Hardware: | x86_64 | ||||||||||||||||||||||
| OS: | Linux | ||||||||||||||||||||||
| Whiteboard: | |||||||||||||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||||||||||
| Clone Of: | Environment: | ||||||||||||||||||||||
| Last Closed: | 2011-06-28 13:36:14 UTC | Type: | --- | ||||||||||||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||||||||||||
| Documentation: | --- | CRM: | |||||||||||||||||||||
| Verified Versions: | Category: | --- | |||||||||||||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||||||||||
| Embargoed: | |||||||||||||||||||||||
| Attachments: |
|
||||||||||||||||||||||
|
Description
Sean Sheedy
2010-09-01 15:29:27 UTC
Created attachment 442437 [details]
/var/log/messages after wake from suspend
Created attachment 442438 [details]
lspci output
Created attachment 442439 [details]
dmesg output from suspend/wakeup
Can you try kernel-2.6.34.6-47? And if that doesn't work, attach the entire dmesg from that kernel from bootup through a suspend/resume cycle, not just the suspend/resume messages. Created attachment 442529 [details]
dmesg output from 2.6.34.6-47
The problem still manifests on kernel 2.6.34.6-47. Attached is the dmesg output from the following sequence:
1. Boot from powered off state
2. Log in
3. Suspend by closing lid
4. Resume by opening lid and pressing key
You can skip the ACPI commands entirely by adding "libata.noacpi=1" to your boot options, but that may not really fix anything. The real problem is that timeouts are happening when the disk is asked to do I/O. Adding "libata.noacpi=1" clears up the problem, including the delay due to disk timeouts. The system now boots in a reasonable time. I'll attach dmesg output from the working version for comparison. Created attachment 442924 [details]
dmesg output from 2.6.34.6-47 with "libata.noacpi=1"
This is the same situation as attachment 44529, but with "libata.noacpi=1" set on boot. This eliminates the SATA errors and the boot delays due to disk timeouts.
The sequence of actions contained here:
1. Boot from powered off state
2. Log in
3. Suspend by closing lid
4. Resume by opening lid and pressing key
Hi Sean, can you please attach the output of "dmidecode", "lspci -vvnn" and "lspci -nn" as well as a full failing log (with the timeouts) on the latest kernel. I've started a thread on linux-kernel about this, so hopefully we can get it resolved. Thanks! Kyle Created attachment 446016 [details]
Output from dmidecode
Created attachment 446017 [details]
Output from "lspci -vvnn"
Created attachment 446018 [details]
Output from "lspci -nn"
Created attachment 446026 [details] /var/log/messages from 2.6.34.6-47 This is the full /var/log/messages output from the failing case on 2.6.34.6-47. This is the same sequence of events described in comment 5: 1. Boot from powered off state 2. Log in 3. Suspend by closing lid 4. Resume by opening lid and pressing key This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '13'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 13's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 13 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |