From: George Dunlap <George.Dunlap@eu.citrix.com>
To: Jan Beulich <JBeulich@novell.com>
Cc: Sander Eikelenboom <linux@eikelenboom.it>,
Yunhong Jiang <yunhong.jiang@intel.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Crash during boot in Debian lenny default dom0 kernel (2.6.26-2-xen-686)
Date: Thu, 25 Feb 2010 11:46:21 +0000 [thread overview]
Message-ID: <de76405a1002250346q32cf093i58429407ccfb5f32@mail.gmail.com> (raw)
In-Reply-To: <4B8665680200007800031406@vpn.id2.novell.com>
I'm looking at the debian source package for this kernel to see if I
can sort out where it got the header from.
Given that this is already in a major distribution, is there any way
we can fail gracefully if someone's running this kernel? I'm not
familiar enough with the MSI to know if this is possible, or what a
good set of "sanity checks" would be for failing the hypercall.
-George
On Thu, Feb 25, 2010 at 10:56 AM, Jan Beulich <JBeulich@novell.com> wrote:
>>>> George Dunlap <George.Dunlap@eu.citrix.com> 25.02.10 11:48 >>>
>>Is it possible that there's actually a bug in the compat code, and
>>that table_base actually *was* set to (uint32_t)1? If a reasonable
>>number for table_base is "1", giving it 64 bits in the structure would
>>seem a bit like overkill...
>
> "1" definitely is not a reasonable value here. And it's also not the
> compat code I'm sure - it is the kernel using a bad structure definition.
>
> Jan
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
next prev parent reply other threads:[~2010-02-25 11:46 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-24 18:47 Crash during boot in Debian lenny default dom0 kernel (2.6.26-2-xen-686) George Dunlap
2010-02-24 19:08 ` Sander Eikelenboom
2010-02-24 20:20 ` Pasi Kärkkäinen
2010-02-24 23:57 ` George Dunlap
2010-02-25 6:50 ` Jiang, Yunhong
2010-02-25 10:48 ` George Dunlap
2010-02-25 10:56 ` Jan Beulich
2010-02-25 11:46 ` George Dunlap [this message]
2010-02-25 12:13 ` George Dunlap
2010-02-25 13:07 ` Jan Beulich
2010-02-25 13:19 ` Sander Eikelenboom
2010-02-25 13:24 ` Pasi Kärkkäinen
2010-02-25 13:43 ` Jan Beulich
2010-02-25 14:05 ` Pasi Kärkkäinen
2010-02-25 13:28 ` George Dunlap
2010-02-26 11:05 ` George Dunlap
2010-02-26 11:14 ` Sander Eikelenboom
2010-02-26 11:21 ` George Dunlap
2010-02-26 12:04 ` Pasi Kärkkäinen
2010-02-26 12:26 ` Sander Eikelenboom
2010-02-26 1:42 ` Jiang, Yunhong
2010-02-26 10:55 ` George Dunlap
2010-02-26 10:56 ` George Dunlap
2010-02-25 13:10 ` Jan Beulich
2010-02-25 9:16 ` Jan Beulich
2010-02-25 9:28 ` Jiang, Yunhong
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=de76405a1002250346q32cf093i58429407ccfb5f32@mail.gmail.com \
--to=george.dunlap@eu.citrix.com \
--cc=JBeulich@novell.com \
--cc=linux@eikelenboom.it \
--cc=xen-devel@lists.xensource.com \
--cc=yunhong.jiang@intel.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;
as well as URLs for NNTP newsgroup(s).