From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753891AbaHEW4X (ORCPT ); Tue, 5 Aug 2014 18:56:23 -0400 Received: from v094114.home.net.pl ([79.96.170.134]:56784 "HELO v094114.home.net.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1753551AbaHEW4W convert rfc822-to-8bit (ORCPT ); Tue, 5 Aug 2014 18:56:22 -0400 From: "Rafael J. Wysocki" To: Janek Kozicki Cc: linux-kernel@vger.kernel.org, Zhang Rui , "Rafael J. Wysocki" , Mika Westerberg Subject: Re: 3.16 crashes on resume from Suspend-To-disk Date: Wed, 06 Aug 2014 01:15 +0200 Message-ID: <140743930.1Lg0eFFrXs@vostro.rjw.lan> User-Agent: KMail/4.11.5 (Linux/3.16.0-rc5+; KDE/4.11.5; x86_64; ; ) In-Reply-To: <20140805190709.2b19c10a@absurd> References: <20140805115834.5e5e76f0@absurd> <20140805190709.2b19c10a@absurd> MIME-Version: 1.0 Content-Transfer-Encoding: 8BIT Content-Type: text/plain; charset="utf-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tuesday, August 05, 2014 07:07:09 PM Janek Kozicki wrote: > 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: This is warning is from _request_firmware() and is triggered by the snd-hda-intel driver (audio). Why don't you file a bug at bugzilla.kernel.org against hibernation/suspend and put that information into it? > 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_sas 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] [] ? dump_stack+0x41/0x51 > Aug 4 17:58:28 absurd kernel: [ 660.993334] [] ? warn_slowpath_common+0x86/0xb0 > Aug 4 17:58:28 absurd kernel: [ 660.993337] [] ? _request_firmware+0x9ab/0x9d0 > Aug 4 17:58:28 absurd kernel: [ 660.993339] [] ? request_firmware+0x35/0x60 > Aug 4 17:58:28 absurd kernel: [ 660.993343] [] ? ca0132_init+0x1bf/0x10d0 [snd_hda_codec_ca0132] > Aug 4 17:58:28 absurd kernel: [ 660.993350] [] ? snd_hda_codec_read+0x51/0xa0 [snd_hda_codec] > Aug 4 17:58:28 absurd kernel: [ 660.993354] [] ? hda_set_power_state+0xa7/0x160 [snd_hda_codec] > Aug 4 17:58:28 absurd kernel: [ 660.993359] [] ? update_rmtp+0x60/0x60 > Aug 4 17:58:28 absurd kernel: [ 660.993363] [] ? hda_call_codec_resume+0x1a1/0x1c0 [snd_hda_codec] > Aug 4 17:58:28 absurd kernel: [ 660.993366] [] ? snd_hda_resume+0x76/0xa0 [snd_hda_codec] > Aug 4 17:58:28 absurd kernel: [ 660.993370] [] ? azx_init_chip+0xf0/0x1f0 [snd_hda_controller] > Aug 4 17:58:28 absurd kernel: [ 660.993373] [] ? azx_resume+0xb1/0x180 [snd_hda_intel] > Aug 4 17:58:28 absurd kernel: [ 660.993377] [] ? pci_pm_default_resume+0x30/0x30 > Aug 4 17:58:28 absurd kernel: [ 660.993380] [] ? dpm_run_callback+0x4b/0xc0 > Aug 4 17:58:28 absurd kernel: [ 660.993382] [] ? device_resume+0x93/0x1d0 > Aug 4 17:58:28 absurd kernel: [ 660.993384] [] ? async_resume+0x14/0x40 > Aug 4 17:58:28 absurd kernel: [ 660.993385] [] ? async_run_entry_fn+0x2d/0x120 > Aug 4 17:58:28 absurd kernel: [ 660.993388] [] ? process_one_work+0x16b/0x400 > Aug 4 17:58:28 absurd kernel: [ 660.993390] [] ? worker_thread+0x114/0x510 > Aug 4 17:58:28 absurd kernel: [ 660.993393] [] ? __schedule+0x2c8/0x760 > Aug 4 17:58:28 absurd kernel: [ 660.993395] [] ? rescuer_thread+0x2c0/0x2c0 > Aug 4 17:58:28 absurd kernel: [ 660.993397] [] ? kthread+0xbc/0xe0 > Aug 4 17:58:28 absurd kernel: [ 660.993398] [] ? flush_kthread_worker+0x80/0x80 > Aug 4 17:58:28 absurd kernel: [ 660.993400] [] ? ret_from_fork+0x7c/0xb0 > Aug 4 17:58:28 absurd kernel: [ 660.993401] [] ? 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? It is documented to some extent in Documentation/power/s2ram.txt Documentation/power/basic-pm-debugging.txt Some of the information in there is outdated, but the rest should still work. Rafael