Bug 947253 - [abrt] BUG: soft lockup - CPU#0 stuck for 23s! [migration/0:8]
Summary: [abrt] BUG: soft lockup - CPU#0 stuck for 23s! [migration/0:8]
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-nouveau
Version: 18
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ben Skeggs
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:01eaf2f13d8d58a6e08c55687f8...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-04-01 23:42 UTC by trevor
Modified: 2014-02-05 20:24 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-02-05 20:24:50 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: dmesg (64.38 KB, text/plain)
2013-04-01 23:42 UTC, trevor
no flags Details
message log (2.23 MB, application/octet-stream)
2013-04-09 00:53 UTC, trevor
no flags Details

Description trevor 2013-04-01 23:42:19 UTC
Description of problem:
Did standard upgrade, i.e. yum upgrade, then rebooted.  The system did not come up.  I needed to revert to earlier kernel.

Additional info:
BUG: soft lockup - CPU#0 stuck for 23s! [migration/0:8]
Modules linked in: ip6table_filter(+) ip6_tables binfmt_misc snd_hda_codec_analog snd_hda_intel snd_hda_codec snd_hwdep snd_seq snd_seq_device snd_pcm snd_page_alloc iTCO_wdt snd_timer iTCO_vendor_support snd lpc_ich i7core_edac edac_core tg3 mfd_core i2c_i801 ptp pps_core soundcore ppdev coretemp serio_raw parport_pc parport dcdbas microcode dell_wmi sparse_keymap vhost_net tun macvtap macvlan kvm_intel nfsd auth_rpcgss nfs_acl lockd sunrpc kvm uinput usb_storage nouveau mxm_wmi video i2c_algo_bit drm_kms_helper ttm crc32c_intel drm i2c_core wmi
CPU 0 
Pid: 8, comm: migration/0 Not tainted 3.8.4-202.fc18.x86_64 #1 Dell Inc. Precision WorkStation T3500  /0K095G
RIP: 0010:[<ffffffff810d6ace>]  [<ffffffff810d6ace>] stop_machine_cpu_stop+0x7e/0xf0
RSP: 0018:ffff88034e529db8  EFLAGS: 00000293
RAX: ffffffff81ce0490 RBX: ffff880349f04980 RCX: dead000000200200
RDX: 0000000000000001 RSI: ffff88034e522ec0 RDI: ffff88034a82fb90
RBP: ffff88034e529dd8 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000001 R12: 0000000000000000
R13: ffff88034e529d38 R14: ffff88034e523350 R15: 0000000000000000
FS:  0000000000000000(0000) GS:ffff88035fc00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 00007f8bf5dd4000 CR3: 0000000001c0c000 CR4: 00000000000007f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Process migration/0 (pid: 8, threadinfo ffff88034e528000, task ffff88034e522ec0)
Stack:
 ffff88034e522ec0 ffff88035fc0ea60 ffff88034a82fb90 ffff88034a82faf8
 ffff88034e529eb8 ffffffff810d6c0b ffff88034e529fd8 ffff88035fc0ea68
 0000000000000000 0000000000000000 ffff88035fc13d80 ffffffff81c47980
Call Trace:
 [<ffffffff810d6c0b>] cpu_stopper_thread+0xcb/0x1a0
 [<ffffffff8164ea56>] ? __schedule+0x3c6/0x7a0
 [<ffffffff810d6b40>] ? stop_machine_cpu_stop+0xf0/0xf0
 [<ffffffff81081fb0>] kthread+0xc0/0xd0
 [<ffffffff81010000>] ? ftrace_define_fields_xen_mc_entry+0xa0/0xf0
 [<ffffffff81081ef0>] ? kthread_create_on_node+0x120/0x120
 [<ffffffff8165882c>] ret_from_fork+0x7c/0xb0
 [<ffffffff81081ef0>] ? kthread_create_on_node+0x120/0x120
Code: 03 74 42 f0 ff 4b 24 0f 94 c1 84 c9 44 89 e2 74 0f 8b 4b 20 8b 73 10 83 c1 01 89 73 24 89 4b 20 83 fa 04 74 38 f3 90 44 8b 63 20 <41> 39 d4 74 f0 41 83 fc 02 75 c7 fa 66 66 90 66 66 90 eb c4 66

