Bug 1139017 - [abrt] BUG: soft lockup - CPU#8 stuck for 23s! [kworker/8:1:9246]
Summary: [abrt] BUG: soft lockup - CPU#8 stuck for 23s! [kworker/8:1:9246]
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-nouveau
Version: 20
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ben Skeggs
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:0e6d82f96ba90ef7ea98336291a...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-09-07 13:49 UTC by Stefan Loones
Modified: 2015-06-29 22:25 UTC (History)
9 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-06-29 22:25:23 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: dmesg (112.50 KB, text/plain)
2014-09-07 13:50 UTC, Stefan Loones
no flags Details

Description Stefan Loones 2014-09-07 13:49:55 UTC
Description of problem:
In my opinion it is still the same (until now unsolved) as 

https://bugzilla.redhat.com/show_bug.cgi?id=883919

with me this happens since I use a 27" monitor with resolution 2560x1440 (before i was using a 24" 1920x1200)



Additional info:
reporter:       libreport-2.2.3
BUG: soft lockup - CPU#8 stuck for 23s! [kworker/8:1:9246]
Modules linked in: nfsv3 nfs_acl rpcsec_gss_krb5 auth_rpcgss nfsv4 dns_resolver nfs lockd sunrpc fscache ip6t_rpfilter ip6t_REJECT xt_conntrack bnep bluetooth cfg80211 rfkill ebtable_nat ebtable_broute bridge stp llc ebtable_filter ebtables ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_mangle ip6table_security ip6table_raw ip6table_filter ip6_tables iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_mangle iptable_security iptable_raw snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic vfat fat iTCO_wdt iTCO_vendor_support x86_pkg_temp_thermal coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel microcode serio_raw sb_edac snd_hda_intel edac_core snd_hda_controller snd_hda_codec i2c_i801 snd_hwdep e1000e snd_seq snd_seq_device lpc_ich snd_pcm ptp mfd_core mei_me pps_core mei snd_timer snd ioatdma soundcore dca shpchp nouveau video mxm_wmi i2c_algo_bit drm_kms_helper ttm drm i2c_core wmi
CPU: 8 PID: 9246 Comm: kworker/8:1 Not tainted 3.15.6-200.fc20.x86_64 #1
Hardware name: Gigabyte Technology Co., Ltd. To be filled by O.E.M./X79-UD3, BIOS F11 07/05/2012
Workqueue: events nve0_fifo_recover_work [nouveau]
task: ffff880426179da0 ti: ffff88036e504000 task.ti: ffff88036e504000
RIP: 0010:[<ffffffffa00ffc58>]  [<ffffffffa00ffc58>] nve0_fifo_recover_work+0x78/0x330 [nouveau]
RSP: 0018:ffff88036e507de0  EFLAGS: 00000293
RAX: 0000000100000000 RBX: ffffffff810c1e4f RCX: 0000000000000020
RDX: 0000000000000009 RSI: 0000000000000282 RDI: 0000000000000282
RBP: ffff88036e507e18 R08: ffff880424c19ce0 R09: dfeef4fdb1619cd8
R10: dfeef4fdb1619cd8 R11: 0000000000000005 R12: ffffffff810c3c79
R13: ffff88036e507d80 R14: ffffffff810c7541 R15: ffff88036e507d80
FS:  0000000000000000(0000) GS:ffff88043fd00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ff8f2e8f000 CR3: 0000000003c11000 CR4: 00000000000407e0
Stack:
 ffff880425b23000 0000000000000001 ffff880424c19cd8 ffff8803b9814f00
 ffff88043fd13f00 ffff88043fd18000 0000000000000200 ffff88036e507e60
 ffffffff810a4af6 000000003fd13f00 0000000000000000 ffff88043fd13f00
Call Trace:
 [<ffffffff810a4af6>] process_one_work+0x176/0x430
 [<ffffffff810a578b>] worker_thread+0x11b/0x3a0
 [<ffffffff810a5670>] ? rescuer_thread+0x3b0/0x3b0
 [<ffffffff810ac528>] kthread+0xd8/0xf0
 [<ffffffff810ac450>] ? insert_kthread_work+0x40/0x40
 [<ffffffff816ff43c>] ret_from_fork+0x7c/0xb0
 [<ffffffff810ac450>] ? insert_kthread_work+0x40/0x40
Code: 86 02 00 00 89 ca 48 89 d8 45 31 f6 0f 1f 80 00 00 00 00 83 ea 17 83 fa 0b 0f 87 64 02 00 00 ff 24 d5 50 c8 15 a0 0f 1f 44 00 00 <ba> 01 00 00 00 0f 1f 00 41 09 d6 ba fe ff ff ff d3 c2 48 63 d2

Comment 1 Stefan Loones 2014-09-07 13:50:00 UTC
Created attachment 935139 [details]
File: dmesg

Comment 2 Fedora End Of Life 2015-05-29 12:48:53 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 '20'.

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 20 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.

Comment 3 Fedora End Of Life 2015-06-29 22:25:23 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.


Note You need to log in before you can comment on or make changes to this bug.