From: Dan Magenheimer <dan.magenheimer@oracle.com>
To: "\"Pasi Kärkkäinen\"" <pasik@iki.fi>
Cc: xen-devel@lists.xensource.com
Subject: RE: need known working 64-bit upstream kernel config file for PV guest
Date: Fri, 14 May 2010 09:58:47 -0700 (PDT) [thread overview]
Message-ID: <fd6d1882-5846-47bf-a2e1-6e77d458b0f4@default> (raw)
In-Reply-To: <abca62c2-7d9e-475d-bb18-0f60e4b5ecd3@default>
> But I hadn't noticed the problem in the earlier part of
> the boot before you pointed it out.
> I'm beginning to suspect that there is a bug in 64-bit
> upstream kernels that is exposed in nash (the lightweight
> shell that gets bundled in a RedHat initrd). If so,
> it will be very difficult to track down, though clearly
> it is fixed in one of the many Fedora kernel patches.
> So I am going to give up on 64-bit upstream kernels
> for now so I can get some other things done and
> come back to this later.
To add one more very interesting piece of data,
booting a 2.6.32 32-bit kernel.org kernel in a PV
guest works, while booting a 2.6.32.13 32-bit
kernel.org kernel doesn't... same config file!
And the failure looks very similar to the one
I've been seeing on several x86_64 kernel.org
kernels.
I'll confirm that I can reproduce this, and then
post as a separate thread.
next prev parent reply other threads:[~2010-05-14 16:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-13 19:34 need known working 64-bit upstream kernel config file for PV guest Dan Magenheimer
2010-05-13 20:30 ` Pasi Kärkkäinen
2010-05-13 20:37 ` Pasi Kärkkäinen
2010-05-13 20:49 ` Dan Magenheimer
2010-05-13 20:57 ` Pasi Kärkkäinen
2010-05-13 23:03 ` Dan Magenheimer
2010-05-14 5:46 ` Pasi Kärkkäinen
2010-05-14 13:16 ` Dan Magenheimer
2010-05-14 16:58 ` Dan Magenheimer [this message]
2010-05-14 17:42 ` Pasi Kärkkäinen
2010-05-14 18:10 ` Dan Magenheimer
2010-05-21 22:15 ` Dan Magenheimer
2010-05-24 10:27 ` Ian Jackson
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=fd6d1882-5846-47bf-a2e1-6e77d458b0f4@default \
--to=dan.magenheimer@oracle.com \
--cc=pasik@iki.fi \
--cc=xen-devel@lists.xensource.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).