Comment 1 trevor 2013-04-01 23:42:22 UTC
Created attachment 730519 [details]
File: dmesg

Comment 2 Josh Boyer 2013-04-03 19:18:56 UTC
Is there more information if you remove 'rhgb' and 'quiet' from the kernel command line?

You seem to be able to get the oops from somewhere.  Would it be possible to get the full dmesg for the 3.8.4 (or 3.8.5) boot?  The dmesg you attached is for 3.7.6.

Comment 3 trevor 2013-04-09 00:51:36 UTC
Sorry for taking so long to reply.  This is my everyday work computer and it is difficult to get time to play about with it.  I tried rebooting without 'rhgb' and 'quiet' but did not get any additional information. Without 'rhgb' and 'quiet' the boot seemed to progress without must trouble until it seemed to want to start X, but I'm not sure, all the messages went by quickly and then the screen just went blank.  I have attached the log file from the original failure which occurs at the timestamp of "Apr  2 09:37:23".

I don't know how to get a dmesg output from the system after it has crashed. The previous output came from the Fedora automatic bug reporting feature.

Comment 4 trevor 2013-04-09 00:53:27 UTC
Created attachment 732894 [details]
message log

Comment 5 Josh Boyer 2013-04-09 11:46:06 UTC
Thanks, that was helpful.  The first lockup is actually with nouveau, which corresponds with your "...until it seemed to want to start X..." observation.

