public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: linux-kernel@vger.kernel.org
Subject: PARAVIRT_GUEST bug? [was: Stable regression: usb-storage is stuck in 2.6.26.5]
Date: Tue, 16 Sep 2008 12:11:49 +0400	[thread overview]
Message-ID: <48CF6A45.3010204@msgid.tls.msk.ru> (raw)
In-Reply-To: <48CBB626.4050300@msgid.tls.msk.ru>

Michael Tokarev wrote:

[usb-storage hangs on asus M2NPV-VM (nVidia GeForce 6150/nForce 430)
  motherboard with latest bios]

> Ok, it turned out to be pretty.. interesting.
> 
> It's not a regression within -stable kernel series.  The problem
> happens when BOTH are true:
> 
>   - using latest BIOS for this mobo (1401), AND
>   - enabling KVM_GUEST in kernel.
> 
> The only difference in my kernel config between .1 and .5 was
> to enable KVM_GUEST and KVM_CLOCK, and also I2C_HELPER_AUTO
> which was added by kernel update.
> 
> Going with previous BIOS (1201) OR disabling PARAVIRT_GUEST
> fixes the problem.  I'll try to figure out which config
> option is at problem here.

After seeing similar situation on another motherboard, I
become curious.

Here's the result:  M3A78-EM motherboard (also from Asus),
AMD780G/SB700 etc.  Updating to one of the latest bios
makes the system unbootable.  Kernel hangs on boot right
after displaying

  SLUB: Genslabs=12, HWalign=64, Order=0-1, MinObjects=4, CPUs=2, Nodes=1

Reverting to the older BIOS or disabling PARAVIRT_GUEST in kernel
fixes this (turning off KVM_GUEST isn't enough), and kernel happily
boots further, with next line being

  hpet clockevent registered
  ...

Reportedly, another Asus motherboard (M2N-SLI DELUXE) also hangs
with new BIOS and KVM_GUEST optimizations turned on, but not on
older BIOS.

So it's quite.. funny.  At least SOME latest BIOSes from Asustec,
together with PARAVIRT_GUEST, -- a problem.  Don't do either of
those, and it's all ok.

The question is if Asus introduced the same bug in quite.. some
of their recent BIOSes, or PARAVIRT_GUEST code is somehow buggy
and the bug is exposed by new BIOS code.

Any hints on this? ;)

Thanks!

/mjt

  reply	other threads:[~2008-09-16  8:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-13 12:16 Stable regression: usb-storage is stuck in 2.6.26.5 Michael Tokarev
2008-09-13 12:46 ` Michael Tokarev
2008-09-16  8:11   ` Michael Tokarev [this message]
2008-09-16 17:19     ` PARAVIRT_GUEST bug? [was: Stable regression: usb-storage is stuck in 2.6.26.5] Jeremy Fitzhardinge
2008-09-16 18:15       ` Michael Tokarev
2008-09-18 10:07     ` Michael Tokarev
2008-09-18 19:27       ` Jeremy Fitzhardinge
2008-09-23 17:54         ` Michael Tokarev

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=48CF6A45.3010204@msgid.tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --cc=linux-kernel@vger.kernel.org \
    /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