Bug 1055047 - [abrt] BUG: soft lockup - CPU#3 stuck for 22s! [qemu-system-x86:2563] [NEEDINFO]
Summary: [abrt] BUG: soft lockup - CPU#3 stuck for 22s! [qemu-system-x86:2563]
Keywords:
Status: CLOSED DUPLICATE of bug 1058209
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 20
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:17d1ca3322a525a3ce149b5a0c1...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-01-18 09:31 UTC by riky
Modified: 2014-03-06 20:23 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-03-06 20:23:56 UTC
Type: ---
Embargoed:
jforbes: needinfo?


Attachments (Terms of Use)
File: dmesg (71.01 KB, text/plain)
2014-01-18 09:31 UTC, riky
no flags Details

Description riky 2014-01-18 09:31:45 UTC
Additional info:
reporter:       libreport-2.1.11.6.g4fe6
BUG: soft lockup - CPU#3 stuck for 22s! [qemu-system-x86:2563]
Modules linked in: tun ipt_MASQUERADE xt_CHECKSUM bnep bluetooth cfg80211 rfkill ip6t_rpfilter ip6t_REJECT 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 x86_pkg_temp_thermal coretemp kvm_intel kvm crc32_pclmul crc32c_intel snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep snd_seq snd_seq_device snd_pcm iTCO_wdt iTCO_vendor_support ppdev 8139too microcode 8139cp i2c_i801 snd_page_alloc lpc_ich serio_raw mii mfd_core snd_timer pcspkr snd soundcore parport_pc parport video nfsd auth_rpcgss nfs_acl lockd sunrpc binfmt_misc radeon i2c_algo_bit drm_kms_helper ttm ata_generic drm pata_acpi i2c_core
CPU: 3 PID: 2563 Comm: qemu-system-x86 Not tainted 3.13.0-0.rc8.git1.1.vanilla.mainline.knurd.1.fc20.i686+PAE #1
Hardware name: Gigabyte Technology Co., Ltd. To be filled by O.E.M./P75-D3, BIOS F4 05/21/2012
task: ee711200 ti: ed91e000 task.ti: ed91e000
EIP: 0060:[<c04a561b>] EFLAGS: 00000286 CPU: 3
EIP is at __srcu_read_unlock+0xb/0x20
EAX: ec6b2024 EBX: ed468000 ECX: 0000401c EDX: 00000000
ESI: 00000000 EDI: 00000000 EBP: ed91fe10 ESP: ed91fe10
 DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
CR0: 80050033 CR2: 91fb81a0 CR3: 2e7f5000 CR4: 000427f0
Stack:
 ed91feb0 fb8c103b 00000000 00000000 0033c328 00000000 ed91fe3c ee711200
 ee711200 00000286 edb16c00 8e1798bb 00000112 05f40c83 0000010f f7590300
 00b16c00 ec6b2024 7ffbfeff fffffffe c047e701 edb16c00 00000246 ed91fe94
Call Trace:
 [<fb8c103b>] kvm_arch_vcpu_ioctl_run+0x22b/0x10c0 [kvm]
 [<c047e701>] ? ttwu_do_activate.constprop.90+0x51/0x60
 [<c0480226>] ? try_to_wake_up+0x136/0x210
 [<fb8bdd3f>] ? kvm_arch_vcpu_load+0x4f/0x1f0 [kvm]
 [<fb8adca4>] ? vcpu_load+0x44/0x70 [kvm]
 [<fb8ae116>] kvm_vcpu_ioctl+0x416/0x4c0 [kvm]
 [<c04b64e4>] ? do_futex+0xf4/0xa90
 [<c059655b>] ? block_ioctl+0x3b/0x50
 [<fb8add00>] ? vcpu_put+0x30/0x30 [kvm]
 [<c05760a2>] do_vfs_ioctl+0x2e2/0x4c0
 [<c064081f>] ? file_has_perm+0x7f/0x90
 [<c064120c>] ? selinux_file_ioctl+0x4c/0xf0
 [<c05762e0>] SyS_ioctl+0x60/0x80
 [<c09ccccd>] sysenter_do_call+0x12/0x28
Code: 04 64 03 05 c4 90 d7 c0 01 d8 8b 48 08 83 c1 01 89 48 08 5b 89 d0 5e 5d c3 8d b4 26 00 00 00 00 55 89 e5 66 66 66 66 90 0f ae f0 <66> 90 8b 40 04 64 ff 0c 90 5d c3 8d 76 00 8d bc 27 00 00 00 00

Comment 1 riky 2014-01-18 09:31:55 UTC
Created attachment 851940 [details]
File: dmesg

Comment 2 Justin M. Forbes 2014-02-24 13:53:22 UTC
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 20 kernel bugs.

Fedora 20 has now been rebased to 3.13.4-200.fc20.  Please test this kernel update and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you experience different issues, please open a new bug report for those.

Comment 3 Josh Boyer 2014-03-06 20:23:56 UTC

*** This bug has been marked as a duplicate of bug 1058209 ***


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