public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Drake <dsd@gentoo.org>
To: zach@vmware.com, gentoo@thebacks.co.uk
Cc: kernel@gentoo.org, linux kernel <linux-kernel@vger.kernel.org>,
	"Dyks, Axel (XL)" <xl@xlsigned.net>
Subject: VMI not initializing in certain configurations
Date: Wed, 10 Dec 2008 23:32:49 +0000	[thread overview]
Message-ID: <494051A1.6090906@gentoo.org> (raw)

Hi Zach,

Thanks for your help on the VMI-related 2.6.27.x regression. I'm hoping
to now pick your mind on a similar but unrelated issue:

Norman has found that with certain kernel configurations, 2.6.27 (plain,
as released by Linus) does not initialize VMI properly, witnessed as
missing initialization messages in the kernel logs. Other configurations
work fine. These are the messages that go missing:

    VMI: Found VMware, Inc. Hypervisor OPROM, API version 3.0, ROM 
version 1.0
    vmi: registering clock event vmi-timer. mult=12582912 shift=22
    Booting paravirtualized kernel on vmi

Do you have any immediate ideas as to what the responsible config 
option(s) might be? It may well be a configuration error, but if that's 
the case then perhaps we could produce a CONFIG_VMI documentation patch 
for that.

Here is the bug report:
https://bugs.gentoo.org/show_bug.cgi?id=250094

Here is the working config:
https://bugs.gentoo.org/attachment.cgi?id=174901&action=view

and here is the broken config:
https://bugs.gentoo.org/attachment.cgi?id=174870&action=view

If you don't have any immediate ideas, say so and hopefully Norman will 
then be able to spend some time "bisecting" the config differences.

cheers
Daniel


             reply	other threads:[~2008-12-10 23:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-10 23:32 Daniel Drake [this message]
2008-12-11  5:34 ` VMI not initializing in certain configurations Zachary Amsden

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=494051A1.6090906@gentoo.org \
    --to=dsd@gentoo.org \
    --cc=gentoo@thebacks.co.uk \
    --cc=kernel@gentoo.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xl@xlsigned.net \
    --cc=zach@vmware.com \
    /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