Bug 1080067 - [abrt] BUG: soft lockup - CPU#0 stuck for 24s! [Xorg:752]
Summary: [abrt] BUG: soft lockup - CPU#0 stuck for 24s! [Xorg:752]
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:700fbc121872ad3a080e5dcbec4...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-03-24 15:44 UTC by John Warriner
Modified: 2015-06-29 19:40 UTC (History)
9 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-06-29 19:40:43 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: dmesg (61.88 KB, text/plain)
2014-03-24 15:44 UTC, John Warriner
no flags Details

Description John Warriner 2014-03-24 15:44:44 UTC
Description of problem:
Hung during boot process

Additional info:
reporter:       libreport-2.2.0
BUG: soft lockup - CPU#0 stuck for 24s! [Xorg:752]
Modules linked in: ip6t_rpfilter ip6t_REJECT bnep bluetooth 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_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep arc4 snd_seq snd_seq_device rt61pci rt2x00pci rt2x00mmio snd_pcm rt2x00lib eeprom_93cx6 binfmt_misc mac80211 cfg80211 ppdev rfkill sky2 edac_core powernow_k8 kvm_amd kvm snd_page_alloc serio_raw k8temp edac_mce_amd shpchp snd_timer snd soundcore i2c_nforce2 parport_pc parport usb_storage ata_generic pata_acpi nouveau video mxm_wmi wmi i2c_algo_bit
drm_kms_helper ttm drm i2c_core firewire_ohci sata_nv pata_amd firewire_core crc_itu_t
CPU: 0 PID: 752 Comm: Xorg Not tainted 3.13.6-200.fc20.x86_64 #1
Hardware name: Acer Aspire T180/EM61SM/EM61PM         , BIOS R01-B3 02/07/2007
task: ffff8800374488a0 ti: ffff880094056000 task.ti: ffff880094056000
RIP: 0010:[<ffffffff81328832>]  [<ffffffff81328832>] ioread32+0x42/0x50
RSP: 0018:ffff880094057b40  EFLAGS: 00000296
RAX: 0000000000000000 RBX: ffff8800940dac60 RCX: 0000000000010000
RDX: ffffffffa0199180 RSI: ffffc90006096a7c RDI: ffffc90006096a7c
RBP: ffff880094057b48 R08: ffff88009e70c7d8 R09: 0000000000000fff
R10: 0000000000000000 R11: 000000000000000f R12: ffff88009402b9c0
R13: ffffffffa0195120 R14: 00000000f5e5372d R15: 00005d3030636630
FS:  00007f533cd7c9c0(0000) GS:ffff8800afa00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fc37bb10000 CR3: 000000009404b000 CR4: 00000000000007f0
Stack:
ffffffffa010e118 ffff880094057b58 ffffffffa010de04 ffff880094057b68
ffffffffa00d4ec9 ffff880094057bb0 ffffffffa00d7afd beef020100804701
0000000000000000 0000000000804701 0000000000000001 ffff88003745ea00
Call Trace:
[<ffffffffa010e118>] ? nv40_instmem_rd32+0x18/0x20 [nouveau]
[<ffffffffa010de04>] nv04_instobj_rd32+0x24/0x30 [nouveau]
[<ffffffffa00d4ec9>] _nouveau_gpuobj_rd32+0x29/0x30 [nouveau]
[<ffffffffa00d7afd>] nouveau_ramht_insert+0xad/0x120 [nouveau]
[<ffffffffa0127c87>] nv40_fifo_object_attach+0x87/0xd0 [nouveau]
[<ffffffffa00d5b7b>] nouveau_handle_create+0xbb/0x1b0 [nouveau]
[<ffffffffa00d70ff>] nouveau_object_new+0x1bf/0x210 [nouveau]
[<ffffffffa0151808>] nouveau_channel_new+0x3f8/0x6f0 [nouveau]
[<ffffffffa015a0df>] nouveau_abi16_ioctl_channel_alloc+0x14f/0x370 [nouveau]
[<ffffffffa0054b52>] drm_ioctl+0x502/0x630 [drm]
[<ffffffffa014fb8e>] nouveau_drm_ioctl+0x4e/0x90 [nouveau]
[<ffffffff811cb758>] do_vfs_ioctl+0x2d8/0x4a0
[<ffffffff811cb9a1>] SyS_ioctl+0x81/0xa0
[<ffffffff81691d7e>] ? do_page_fault+0xe/0x10
[<ffffffff816962e9>] system_call_fastpath+0x16/0x1b
Code: 66 0f 1f 84 00 00 00 00 00 55 48 c7 c6 60 12 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 John Warriner 2014-03-24 15:44:53 UTC
Created attachment 878108 [details]
File: dmesg

Comment 2 Fedora End Of Life 2015-05-29 11:21:20 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 19:40:43 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.