Bug 183138
| Summary: | SATA failure after pm-suspend/resume ata1: handling error/timeout | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Andy Burns <fedora> | ||||
| Component: | kernel | Assignee: | Dave Jones <davej> | ||||
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Brian Brock <bbrock> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 5 | CC: | bertil, d.bz-redhat, kweidner, pb, pfrields, wtogami | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| URL: | http://adslpipe.co.uk/pics/sataresumefail.jpg | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2006-11-24 22:48:29 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
Andy Burns
2006-02-26 22:13:12 UTC
Just to confirm this problem has not been fixed by recent kernels, upto and including 2.6.15-1.2032_FC5 I've experienced the same problem on kernel-2.6.15-1.2054_FC5. SATA disk won't resume after resuming. Created attachment 126959 [details] dmesg and lspci output from boot (vanilla 2.6.16 kernel, as additional info only. The bug appears in the FC5 kernel.) See also bug #169201, this may be related. An extra data point - while experimenting, I noticed that my Thinkpad T60 failed to boot when using a kernel with no ACPI support, the SATA drive didn't get detected after a "failed to respond" timeout. Including ACPI made it boot. extract of dmesg from a successful boot (full log attached): libata version 1.20 loaded. ahci 0000:00:1f.2: version 1.2 acpi_bus-0201 [-3] bus_set_power : Device is not power manageable ACPI: PCI Interrupt 0000:00:1f.2[B] -> GSI 16 (level, low) -> IRQ 16 PCI: Setting latency timer of device 0000:00:1f.2 to 64 ahci 0000:00:1f.2: AHCI 0001.0100 32 slots 4 ports 1.5 Gbps 0x1 impl SATA mode ahci 0000:00:1f.2: flags: 64bit ncq pm led clo pio slum part [...] ata1: dev 0 ATA-7, max UDMA/100, 195371568 sectors: LBA48 from lspci: 0000:00:1f.2 0106: Intel Corporation 82801GBM/GHM (ICH7 Family) Serial ATA Storage Controllers cc=AHCI (rev 02) I couldn't save the unsuccessful boot. It obviously didn't have ACPI messages, and it timed out instead of detecting the SATA disk. Is the problem maybe a missing power on ACPI command after resume? Here's a proposed patch by Greg KH: https://bugzilla.novell.com/show_bug.cgi?id=162090 I run into similar problem with a Promise SATA 300 TX4 controller buyed yesterday. Connected a Samsung 300 GB drive and Seagate 300 GB + 160 GB. Can't neither copy huge files via NFS nor local to another disk, got in addition SCSI CRC errors. A new kernel update has been released (Version: 2.6.18-1.2200.fc5) based upon a new upstream kernel release. Please retest against this new kernel, as a large number of patches go into each upstream release, possibly including changes that may address this problem. This bug has been placed in NEEDINFO state. Due to the large volume of inactive bugs in bugzilla, if this bug is still in this state in two weeks time, it will be closed. Should this bug still be relevant after this period, the reporter can reopen the bug at any time. Any other users on the Cc: list of this bug can request that the bug be reopened by adding a comment to the bug. In the last few updates, some users upgrading from FC4->FC5 have reported that installing a kernel update has left their systems unbootable. If you have been affected by this problem please check you only have one version of device-mapper & lvm2 installed. See bug 207474 for further details. If this bug is a problem preventing you from installing the release this version is filed against, please see bug 169613. If this bug has been fixed, but you are now experiencing a different problem, please file a separate bug for the new problem. Thank you. This bug has been mass-closed along with all other bugs that have been in NEEDINFO state for several months. Due to the large volume of inactive bugs in bugzilla, this is the only method we have of cleaning out stale bug reports where the reporter has disappeared. If you can reproduce this bug after installing all the current updates, please reopen this bug. If you are not the reporter, you can add a comment requesting it be reopened, and someone will get to it asap. Thank you. |