mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jeff Chua" <jeff.chua.linux@gmail.com>
To: "Ingo Molnar" <mingo@elte.hu>
Cc: "Jan Engelhardt" <jengelh@computergmbh.de>,
	"Thomas Gleixner" <tglx@linutronix.de>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	petr@vandrovec.name
Subject: Re: Commit f06e4ec breaks vmware
Date: Mon, 4 Feb 2008 22:01:59 +0800	[thread overview]
Message-ID: <b6a2187b0802040601s76222435t306aef2059cbbb2b@mail.gmail.com> (raw)
In-Reply-To: <20080204115144.GA17850@elte.hu>

On Feb 4, 2008 7:51 PM, Ingo Molnar <mingo@elte.hu> 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 <gcosta@redhat.com>
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.

  reply	other threads:[~2008-02-04 14:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-03 14:11 Jan Engelhardt
2008-02-04  4:19 ` Petr Vandrovec
2008-02-04 11:51 ` Ingo Molnar
2008-02-04 14:01   ` Jeff Chua [this message]
2008-02-04 14:48     ` Ingo Molnar
2008-02-04 14:53     ` Ingo Molnar
2008-02-04 15:30       ` Jeff Chua
2008-02-04 15:36         ` Ingo Molnar
2008-02-04 15:48           ` Jeff Chua
2008-02-05  1:31           ` Zachary Amsden
2008-02-04 14:58   ` Jan Engelhardt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=b6a2187b0802040601s76222435t306aef2059cbbb2b@mail.gmail.com \
    --to=jeff.chua.linux@gmail.com \
    --cc=jengelh@computergmbh.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=petr@vandrovec.name \
    --cc=tglx@linutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®