http://bugzilla.opensuse.org/show_bug.cgi?id=913105 --- Comment #2 from Mark Scott --- Created attachment 619583 --> http://bugzilla.opensuse.org/attachment.cgi?id=619583&action=edit Hwinfo output Bug 913105 hwinfo -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=913105 --- Comment #5 from Mark Scott --- Created attachment 620319 --> http://bugzilla.opensuse.org/attachment.cgi?id=620319&action=edit DMESG ACPI Output For OS 3.12 K3.16 Hi Takashi and thank you for the reply. Please find attached the ACPI info from Dmesg just for info. I've a spare disk that I'll throw a fresh OS 13.2 to on and use that as a test rig as per your suggestions. In the meantime I've tried Fedora 21 with the same results. Looks like some hardwork ahead for me and a learning experience. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=913105 --- Comment #7 from Mark Scott --- Bad News and Good News ! The bad news is my failure to resume from ram is back now I've connected everything together. The good news is I've found the cause. It's the pair of WD black 2TB drives. If either one of them is in or both (see HWinfo output) then resume from RAM fails. I've taken them out and tried lots of other drives in their place and S3 resume works for everything else but these drives, please note they are NTFS formatted. I've tried both ext 4 and NTFS formatted other drives in their place and they all work perfectly. These drives are definitely the root cause of my issue, now I need to find out why they worked under Kernel 3.11 but not later. Any suggestions as to my next step would be appreciated. The models are: WD2003FZEX-00Z4SA0 and WD2002FAEX-0 NB BIOS is set to legacy boot and not UEFI. The other drives I tried were all either 1gb or less, don't know if 2gb size is important. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=913105 --- Comment #9 from Mark Scott --- Hi Takashi A couple of things to note: 1) I've had a look at all the drives I have tested under Windows using Crystaldiskinfo and curiously the pair of WD 2TB don't show the APM flag while all others do. 2) I noticed both WD 2TB drives have Grub2 bootloaders in their MBRs - an overhang from previous configurations that I forgot to get rid of. I've checked journalctrl and there appears to be no kernel problems regards these drives, if you want the logs I can post. I tried no_console_suspend=1 in kernel boot parameters but makes no difference, I assume I did that correctly ? Thanks -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=913105 --- Comment #11 from Mark Scott --- Hi Takashi Yes it does go BOOM but the graphics does come up with about half a line and then freezes, the entire system locks hard and only a physical power reset will do. I'm of the opinion best candidate causing the issue is to do with the fact that APM is not supported by these two drives and this scenario used to be handled by K3.11 however a commit beyond this kernel has caused a regression, unfortunately I have no other drives that do not support APM to test this theory. All other drives I have tested (about 6 in total including other WD) do support APM and cause no problem when resuming from ram. I did find a thread over at Arch linux into odd APM behaviour regarding WD drives that may be semi-relevent. Just for info: # smartctl -x /dev/sda | grep APM APM feature is: Unavailable https://bbs.archlinux.org/viewtopic.php?id=159233 Thanks -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=913105 --- Comment #13 from Mark Scott --- Hi All, I think in all probability this is a kernel bug regression so I'm of the mind to open a bug report at the Kernel Bug Tracker. Thanks -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=913105 Mark Scott changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Normal |Major --- Comment #15 from Mark Scott --- Uprated the bug to major as anything that causes a hard crash is major. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=913105 --- Comment #16 from Mark Scott --- Hi, I think I may have found someone else with a similar bug: https://bugzilla.opensuse.org/show_bug.cgi?id=913885 The are using WDC WD30EFRX - 3TB WD red which also does not support APM. As it's 3TB they are using UEFI boot as opposed to my legacy boot. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=913105 --- Comment #18 from Mark Scott --- A little bit more info Using the debug method: sh -c "sync && echo 1 > /sys/power/pm_trace && pm-suspend" The magic number returned is: [ 2.941809] Magic number: 0:278:890 [ 2.961872] hash matches ../drivers/base/power/main.c:736 however this does match any pci device so using: cat /sys/power/pm_trace_dev_match The resulting output is: bsg scsi_device scsi_disk sd pci Thanks -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=913105 --- Comment #19 from Mark Scott --- Hi All, I've managed to get my hands on Western Digital WD10EADS-65M280 which is a 1gb Caviar green which does not support APM. Testing the sytem with this drive attached, suspend to ram resume was successful so lack of APM does appear to be a universal factor with WD drives. Stumped for my next move. Thanks -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=913105 --- Comment #21 from Mark Scott --- With reference to comment 18 PM_trace was performed on Opensuse 13.2 using kernel 3.16.7 Thanks -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=913105 --- Comment #23 from Björn Voigt --- Today I had an SATA drive exception after resume from suspend-to-disk. I am relatively sure, that the exception occured after first I/O operation with this disk. (My Seamonkey profile uses the drive as cache and for some mail folders. I mount the EXT4 filesystem with option errors=remount-ro.) Is this exception power-management related? Setup: - Kernel 3.12.36 - Mainboard & BIOS: DH55TC, BIOS TCIBX10H.86A.0048.2011.1206.1342 12/06/2011 - Second drive: ata4.00: ATA-9: WDC WD30EFRX-68EUZN0, 80.00A80, max UDMA/133 (Western Digital Red 3 TB) The exception (from /var/log/messages): 2015-01-27T09:07:15.986794+01:00 mybox sudo: pam_unix(sudo:session): session closed for user root 2015-01-27T09:07:17.087711+01:00 mybox kernel: [59711.988610] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 2015-01-27T09:07:17.087729+01:00 mybox kernel: [59711.988615] ata4.00: irq_stat 0x40000001 2015-01-27T09:07:17.087730+01:00 mybox kernel: [59711.988620] ata4.00: failed command: READ DMA EXT 2015-01-27T09:07:17.087732+01:00 mybox kernel: [59711.988629] ata4.00: cmd 25/00:08:b0:1d:ed/00:00:a0:00:00/e0 tag 7 dma 4096 in 2015-01-27T09:07:17.087733+01:00 mybox kernel: [59711.988629] res 51/40:08:b0:1d:ed/00:00:a0:00:00/e0 Emask 0x9 (media error) 2015-01-27T09:07:17.087735+01:00 mybox kernel: [59711.988633] ata4.00: status: { DRDY ERR } 2015-01-27T09:07:17.087736+01:00 mybox kernel: [59711.988636] ata4.00: error: { UNC } 2015-01-27T09:07:17.090989+01:00 mybox kernel: [59711.993572] ata4.00: configured for UDMA/133 2015-01-27T09:07:17.090993+01:00 mybox kernel: [59711.993579] sd 3:0:0:0: [sdb] Unhandled sense code 2015-01-27T09:07:17.090994+01:00 mybox kernel: [59711.993580] sd 3:0:0:0: [sdb] 2015-01-27T09:07:17.090994+01:00 mybox kernel: [59711.993581] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE 2015-01-27T09:07:17.090995+01:00 mybox kernel: [59711.993582] sd 3:0:0:0: [sdb] 2015-01-27T09:07:17.090995+01:00 mybox kernel: [59711.993584] Sense Key : Medium Error [current] [descriptor] 2015-01-27T09:07:17.090996+01:00 mybox kernel: [59711.993586] Descriptor sense data with sense descriptors (in hex): 2015-01-27T09:07:17.090996+01:00 mybox kernel: [59711.993590] 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 2015-01-27T09:07:17.090997+01:00 mybox kernel: [59711.993595] a0 ed 1d b0 2015-01-27T09:07:17.090997+01:00 mybox kernel: [59711.993597] sd 3:0:0:0: [sdb] 2015-01-27T09:07:17.090998+01:00 mybox kernel: [59711.993598] Add. Sense: Unrecovered read error - auto reallocate failed 2015-01-27T09:07:17.090998+01:00 mybox kernel: [59711.993599] sd 3:0:0:0: [sdb] CDB: 2015-01-27T09:07:17.090999+01:00 mybox kernel: [59711.993600] Read(16): 88 00 00 00 00 00 a0 ed 1d b0 00 00 00 08 00 00 2015-01-27T09:07:17.090999+01:00 mybox kernel: [59711.993606] end_request: I/O error, dev sdb, sector 2699894192 2015-01-27T09:07:17.091000+01:00 mybox kernel: [59711.993619] ata4: EH complete 2015-01-27T09:07:17.111065+01:00 mybox kernel: [59712.011555] EXT4-fs error (device sdb6): ext4_find_entry:1303: inode #50857019: comm seamonkey-bin: reading directory lblock 0 2015-01-27T09:07:17.111081+01:00 mybox kernel: [59712.011560] Aborting journal on device sdb6-8. 2015-01-27T09:07:17.111083+01:00 mybox kernel: [59712.011737] EXT4-fs (sdb6): Remounting filesystem read-only 2015-01-27T09:09:34.637633+01:00 mybox kernel: [59849.546908] usb 2-1.4: usbfs: process 3898 (amarok) did not claim interface 0 before use -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=913105 --- Comment #25 from Mark Scott --- Hi Takashi, I've done some more Kernel version testing on this bug and I can reproduce exactly the same results as this bug report: https://bugs.freedesktop.org/show_bug.cgi?id=86115 So the last known good kernel is 3.12.37 and the first known bad Kernel is 3.13.7 I think it's safe to assume that https://bugzilla.suse.com/show_bug.cgi?id=904483 is a duplicate of this bug. Thanks -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=913105 --- Comment #27 from Takashi Iwai --- (In reply to Mark Scott from comment #26)

Hi Takashi,

I need some help with some investigation work into this bug as the things I need to progress this are currently above my level of understanding and skill set.

please see kernel bug report comments 13 & 14.

You need to build your kernel from scratch, and find out the regression point via git bisect. Sorry, it's not what we can provide as a package. You need to learn how to compile and install a kernel manually. A brief instruction can be found in the bugzilla comment below, for example: https://apibugzilla.novell.com/show_bug.cgi?id=907368#c36 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=913105 --- Comment #28 from Mark Scott --- Hi Takashi, Thanks for the link, I'll give it a go and wish me luck. I'm going to have one grumpy wife and a big coffee bill :) Do you think I should open a separate bug report on this as we have two issues here ? 1) Resume busted by Nouveau 2) Resume busted by unknown WD disk problem. Issue 1 has already been reported upstream so you might as well consider that part of the bug report closed as it's moved upstream. Issue 2 - New bug report ? Many Thanks -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=913105 --- Comment #31 from Takashi Iwai --- Could you try the oS 13.2 test kernel in OBS home:tiwai:bnc934397 repo? This worked for a similar bug report with WD HD. -- You are receiving this mail because: You are on the CC list for the bug.