All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PARAVIRT_GUEST bug? [was: Stable regression: usb-storage is stuck in 2.6.26.5]
Date: Tue, 16 Sep 2008 22:15:05 +0400	[thread overview]
Message-ID: <48CFF7A9.3070007@msgid.tls.msk.ru> (raw)
In-Reply-To: <48CFEA8C.3020703@goop.org>

Jeremy Fitzhardinge wrote:
[...]
> Michael Tokarev wrote:
>> 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? ;)
> 
> PARAVIRT_GUEST doesn't enable anything by itself; it just makes other
> config options appear.  What other config options are you enabling?
> 
> That is, what's the diff between a working and a non-working .config?

I stand corrected.  I meant to say CONFIG_PARAVIRT, not CONFIG_PARAVIRT_GUEST:

# diff -U0 config.working config.bad
--- config.working	2008-09-16 22:09:14.844324435 +0400
+++ .config.bad	2008-09-16 22:10:04.914320258 +0400
@@ -4 +4 @@
-# Tue Sep 16 21:47:31 2008
+# Tue Sep 16 22:10:04 2008
@@ -181 +181 @@
-# CONFIG_PARAVIRT is not set
+CONFIG_PARAVIRT=y

/mjt

  reply	other threads:[~2008-09-16 18:15 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   ` PARAVIRT_GUEST bug? [was: Stable regression: usb-storage is stuck in 2.6.26.5] Michael Tokarev
2008-09-16 17:19     ` Jeremy Fitzhardinge
2008-09-16 18:15       ` Michael Tokarev [this message]
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=48CFF7A9.3070007@msgid.tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --cc=jeremy@goop.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.