Bug 1101909 - [abrt] BUG: soft lockup - CPU#0 stuck for 24s! [Xorg:612]
Summary: [abrt] BUG: soft lockup - CPU#0 stuck for 24s! [Xorg:612]
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-nouveau
Version: 19
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:c721afcf0fd2c654c0f4220af7c...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-05-28 07:00 UTC by killcap
Modified: 2015-02-17 20:17 UTC (History)
9 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-02-17 20:17:14 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: dmesg (85.07 KB, text/plain)
2014-05-28 07:00 UTC, killcap
no flags Details

Description killcap 2014-05-28 07:00:03 UTC
Description of problem:
It was after last upgrade. It can be concted to nouevau driver.  It is Ok when I choose older kernel

Additional info:
reporter:       libreport-2.2.1
BUG: soft lockup - CPU#0 stuck for 24s! [Xorg:612]
Modules linked in: ip6t_rpfilter ip6t_REJECT xt_conntrack rfcomm bnep 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 arc4 b43 bcma mac80211 cfg80211 powernow_k8 sdhci_pci ssb sdhci mmc_core ppdev stkwebcam v4l2_common videodev media snd_intel8x0m snd_intel8x0 snd_ac97_codec ac97_bus snd_seq snd_seq_device snd_pcm r8169 mii r592 memstick serio_raw k8temp edac_core edac_mce_amd snd_page_alloc snd_timer btusb sparse_keymap bluetooth snd rfkill parport_pc shpchp parport input_polldev soundcore uinput ata_generic pata_acpi nouveau mxm_wmi wmi i2c_algo_bit drm_kms_helper ttm drm firewire_ohci firewire_core crc_itu_t yenta_socket pata_sis i2c_core video
CPU: 0 PID: 612 Comm: Xorg Not tainted 3.13.11-100.fc19.x86_64 #1
Hardware name: ASUSTeK Computer Inc.  A6Km      /A6Km      , BIOS 210     05/08/2006
task: ffff880035eadee0 ti: ffff880034242000 task.ti: ffff880034242000
RIP: 0010:[<ffffffff81328392>]  [<ffffffff81328392>] ioread32+0x42/0x50
RSP: 0018:ffff880034243aa0  EFLAGS: 00000292
RAX: 0000000000000004 RBX: 0000000000000000 RCX: 0000000000000042
RDX: 00000000000094a1 RSI: ffffc90010388048 RDI: ffffc90010388048
RBP: ffff880034243aa8 R08: ffff8800342b1780 R09: ffff88003e001b00
R10: ffffffffa0157cae R11: ffffffffa015eaab R12: 0000000000000246
R13: 0000000000000000 R14: 0000000100100010 R15: 000000000010000f
FS:  00007fa5a3146980(0000) GS:ffff88003fc00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 00007fb4c3937088 CR3: 000000003bf52000 CR4: 00000000000007f0
Stack:
 ffffffffa012ae65 ffff880034243ab8 ffffffffa015fb3f ffff880034243ae8
 ffffffffa015737a ffff880028977d00 0000000000000000 0000000000000000
 ffff880035eadee0 ffff880034243b40 ffffffffa0157985 ffff880028977d00
Call Trace:
 [<ffffffffa012ae65>] ? _nouveau_fifo_channel_rd32+0x15/0x20 [nouveau]
 [<ffffffffa015fb3f>] nv10_fence_read+0x1f/0x30 [nouveau]
 [<ffffffffa015737a>] nouveau_fence_update+0x5a/0x80 [nouveau]
 [<ffffffffa0157985>] nouveau_fence_wait+0xc5/0x1a0 [nouveau]
 [<ffffffffa0157cd8>] ? nouveau_fence_new+0x68/0xb0 [nouveau]
 [<ffffffffa0155fad>] nouveau_channel_idle+0x6d/0x90 [nouveau]
 [<ffffffffa015e9c2>] nouveau_abi16_chan_fini.isra.2+0x32/0x190 [nouveau]
 [<ffffffffa015ed2e>] nouveau_abi16_fini+0x3e/0x80 [nouveau]
 [<ffffffffa0154f5e>] nouveau_drm_preclose+0x3e/0x80 [nouveau]
 [<ffffffffa00519c1>] drm_release+0x71/0x5b0 [drm]
 [<ffffffff811b9f1c>] __fput+0xdc/0x230
 [<ffffffff811ba0be>] ____fput+0xe/0x10
 [<ffffffff8108c064>] task_work_run+0xc4/0xe0
 [<ffffffff8106f7c4>] do_exit+0x2b4/0xa20
 [<ffffffffa00db91c>] ? nouveau_object_ref+0x5c/0xc0 [nouveau]
 [<ffffffffa00dbb17>] ? nouveau_object_del+0x97/0xb0 [nouveau]
 [<ffffffff8106ffaf>] do_group_exit+0x3f/0xa0
 [<ffffffff8107e9fb>] get_signal_to_deliver+0x1cb/0x5d0
 [<ffffffff81013438>] do_signal+0x48/0x5e0
 [<ffffffffa0154bb7>] ? nouveau_drm_ioctl+0x77/0x90 [nouveau]
 [<ffffffff811cb058>] ? do_vfs_ioctl+0x2d8/0x4a0
 [<ffffffff81013a40>] do_notify_resume+0x70/0xa0
 [<ffffffff816909e2>] int_signal+0x12/0x17
Code: 66 0f 1f 84 00 00 00 00 00 55 48 c7 c6 d0 06 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 killcap 2014-05-28 07:00:09 UTC
Created attachment 899851 [details]
File: dmesg

Comment 2 Fedora End Of Life 2015-01-09 21:23:21 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

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 19 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-02-17 20:17:14 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.