Bug#774036: linux-image-3.16.0-4-amd64: Untainted Kernel shows similar issue

[Emil Goode <emilgoode@gmail.com>]

Hello Rainer,

On Sat, Mar 07, 2015 at 06:47:31PM +0100, Rainer Dorsch wrote:
> Hi Emil,
> 
> Am Samstag 07 März 2015, 14:26:17 schrieb Emil Goode:
> > Just to clarify, suspend/resume is working but it takes more than 60 sec for
> > suspend to complete?
> 
> yes, suspend/resume is working. I did three cycles and measured the time for 
> suspend:
> 
> The first suspend took approx. 60 seconds, the second and third approx. 30 
> seconds.

I see, it looks like its an issue with the ATA subsystem that is stalling
the suspend process.

[  181.992086] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[  181.992090] ata3.00: failed command: FLUSH CACHE
[  181.992098] ata3.00: cmd e7/00:00:00:00:00/00:00:00:00:00/a0 tag 16
         res 40/00:c8:30:0e:40/84:00:09:00:00/40 Emask 0x4 (timeout)
[  181.992100] ata3.00: status: { DRDY }
[  181.992106] ata3: hard resetting link
[  181.992108] ata3: nv: skipping hardreset on occupied port
[  182.460049] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[  182.476330] ata3.00: configured for UDMA/133
[  182.476333] ata3.00: retrying FLUSH 0xe7 Emask 0x4
[  182.476963] ata3: EH complete
[  182.477033] ata3.00: Enabling discard_zeroes_data
[  182.477598] sd 2:0:0:0: [sda] Stopping disk
[  182.736087] PM: suspend of devices complete after 61889.003 msecs

Since it is a regression what you could do is use git bisect to try and locate
the commit that introduced the issue. But its time consuming and it doesn't
always work.

Other than that I think you should post a bug in the kernel bugzilla.

Best regards,

Emil