Hi I recently updated from a T540p to a T460, and I've been noticing that the laptop doesn't always come back from a suspend. This is on a kernel which is 4.8.0 plus the ext4 development branch (since merged in Linus's tree): Oct 18 11:36:07 callcc kernel: [78989.876606] general protection fault: 0000 [#1] SMP Oct 18 11:36:07 callcc kernel: [78989.876647] Modules linked in: ccm snd_seq_dummy bnep ipt_MASQUERADE nf_nat_masquerade_ipv4 xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype iptable_filter xt_conntrack nf_nat nf_conntrack br_netfilter bridge stp llc overlay binfmt_misc snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic nls_iso8859_1 nls_cp437 vfat fat iwlmvm mac80211 x86_pkg_temp_thermal intel_powerclamp kvm_intel kvm irqbypass pcspkr serio_raw iwlwifi snd_hda_intel snd_hda_codec snd_hda_core i2c_i801 cfg80211 btusb btrtl snd_usb_audio btbcm snd_usbmidi_lib uvcvideo btintel snd_hwdep hid_multitouch bluetooth snd_rawmidi videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core thinkpad_acpi nvram i915 drm_kms_helper tpm_crb drm intel_gtt fb_sys_fops syscopyarea sysfillrect sysimgblt tpm_tis tpm_tis_core tpm parport_pc ppdev lp parport ip_tables x_tables autofs4 algif_skcipher af_alg uas usb_storage hid_generic usbhid hid rtsx_pci_sdmmc crc32_pclmul ghash_clmulni_intel rtsx_pci e1000e ptp mfd_core pps_core xhci_pci xhci_hcd Oct 18 11:36:07 callcc kernel: [78989.876668] CPU: 0 PID: 2481 Comm: Xorg Not tainted 4.8.0-00042-g5a2dfbe #1 Oct 18 11:36:07 callcc kernel: [78989.876669] Hardware name: LENOVO 20FNCTO1WW/20FNCTO1WW, BIOS R06ET40W (1.14 ) 08/03/2016 Oct 18 11:36:07 callcc kernel: [78989.876670] task: ffffa47970108000 task.stack: ffffa47970114000 Oct 18 11:36:07 callcc kernel: [78989.876677] RIP: 0010:[<ffffffffbc0c9bdd>] [<ffffffffbc0c9bdd>] __lock_acquire+0xee/0x1007 Oct 18 11:36:07 callcc kernel: [78989.876679] RSP: 0018:ffffa479701177c0 EFLAGS: 00010086 Oct 18 11:36:07 callcc kernel: [78989.876680] RAX: 8000000000040028 RBX: ffffa47971255328 RCX: 0000000000000000 Oct 18 11:36:07 callcc kernel: [78989.876682] RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffffea001a641db8 Oct 18 11:36:07 callcc kernel: [78989.876683] RBP: ffffa47970117870 R08: 0000000000000001 R09: 0000000000000000 Oct 18 11:36:07 callcc kernel: [78989.876684] R10: ffffa47970117888 R11: 0000000000000804 R12: 0000000000000001 Oct 18 11:36:07 callcc kernel: [78989.876686] R13: 0000000000000000 R14: ffffa47970108000 R15: ffffea001a641db8 Oct 18 11:36:07 callcc kernel: [78989.876688] FS: 00007f76107c7a40(0000) GS:ffffa47980e00000(0000) knlGS:0000000000000000 Oct 18 11:36:07 callcc kernel: [78989.876689] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Oct 18 11:36:07 callcc kernel: [78989.876691] CR2: 00001d089c882308 CR3: 00000007fc3ee000 CR4: 00000000003406f0 Oct 18 11:36:07 callcc kernel: [78989.876692] Stack: Oct 18 11:36:07 callcc kernel: [78989.876697] 00000000bd818820 0953bd7e00000000 ffffffffc0386dac 0000000000000000 Oct 18 11:36:07 callcc kernel: [78989.876701] ffffa47900000000 ffffa47900000000 0000000000000000 ffffffffbc0c9476 Oct 18 11:36:07 callcc kernel: [78989.876704] 0000000000000006 ffffa47970117828 ffffa47970117828 0000000000000003 Oct 18 11:36:07 callcc kernel: [78989.876705] Call Trace: Oct 18 11:36:07 callcc kernel: [78989.876738] [<ffffffffc0386dac>] ? modeset_lock+0x13c/0x1cd [drm] Oct 18 11:36:07 callcc kernel: [78989.876742] [<ffffffffbc0c9476>] ? mark_lock+0x2a/0x203 Oct 18 11:36:07 callcc kernel: [78989.876745] [<ffffffffbc0caed7>] lock_acquire+0x139/0x1cd Oct 18 11:36:07 callcc kernel: [78989.876748] [<ffffffffbc0caed7>] ? lock_acquire+0x139/0x1cd Oct 18 11:36:07 callcc kernel: [78989.876777] [<ffffffffc0386dac>] ? modeset_lock+0x13c/0x1cd [drm] Oct 18 11:36:07 callcc kernel: [78989.876782] [<ffffffffbc66b492>] __ww_mutex_lock+0x94/0x5b0 Oct 18 11:36:07 callcc kernel: [78989.876809] [<ffffffffc0386dac>] ? modeset_lock+0x13c/0x1cd [drm] Oct 18 11:36:07 callcc kernel: [78989.876813] [<ffffffffbc66b441>] ? __ww_mutex_lock+0x43/0x5b0 Oct 18 11:36:07 callcc kernel: [78989.876821] [<ffffffffbc0ac73b>] ? __might_sleep+0x9f/0xa6 Oct 18 11:36:07 callcc kernel: [78989.876848] [<ffffffffc0386dac>] ? modeset_lock+0x13c/0x1cd [drm] Oct 18 11:36:07 callcc kernel: [78989.876875] [<ffffffffc0386dac>] ? modeset_lock+0x13c/0x1cd [drm] Oct 18 11:36:07 callcc kernel: [78989.876879] [<ffffffffbc66b441>] ? __ww_mutex_lock+0x43/0x5b0 Oct 18 11:36:07 callcc kernel: [78989.876907] [<ffffffffc0386dac>] modeset_lock+0x13c/0x1cd [drm] Oct 18 11:36:07 callcc kernel: [78989.876934] [<ffffffffc0386dac>] ? modeset_lock+0x13c/0x1cd [drm] Oct 18 11:36:07 callcc kernel: [78989.876962] [<ffffffffc0386e79>] drm_modeset_lock+0x17/0x24 [drm] Oct 18 11:36:07 callcc kernel: [78989.876989] [<ffffffffc0387500>] drm_atomic_get_connector_state+0x43/0x14e [drm] Oct 18 11:36:07 callcc kernel: [78989.877003] [<ffffffffc03f3efd>] __drm_atomic_helper_set_config+0x229/0x2a6 [drm_kms_helper] Oct 18 11:36:07 callcc kernel: [78989.877017] [<ffffffffc03f5ac2>] restore_fbdev_mode+0xfd/0x21b [drm_kms_helper] Oct 18 11:36:07 callcc kernel: [78989.877032] [<ffffffffc03f6b78>] drm_fb_helper_restore_fbdev_mode_unlocked+0x36/0x6d [drm_kms_helper] Oct 18 11:36:07 callcc kernel: [78989.877045] [<ffffffffc03f6bf0>] drm_fb_helper_set_par+0x41/0x4d [drm_kms_helper] Oct 18 11:36:07 callcc kernel: [78989.877096] [<ffffffffc049ebb1>] intel_fbdev_set_par+0x17/0x56 [i915] Oct 18 11:36:07 callcc kernel: [78989.877100] [<ffffffffbc378ae6>] fb_set_var+0x2b2/0x3a9 Oct 18 11:36:07 callcc kernel: [78989.877105] [<ffffffffbc01ead3>] ? native_sched_clock+0x1a/0x35 Oct 18 11:36:07 callcc kernel: [78989.877107] [<ffffffffbc0c9476>] ? mark_lock+0x2a/0x203 Oct 18 11:36:07 callcc kernel: [78989.877111] [<ffffffffbc0ca1f6>] ? __lock_acquire+0x707/0x1007 Oct 18 11:36:07 callcc kernel: [78989.877115] [<ffffffffbc374289>] fbcon_blank+0x89/0x1fa Oct 18 11:36:07 callcc kernel: [78989.877121] [<ffffffffbc3df862>] do_unblank_screen+0xf6/0x164 Oct 18 11:36:07 callcc kernel: [78989.877125] [<ffffffffbc3d6bff>] complete_change_console+0x56/0xc5 Oct 18 11:36:07 callcc kernel: [78989.877129] [<ffffffffbc3d7c3c>] vt_ioctl+0xfce/0x1276 Oct 18 11:36:07 callcc kernel: [78989.877149] [<ffffffffc03713d5>] ? drm_ioctl+0x2ff/0x3ed [drm] Oct 18 11:36:07 callcc kernel: [78989.877153] [<ffffffffbc3cd2c7>] tty_ioctl+0xbef/0xc85 Oct 18 11:36:07 callcc kernel: [78989.877156] [<ffffffffbc01ead3>] ? native_sched_clock+0x1a/0x35 Oct 18 11:36:07 callcc kernel: [78989.877159] [<ffffffffbc01ead3>] ? native_sched_clock+0x1a/0x35 Oct 18 11:36:07 callcc kernel: [78989.877162] [<ffffffffbc0b3a00>] ? sched_clock_cpu+0x1a/0xad Oct 18 11:36:07 callcc kernel: [78989.877167] [<ffffffffbc1e716a>] vfs_ioctl+0x18/0x34 Oct 18 11:36:07 callcc kernel: [78989.877169] [<ffffffffbc1e778e>] do_vfs_ioctl+0x56d/0x623 Oct 18 11:36:07 callcc kernel: [78989.877172] [<ffffffffbc0c60e7>] ? percpu_up_read+0x2d/0x54 Oct 18 11:36:07 callcc kernel: [78989.877175] [<ffffffffbc66ded2>] ? entry_SYSCALL_64_fastpath+0x5/0xac Oct 18 11:36:07 callcc kernel: [78989.877178] [<ffffffffbc0c983e>] ? trace_hardirqs_on_caller+0x183/0x19f Oct 18 11:36:07 callcc kernel: [78989.877181] [<ffffffffbc1e789b>] SyS_ioctl+0x57/0x79 Oct 18 11:36:07 callcc kernel: [78989.877184] [<ffffffffbc66dee9>] entry_SYSCALL_64_fastpath+0x1c/0xac Oct 18 11:36:07 callcc kernel: [78989.877187] [<ffffffffbc0c6939>] ? trace_hardirqs_off_caller+0x40/0xad Oct 18 11:36:07 callcc kernel: [78989.877233] Code: e9 b7 00 00 0f 84 91 00 00 00 49 81 3f 00 4f 09 bd b8 00 00 00 00 44 0f 44 e0 83 fe 01 77 5e 89 f0 49 8b 44 c7 08 48 85 c0 74 52 <f0> ff 80 98 01 00 00 45 8b ae 50 08 00 00 41 83 fd 2f 76 64 83 Oct 18 11:36:07 callcc kernel: [78989.877238] RSP <ffffa479701177c0> Oct 18 11:36:07 callcc kernel: [78989.877240] ---[ end trace bb751c011e2df8dc ]--- Also common after coming back from a suspend to memory: [ 30.641438] [drm] Finished loading i915/skl_dmc_ver1_26.bin (v1.26) [ 31.352660] [drm] Initialized i915 1.6.0 20160711 for 0000:00:02.0 on minor 0 [ 32.012007] snd_hda_intel 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915]) [ 33.840163] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device [ 47.122079] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun [ 6032.141510] [drm:intel_dp_link_training_clock_recovery [i915]] *ERROR* failed to enable link training [ 6032.414251] [drm:intel_dp_start_link_train [i915]] *ERROR* failed to start channel equalization There are also times when the screen locks up, and from the messages file: Oct 16 16:56:56 callcc kernel: [189350.055406] [drm] GPU HANG: ecode 9:0:0x86dffffd, in Xorg [2404], reason: Hang on render ring, action: reset Oct 16 16:56:56 callcc kernel: [189350.055555] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. Oct 16 16:56:56 callcc kernel: [189350.055556] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel Oct 16 16:56:56 callcc kernel: [189350.055557] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. Oct 16 16:56:56 callcc kernel: [189350.055558] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. Oct 16 16:56:56 callcc kernel: [189350.055559] [drm] GPU crash dump saved to /sys/class/drm/card0/error Oct 16 16:56:56 callcc kernel: [189350.057998] drm/i915: Resetting chip after gpu hang Oct 16 16:56:56 callcc kernel: [189350.061603] [drm] GuC firmware load skipped Oct 16 16:56:58 callcc kernel: [189352.047829] [drm] RC6 on and later: Oct 16 19:29:28 callcc kernel: [198501.953012] drm/i915: Resetting chip after gpu hang Oct 16 19:29:28 callcc kernel: [198501.958820] [drm] GuC firmware load skipped Oct 16 19:29:30 callcc kernel: [198503.952587] [drm] RC6 on Oct 16 19:29:44 callcc kernel: [198517.952829] drm/i915: Resetting chip after gpu hang Oct 16 19:29:44 callcc kernel: [198517.956557] [drm] GuC firmware load skipped Oct 16 19:29:46 callcc kernel: [198519.952264] [drm] RC6 on Oct 16 19:38:45 callcc xfce4-notifyd[28119]: Failed to parse css file: gtk.css:10:14not a number Oct 16 22:11:12 callcc kernel: [208205.943794] drm/i915: Resetting chip after gpu hang Oct 16 22:11:12 callcc kernel: [208205.945629] [drm] GuC firmware load skipped Oct 16 22:11:14 callcc kernel: [208207.943659] [drm] RC6 on Oct 16 22:13:00 callcc kernel: [208314.023438] drm/i915: Resetting chip after gpu hang Oct 16 22:13:00 callcc kernel: [208314.025159] [drm] GuC firmware load skipped Oct 16 22:13:02 callcc kernel: [208316.033501] [drm] RC6 on Thanks!! - Ted _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/intel-gfx
