Bug 880949 - [abrt]: BUG: soft lockup - CPU#1 stuck for 22s! [flush-8:16:3137]
Summary: [abrt]: BUG: soft lockup - CPU#1 stuck for 22s! [flush-8:16:3137]
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 17
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:85e67e4a6379f71dc10b9b64d1b...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-11-28 09:14 UTC by Sandy
Modified: 2013-02-01 15:50 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-02-01 15:50:56 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Sandy 2012-11-28 09:14:53 UTC
Additional info:
libreport version: 2.0.18
abrt_version:   2.0.18
cmdline:        BOOT_IMAGE=/vmlinuz-3.6.7-4.fc17.x86_64 root=/dev/mapper/vg_san--pc-lv_root ro rd.md=0 rd.lvm.lv=vg_san-pc/lv_swap rd.dm=0 rd.lvm.lv=vg_san-pc/lv_root KEYTABLE=us rd.luks=0 SYSFONT=True LANG=en_US.UTF-8 rhgb quiet
kernel:         3.6.7-4.fc17.x86_64

backtrace:
:BUG: soft lockup - CPU#1 stuck for 22s! [flush-8:16:3137]
:Modules linked in: vfat fat usb_storage fuse bnep bluetooth ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 xt_state ip6table_filter ip6_tables nf_conntrack arc4 snd_hda_codec_realtek ath9k_htc ppdev ath9k_common ath9k_hw snd_hda_intel snd_hda_codec ath mac80211 parport_pc snd_hwdep iTCO_wdt iTCO_vendor_support snd_seq snd_seq_device snd_pcm cfg80211 snd_page_alloc snd_timer parport r8169 snd rfkill soundcore lpc_ich mfd_core i2c_i801 coretemp mii microcode binfmt_misc uinput i915 video i2c_algo_bit drm_kms_helper drm i2c_core
:CPU 1 
:Pid: 3137, comm: flush-8:16 Not tainted 3.6.7-4.fc17.x86_64 #1                  /DG41RQ
:RIP: 0010:[<ffffffff812eeb8c>]  [<ffffffff812eeb8c>] __list_del_entry+0x2c/0xd0
:RSP: 0018:ffff88003cfb1cc0  EFLAGS: 00000202
:RAX: ffff88003c205108 RBX: 0000000000000000 RCX: dead000000200200
:RDX: ffff880135014138 RSI: ffff8801350140b0 RDI: ffff88003c2013a8
:RBP: ffff88003cfb1cc0 R08: ffff88003c2013a8 R09: 0000000000000000
:R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
:R13: ffff88003cfb1cd0 R14: ffff880137959ee8 R15: ffff88003cfb1cc0
:FS:  0000000000000000(0000) GS:ffff88013fc80000(0000) knlGS:0000000000000000
:CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
:CR2: 00007f149e7f6000 CR3: 0000000001c0b000 CR4: 00000000000407e0
:DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
:DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
:Process flush-8:16 (pid: 3137, threadinfo ffff88003cfb0000, task ffff8800a0af9710)
:Stack:
: ffff88003cfb1cf0 ffffffff811b783e ffff88003cfb1cf0 ffff8801350140b0
: ffff88010f7f9800 0000000000000000 ffff88003cfb1d40 ffffffff811b8212
: 000000010049bb89 ffff8801173c3140 ffff88003cfb1d20 ffff8801173c3140
:Call Trace:
: [<ffffffff811b783e>] redirty_tail+0x5e/0x80
: [<ffffffff811b8212>] __writeback_inodes_wb+0x72/0xd0
: [<ffffffff811b980b>] wb_writeback+0x23b/0x2d0
: [<ffffffff811b9b5c>] wb_do_writeback+0xac/0x1f0
: [<ffffffff8106c0e0>] ? __internal_add_timer+0x130/0x130
: [<ffffffff811b9d2b>] bdi_writeback_thread+0x8b/0x230
: [<ffffffff811b9ca0>] ? wb_do_writeback+0x1f0/0x1f0
: [<ffffffff8107fde3>] kthread+0x93/0xa0
: [<ffffffff81627e04>] kernel_thread_helper+0x4/0x10
: [<ffffffff8107fd50>] ? kthread_freezable_should_stop+0x70/0x70
: [<ffffffff81627e00>] ? gs_change+0x13/0x13
:Code: 48 8b 17 48 b9 00 01 10 00 00 00 ad de 48 8b 47 08 48 89 e5 48 39 ca 74 29 48 b9 00 02 20 00 00 00 ad de 48 39 c8 74 7a 4c 8b 00 <4c> 39 c7 75 53 4c 8b 42 08 4c 39 c7 75 2b 48 89 42 08 48 89 10

Comment 1 Josh Boyer 2013-01-02 15:07:01 UTC
Do you recall what was happening when this triggered?  Possibly writing to a USB key?

Comment 2 Justin M. Forbes 2013-02-01 15:50:56 UTC
This bug is being closed because it has been set needinfo for more than 2 weeks without a response. If this is still an issue, please reopen and reply with the requested information.


Note You need to log in before you can comment on or make changes to this bug.