Apr  2 09:37:23 kelpie9 kernel: [   32.343121] BUG: soft lockup - CPU#5 stuck for 22s! [kworker/5:2:243]
Apr  2 09:37:23 kelpie9 kernel: [   32.343154] Modules linked in: usb_storage nouveau mxm_wmi video i2c_algo_bit drm_kms_helper ttm crc32c_intel drm i2c_core wmi
Apr  2 09:37:23 kelpie9 kernel: [   32.343161] CPU 5 
Apr  2 09:37:23 kelpie9 kernel: [   32.343164] Pid: 243, comm: kworker/5:2 Not tainted 3.8.4-202.fc18.x86_64 #1 Dell Inc. Precision WorkStation T3500  /0K095G
Apr  2 09:37:23 kelpie9 kernel: [   32.343165] RIP: 0010:[<ffffffffa00d3600>]  [<ffffffffa00d3600>] nouveau_i2c_sense_scl+0x90/0xc0 [nouveau]
Apr  2 09:37:23 kelpie9 kernel: [   32.343182] RSP: 0018:ffff880349b7ba98  EFLAGS: 00000297
Apr  2 09:37:23 kelpie9 kernel: [   32.343183] RAX: 0000000000000000 RBX: ffffffffa003487a RCX: ffff880349c13c00
Apr  2 09:37:23 kelpie9 kernel: [   32.343184] RDX: ffff88034e642800 RSI: 0000000000000005 RDI: 000000000000e138
Apr  2 09:37:23 kelpie9 kernel: [   32.343185] RBP: ffff880349b7ba98 R08: 0000000000016b80 R09: ffff880353002800
Apr  2 09:37:23 kelpie9 kernel: [   32.343186] R10: ffffffffa003487a R11: 0000000000000002 R12: ffffffffa003487a
Apr  2 09:37:23 kelpie9 kernel: [   32.343187] R13: ffff880349b7baa8 R14: ffffffffa003487a R15: ffff880349b7ba78
Apr  2 09:37:23 kelpie9 kernel: [   32.343189] FS:  0000000000000000(0000) GS:ffff88035fd40000(0000) knlGS:0000000000000000
Apr  2 09:37:23 kelpie9 kernel: [   32.343190] CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
Apr  2 09:37:23 kelpie9 kernel: [   32.343191] CR2: 00007f1016fb5898 CR3: 0000000001c0c000 CR4: 00000000000007e0
Apr  2 09:37:23 kelpie9 kernel: [   32.343192] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Apr  2 09:37:23 kelpie9 kernel: [   32.343193] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Apr  2 09:37:23 kelpie9 kernel: [   32.343194] Process kworker/5:2 (pid: 243, threadinfo ffff880349b7a000, task ffff880349940000)
Apr  2 09:37:23 kelpie9 kernel: [   32.343195] Stack:
Apr  2 09:37:23 kelpie9 kernel: [   32.343196]  ffff880349b7bab8 ffffffffa005d05e ffff88034a3e7f58 ffff88034a3e7c00
Apr  2 09:37:23 kelpie9 kernel: [   32.343198]  ffff880349b7bad8 ffffffffa005d116 ffff88034a3e7f58 0000000000000036
Apr  2 09:37:23 kelpie9 kernel: [   32.343200]  ffff880349b7bb68 ffffffffa005d9fc 0000000200500005 ffff880349940048
Apr  2 09:37:23 kelpie9 kernel: [   32.343202] Call Trace:
Apr  2 09:37:23 kelpie9 kernel: [   32.343206]  [<ffffffffa005d05e>] sclhi+0x4e/0x80 [i2c_algo_bit]
Apr  2 09:37:23 kelpie9 kernel: [   32.343208]  [<ffffffffa005d116>] acknak+0x36/0x90 [i2c_algo_bit]
Apr  2 09:37:23 kelpie9 kernel: [   32.343210]  [<ffffffffa005d9fc>] bit_xfer+0x26c/0x870 [i2c_algo_bit]
Apr  2 09:37:23 kelpie9 kernel: [   32.343213]  [<ffffffffa000a224>] __i2c_transfer+0x64/0x80 [i2c_core]
Apr  2 09:37:23 kelpie9 kernel: [   32.343216]  [<ffffffffa000ab84>] i2c_transfer+0x64/0xe0 [i2c_core]
Apr  2 09:37:23 kelpie9 kernel: [   32.343225]  [<ffffffffa0032857>] drm_do_probe_ddc_edid+0xa7/0x110 [drm]
Apr  2 09:37:23 kelpie9 kernel: [   32.343230]  [<ffffffffa003489a>] drm_get_edid+0x8a/0x2f0 [drm]
Apr  2 09:37:23 kelpie9 kernel: [   32.343239]  [<ffffffffa00d3fcf>] ? nv_probe_i2c+0x4f/0x60 [nouveau]
Apr  2 09:37:23 kelpie9 kernel: [   32.343252]  [<ffffffffa013d30f>] nouveau_connector_detect+0x16f/0x390 [nouveau]
Apr  2 09:37:23 kelpie9 kernel: [   32.343256]  [<ffffffffa007a972>] drm_helper_hpd_irq_event+0xb2/0x140 [drm_kms_helper]
Apr  2 09:37:23 kelpie9 kernel: [   32.343264]  [<ffffffffa00d2219>] ? nouveau_gpio_find+0x59/0xe0 [nouveau]
Apr  2 09:37:23 kelpie9 kernel: [   32.343277]  [<ffffffffa013d001>] nouveau_connector_hotplug+0x51/0xc0 [nouveau]
Apr  2 09:37:23 kelpie9 kernel: [   32.343285]  [<ffffffffa00d2563>] nouveau_gpio_isr_bh+0x33/0x60 [nouveau]
Apr  2 09:37:23 kelpie9 kernel: [   32.343289]  [<ffffffff8107a693>] process_one_work+0x163/0x490
Apr  2 09:37:23 kelpie9 kernel: [   32.343291]  [<ffffffff8107ceee>] worker_thread+0x15e/0x450
Apr  2 09:37:23 kelpie9 kernel: [   32.343292]  [<ffffffff8107cd90>] ? busy_worker_rebind_fn+0x110/0x110
Apr  2 09:37:23 kelpie9 kernel: [   32.343294]  [<ffffffff81081fb0>] kthread+0xc0/0xd0
Apr  2 09:37:23 kelpie9 kernel: [   32.343298]  [<ffffffff81010000>] ? ftrace_define_fields_xen_mc_entry+0xa0/0xf0
Apr  2 09:37:23 kelpie9 kernel: [   32.343300]  [<ffffffff81081ef0>] ? kthread_create_on_node+0x120/0x120
Apr  2 09:37:23 kelpie9 kernel: [   32.343303]  [<ffffffff8165882c>] ret_from_fork+0x7c/0xb0
Apr  2 09:37:23 kelpie9 kernel: [   32.343305]  [<ffffffff81081ef0>] ? kthread_create_on_node+0x120/0x120
Apr  2 09:37:23 kelpie9 kernel: [   32.343306] Code: 04 83 e0 01 5d c3 0f 1f 44 00 00 0f b6 97 b4 03 00 00 31 f6 48 89 cf e8 0f 0a 01 00 c0 e8 02 83 e0 01 5d c3 0f 1f 80 00 00 00 00 <48> 03 79 48 e8 47 4c 23 e1 5d 83 e0 01 c3 66 90 8b bf b4 03 00 
Apr  2 09:37:23 kelpie9 kernel: [   57.292472] [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 207
Apr  2 09:37:23 kelpie9 kernel: [   57.292481] Raw EDID:
Apr  2 09:37:23 kelpie9 kernel: [   57.292485]  	00 ff ff ff ff ff ff 00 10 ac 2b a0 53 46 47 30
Apr  2 09:37:23 kelpie9 kernel: [   57.333573]  	10 50 54 a5 4b 00 81 80 a9 40 71 4f 01 01 01 01
Apr  2 09:37:23 kelpie9 kernel: [   57.333579]  	01 01 01 01 01 01 28 3c 80 a0 70 b0 23 40 30 20
Apr  2 09:37:23 kelpie9 kernel: [   57.333584]  	36 00 07 40 21 00 00 1a 00 00 00 ff 00 47 32 39
Apr  2 09:37:23 kelpie9 kernel: [   57.333589]  	31 48 38 39 43 30 47 46 53 0a 00 00 00 fc 00 44
Apr  2 09:37:23 kelpie9 kernel: [   57.333594]  	45 4c 4c 20 32 34 30 38 57 46 50 0a 00 00 00 fd
Apr  2 09:37:23 kelpie9 kernel: [   57.333598]  	ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Apr  2 09:37:23 kelpie9 kernel: [   57.381467]  	ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Apr  2 09:37:23 kelpie9 kernel: [   60.490164] [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 167
Apr  2 09:37:23 kelpie9 kernel: [   60.490171] Raw EDID:
Apr  2 09:37:23 kelpie9 kernel: [   60.490175]  	00 ff ff ff ff ff ff 00 10 ac 2b a0 53 46 47 30
Apr  2 09:37:23 kelpie9 kernel: [   60.575569]  	25 12 01 04 a5 34 20 78 22 b3 25 ac 51 30 b4 26
Apr  2 09:37:23 kelpie9 kernel: [   60.575574]  	10 50 54 a5 4b 00 81 80 a9 40 71 4f 01 01 01 01
Apr  2 09:37:23 kelpie9 kernel: [   60.575579]  	31 48 38 39 43 30 47 46 53 0a 00 00 00 fc 00 44
Apr  2 09:37:23 kelpie9 kernel: [   60.575584]  	45 4c 4c 20 32 34 30 38 57 46 50 0a 00 00 00 fd
Apr  2 09:37:23 kelpie9 kernel: [   60.575588]  	ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Apr  2 09:37:23 kelpie9 kernel: [   60.575593]  	ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Apr  2 09:37:23 kelpie9 kernel: [   60.575597]  	ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Apr  2 09:37:23 kelpie9 kernel: [   63.749948] nouveau E[     DRM] DDC responded, but no EDID for DVI-I-1
Apr  2 09:37:23 kelpie9 kernel: [   63.781607] nouveau E[     DRM] DDC responded, but no EDID for DVI-I-1
Apr  2 09:37:23 kelpie9 kernel: [   64.148249] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)

Comment 6 trevor 2013-05-21 08:29:27 UTC
I am still experiencing this with kernel 3.9.2-200.fc18.x86_64

Comment 7 Fedora End Of Life 2013-12-21 12:36:15 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 
'version' of '18'.

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 prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 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 to Fedora 18's end of life.

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 8 Fedora End Of Life 2014-02-05 20:24:50 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.