Bug 1447677
Summary: | Soft kernel lockup with 4.10.12-200.fc25.x86_64 and 4.10.13-200.fc25.x86_64 on Dell XPS 15 9560 | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Galen Lynch <galen.lynch> |
Component: | xorg-x11-drv-nouveau | Assignee: | Ben Skeggs <bskeggs> |
Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | urgent | Docs Contact: | |
Priority: | unspecified | ||
Version: | 29 | CC: | absal0m, accounts+fedora, airlied, ajax, bskeggs, chanueting, eminguez, eric.prestat, galen.lynch, gansalmon, ghisha, hdegoede, ichavero, itamar, itten, jan.public, jonathan, jones.peter.busi, kernel-maint, kherbst, labbott, lcm, lemenkov, madhu.chinakonda, mchehab, michael.heiss, mszpak, ozy, patrick.guio, pliuphys, robin+redhat, sroza, tadej.j, tnagata |
Target Milestone: | --- | Keywords: | Reopened |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-11-27 22:24:42 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Attachments: |
Description
Galen Lynch
2017-05-03 13:13:43 UTC
I can confirm this bug on my Dell XPS 15 9560 as well. The last working kernel was 4.10.10. Every update since then (up to and including 4.10.14) crashes on the graphical login. Apparently someone had the same problem with an Ubuntu build and they tracked the problem to this specific commit: commit 3287a46c7829c7c949862bc926cb8dda6756d6a1 Author: Ben Skeggs <bskeggs> Date: Thu Apr 6 10:35:26 2017 +1000 drm/nouveau: initial support (display-only) for GP107 commit da2ba564a6dcf46df4f828624ff55531ff11d5b0 upstream. Forked from GP106 implementation. Split out from commit enabling secboot/gr support so that it can be added to earlier kernels. Signed-off-by: Ben Skeggs <bskeggs> Signed-off-by: Greg Kroah-Hartman <gregkh> Maybe that helps... This also happens on 4.10.14. I have the same problem with 4.11.0-2.fc26 on my 9560. On the other hand, rc3 from the live CD works fine. Michael's Comment 2 sounds very plausible to me: the first time I installed F26 alpha it was OK, but I vaguely remember the problem started around rc8. It seems the commit was accepted in rc7. Thanks for the pointer to the commit. Let's have the nouveau team look at this. Can you post the full kernel log please? I suspect that PCI/ACPI aren't powering up the device properly when nouveau asks it to. You can likely work around this with "nouveau.runpm=0" in your kernel options in the meantime. I can't figure out how to generate a full kernel log, because I cannot boot into linux in the affected kernels. Is there some way that I can get the output of dmesg after I boot but before I can use gnome or a virtual terminal? Created attachment 1279686 [details]
Kernel log with soft lockup, XPS 9560
I tried to make one with journalctl _TRANSPORT=kernel and attached it above. Adding nouveau.runpm=0 to the kernel options allows me to login. $ uname -a Linux junichi 4.11.0-2.fc26.x86_64 #1 SMP Tue May 9 15:24:49 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Created attachment 1279693 [details]
4.10.14-200.fc25.x86_64 kernel log with lockup dell xps 9560
Can you try booting with acpi_rev_override=5? There are potentially other workarounds here: https://bugzilla.kernel.org/show_bug.cgi?id=156341 As far as I can tell, this isn't a bug in the driver, but the PCI/ACPI kernel layers. As I read the kernel bug too, it hasn't been entirely solved. Created attachment 1279859 [details]
Kernel log with acpi_rev_override=5
I tried booting with acpi_rev_override=5 and was unable to boot, with occasional soft lockup warnings. I have attached the kernel log with this boot option above. I saw a bunch of commits from Ben Skeggs in 4.11.3 and tested the Fedora kernel. After typing my password, the mouse didn't freeze (I remember that's the case for older versions). But I still didn't get in, and tried to reboot by clicking the triangle in the top right corner. After clicking reboot(restart?) in the pop-up window the mouse froze and I rebooted with SysRq. Created attachment 1282795 [details]
Kernel log, XPS 15+Fedora 26 Alpha, kernel 4.11.3-300.fc26.x86_64
Created attachment 1287384 [details]
Kernel log, XPS 15+Fedora 26 Alpha, vanilla kernel 4.12.0-rc5
I blindly tried 4.12.0-rc5, no luck. Behavior same as 4.11.3-300.fc26.x86_64.
Tried to install Fedora 26 from a liveusb to a new dell xps 15 9560 - got same problem @Ben Skeggs it is my understanding that acpi_rev_override would not work with the standard kernel because fedora kernels are compile without the CONFIG_ACPI_REV_OVERRIDE_POSSIBLE flag enabled. Eventually I managed to install Fedora 26 on dell xps 15 9560 after I set nomodeset in boot params Thanks for the advice Dmitry. I'm not familiar enough with Linux graphics to understand the implications of using nomodeset. My understanding is that it disables kernel mode setting for both Intel and Nvidia drivers, which seems like it would negatively impact performance. Is that right? Recent kernels and nouveau have still not worked for me. I just switched to bumblebee and closed source drivers and it fixed the problem. This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. *** Bug 1315392 has been marked as a duplicate of this bug. *** *** Bug 1399983 has been marked as a duplicate of this bug. *** *** Bug 912881 has been marked as a duplicate of this bug. *** *** Bug 1257347 has been marked as a duplicate of this bug. *** *** Bug 1054122 has been marked as a duplicate of this bug. *** *** Bug 1470371 has been marked as a duplicate of this bug. *** It's still there with kernel 4.16.12 and few older ones. Jun 12 12:51:17 lemenkov.example.com kernel: watchdog: BUG: soft lockup - CPU#4 stuck for 22s! [Xorg:2741] Jun 12 12:51:17 lemenkov.example.com kernel: Modules linked in: xfs fuse ccm xt_CHECKSUM ipt_MASQUERADE nf_nat_masquerade_ipv4 tun xt_addrtype nf_conntrack_netbios_ns nf_conntrack_broadcast xt_CT ip6t_rpfilt> Jun 12 12:51:18 lemenkov.example.com kernel: intel_powerclamp coretemp kvm_intel mac80211 kvm irqbypass intel_cstate intel_uncore intel_rapl_perf snd_hda_intel snd_usb_audio iwlwifi btusb snd_hda_codec btrt> Jun 12 12:51:18 lemenkov.example.com kernel: CPU: 4 PID: 2741 Comm: Xorg Not tainted 4.16.14-300.fc28.x86_64 #1 Jun 12 12:51:18 lemenkov.example.com kernel: Hardware name: LENOVO 20EGS0R60R/20EGS0R60R, BIOS GNET71WW (2.19 ) 02/05/2015 Jun 12 12:51:18 lemenkov.example.com kernel: RIP: 0010:ioread32+0x2b/0x30 Jun 12 12:51:18 lemenkov.example.com kernel: RSP: 0018:ffffabaa48d77b98 EFLAGS: 00000296 ORIG_RAX: ffffffffffffff12 Jun 12 12:51:18 lemenkov.example.com kernel: RAX: 00000000ffffffff RBX: ffff9acbe7b34800 RCX: ffffffffc08f73cc Jun 12 12:51:18 lemenkov.example.com kernel: RDX: ffffabaa4910a014 RSI: ffffabaa4910a014 RDI: ffffabaa49009410 Jun 12 12:51:18 lemenkov.example.com kernel: RBP: ffff9acbe7b34800 R08: 0000000000000002 R09: ffffabaa48d77b9c Jun 12 12:51:18 lemenkov.example.com kernel: R10: 0000000000000000 R11: 0000000000000001 R12: ffff9acbe75a0180 Jun 12 12:51:18 lemenkov.example.com kernel: R13: ffff9acbeb946900 R14: ffffffffffffffff R15: ffff9acbeb4830a0 Jun 12 12:51:18 lemenkov.example.com kernel: FS: 00007f4850578ac0(0000) GS:ffff9acbfe300000(0000) knlGS:0000000000000000 Jun 12 12:51:18 lemenkov.example.com kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Jun 12 12:51:18 lemenkov.example.com kernel: CR2: 00007f271c00b000 CR3: 000000042e29e001 CR4: 00000000001606e0 Jun 12 12:51:18 lemenkov.example.com kernel: Call Trace: Jun 12 12:51:18 lemenkov.example.com kernel: nv04_timer_read+0x1d/0x60 [nouveau] Jun 12 12:51:18 lemenkov.example.com kernel: nvkm_pmu_reset+0x62/0x160 [nouveau] Jun 12 12:51:18 lemenkov.example.com kernel: nvkm_subdev_preinit+0x32/0x100 [nouveau] Jun 12 12:51:18 lemenkov.example.com kernel: nvkm_device_init+0x5d/0x280 [nouveau] Jun 12 12:51:18 lemenkov.example.com kernel: nvkm_udevice_init+0x41/0x60 [nouveau] Jun 12 12:51:18 lemenkov.example.com kernel: nvkm_object_init+0x3e/0x100 [nouveau] Jun 12 12:51:18 lemenkov.example.com kernel: nvkm_object_init+0x71/0x100 [nouveau] Jun 12 12:51:18 lemenkov.example.com kernel: nvkm_object_init+0x71/0x100 [nouveau] Jun 12 12:51:18 lemenkov.example.com kernel: nouveau_do_resume+0x28/0x150 [nouveau] Jun 12 12:51:18 lemenkov.example.com kernel: nouveau_pmops_runtime_resume+0x8c/0x160 [nouveau] Jun 12 12:51:18 lemenkov.example.com kernel: ? pci_restore_standard_config+0x40/0x40 Jun 12 12:51:18 lemenkov.example.com kernel: pci_pm_runtime_resume+0x78/0xb0 Jun 12 12:51:18 lemenkov.example.com kernel: __rpm_callback+0xca/0x210 Jun 12 12:51:18 lemenkov.example.com kernel: ? pci_restore_standard_config+0x40/0x40 Jun 12 12:51:18 lemenkov.example.com kernel: rpm_callback+0x1f/0x70 Jun 12 12:51:18 lemenkov.example.com kernel: ? pci_restore_standard_config+0x40/0x40 Jun 12 12:51:18 lemenkov.example.com kernel: rpm_resume+0x560/0x780 Jun 12 12:51:18 lemenkov.example.com kernel: __pm_runtime_resume+0x47/0x70 Jun 12 12:51:18 lemenkov.example.com kernel: nouveau_drm_ioctl+0x35/0xc0 [nouveau] Jun 12 12:51:18 lemenkov.example.com kernel: do_vfs_ioctl+0xa4/0x610 Jun 12 12:51:18 lemenkov.example.com kernel: SyS_ioctl+0x74/0x80 Jun 12 12:51:18 lemenkov.example.com kernel: do_syscall_64+0x74/0x180 Jun 12 12:51:18 lemenkov.example.com kernel: entry_SYSCALL_64_after_hwframe+0x3d/0xa2 Jun 12 12:51:18 lemenkov.example.com kernel: RIP: 0033:0x7f484d7fbdf7 Jun 12 12:51:18 lemenkov.example.com kernel: RSP: 002b:00007ffdf1710518 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 Jun 12 12:51:18 lemenkov.example.com kernel: RAX: ffffffffffffffda RBX: 00000000025cab80 RCX: 00007f484d7fbdf7 Jun 12 12:51:18 lemenkov.example.com kernel: RDX: 00007ffdf1710564 RSI: 00000000c00464b4 RDI: 000000000000000d Jun 12 12:51:18 lemenkov.example.com kernel: RBP: 00007ffdf1710564 R08: 00000000025d1730 R09: 0000000000000007 Jun 12 12:51:18 lemenkov.example.com kernel: R10: fffffffffffffc86 R11: 0000000000000246 R12: 00000000c00464b4 Jun 12 12:51:18 lemenkov.example.com kernel: R13: 000000000000000d R14: 000000000084f438 R15: 0000000000830c18 Jun 12 12:51:18 lemenkov.example.com kernel: Code: 48 81 ff ff ff 03 00 77 20 48 81 ff 00 00 01 00 76 05 0f b7 d7 ed c3 48 c7 c6 89 ac 0e b7 e8 2d ff ff ff b8 ff ff ff ff c3 8b 07 <c3> 0f 1f 40 00 48 89 f2 4> Im my case it's x86_64 so I believe CPU architecture doesn't matter here. (In reply to Peter Lemenkov from comment #31) > It's still there with kernel 4.16.12 and few older ones. > > Jun 12 12:51:17 lemenkov.example.com kernel: watchdog: BUG: soft lockup - > CPU#4 stuck for 22s! [Xorg:2741] > Jun 12 12:51:17 lemenkov.example.com kernel: Modules linked in: xfs fuse ccm > xt_CHECKSUM ipt_MASQUERADE nf_nat_masquerade_ipv4 tun xt_addrtype > nf_conntrack_netbios_ns nf_conntrack_broadcast xt_CT ip6t_rpfilt> > Jun 12 12:51:18 lemenkov.example.com kernel: intel_powerclamp coretemp > kvm_intel mac80211 kvm irqbypass intel_cstate intel_uncore intel_rapl_perf > snd_hda_intel snd_usb_audio iwlwifi btusb snd_hda_codec btrt> > Jun 12 12:51:18 lemenkov.example.com kernel: CPU: 4 PID: 2741 Comm: Xorg Not > tainted 4.16.14-300.fc28.x86_64 #1 > Jun 12 12:51:18 lemenkov.example.com kernel: Hardware name: LENOVO > 20EGS0R60R/20EGS0R60R, BIOS GNET71WW (2.19 ) 02/05/2015 > Jun 12 12:51:18 lemenkov.example.com kernel: RIP: 0010:ioread32+0x2b/0x30 > Jun 12 12:51:18 lemenkov.example.com kernel: RSP: 0018:ffffabaa48d77b98 > EFLAGS: 00000296 ORIG_RAX: ffffffffffffff12 > Jun 12 12:51:18 lemenkov.example.com kernel: RAX: 00000000ffffffff RBX: > ffff9acbe7b34800 RCX: ffffffffc08f73cc > Jun 12 12:51:18 lemenkov.example.com kernel: RDX: ffffabaa4910a014 RSI: > ffffabaa4910a014 RDI: ffffabaa49009410 > Jun 12 12:51:18 lemenkov.example.com kernel: RBP: ffff9acbe7b34800 R08: > 0000000000000002 R09: ffffabaa48d77b9c > Jun 12 12:51:18 lemenkov.example.com kernel: R10: 0000000000000000 R11: > 0000000000000001 R12: ffff9acbe75a0180 > Jun 12 12:51:18 lemenkov.example.com kernel: R13: ffff9acbeb946900 R14: > ffffffffffffffff R15: ffff9acbeb4830a0 > Jun 12 12:51:18 lemenkov.example.com kernel: FS: 00007f4850578ac0(0000) > GS:ffff9acbfe300000(0000) knlGS:0000000000000000 > Jun 12 12:51:18 lemenkov.example.com kernel: CS: 0010 DS: 0000 ES: 0000 > CR0: 0000000080050033 > Jun 12 12:51:18 lemenkov.example.com kernel: CR2: 00007f271c00b000 CR3: > 000000042e29e001 CR4: 00000000001606e0 > Jun 12 12:51:18 lemenkov.example.com kernel: Call Trace: > Jun 12 12:51:18 lemenkov.example.com kernel: nv04_timer_read+0x1d/0x60 > [nouveau] > Jun 12 12:51:18 lemenkov.example.com kernel: nvkm_pmu_reset+0x62/0x160 > [nouveau] > Jun 12 12:51:18 lemenkov.example.com kernel: nvkm_subdev_preinit+0x32/0x100 > [nouveau] > Jun 12 12:51:18 lemenkov.example.com kernel: nvkm_device_init+0x5d/0x280 > [nouveau] > Jun 12 12:51:18 lemenkov.example.com kernel: nvkm_udevice_init+0x41/0x60 > [nouveau] > Jun 12 12:51:18 lemenkov.example.com kernel: nvkm_object_init+0x3e/0x100 > [nouveau] > Jun 12 12:51:18 lemenkov.example.com kernel: nvkm_object_init+0x71/0x100 > [nouveau] > Jun 12 12:51:18 lemenkov.example.com kernel: nvkm_object_init+0x71/0x100 > [nouveau] > Jun 12 12:51:18 lemenkov.example.com kernel: nouveau_do_resume+0x28/0x150 > [nouveau] > Jun 12 12:51:18 lemenkov.example.com kernel: > nouveau_pmops_runtime_resume+0x8c/0x160 [nouveau] > Jun 12 12:51:18 lemenkov.example.com kernel: ? > pci_restore_standard_config+0x40/0x40 > Jun 12 12:51:18 lemenkov.example.com kernel: pci_pm_runtime_resume+0x78/0xb0 > Jun 12 12:51:18 lemenkov.example.com kernel: __rpm_callback+0xca/0x210 > Jun 12 12:51:18 lemenkov.example.com kernel: ? > pci_restore_standard_config+0x40/0x40 > Jun 12 12:51:18 lemenkov.example.com kernel: rpm_callback+0x1f/0x70 > Jun 12 12:51:18 lemenkov.example.com kernel: ? > pci_restore_standard_config+0x40/0x40 > Jun 12 12:51:18 lemenkov.example.com kernel: rpm_resume+0x560/0x780 > Jun 12 12:51:18 lemenkov.example.com kernel: __pm_runtime_resume+0x47/0x70 > Jun 12 12:51:18 lemenkov.example.com kernel: nouveau_drm_ioctl+0x35/0xc0 > [nouveau] > Jun 12 12:51:18 lemenkov.example.com kernel: do_vfs_ioctl+0xa4/0x610 > Jun 12 12:51:18 lemenkov.example.com kernel: SyS_ioctl+0x74/0x80 > Jun 12 12:51:18 lemenkov.example.com kernel: do_syscall_64+0x74/0x180 > Jun 12 12:51:18 lemenkov.example.com kernel: > entry_SYSCALL_64_after_hwframe+0x3d/0xa2 > Jun 12 12:51:18 lemenkov.example.com kernel: RIP: 0033:0x7f484d7fbdf7 > Jun 12 12:51:18 lemenkov.example.com kernel: RSP: 002b:00007ffdf1710518 > EFLAGS: 00000246 ORIG_RAX: 0000000000000010 > Jun 12 12:51:18 lemenkov.example.com kernel: RAX: ffffffffffffffda RBX: > 00000000025cab80 RCX: 00007f484d7fbdf7 > Jun 12 12:51:18 lemenkov.example.com kernel: RDX: 00007ffdf1710564 RSI: > 00000000c00464b4 RDI: 000000000000000d > Jun 12 12:51:18 lemenkov.example.com kernel: RBP: 00007ffdf1710564 R08: > 00000000025d1730 R09: 0000000000000007 > Jun 12 12:51:18 lemenkov.example.com kernel: R10: fffffffffffffc86 R11: > 0000000000000246 R12: 00000000c00464b4 > Jun 12 12:51:18 lemenkov.example.com kernel: R13: 000000000000000d R14: > 000000000084f438 R15: 0000000000830c18 > Jun 12 12:51:18 lemenkov.example.com kernel: Code: 48 81 ff ff ff 03 00 77 > 20 48 81 ff 00 00 01 00 76 05 0f b7 d7 ed c3 48 c7 c6 89 ac 0e b7 e8 2d ff > ff ff b8 ff ff ff ff c3 8b 07 <c3> 0f 1f 40 00 48 89 f2 4> > > > Im my case it's x86_64 so I believe CPU architecture doesn't matter here. are you able to boot with nouveau.runpm=0 set? (In reply to Karol Herbst from comment #32) > > are you able to boot with nouveau.runpm=0 set? Hello Karol, Yes it solved the issue! Also I was able to boot to GNOME on my Lenovo W541 while attached to dock-station with secondary monitor plugged in. This wasn't possible before - I had to deattach laptop, boot to gnome-shell, and then (and only then) attach laptop to dock-station. But it looks like a different issue (something which might be related to bug 1549042, bug 1426245, or bug 1527669). The similar soft lockup occurred in 4.17.4-200.fc28.x86_64. ~~~ [532008.646574] video LNXVIDEO:01: Cannot transition to power state D0 for parent in D3cold [532008.646577] pci_raw_set_power_state: 67 callbacks suppressed [532008.646579] nouveau 0000:01:00.0: Refused to change power state, currently in D3 [532008.706767] video LNXVIDEO:01: Cannot transition to power state D0 for parent in D3cold [532008.719557] nouveau 0000:01:00.0: Refused to change power state, currently in D3 [532008.719562] video LNXVIDEO:01: Cannot transition to power state D0 for parent in D3cold [532008.731549] nouveau 0000:01:00.0: Refused to change power state, currently in D3 [532031.933880] watchdog: BUG: soft lockup - CPU#3 stuck for 23s! [Xorg:5592] [532031.933893] Modules linked in: rpcsec_gss_krb5 vhost_net vhost tap rfcomm fuse xt_CHECKSUM ipt_MASQUERADE nf_nat_masquerade_ipv4 tun devlink ip6 t_rpfilter ip6t_REJECT nf_reject_ipv6 xt_conntrack ip_set nfnetlink ebtable_nat ebtable_broute bridge stp llc ip6table_nat nf_conntrack_ipv6 nf_defr ag_ipv6 nf_nat_ipv6 ip6table_mangle ip6table_raw ip6table_security iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack ipta ble_mangle iptable_raw iptable_security ebtable_filter ebtables ip6table_filter ip6_tables cmac bnep rmi_smbus rmi_core arc4 mei_wdt iTCO_wdt iTCO_v endor_support intel_rapl gpio_ich x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel uvcvideo kvm iwlmvm videobuf2_vmalloc snd_hda_codec_realt ek videobuf2_memops snd_hda_codec_generic snd_hda_codec_hdmi btusb videobuf2_v4l2 [532031.933930] mac80211 videobuf2_common btrtl btbcm btintel snd_hda_intel irqbypass intel_cstate videodev snd_hda_codec bluetooth intel_uncore in tel_rapl_perf iwlwifi snd_hda_core snd_hwdep snd_seq snd_seq_device snd_pcm joydev media cfg80211 ecdh_generic wmi_bmof thinkpad_acpi i2c_i801 snd_t imer mei_me mei lpc_ich snd rfkill soundcore shpchp ie31200_edac nfsd auth_rpcgss nfs_acl lockd grace sunrpc xfs libcrc32c dm_crypt uas usb_storage nouveau i915 mxm_wmi ttm sdhci_pci i2c_algo_bit cqhci drm_kms_helper crct10dif_pclmul crc32_pclmul crc32c_intel sdhci ghash_clmulni_intel drm e1000e serio_raw mmc_core wmi video [532031.933958] CPU: 3 PID: 5592 Comm: Xorg Kdump: loaded Not tainted 4.17.4-200.fc28.x86_64 #1 [532031.933958] Hardware name: LENOVO 20EGS0R60Z/20EGS0R60Z, BIOS GNET71WW (2.19 ) 02/05/2015 [532031.933963] RIP: 0010:ioread32+0x2b/0x30 [532031.933963] RSP: 0018:ffffc13503a1fba0 EFLAGS: 00000292 ORIG_RAX: ffffffffffffff13 [532031.933965] RAX: 00000000ffffffff RBX: ffff9f10185be800 RCX: ffffffffc05d53cc [532031.933965] RDX: ffffc1350910a014 RSI: ffffc1350910a014 RDI: ffffc13509009400 [532031.933966] RBP: 00000000ffffffff R08: 0000000000000002 R09: ffffc13503a1fba4 [532031.933966] R10: 0000000000000000 R11: 0000000000000001 R12: ffff9f10151c70c0 [532031.933967] R13: ffff9f10107b2b40 R14: ffffffffffffffff R15: ffff9f1019da80a0 [532031.933968] FS: 00007f9b063c9ac0(0000) GS:ffff9f103e2c0000(0000) knlGS:0000000000000000 [532031.933968] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [532031.933969] CR2: 00007f9aeff02000 CR3: 00000007a262c004 CR4: 00000000001626e0 [532031.933970] Call Trace: [532031.934003] nv04_timer_read+0x2f/0x60 [nouveau] [532031.934023] nvkm_pmu_reset+0x62/0x160 [nouveau] [532031.934036] nvkm_subdev_preinit+0x32/0x100 [nouveau] [532031.934055] nvkm_device_init+0x5d/0x280 [nouveau] [532031.934073] nvkm_udevice_init+0x41/0x60 [nouveau] [532031.934085] nvkm_object_init+0x3e/0x100 [nouveau] [532031.934096] nvkm_object_init+0x71/0x100 [nouveau] [532031.934107] nvkm_object_init+0x71/0x100 [nouveau] [532031.934109] ? pci_restore_standard_config+0x40/0x40 [532031.934128] nouveau_do_resume+0x28/0x150 [nouveau] [532031.934146] nouveau_pmops_runtime_resume+0x88/0x150 [nouveau] [532031.934148] pci_pm_runtime_resume+0x78/0xb0 [532031.934151] __rpm_callback+0xca/0x210 [532031.934152] ? pci_restore_standard_config+0x40/0x40 [532031.934153] rpm_callback+0x1f/0x70 [532031.934155] ? pci_restore_standard_config+0x40/0x40 [532031.934156] rpm_resume+0x560/0x780 [532031.934166] ? drm_mode_connector_property_set_ioctl+0x60/0x60 [drm] [532031.934167] __pm_runtime_resume+0x47/0x70 [532031.934187] nouveau_drm_ioctl+0x35/0xc0 [nouveau] [532031.934190] do_vfs_ioctl+0xa4/0x610 [532031.934191] ksys_ioctl+0x60/0x90 [532031.934192] __x64_sys_ioctl+0x16/0x20 [532031.934195] do_syscall_64+0x5b/0x160 [532031.934197] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [532031.934198] RIP: 0033:0x7f9b0363ae17 [532031.934199] RSP: 002b:00007ffd51539b78 EFLAGS: 00003246 ORIG_RAX: 0000000000000010 [532031.934200] RAX: ffffffffffffffda RBX: 00000000017e3530 RCX: 00007f9b0363ae17 [532031.934201] RDX: 00007ffd51539bb0 RSI: 00000000c05064a7 RDI: 0000000000000010 [532031.934201] RBP: 00007ffd51539bb0 R08: 00000000017db770 R09: 0000000000000007 [532031.934202] R10: 0000000000000000 R11: 0000000000003246 R12: 00000000c05064a7 [532031.934202] R13: 0000000000000010 R14: 0000000000000010 R15: 00007ffd51539bb0 [532031.934203] Code: 48 81 ff ff ff 03 00 77 20 48 81 ff 00 00 01 00 76 05 0f b7 d7 ed c3 48 c7 c6 81 7b 10 bd e8 2d ff ff ff b8 ff ff ff ff c3 8b 07 <c3> 0f 1f 40 00 48 89 f2 48 81 fe ff ff 03 00 76 04 40 88 3e c3 ~~~ (In reply to Takayuki Nagata from comment #34) > The similar soft lockup occurred in 4.17.4-200.fc28.x86_64. > I see it on 4.17.9-200.fc28.x86_64 as well. Just booted with nouveau.runpm=0. No soft lockups yet, but it has only been a few minutes. kernel-4.17.19-100.fc27.x86_64 needs nouveau.runpm=0. This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '28'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 28 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. This message is a reminder that Fedora 29 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '29'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 29 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |