Bug 750033

Summary: disk accessed via sata port multipliers are inaccessible after resuming from suspend
Product: [Fedora] Fedora Reporter: Jonathan Matthew <notverysmart>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 16CC: bmr, gansalmon, itamar, jonathan, kernel-maint, lis82, madhu.chinakonda
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-02-13 15:34:27 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 Flags
dmesg
none
lspci -nnvv none

Description Jonathan Matthew 2011-10-30 07:11:42 UTC
Description of problem:

Disks attached to a port multiplier (SiI3726) connected to an internal SATA port on this amd e350 board do not come back after resuming from suspend.  The exact symptoms seem to vary, but the system rapidly becomes useless if any important filesystems are accessed via the port multiplier.

dmesg fragment, appears to be before suspend:

[  276.660078] ata1.15: qc timeout (cmd 0xe4)
[  276.660093] ata1.15: failed to read PMP product ID (Emask=0x4)
[  277.375097] ata1.15: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[  280.375102] ata1.15: qc timeout (cmd 0xe4)
[  280.375115] ata1.15: failed to read PMP GSCR[0] (Emask=0x4)
[  280.375120] ata1.15: PMP revalidation failed (errno=-5)
[  280.375125] ata1.15: limiting SATA link speed to 1.5 Gbps
[  283.039063] ata1.15: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[  286.039031] ata1.15: qc timeout (cmd 0xe4)
[  286.039044] ata1.15: failed to read PMP GSCR[0] (Emask=0x4)
[  286.039048] ata1.15: PMP revalidation failed (errno=-5)
[  288.703091] ata1.15: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[  291.703110] ata1.15: qc timeout (cmd 0xe4)
[  291.703122] ata1.15: failed to read PMP GSCR[0] (Emask=0x4)
[  291.703126] ata1.15: PMP revalidation failed (errno=-5)
[  294.367091] ata1.15: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[  297.367098] ata1.15: qc timeout (cmd 0xe4)
[  297.367110] ata1.15: failed to read PMP GSCR[0] (Emask=0x4)
[  297.367114] ata1.15: PMP revalidation failed (errno=-5)
[  297.367118] ata1.15: failed to recover PMP after 5 tries, giving up
[  297.367122] ata1.15: Port Multiplier detaching
[  297.367127] ata1.00: disabled
[  297.367185] ata1.00: disabled
[  297.367224] ata1.00: detaching (SCSI 0:0:0:0)

after resume, sda (accessed via the port multiplier) doesn't appear in /proc/partitions.

Version-Release number of selected component (if applicable):

kernel-3.1.0.1.fc16.i686 (current f16); no idea if this worked on any previous version.

How reproducible:

happened every time out of <10 so far

Steps to Reproduce:
1. suspend
2. resume

Comment 1 Josh Boyer 2012-02-29 00:14:40 UTC
Are you still seeing this on the 3.2.7 kernel update?  If so, please attach dmesg and lspci -nnvv output.

Comment 2 Jonathan Matthew 2012-02-29 10:10:05 UTC
Created attachment 566506 [details]
dmesg

This still occurs with the 3.2.7 kernel update.

Comment 3 Jonathan Matthew 2012-02-29 10:10:33 UTC
Created attachment 566507 [details]
lspci -nnvv

Comment 4 Bryn M. Reeves 2012-03-09 16:22:08 UTC
I see a very similar problem with 2.6.42.9-1 in f15 although my problems are not exclusively related to resumes - I have a Winstars eSATA cradle with two devices. At times I get an identical sequence of failures as reported here but no real clue as to what triggers it yet.

Comment 5 Dave Jones 2012-03-22 17:13:18 UTC
[mass update]
kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository.
Please retest with this update.

Comment 6 Dave Jones 2012-03-22 17:15:32 UTC
[mass update]
kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository.
Please retest with this update.

Comment 7 Dave Jones 2012-03-22 17:24:34 UTC
[mass update]
kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository.
Please retest with this update.

Comment 8 Sergey 2012-08-27 18:41:48 UTC
These same issue on F17 kernel 3.5.2-3.fc17.x86-64

My laptop Acer Aspire 6935G, bios 1.20, SATA mode - AHCI.

if i set SATA mode to "IDE mode" problem disappears.

on screen repeats these errors:

[<time>] ata1: exception Emask 0x10 SAct 0x0 SErr 0x4000000 action 0xe frozen
[<time>] ata1: irq_stat 0x00000040, connection status changed
[<time>] ata1: SError: {DevExch}
[<time>] ata2: exception Emask 0x10 SAct 0x0 SErr 0x4000000 action 0xe frozen
[<time>] ata2: irq_stat 0x00000040, connection status changed
[<time>] ata2: SError: {DevExch}


PS: sorry for my English.

Comment 9 Dave Jones 2012-10-23 15:35:00 UTC
# 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).

Comment 10 Sergey 2012-10-24 05:49:02 UTC
Kernel 3.6.2-4.fc17.x86_64 problem still persist (see Comment #8).

Comment 11 Fedora End Of Life 2013-01-16 14:30:47 UTC
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

Comment 12 Fedora End Of Life 2013-02-13 15:34:31 UTC
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.