| Summary: | slow resume (~10s) with SB850 and samsung hard drives | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Oliver Henshaw <oliver.henshaw> | ||||
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||
| Status: | CLOSED WORKSFORME | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 17 | CC: | gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda | ||||
| Target Milestone: | --- | Keywords: | Reopened | ||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2013-08-01 17:18:54 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Attachments: |
|
||||||
|
Description
Oliver Henshaw
2011-09-15 17:13:19 UTC
And here's an extract from dmesg from boot time, to show what devices are on what sata ports. $ dmesg | egrep "scsi|ahci|ata|sd" [ 0.237721] libata version 3.00 loaded. [ 0.688537] ahci 0000:00:11.0: version 3.0 [ 0.688559] ahci 0000:00:11.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19 [ 0.688615] ahci 0000:00:11.0: irq 42 for MSI/MSI-X [ 0.688702] ahci 0000:00:11.0: AHCI 0001.0200 32 slots 6 ports 6 Gbps 0x3f impl SATA mode [ 0.688705] ahci 0000:00:11.0: flags: 64bit ncq sntf ilck pm led clo pmp pio slum part [ 0.689367] scsi0 : ahci [ 0.689512] scsi1 : ahci [ 0.689614] scsi2 : ahci [ 0.689668] scsi3 : ahci [ 0.689715] scsi4 : ahci [ 0.689768] scsi5 : ahci [ 0.689863] ata1: SATA max UDMA/133 abar m1024@0xfe02f000 port 0xfe02f100 irq 42 [ 0.689866] ata2: SATA max UDMA/133 abar m1024@0xfe02f000 port 0xfe02f180 irq 42 [ 0.689868] ata3: SATA max UDMA/133 abar m1024@0xfe02f000 port 0xfe02f200 irq 42 [ 0.689870] ata4: SATA max UDMA/133 abar m1024@0xfe02f000 port 0xfe02f280 irq 42 [ 0.689873] ata5: SATA max UDMA/133 abar m1024@0xfe02f000 port 0xfe02f300 irq 42 [ 0.689876] ata6: SATA max UDMA/133 abar m1024@0xfe02f000 port 0xfe02f380 irq 42 [ 0.690001] ahci 0000:05:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 [ 0.690124] ahci 0000:05:00.0: AHCI 0001.0000 32 slots 2 ports 3 Gbps 0x3 impl SATA mode [ 0.690127] ahci 0000:05:00.0: flags: 64bit ncq pm led clo pmp pio slum part [ 0.690132] ahci 0000:05:00.0: setting latency timer to 64 [ 0.690437] scsi6 : ahci [ 0.690528] scsi7 : ahci [ 0.690560] ata7: SATA max UDMA/133 abar m8192@0xfd9fe000 port 0xfd9fe100 irq 17 [ 0.690563] ata8: SATA max UDMA/133 abar m8192@0xfd9fe000 port 0xfd9fe180 irq 17 [ 0.995085] ata6: SATA link down (SStatus 0 SControl 300) [ 0.995133] ata4: SATA link down (SStatus 0 SControl 300) [ 0.996108] ata8: SATA link down (SStatus 0 SControl 300) [ 0.996148] ata7: SATA link down (SStatus 0 SControl 300) [ 0.996186] ata2: SATA link down (SStatus 0 SControl 300) [ 1.149088] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 1.150080] ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 1.151082] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 1.151737] ata5.00: ATAPI: Optiarc DVD RW AD-7261S, 1.01, max UDMA/100 [ 1.153749] ata5.00: configured for UDMA/100 [ 1.155017] ata1.00: ATA-8: SAMSUNG HD153WI, 1AN10003, max UDMA/133 [ 1.155024] ata1.00: 2930277168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA [ 1.156799] ata3.00: ATA-8: SAMSUNG HD103SJ, 1AJ10001, max UDMA/133 [ 1.156802] ata3.00: 1953525168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA [ 1.160986] ata1.00: configured for UDMA/133 [ 1.161194] scsi 0:0:0:0: Direct-Access ATA SAMSUNG HD153WI 1AN1 PQ: 0 ANSI: 5 [ 1.161344] sd 0:0:0:0: Attached scsi generic sg0 type 0 [ 1.161435] sd 0:0:0:0: [sda] 2930277168 512-byte logical blocks: (1.50 TB/1.36 TiB) [ 1.161524] sd 0:0:0:0: [sda] Write Protect is off [ 1.161526] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [ 1.161556] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 1.162555] ata3.00: configured for UDMA/133 [ 1.162741] scsi 2:0:0:0: Direct-Access ATA SAMSUNG HD103SJ 1AJ1 PQ: 0 ANSI: 5 [ 1.162877] sd 2:0:0:0: Attached scsi generic sg1 type 0 [ 1.162901] sd 2:0:0:0: [sdb] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB) [ 1.162936] sd 2:0:0:0: [sdb] Write Protect is off [ 1.162938] sd 2:0:0:0: [sdb] Mode Sense: 00 3a 00 00 [ 1.162951] sd 2:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 1.164242] scsi 4:0:0:0: CD-ROM Optiarc DVD RW AD-7261S 1.01 PQ: 0 ANSI: 5 [ 1.166444] sr0: scsi3-mmc drive: 48x/48x writer dvd-ram cd/rw xa/form2 cdda tray [ 1.166553] sr 4:0:0:0: Attached scsi CD-ROM sr0 [ 1.166619] sr 4:0:0:0: Attached scsi generic sg2 type 5 [ 1.169460] sdb: sdb1 sdb2 [ 1.169682] sd 2:0:0:0: [sdb] Attached SCSI disk [ 1.194575] sda: sda1 [ 1.195020] sd 0:0:0:0: [sda] Attached SCSI disk [ 2.193723] pata_jmicron 0000:05:00.1: enabling device (0000 -> 0001) [ 2.193733] pata_jmicron 0000:05:00.1: PCI INT B -> GSI 17 (level, low) -> IRQ 17 [ 2.193761] pata_jmicron 0000:05:00.1: setting latency timer to 64 [ 2.201486] scsi8 : pata_jmicron [ 2.201588] scsi9 : pata_jmicron [ 2.201618] ata9: PATA max UDMA/100 cmd 0xaf00 ctl 0xae00 bmdma 0xab00 irq 17 [ 2.201620] ata10: PATA max UDMA/100 cmd 0xad00 ctl 0xac00 bmdma 0xab08 irq 17 [ 2.535713] dracut: Scanning devices sda1 sdb2 for LVM volume groups Both the slow resume and the "softreset failed (device not ready)" message persists in F16, kernel-3.1.0-7.fc16.x86_64. [mass update] kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository. Please retest with this update. [mass update] kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository. Please retest with this update. [mass update] kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository. Please retest with this update. Created attachment 573606 [details] messages loggied to dmesg over suspend/resume Problem persists in 3.3.0-4.fc16.x86_64. The thread https://lkml.org/lkml/2012/1/17/279 suggests that there's some work in this area. While resume times haven't improved, there is some subtle difference in the logs - in the original report (and in all old /var/log/messages* going back a month) the "starting disk" messages came in immediate succession near the beginning of the resume: Sep 15 12:49:20 alpine kernel: [ 8202.874180] sd 0:0:0:0: [sda] Starting disk Sep 15 12:49:20 alpine kernel: [ 8202.874264] sd 2:0:0:0: [sdb] Starting disk but in kernel 3.3 they are separated by a few seconds and come at the end of the resume: [14378.508649] sd 2:0:0:0: [sdb] Starting disk [14380.894054] ata1: softreset failed (device not ready) [14381.864087] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [14381.875957] ata1.00: configured for UDMA/133 [14381.876034] sd 0:0:0:0: [sda] Starting disk Not sure if that means anything, but I've attached an updated extract from dmesg over suspend/resume. Are you still seeing this with the 3.4 or 3.5 kernel updates? Still seeing it with kernel-3.4.9-2.fc16.x86_64. # Mass update to all open bugs. Kernel 3.6.2-1.fc16 has just been pushed to updates. This update is a significant rebase from the previous version. Please retest with this kernel, and let us know if your problem has been fixed. In the event that you have upgraded to a newer release and the bug you reported is still present, please change the version field to the newest release you have encountered the issue with. Before doing so, please ensure you are testing the latest kernel update in that release and attach any new and relevant information you may have gathered. If you are not the original bug reporter and you still experience this bug, please file a new report, as it is possible that you may be seeing a different problem. (Please don't clone this bug, a fresh bug referencing this bug in the comment is sufficient). Unchanged with 3.6.2-1.fc16.x86_64 This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. 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 '16'. 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 16'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 16 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, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. 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 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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. Still see this with kernel-3.8.13-100.fc17.x86_64 This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. 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 '17'. 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 17'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 17 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, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. 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. Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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. Still happens on F20, but doesn't slow resume anymore. Since it did still slow resume on F19, this was probably improved by http://kernelnewbies.org/Linux_3.15#head-3abfee1e7c09473e1d9617d8765ce0925396baa4 |