You are not logged in.
After the upgrade to the kernel 4.15.3-2, my laptop resumes from sleep to a blank screen with a cursor that does not blink and freezes. Even the virtual consoles don't seem to work. I switched to the linux-lts kernel and now it resumes flawlessly. Is it a bug in the kernel? Will it be fixed in the next kernel upgrade? Or will I need to wait longer and use the lts kernel till then?
Offline
The journalctl seems to end abruptly with the following lines
Feb 19 18:34:13 wire systemd-sleep[1301]: Suspending system...
Feb 19 18:34:13 wire kernel: PM: suspend entry (deep)After the system froze on resuming, I use the Magic key combination REISUB to reboot the system. But that did not get logged in the journals.
Last edited by kevinselvaprasanna (2018-02-19 13:30:41)
Offline
Same issue here, with a i7-4700MQ, on a Toshiba Laptop.
May be an issue related to the new kernel build flags?
Roberto
Offline
After the upgrade to the kernel 4.15.3-2, my laptop resumes from sleep to a blank screen with a cursor that does not blink and freezes.
What was kernel version you upgraded from that did not have the issue?
May be an issue related to the new kernel build flags?
What new kernel build flags?
Offline
What new kernel build flags?
From the Archlinux changelog for the kernel 4.15.3-2:
Pick some config options from Ubuntu
Re-enable CONFIG_X86_VSYSCALL_EMULATION in the future build
Last edited by GaalDornick (2018-02-19 16:12:46)
Roberto
Offline
@GaalDornick so linux 4.15.3-1 did not have the issue on your system?
Offline
@GaalDornick so linux 4.15.3-1 did not have the issue on your system?
Linux 4.15.3-1 worked fine.
Roberto
Offline
On 4.15-3-2 do you have either of nvidiafb or rivafb modules loaded?
Offline
@loqs: yes.
Here is the nvidia modules list
$ lsmod | grep nvidia
nvidiafb 57344 0
vgastate 20480 1 nvidiafb
fb_ddc 16384 1 nvidiafb
i2c_algo_bit 16384 3 nvidiafb,nouveau,i915
Last edited by GaalDornick (2018-02-19 18:12:57)
Roberto
Offline
If you blacklist nvidiafb or even try unloading it then try resuming the system from sleep any difference?
Offline
@loqs: bingo! the problem is related to the nvidiafb module. I removed it, with the rmmod command (I don't need it, as I used only the Intel video driver) and my laptop resumed from sleep.
Thank you for your hint.
PS: I just read in another thread that nvidiafb was introduced with 4.15.3-2.
Last edited by GaalDornick (2018-02-19 18:51:41)
Roberto
Offline
Had a similar issue. The display would black out during early boot, when it attempted to initiate modesetting. Strangely I upgraded to linux 4.15.3-2 a few days ago and didn't start seeing the issue until today... anyway, blacklisting nvidiafb also fixed the problem for me. Here's a slice of the offending dmesg output in case it helps. I found a similar report here http://lkml.iu.edu/hypermail/linux/kern … 00397.html so it appears to be an upstream issue that was only recently enabled in the arch kernel (https://git.archlinux.org/svntogit/pack … 069c84aaec).
Feb 19 14:37:16 arcana kernel: nvidiafb: Unable to detect display type...
Feb 19 14:37:16 arcana kernel: ...Using default of CRT
Feb 19 14:37:16 arcana kernel: nvidiafb: Unable to detect which CRTCNumber...
Feb 19 14:37:16 arcana kernel: ...Defaulting to CRTCNumber 0
Feb 19 14:37:16 arcana kernel: nvidiafb: Using CRT on CRTC 0
Feb 19 14:37:16 arcana kernel: divide error: 0000 [#1] PREEMPT SMP PTI
Feb 19 14:37:16 arcana kernel: Modules linked in: intel_rapl x86_pkg_temp_thermal intel_powerclamp iwlmvm(+) coretemp kvm_intel mac80211 ofpart cmdlinepart intel_spi_platform intel_spi spi_nor iTCO_wdt mtd iTCO_vendor_support asus_nb_wmi asus_wmi i915 sparse_keymap iwlwifi mxm_wmi kvm nls_iso8859_1 snd_hda_codec_realtek nls_cp437 snd_hda_codec_generic vfat fat cfg80211 snd_hda_intel snd_hda_codec irqbypass intel_cstate intel_uncore drm_kms_helper intel_rapl_perf psmouse input_leds pcspkr snd_hda_core i2c_i801 rfkill drm r8169 snd_hwdep nvidiafb(+) mei_me mii vgastate intel_pch_thermal lpc_ich fb_ddc mei snd_pcm shpchp snd_timer processor_thermal_device int340x_thermal_zone intel_gtt battery snd agpgart rtc_cmos syscopyarea sysfillrect soundcore sysimgblt intel_soc_dts_iosf fb_sys_fops ac int3400_thermal wmi asus_wireless
Feb 19 14:37:16 arcana kernel: evdev mac_hid i2c_algo_bit acpi_thermal_rel ip_tables x_tables ext4 crc16 mbcache jbd2 fscrypto algif_skcipher af_alg rtsx_usb_sdmmc led_class mmc_core rtsx_usb uas usb_storage dm_crypt dm_mod hid_logitech_hidpp hid_logitech_dj sd_mod crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel pcbc serio_raw atkbd libps2 ahci libahci aesni_intel libata aes_x86_64 crypto_simd glue_helper cryptd xhci_pci scsi_mod xhci_hcd i8042 serio hid_generic usbhid hid usbcore usb_common
Feb 19 14:37:16 arcana kernel: CPU: 1 PID: 340 Comm: systemd-udevd Not tainted 4.15.3-2-ARCH #1
Feb 19 14:37:16 arcana kernel: Hardware name: ASUSTeK COMPUTER INC. K501LX/K501LX, BIOS K501LX.203 04/16/2015
Feb 19 14:37:16 arcana kernel: RIP: 0010:nvGetClocks+0x74/0x260 [nvidiafb]
Feb 19 14:37:16 arcana kernel: RSP: 0018:ffffa4b6c11f7798 EFLAGS: 00010206
Feb 19 14:37:16 arcana kernel: RAX: 000000000516b430 RBX: 00000000000000df RCX: 0000000000000007
Feb 19 14:37:16 arcana kernel: RDX: 0000000000000000 RSI: ffffa4b6c11f77d8 RDI: ffff946d14352418
Feb 19 14:37:16 arcana kernel: RBP: ffff946d14352510 R08: ffffa4b6c11f77ec R09: 0000000000000000
Feb 19 14:37:16 arcana kernel: R10: 0000000000001290 R11: 00000000000000ba R12: 0000000000006247
Feb 19 14:37:16 arcana kernel: R13: 0000000000000010 R14: 0000000000050000 R15: 0000000000000008
Feb 19 14:37:16 arcana kernel: FS: 00007ff3fcb3b8c0(0000) GS:ffff946d1ec80000(0000) knlGS:0000000000000000
Feb 19 14:37:16 arcana kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Feb 19 14:37:16 arcana kernel: CR2: 00007f93b3cab020 CR3: 00000002533b0003 CR4: 00000000003606e0
Feb 19 14:37:16 arcana kernel: Call Trace:
Feb 19 14:37:16 arcana kernel: NVCalcStateExt+0x636/0x8d0 [nvidiafb]
Feb 19 14:37:16 arcana kernel: ? kmem_cache_alloc_trace+0x183/0x1c0
Feb 19 14:37:16 arcana kernel: ? kmem_cache_alloc_trace+0xa1/0x1c0
Feb 19 14:37:16 arcana kernel: nvidiafb_set_par+0x471/0xa00 [nvidiafb]
Feb 19 14:37:16 arcana kernel: fbcon_init+0x482/0x660
Feb 19 14:37:16 arcana kernel: visual_init+0xd5/0x130
Feb 19 14:37:16 arcana kernel: do_bind_con_driver+0x1f4/0x400
Feb 19 14:37:16 arcana kernel: do_take_over_console+0x7b/0x190
Feb 19 14:37:16 arcana kernel: do_fbcon_takeover+0x58/0xb0
Feb 19 14:37:16 arcana kernel: notifier_call_chain+0x47/0x70
Feb 19 14:37:16 arcana kernel: blocking_notifier_call_chain+0x3e/0x60
Feb 19 14:37:16 arcana kernel: ? down+0x12/0x50
Feb 19 14:37:16 arcana kernel: register_framebuffer+0x248/0x350
Feb 19 14:37:16 arcana kernel: nvidiafb_probe+0x612/0x9e0 [nvidiafb]
Feb 19 14:37:16 arcana kernel: local_pci_probe+0x42/0xa0
Feb 19 14:37:16 arcana kernel: ? pci_match_device+0xd9/0x100
Feb 19 14:37:16 arcana kernel: pci_device_probe+0x146/0x1b0
Feb 19 14:37:16 arcana kernel: driver_probe_device+0x315/0x480
Feb 19 14:37:16 arcana kernel: __driver_attach+0xa0/0xe0
Feb 19 14:37:16 arcana kernel: ? driver_probe_device+0x480/0x480
Feb 19 14:37:16 arcana kernel: bus_for_each_dev+0x6b/0xb0
Feb 19 14:37:16 arcana kernel: bus_add_driver+0x1c2/0x260
Feb 19 14:37:16 arcana kernel: ? nvidiafb_resume+0x90/0x90 [nvidiafb]
Feb 19 14:37:16 arcana kernel: driver_register+0x57/0xc0
Feb 19 14:37:16 arcana kernel: ? nvidiafb_resume+0x90/0x90 [nvidiafb]
Feb 19 14:37:16 arcana kernel: do_one_initcall+0x4e/0x190
Feb 19 14:37:16 arcana kernel: ? free_unref_page_commit+0x66/0xf0
Feb 19 14:37:16 arcana kernel: ? kmem_cache_alloc_trace+0xa1/0x1c0
Feb 19 14:37:16 arcana kernel: do_init_module+0x5b/0x205
Feb 19 14:37:16 arcana kernel: load_module+0x26ad/0x2b30
Feb 19 14:37:16 arcana kernel: ? kmem_cache_alloc_node_trace+0xe5/0x1d0
Feb 19 14:37:16 arcana kernel: ? vmap_page_range_noflush+0x27b/0x380
Feb 19 14:37:16 arcana kernel: ? SyS_init_module+0x163/0x1a0
Feb 19 14:37:16 arcana kernel: SyS_init_module+0x163/0x1a0
Feb 19 14:37:16 arcana kernel: do_syscall_64+0x75/0x190
Feb 19 14:37:16 arcana kernel: entry_SYSCALL_64_after_hwframe+0x21/0x86
Feb 19 14:37:16 arcana kernel: RIP: 0033:0x7ff3fc4656ca
Feb 19 14:37:16 arcana kernel: RSP: 002b:00007ffde086e208 EFLAGS: 00000246 ORIG_RAX: 00000000000000af
Feb 19 14:37:16 arcana kernel: RAX: ffffffffffffffda RBX: 000055f8e57efbc0 RCX: 00007ff3fc4656ca
Feb 19 14:37:16 arcana kernel: RDX: 00007ff3fbd1dcb5 RSI: 0000000000015250 RDI: 000055f8e581f1a0
Feb 19 14:37:16 arcana kernel: RBP: 00007ff3fbd1dcb5 R08: 0000000000000005 R09: 00007ff3fc721240
Feb 19 14:37:16 arcana kernel: R10: 0000000000000005 R11: 0000000000000246 R12: 000055f8e581f1a0
Feb 19 14:37:16 arcana kernel: R13: 000055f8e57d9470 R14: 0000000000020000 R15: 00007ffde086ed00
Feb 19 14:37:16 arcana kernel: Code: 00 41 81 e2 f0 fe 00 00 41 81 fa 90 02 00 00 74 11 41 89 db c1 eb 10 0f b6 db 41 c1 eb 18 44 0f af cb 0f af c2 31 d2 41 0f af c3 <41> f7 f1 d3 e8 89 06 48 8b 87 40 11 00 00 8b 88 00 40 00 00 8b
Feb 19 14:37:16 arcana kernel: RIP: nvGetClocks+0x74/0x260 [nvidiafb] RSP: ffffa4b6c11f7798Offline
Removing the nvidiafb module fixed my laptop too. Thanks everybody!
Offline
As noted in https://bbs.archlinux.org/viewtopic.php … 1#p1769601, me and other users have the same problem with kernels 4.15.3-2 and up.
I am using the drivers from the mesa package and not the nvidia or intel (xf86-video-intel drivers. lsmod | grep i915 shows the relevant drivers loaded:
i915 1908736 24
video 45056 3 nouveau,i915,ideapad_laptop
button 16384 2 nouveau,i915
i2c_algo_bit 16384 2 nouveau,i915
drm_kms_helper 192512 2 nouveau,i915
drm 438272 15 nouveau,i915,ttm,drm_kms_helper
intel_gtt 24576 2 intel_agp,i915
The nvidiafb and rivafb modules are not loaded.
With kernel 4.15.2 suspending to ram and resuming worked properly but from 4.15.3 and up, I get a kernel panic (caps lock led flashing) and the display seems turned off, no response from the keyboard. Resuming in linux-lts works fine as well. Any ideas on what to try next?
Last edited by deadveal (2018-02-21 23:28:48)
Offline
@deadval doublecheck nvidiafb and rivafb are not loaded. If not start a new thread for the separate issue.
If 4.15.2-2 worked but 4.15.3-1 did not build 4.15.3 with the config from 4.15.2-2 and try that and report the results in the new thread.
Offline
Huh, that is weird, I checked lsmod | grep nvidia before and nvidiafb was not loaded. I added the blacklist though and resumes works for 4.15.3-2 and 4.15.4-1-hardened. Guess I had nothing to lose by adding the option to my boot entries!
Last edited by deadveal (2018-02-22 00:06:07)
Offline