Rafael J. Wysocki said: (by the date of Tue, 05 Aug 2014 03:30:58 +0200)
> On Monday, August 04, 2014 09:06:52 AM Markus Gutschke wrote: > > Thanks for checking in. And no, I have not heard from Zhang since my > > last e-mail. I suspect he is still working on finding a solution. But > > you are of course right, reverting the patch in the meantime might be > > a good idea. > > It has too many dependencies. Besides, reverting it now (at the beginning of > a merge window) won't be particularly useful anyway. > > We need to fix it. Hi, sorry for hijacking this thread, but apparently my other plead for help got ignored in this very busy mailing list. I have an up-to-date recently installed debian wheezy. I downloaded https://www.kernel.org/pub/linux/kernel/v3.x/linux-3.16.tar.xz and compiled it using: cp /boot/config-`uname -r` ./.config make menuconfig fakeroot make-kpkg --initrd --append-to-version=-vanilla.1 kernel_image kernel_headers -j38 dpkg -i linux-image-3.16.0-vanilla.1_3.16.0-vanilla.1-10.00.Custom_amd64.deb linux-headers-3.16.0-vanilla.1_3.16.0-vanilla.1-10.00.Custom_amd64.deb where .config was taken from debian /boot/config-3.14-0.bpo.1-amd64 my PC has 64GB of RAM, 32 Xeon E5-2687W cores and motherboard SuperMicro MBD-X9DRI I just did 25 tries of suspend/resume cycle. I tried 4 different methods of hibernation: 1. /usr/sbin/hibernate # 7 successess, 1 failure 2. /usr/sbin/s2disk # 8 successess, 2 failures 3. echo platform > /sys/power/disk # 0 successess, 5 failures echo disk > /sys/power/state 4. echo shutdown > /sys/power/disk # 2 successess, 3 failures echo disk > /sys/power/state The failure was always a reboot after resume had almost succeeded. In cases when there was a success there was a following ---[cut here]--- part: Aug 4 17:58:28 absurd kernel: [ 660.993238] ------------[ cut here ]------------ Aug 4 17:58:28 absurd kernel: [ 660.993247] WARNING: CPU: 10 PID: 11371 at drivers/base/firmware_class.c:1105 _request_firmware+0x9ab/0x9d0() Aug 4 17:58:28 absurd kernel: [ 660.993291] Modules linked in: parport_pc ppdev lp parport bnep rfcomm bluetooth rfkill pci_stub vboxpci(O) vboxnetadp(O) vboxnetflt(O) vboxdrv(O) binfmt_misc nfsd auth_rpcgss oid_registry nfs_acl nfs fscache lockd sunrpc loop hid_logitech_dj raid1 usb_storage snd_hda_codec_hdmi x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel nvidia(PO) kvm joydev hid_generic snd_hda_codec_ca0132 crct10dif_pclmul iTCO_wdt crc32_pclmul iTCO_vendor_support usbhid ghash_clmulni_intel hid mxm_wmi evdev aesni_intel snd_hda_intel aes_x86_64 ablk_helper cryptd glue_helper lrw snd_hda_controller gf128mul snd_hda_codec pcspkr snd_hwdep sb_edac snd_pcm edac_core snd_seq i2c_i801 snd_seq_device snd_timer snd lpc_ich mei_me mfd_core soundcore mei ioatdma ipmi_si ipmi_msghandler tpm_tis tpm processor wmi thermal_sys button ext4 mbcache crc16 jbd2 sr_mod cdrom sg sd_mod crc_t10dif crct10dif_common dm_mod md_mod crc32c_intel isci ahci libsas libahci libata scsi_transport_s as scsi_mod igb usbcore i2c_a Aug 4 17:58:28 absurd kernel: lgo_bit usb_common i2c_core dca ptp pps_core [last unloaded: ehci_hcd] Aug 4 17:58:28 absurd kernel: [ 660.993309] CPU: 10 PID: 11371 Comm: kworker/u66:1 Tainted: P W O 3.16.0-vanilla.1 #1 Aug 4 17:58:28 absurd kernel: [ 660.993310] Hardware name: Supermicro X9DR3-F/X9DR3-F, BIOS 3.0a 07/31/2013 Aug 4 17:58:28 absurd kernel: [ 660.993316] Workqueue: events_unbound async_run_entry_fn Aug 4 17:58:28 absurd kernel: [ 660.993318] 0000000000000000 0000000000000009 ffffffff814fd161 0000000000000000 Aug 4 17:58:28 absurd kernel: [ 660.993319] ffffffff810664f6 ffffffffa03ff09b ffff881056e35ae0 ffff881055168100 Aug 4 17:58:28 absurd kernel: [ 660.993321] ffff880882a2fc90 ffff88105796b000 ffffffff813a7d3b ffff881055182200 Aug 4 17:58:28 absurd kernel: [ 660.993321] Call Trace: Aug 4 17:58:28 absurd kernel: [ 660.993329] [<ffffffff814fd161>] ? dump_stack+0x41/0x51 Aug 4 17:58:28 absurd kernel: [ 660.993334] [<ffffffff810664f6>] ? warn_slowpath_common+0x86/0xb0 Aug 4 17:58:28 absurd kernel: [ 660.993337] [<ffffffff813a7d3b>] ? _request_firmware+0x9ab/0x9d0 Aug 4 17:58:28 absurd kernel: [ 660.993339] [<ffffffff813a7e45>] ? request_firmware+0x35/0x60 Aug 4 17:58:28 absurd kernel: [ 660.993343] [<ffffffffa03fe03f>] ? ca0132_init+0x1bf/0x10d0 [snd_hda_codec_ca0132] Aug 4 17:58:28 absurd kernel: [ 660.993350] [<ffffffffa02cfe21>] ? snd_hda_codec_read+0x51/0xa0 [snd_hda_codec] Aug 4 17:58:28 absurd kernel: [ 660.993354] [<ffffffffa02cff17>] ? hda_set_power_state+0xa7/0x160 [snd_hda_codec] Aug 4 17:58:28 absurd kernel: [ 660.993359] [<ffffffff81089d70>] ? update_rmtp+0x60/0x60 Aug 4 17:58:28 absurd kernel: [ 660.993363] [<ffffffffa02cf951>] ? hda_call_codec_resume+0x1a1/0x1c0 [snd_hda_codec] Aug 4 17:58:28 absurd kernel: [ 660.993366] [<ffffffffa02d1776>] ? snd_hda_resume+0x76/0xa0 [snd_hda_codec] Aug 4 17:58:28 absurd kernel: [ 660.993370] [<ffffffffa03ab070>] ? azx_init_chip+0xf0/0x1f0 [snd_hda_controller] Aug 4 17:58:28 absurd kernel: [ 660.993373] [<ffffffffa0334c91>] ? azx_resume+0xb1/0x180 [snd_hda_intel] Aug 4 17:58:28 absurd kernel: [ 660.993377] [<ffffffff812d9b10>] ? pci_pm_default_resume+0x30/0x30 Aug 4 17:58:28 absurd kernel: [ 660.993380] [<ffffffff813a128b>] ? dpm_run_callback+0x4b/0xc0 Aug 4 17:58:28 absurd kernel: [ 660.993382] [<ffffffff813a1cd3>] ? device_resume+0x93/0x1d0 Aug 4 17:58:28 absurd kernel: [ 660.993384] [<ffffffff813a1e24>] ? async_resume+0x14/0x40 Aug 4 17:58:28 absurd kernel: [ 660.993385] [<ffffffff8108d02d>] ? async_run_entry_fn+0x2d/0x120 Aug 4 17:58:28 absurd kernel: [ 660.993388] [<ffffffff81080adb>] ? process_one_work+0x16b/0x400 Aug 4 17:58:28 absurd kernel: [ 660.993390] [<ffffffff81081184>] ? worker_thread+0x114/0x510 Aug 4 17:58:28 absurd kernel: [ 660.993393] [<ffffffff814ff3f8>] ? __schedule+0x2c8/0x760 Aug 4 17:58:28 absurd kernel: [ 660.993395] [<ffffffff81081070>] ? rescuer_thread+0x2c0/0x2c0 Aug 4 17:58:28 absurd kernel: [ 660.993397] [<ffffffff810876cc>] ? kthread+0xbc/0xe0 Aug 4 17:58:28 absurd kernel: [ 660.993398] [<ffffffff81087610>] ? flush_kthread_worker+0x80/0x80 Aug 4 17:58:28 absurd kernel: [ 660.993400] [<ffffffff81502f3c>] ? ret_from_fork+0x7c/0xb0 Aug 4 17:58:28 absurd kernel: [ 660.993401] [<ffffffff81087610>] ? flush_kthread_worker+0x80/0x80 Aug 4 17:58:28 absurd kernel: [ 660.993402] ---[ end trace db395c2b3c06720c ]--- To start debugging this my first question is: how can I retrieve some useful logs from a failed resume attempt? best regards -- Janek Kozicki http://janek.kozicki.pl/ | -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
