On Feb 4, 2008 7:51 PM, Ingo Molnar <[EMAIL PROTECTED]> wrote:
> > sad to say, but f06e4ec... breaks booting the kernel in vmware
> > commit f06e4ec1c15691b0cfd2397ae32214fa36c90d71
I had the same problem. But I bisect down to a earlier commit.
Reverting this patch, and I can boot up using vmware.
commit 8d947344c47a40626730bb80d136d8daac9f2060
Author: Glauber de Oliveira Costa <[EMAIL PROTECTED]>
Date: Wed Jan 30 13:31:12 2008 +0100
x86: change write_idt_entry signature
> could you send us the /proc/cpuinfo data of the guest CPU?
Here's my guest's /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 14
model name : Intel(R) Core(TM) Duo CPU L2500 @ 1.83GHz
stepping : 8
cpu MHz : 1828.645
cache size : 2048 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 10
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
mca cmov pat clflush dts acpi mmx fxsr sse sse2 ss constant_tsc up
arch_perfmon pebs bts pni
bogomips : 3546.54
clflush size : 64
> if latest -git still fails, does the patch below solve the problem?
Doesn't seem to work for me.
Thanks,
Jeff.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
