Bug 473746 - Problem booting FC10 and recent FC9 x86_64 kernels in virtual machine
Summary: Problem booting FC10 and recent FC9 x86_64 kernels in virtual machine
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 9
Hardware: All
OS: Linux
medium
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-11-30 07:08 UTC by David Carter
Modified: 2008-12-06 20:50 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2008-12-06 20:50:54 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Screenshot of boot screen (133.52 KB, image/png)
2008-11-30 07:08 UTC, David Carter
no flags Details

Description David Carter 2008-11-30 07:08:15 UTC
Created attachment 325113 [details]
Screenshot of boot screen

Description of problem:

I've been running some 64 bit virtual machines using Workstation 6 for quite some time now. With the 2 most reccent kernel updates, I'm getting kernel panics early in the boot process. The same happens if I try to install a 64 bit FC10. FC9 works fine when booting with an older kernel such as 2.6.26.6-79.fc9.x86_64

I tried booting the FC10 install on the bare metal, and it seems to boot fine. The host machine is a dual Opteron 250.

Version-Release number of selected component (if applicable):

FC9 Kernels 2.6.27.5-41.fc9.x86_64 2.6.27.5-37.fc9.x86_64
FC10 kernel 2.6.27.5-117.fc10.x86_64

How reproducible:
Consistently


Steps to Reproduce:
1. Boot with indicated kernels
  
Actual results:
Command line: initrd=initrd.img earlyprintk=vga vga=1 BOOT_IMAGE=vmlinuz
KERNEL supported cpus:
  Intel GenuineIntel
  AMD AuthenticAMD
  Centaur CentaurHauls
BIOS-provided physical RAM map:
 BIOS-e820:  0000000000000000 - 000000000009f800 (usable)
 BIOS-e820:  000000000009f800 - 00000000000a0000 (reserved)
 BIOS-e820:  00000000000ca000 - 00000000000cc000 (reserved)
 BIOS-e820:  00000000000dc000 - 0000000000100000 (reserved)
 BIOS-e820:  0000000000100000 - 000000003fef0000 (usable)
 BIOS-e820:  000000003fef0000 - 000000003feff000 (ACPI data)
 BIOS-e820:  000000003feff000 - 000000003ff00000 (ACPI NVS)
 BIOS-e820:  000000003ff00000 - 0000000040000000 (usable)
 BIOS-e820:  00000000fec00000 - 00000000fec10000 (reserved)
 BIOS-e820:  00000000fee00000 - 00000000fee01000 (reserved)
 BIOS-e820:  00000000fffe0000 - 0000000100000000 (reserved)
console [earlyvga0] enabled
last pfn = 0x40000 max_arch_pfn = 0x3ffffffff
x86 FAT enabled: cpu 0, old 0x0, new 0x7010600070106
init-memory-mapping
last_map_addr: 40000000 end: 40000000
RAMDISK: 3ede0000 - 3fecfde0
DMI present.
PANIC: early exception 0e rip 10:ffffffff815c986d error 0 cr2 fffffffeff34003d
Pid: 0, comm: swapper Not tainted 2.6.27.5-117.fc10.x86_64 #1

Call Trace:
 [<ffffffff8159d19e>] early_idt_handler+0x5e/0x72
 [<ffffffff815c986d>] ? dmi_string_nosave+0x44/0x90
 [<ffffffff815c989c>] ? dmi_string_nosave+0x73/0x90
 [<ffffffff815c98cb>] dmi_string+0x12/0x7d
 [<ffffffff810423a8>] ? vprintk+0x30b/0x33b
 [<ffffffff815c9959>] dmi_save_ident+0x23/0x35
 [<ffffffff815c9a8e>] dmi_decode+0x77/0x464
 [<ffffffff810423a8>] ? vprintk+0x30b/0x33b
 [<ffffffff8131f572>] ? init_memory_mapping+0x5c7/0x5dc
 [<ffffffff812873dd>] dmi_table+0x71/0x82
 [<ffffffff815c9a17>] ? dmi_decode+0x0/0x464
 [<ffffffff8159d140>] ? early_idt_handler+0x0/0x72
 [<ffffffff815c9731>] dmi_present+0x108/0x127
 [<ffffffff815c97e0>] dmi_scan_machine+0x90/0xd9
 [<ffffffff815a4f68>] setup_arch+0x594/0x76b
 [<ffffffff81331deb>] ? _spin_lock+0xa/0xc
 [<ffffffff8159da34>] start_kernel+0x8d/0x3aa
 [<ffffffff8159d2ba>] x86_64_start_reservations+0xa5/0xa9
 [<ffffffff8159d3ae>] x86_64_start_kernel+0xcd/0xdc

RIP 0x10


Expected results:


Additional info:
/proc/cpuinfo (from virtual machine)
processor       : 0
vendor_id       : AuthenticAMD
cpu family      : 15
model           : 37
model name      : AMD Opteron(tm) Processor 250
stepping        : 1
cpu MHz         : 2395.080
cache size      : 1024 KB
fpu             : yes
fpu_exception   : yes
cpuid level     : 1
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat pse36 clflush mmx fxsr sse sse2 syscall nx mmxext fxsr_opt lm 3dnowext 3dnow
 up rep_good pni
bogomips        : 4794.13
TLB size        : 1024 4K pages
clflush size    : 64
cache_alignment : 64
address sizes   : 36 bits physical, 48 bits virtual
power management: ts fid vid ttp

Comment 1 David Carter 2008-12-06 20:50:54 UTC
Despite having used their menu to check for updates and being told there were none, there were. Latest Workstation fixed this issue.


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