Bug 1153716 - [abrt] BUG: soft lockup - CPU#0 stuck for 22s! [X:645]
Summary: [abrt] BUG: soft lockup - CPU#0 stuck for 22s! [X:645]
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-nouveau
Version: 20
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ben Skeggs
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:80e240588d1c205b1af43382389...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-10-16 16:00 UTC by guillaume.rbl
Modified: 2015-06-29 22:56 UTC (History)
9 users (show)

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


Attachments (Terms of Use)
File: dmesg (55.17 KB, text/plain)
2014-10-16 16:00 UTC, guillaume.rbl
no flags Details

Description guillaume.rbl 2014-10-16 16:00:25 UTC
Description of problem:
after entering username and password nothing happens and the system goes back to login screen. Only the rescue mode of KDE plasma seems to work properly

Additional info:
reporter:       libreport-2.2.3
BUG: soft lockup - CPU#0 stuck for 22s! [X:645]
at-spi2-registr[1532]: segfault at 4d0 ip 42d0d812 sp bf81db00 error 4 in libX11.so.6.3.0[42cdd000+138000]
nouveau E[kwin[1376]] failed to idle channel 0xcccc0000 [kwin[1376]]
BUG: soft lockup - CPU#0 stuck for 23s! [kwin:1376]
Modules linked in: bnep bluetooth ip6t_rpfilter ip6t_REJECT cfg80211 rfkill xt_conntrack 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_intel8x0 snd_ac97_codec ac97_bus snd_seq snd_seq_device snd_pcm snd_timer iTCO_wdt iTCO_vendor_support ppdev dcdbas microcode serio_raw i2c_i801 snd soundcore lpc_ich i82875p_edac mfd_core edac_core parport_pc parport nfsd auth_rpcgss nfs_acl lockd sunrpc nouveau video mxm_wmi wmi i2c_algo_bit drm_kms_helper ttm e1000 ata_generic drm pata_acpi i2c_core
CPU: 0 PID: 1376 Comm: kwin Not tainted 3.16.4-200.fc20.i686+PAE #1
Hardware name: Dell Computer Corporation Precision WorkStation 360    /0W2563, BIOS A06 05/17/2004
task: ec9a5940 ti: eca30000 task.ti: eca30000
EIP: 0060:[<c0a255c2>] EFLAGS: 00000282 CPU: 0
EIP is at _raw_spin_lock+0x12/0x30
EAX: eca4a2e4 EBX: 00000000 ECX: ec9a5940 EDX: 0000b5b5
ESI: eca4a2c0 EDI: ec97a200 EBP: eca31c90 ESP: eca31c90
 DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
CR0: 8005003b CR2: b771d000 CR3: 304da000 CR4: 000007f0
Stack:
 eca31ca8 f7edd7dc ec97fa00 00000000 000003e8 ec97a200 eca31cf8 f7eddb45
 f7ee5426 0025a360 00000040 00000000 ec9a5940 00000000 ec9a5940 00001ce0
 f7edd8f6 ec97fa00 eca31d14 ec97a200 eca31cf8 f7ede046 38d13596 00000000
Call Trace:
 [<f7edd7dc>] nouveau_fence_update+0x1c/0x70 [nouveau]
 [<f7eddb45>] nouveau_fence_wait+0x205/0x4f0 [nouveau]
 [<f7ee5426>] ? nv10_fence_emit+0xa6/0xe0 [nouveau]
 [<f7edd8f6>] ? nouveau_fence_emit+0x66/0x80 [nouveau]
 [<f7ede046>] ? nouveau_fence_new+0x56/0xa0 [nouveau]
 [<f7edc4c4>] nouveau_channel_idle+0x84/0xa0 [nouveau]
 [<f7edc511>] nouveau_channel_del+0x31/0xe0 [nouveau]
 [<f7ee428e>] nouveau_abi16_chan_fini+0xfe/0x170 [nouveau]
 [<f7ee4503>] nouveau_abi16_fini+0x33/0x70 [nouveau]
 [<f7edb100>] nouveau_drm_preclose+0x30/0x60 [nouveau]
 [<f7cac1c0>] drm_release+0x50/0x530 [drm]
 [<c06d274b>] ? lockref_put_or_lock+0xb/0x30
 [<c0588dd4>] __fput+0xc4/0x1b0
 [<c0588efd>] ____fput+0xd/0x10
 [<c0479921>] task_work_run+0x91/0xb0
 [<c046072b>] do_exit+0x26b/0x8f0
 [<c046bffa>] ? __dequeue_signal+0x1a/0x1d0
 [<c046bbb7>] ? recalc_sigpending+0x17/0x50
 [<c046c1db>] ? dequeue_signal+0x2b/0x160
 [<c0460e24>] do_group_exit+0x34/0xa0
 [<c046e886>] get_signal_to_deliver+0x186/0x590
 [<c0410605>] do_signal+0x45/0x940
 [<c040ffb7>] ? __switch_to+0xe7/0x430
 [<c0a2238e>] ? __schedule+0x23e/0x6f0
 [<c048e925>] ? sched_clock_local+0x45/0x140
 [<c048ec37>] ? sched_clock_cpu+0xd7/0x110
 [<c0410f67>] do_notify_resume+0x67/0x90
 [<c0a25ba5>] work_notifysig+0x30/0x37
Code: d0 75 07 89 d8 5b 5d c3 f3 90 0f b6 11 38 d0 75 f7 eb f0 8d b6 00 00 00 00 55 89 e5 3e 8d 74 26 00 ba 00 01 00 00 3e 66 0f c1 10 <0f> b6 ce 38 d1 75 04 5d c3 f3 90 0f b6 10 38 ca 75 f7 5d c3 8d

Comment 1 guillaume.rbl 2014-10-16 16:00:33 UTC
Created attachment 947670 [details]
File: dmesg

Comment 2 Fedora End Of Life 2015-05-29 13:06:03 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:56:03 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.