Additional info: BUG: soft lockup - CPU#1 stuck for 22s! [upowerd:1189] Modules linked in: tcp_lp nls_utf8 ebtable_nat fuse ipt_MASQUERADE nf_conntrack_netbios_ns nf_conntrack_broadcast bnep bluetooth rfkill ip6table_mangle ip6t_REJECT be2iscsi nf_conntrack_ipv6 nf_defrag_ipv6 iscsi_boot_sysfs bnx2i cnic uio iptable_nat nf_nat_ipv4 nf_nat cxgb4i cxgb4 cxgb3i cxgb3 mdio libcxgbi iptable_mangle ib_iser rdma_cm ib_addr iw_cm ib_cm ib_sa ib_mad ib_core iscsi_tcp nf_conntrack_ipv4 libiscsi_tcp nf_defrag_ipv4 xt_conntrack libiscsi nf_conntrack scsi_transport_iscsi ebtable_filter ebtables ip6table_filter ip6_tables snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_intel joydev snd_hda_codec snd_hwdep snd_seq snd_seq_device snd_pcm k10temp i2c_nforce2 serio_raw snd_page_alloc snd_timer snd soundcore microcode vhost_net tun macvtap macvlan kvm_amd kvm uinput dm_crypt nouveau mxm_wmi video i2c_algo_bit drm_kms_helper ttm drm ata_generic pata_acpi i2c_core sata_nv forcedeth pata_amd wmi usb_storage sunrpc Pid: 1189, comm: upowerd Not tainted 3.7.7-201.fc18.i686 #1 eMachines EL1352/EL1352 EIP: 0060:[<c067dac2>] EFLAGS: 00000296 CPU: 1 EIP is at ioread32+0x32/0x40 EAX: ffffffff EBX: f1fb0ea0 ECX: 00000000 EDX: 00000000 ESI: f1e7be00 EDI: 00000000 EBP: ef5f1e4c ESP: ef5f1e3c DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 CR0: 80050033 CR2: fdf8f0c0 CR3: 2f5c0000 CR4: 000007d0 DR0: 00000000 DR1: 00000000 DR2: 00000000 DR3: 00000000 DR6: ffff0ff0 DR7: 00000400 Process upowerd (pid: 1189, ti=ef5f0000 task=efde25b0 task.ti=ef5f0000) Stack: f83629ed f1fb0ea0 f1e7be00 00000000 ef5f1e6c f8362798 77359400 ffffffff ffffffff f1ec3c00 f1e7be00 00000800 ef5f1eac f83d3e03 0061a804 80000000 00000000 f8222784 e0e0e0e0 00000001 00000000 ffffffff 00000001 f5850000 Call Trace: [<f83629ed>] ? nv04_timer_read+0x1d/0x50 [nouveau] [<f8362798>] nouveau_timer_wait_eq+0x58/0xa0 [nouveau] [<f83d3e03>] nv50_dac_detect+0x93/0x2b0 [nouveau] [<f8222784>] ? drm_mode_object_find+0x54/0x70 [drm] [<f83b9b0a>] nouveau_connector_detect+0x23a/0x290 [nouveau] [<f822061a>] status_show+0x3a/0x80 [drm] [<f82205e0>] ? dpms_show+0x60/0x60 [drm] [<c0738dcf>] dev_attr_show+0x1f/0x50 [<c05a0dc5>] sysfs_read_file+0x85/0x160 [<c05425b3>] ? rw_verify_area+0x63/0x110 [<c05a0d40>] ? sysfs_write_file+0xf0/0xf0 [<c0542849>] vfs_read+0x89/0x160 [<c05a0d40>] ? sysfs_write_file+0xf0/0xf0 [<c0542967>] sys_read+0x47/0x80 [<c096c8cd>] sysenter_do_call+0x12/0x28 Code: 3d 00 00 01 00 76 0a 0f b7 d0 ed c3 90 8d 74 26 00 55 ba 60 42 b0 c0 89 e5 e8 4b fe ff ff b8 ff ff ff ff 5d c3 8d 74 26 00 8b 00 <c3> 8d b6 00 00 00 00 8d bc 27 00 00 00 00 3d ff ff 03 00 77 29
Duplicate of bug 981747?
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 'version' of '18'. 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 prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 to Fedora 18's end of life. 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 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.
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.
*** This bug has been marked as a duplicate of bug 1447677 ***