Bug 1032614 - [abrt] WARNING: CPU: 0 PID: 1 at arch/x86/kernel/apic/apic.c:1389 setup_local_APIC+0x268/0x320()
Summary: [abrt] WARNING: CPU: 0 PID: 1 at arch/x86/kernel/apic/apic.c:1389 setup_local...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 20
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:39bdab96af1a9407d348d8ceab0...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-20 13:29 UTC by Moez Roy
Modified: 2013-11-20 14:05 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-11-20 14:05:36 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: dmesg (32.54 KB, text/plain)
2013-11-20 13:29 UTC, Moez Roy
no flags Details

Description Moez Roy 2013-11-20 13:29:50 UTC
Additional info:
reporter:       libreport-2.1.9
WARNING: CPU: 0 PID: 1 at arch/x86/kernel/apic/apic.c:1389 setup_local_APIC+0x268/0x320()
Modules linked in:
CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.11.8-300.fc20.x86_64 #1
Hardware name: innotek GmbH VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006
 0000000000000009 ffff88007c757e00 ffffffff8164374b 0000000000000000
 ffff88007c757e38 ffffffff8106715d 0000000000000001 0000000000000000
 00000000000000f0 0000000000000000 00000000ffffffff ffff88007c757e48
Call Trace:
 [<ffffffff8164374b>] dump_stack+0x45/0x56
 [<ffffffff8106715d>] warn_slowpath_common+0x7d/0xa0
 [<ffffffff8106723a>] warn_slowpath_null+0x1a/0x20
 [<ffffffff81041378>] setup_local_APIC+0x268/0x320
 [<ffffffff81d1f623>] native_smp_prepare_cpus+0x2f0/0x3c2
 [<ffffffff81d0efbd>] kernel_init_freeable+0xba/0x1ff
 [<ffffffff81639960>] ? rest_init+0x80/0x80
 [<ffffffff8163996e>] kernel_init+0xe/0x190
 [<ffffffff816528ac>] ret_from_fork+0x7c/0xb0
 [<ffffffff81639960>] ? rest_init+0x80/0x80

Potential duplicate: bug 1030420

Comment 1 Moez Roy 2013-11-20 13:29:55 UTC
Created attachment 826645 [details]
File: dmesg

Comment 2 Josh Boyer 2013-11-20 14:05:36 UTC
This happened inside a virtualbox guest.  We don't support virtualbox.  Please reopen if this occurs on a normal machine or in a KVM guest.


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