Bug 1088052 - [abrt] BUG: soft lockup - CPU#3 stuck for 22s! [X:1661]
Summary: [abrt] BUG: soft lockup - CPU#3 stuck for 22s! [X:1661]
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:f5cc0145e7d271c1b6f8629a5ec...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-04-15 23:42 UTC by Tim Wegener
Modified: 2015-06-29 20:07 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-06-29 20:07:10 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: dmesg (246.36 KB, text/plain)
2014-04-15 23:43 UTC, Tim Wegener
no flags Details

Description Tim Wegener 2014-04-15 23:42:49 UTC
Description of problem:
Rebooted the computer.

Additional info:
reporter:       libreport-2.2.1
BUG: soft lockup - CPU#3 stuck for 22s! [X:1661]
Modules linked in: fuse ccm ip6t_rpfilter ip6t_REJECT xt_conntrack ebtable_nat ebtable_broute bridge stp llc bnep 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 iTCO_wdt iTCO_vendor_support dell_wmi ppdev sparse_keymap dell_laptop dcdbas arc4 iwldvm mac80211 snd_hda_codec_idt x86_pkg_temp_thermal coretemp uvcvideo kvm_intel videobuf2_vmalloc videobuf2_memops videobuf2_core videodev media kvm snd_hda_intel iwlwifi snd_hda_codec snd_hwdep joydev cfg80211 snd_seq btusb microcode sdhci_pci bluetooth i2c_i801 serio_raw sdhci snd_seq_device mmc_core snd_pcm rfkill snd_page_alloc snd_timer lpc_ich parport_pc snd mei_me soundcore mfd_core parport mei shpchp nfsd auth_rpcgss nfs_acl lockd sunrpc dm_crypt nouveau i915 mxm_wmi crct10dif_pclmul crc32_pclmul ttm i2c_algo_bit drm_kms_helper crc32c_intel ghash_clmulni_intel e1000e drm ptp i2c_core pps_core wmi video
CPU: 3 PID: 1661 Comm: X Not tainted 3.13.9-200.fc20.x86_64 #1
Hardware name: Dell Inc. Latitude E6520/0J4TFW, BIOS A06 07/11/2011
task: ffff88022f3d9140 ti: ffff88022fa60000 task.ti: ffff88022fa60000
RIP: 0010:[<ffffffff81328d52>]  [<ffffffff81328d52>] ioread32+0x42/0x50
RSP: 0018:ffff88022fa61b50  EFLAGS: 00000296
RAX: 00000000ffffffff RBX: 0000000080000000 RCX: 0000000080000000
RDX: ffff88022e7dbc00 RSI: 0000000077359400 RDI: ffffc9000571a804
RBP: ffff88022fa61b90 R08: 0000000000000000 R09: ffff880230f2f800
R10: 0000000000000000 R11: 0000000000000001 R12: 0000000000000000
R13: ffff880230f2f800 R14: 0000000000000000 R15: 0000000000000001
FS:  00007fa2c43369c0(0000) GS:ffff88023dc60000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00000000018abc40 CR3: 000000023048f000 CR4: 00000000000407e0
Stack:
 ffffffffa02a0464 0000000077359400 ffffffffffffffff 0000000000100154
 ffff88022eb5f600 000000000061a804 000000000061a804 000000000061a80c
 ffff88022fa61bd0 ffffffffa02af1fa 000000012fa61bd0 ffff88022fa61bfc
Call Trace:
 [<ffffffffa02a0464>] ? nouveau_timer_wait_eq+0x64/0xd0 [nouveau]
 [<ffffffffa02af1fa>] nv50_dac_sense+0x7a/0x150 [nouveau]
 [<ffffffffa02af30c>] nv50_dac_mthd+0x3c/0x80 [nouveau]
 [<ffffffffa0304fcc>] nv50_dac_detect+0x7c/0x90 [nouveau]
 [<ffffffffa02ef1bd>] nouveau_connector_detect+0x3cd/0x440 [nouveau]
 [<ffffffffa018327b>] drm_helper_probe_single_connector_modes+0x1eb/0x380 [drm_kms_helper]
 [<ffffffffa0055117>] drm_mode_getconnector+0x417/0x480 [drm]
 [<ffffffffa00521c1>] ? drm_crtc_convert_to_umode+0xd1/0x150 [drm]
 [<ffffffffa0046b52>] drm_ioctl+0x502/0x630 [drm]
 [<ffffffffa02dbb8e>] nouveau_drm_ioctl+0x4e/0x90 [nouveau]
 [<ffffffff811cbae8>] do_vfs_ioctl+0x2d8/0x4a0
 [<ffffffff811cbd31>] SyS_ioctl+0x81/0xa0
 [<ffffffff81696d69>] system_call_fastpath+0x16/0x1b
Code: 66 0f 1f 84 00 00 00 00 00 55 48 c7 c6 d0 15 a4 81 48 89 e5 e8 f0 fe ff ff b8 ff ff ff ff 5d c3 66 0f 1f 84 00 00 00 00 00 8b 07 <c3> 66 66 66 66 2e 0f 1f 84 00 00 00 00 00 48 81 fe ff ff 03 00

Comment 1 Tim Wegener 2014-04-15 23:43:00 UTC
Created attachment 886686 [details]
File: dmesg

Comment 2 Fedora End Of Life 2015-05-29 11:34:59 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 20:07:10 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.