Bug 1099759 - [abrt] BUG: soft lockup - CPU#0 stuck for 21s! [gnome-session-c:1331]
Summary: [abrt] BUG: soft lockup - CPU#0 stuck for 21s! [gnome-session-c:1331]
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-21 07:09 UTC by killcap
Modified: 2015-02-17 20:16 UTC (History)
10 users (show)

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


Attachments (Terms of Use)
File: dmesg (63.73 KB, text/plain)
2014-05-21 07:09 UTC, killcap
no flags Details

Description killcap 2014-05-21 07:09:12 UTC
Description of problem:
probably noevau driver. choosing older kernel is OK.

Additional info:
reporter:       libreport-2.2.1
BUG: soft lockup - CPU#0 stuck for 21s! [gnome-session-c:1331]
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 snd_intel8x0 b43 snd_intel8x0m snd_ac97_codec bcma stkwebcam mac80211 v4l2_common ac97_bus ppdev videodev cfg80211 media snd_seq serio_raw powernow_k8 sdhci_pci snd_seq_device sdhci edac_core k8temp edac_mce_amd r8169 mii btusb r592 bluetooth memstick snd_pcm ssb mmc_core snd_page_alloc snd_timer snd sparse_keymap rfkill soundcore parport_pc parport input_polldev shpchp 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 i2c_core pata_sis video
CPU: 0 PID: 1331 Comm: gnome-session-c Not tainted 3.13.11-100.fc19.x86_64 #1
Hardware name: ASUSTeK Computer Inc.  A6Km      /A6Km      , BIOS 210     05/08/2006
task: ffff88002d844da0 ti: ffff88003bf30000 task.ti: ffff88003bf30000
RIP: 0010:[<ffffffff81328392>]  [<ffffffff81328392>] ioread32+0x42/0x50
RSP: 0018:ffff88003bf31c50  EFLAGS: 00000292
RAX: 0000000000000001 RBX: 0000000000000000 RCX: 0000000000000040
RDX: 000000000000cf1c RSI: ffffc900117ce048 RDI: ffffc900117ce048
RBP: ffff88003bf31c58 R08: ffff880033824900 R09: ffff88003e001b00
R10: ffffffffa0155cae R11: ffff88003bf31de8 R12: ffff8800338553d8
R13: 0000000000000000 R14: 000000018010000e R15: 000000018010000d
FS:  00007f849c114840(0000) GS:ffff88003fc00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fff8a7ba000 CR3: 000000002bf3c000 CR4: 00000000000007f0
Stack:
 ffffffffa0128e65 ffff88003bf31c68 ffffffffa015db3f ffff88003bf31c98
 ffffffffa015537a ffff88003bf2ee40 0000000000000000 0000000000000000
 ffff88002d844da0 ffff88003bf31cf0 ffffffffa0155985 ffff88003bf2ee40
Call Trace:
 [<ffffffffa0128e65>] ? _nouveau_fifo_channel_rd32+0x15/0x20 [nouveau]
 [<ffffffffa015db3f>] nv10_fence_read+0x1f/0x30 [nouveau]
 [<ffffffffa015537a>] nouveau_fence_update+0x5a/0x80 [nouveau]
 [<ffffffffa0155985>] nouveau_fence_wait+0xc5/0x1a0 [nouveau]
 [<ffffffffa0155cd8>] ? nouveau_fence_new+0x68/0xb0 [nouveau]
 [<ffffffffa0153fad>] nouveau_channel_idle+0x6d/0x90 [nouveau]
 [<ffffffffa015c9c2>] nouveau_abi16_chan_fini.isra.2+0x32/0x190 [nouveau]
 [<ffffffffa015d384>] nouveau_abi16_ioctl_channel_free+0x84/0xb0 [nouveau]
 [<ffffffffa005db52>] drm_ioctl+0x502/0x630 [drm]
 [<ffffffff8119d03a>] ? kmem_cache_free+0x1da/0x200
 [<ffffffff811cd8cf>] ? __d_free+0x3f/0x60
 [<ffffffffa0152b8e>] nouveau_drm_ioctl+0x4e/0x90 [nouveau]
 [<ffffffff811cb058>] do_vfs_ioctl+0x2d8/0x4a0
 [<ffffffff811ba0be>] ? ____fput+0xe/0x10
 [<ffffffff811cb2a1>] SyS_ioctl+0x81/0xa0
 [<ffffffff81690729>] system_call_fastpath+0x16/0x1b
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-21 07:09:17 UTC
Created attachment 897844 [details]
File: dmesg

Comment 2 Fedora End Of Life 2015-01-09 21:22:47 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:16:23 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.