From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Sander Eikelenboom <linux@eikelenboom.it>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Keir Fraser <keir.fraser@eu.citrix.com>,
Sisu Xi <xisisu@gmail.com>
Subject: Re: problem using compiled kernel -- Sisu
Date: Mon, 2 Aug 2010 11:29:34 -0400 [thread overview]
Message-ID: <20100802152934.GA9122@phenom.dumpdata.com> (raw)
In-Reply-To: <4C56E32D.4020009@goop.org>
On Mon, Aug 02, 2010 at 08:24:29AM -0700, Jeremy Fitzhardinge wrote:
> On 08/02/2010 07:49 AM, Konrad Rzeszutek Wilk wrote:
> >On Fri, Jul 30, 2010 at 04:20:06PM -0500, Sisu Xi wrote:
> >>Hi, all:
> >>
> >>Sorry to trouble you again. But I really tried very hard on installing
> >>xen on my machine. I reformatted my whole disk, install Ubuntu 10.04,
> >>and compile Xen and Kernel from the source code.
> >Ok.. why? Why didn't you just re-build?
> >
> >>it gives out info this time, saying something about
> >>BUG: scheduling while atomic: rsyslogd/565/0x10000001
> >>kernel BUG at arch/x86/mm/highmem_32.c:45!
> >The .config that Pasi pointed has this:
> >
> ># CONFIG_HIGHPTE is not set
> >
> >That is what you need in your .config file.
>
> Why? That shouldn't be necessary, and is disabled at runtime even
> if you enable it.
Didn't we have some trouble with this?
next prev parent reply other threads:[~2010-08-02 15:29 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-26 21:57 problem using compiled kernel -- Sisu Sisu Xi
2010-07-27 2:02 ` Jeremy Fitzhardinge
2010-07-27 2:13 ` Sisu Xi
[not found] ` <AANLkTimOUJLndxscJW5CehXYYe0gWUFqsc8PSxewFpAM@mail.gmail.com>
2010-07-27 3:05 ` Jeremy Fitzhardinge
2010-07-27 3:08 ` Sisu Xi
[not found] ` <AANLkTimoL+A=nX7+zqY6+LVuzgNKGrW8eyaJTtS_NqFK@mail.gmail.com>
2010-07-27 17:05 ` Jeremy Fitzhardinge
2010-07-27 17:52 ` Sisu Xi
2010-07-27 19:01 ` Jeremy Fitzhardinge
2010-07-27 19:19 ` Sisu Xi
2010-07-27 20:23 ` Konrad Rzeszutek Wilk
2010-07-27 20:37 ` Pasi Kärkkäinen
2010-07-27 21:09 ` Keir Fraser
2010-07-27 21:59 ` Sander Eikelenboom
2010-07-28 7:49 ` Keir Fraser
2010-07-28 16:53 ` Sisu Xi
2010-07-28 17:49 ` Konrad Rzeszutek Wilk
2010-07-28 22:14 ` Sisu Xi
2010-07-30 0:29 ` Sisu Xi
2010-07-30 0:35 ` Jeremy Fitzhardinge
2010-07-30 0:40 ` Sisu Xi
2010-07-30 17:47 ` Sisu Xi
2010-07-30 21:20 ` Sisu Xi
2010-07-30 21:21 ` Sisu Xi
2010-07-30 21:25 ` Sisu Xi
2010-08-02 16:54 ` Jeremy Fitzhardinge
2010-08-02 18:02 ` Sisu Xi
2010-08-03 3:25 ` Sisu Xi
2010-08-03 6:23 ` Keir Fraser
2010-08-03 17:01 ` Jeremy Fitzhardinge
2010-08-04 14:24 ` Konrad Rzeszutek Wilk
2010-08-04 17:55 ` Sisu Xi
2010-08-04 19:06 ` Konrad Rzeszutek Wilk
2010-08-04 19:12 ` Sisu Xi
2010-08-02 14:49 ` Konrad Rzeszutek Wilk
2010-08-02 15:24 ` Jeremy Fitzhardinge
2010-08-02 15:29 ` Konrad Rzeszutek Wilk [this message]
2010-08-02 15:37 ` Jeremy Fitzhardinge
2010-08-02 15:48 ` Sisu Xi
2010-08-02 16:02 ` Konrad Rzeszutek Wilk
2010-08-02 14:44 ` Konrad Rzeszutek Wilk
2010-08-02 15:58 ` Jean-Yves Landry
2010-08-02 13:21 ` Sander Eikelenboom
2010-08-10 7:36 ` Keir Fraser
2010-08-10 9:57 ` Xen Grub2 testing needed Pasi Kärkkäinen
2010-08-10 14:27 ` problem using compiled kernel -- Sisu Sander Eikelenboom
2010-08-10 14:41 ` Keir Fraser
2010-07-28 4:51 ` Mike Viau
2010-07-27 6:09 ` Pasi Kärkkäinen
2010-07-27 16:26 ` Sisu Xi
2010-07-27 20:27 ` Pasi Kärkkäinen
2010-08-03 11:04 ` Stefan Kuhne
2010-08-03 20:37 ` (XEN) d0:v0: unhandled page fault (ec=0009) Stefan Kuhne
2010-08-03 22:15 ` Jeremy Fitzhardinge
2010-08-03 22:22 ` Stefan Kuhne
2010-08-03 22:37 ` Jeremy Fitzhardinge
2010-08-04 5:58 ` Stefan Kuhne
2010-08-04 8:45 ` Stefan Kuhne
2010-08-04 14:09 ` Konrad Rzeszutek Wilk
2010-08-04 15:46 ` Stefan Kuhne
2010-08-04 20:12 ` Stefan Kuhne
2010-08-06 14:49 ` Konrad Rzeszutek Wilk
2010-08-06 14:50 ` Konrad Rzeszutek Wilk
2010-08-06 20:12 ` Stefan Kuhne
2010-08-09 4:41 ` Konrad Rzeszutek Wilk
2010-08-09 7:06 ` Stefan Kuhne
2010-08-10 8:15 ` Stefan Kuhne
2010-08-13 15:24 ` Stefan Kuhne
2010-08-06 9:10 ` Stefan Kuhne
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=20100802152934.GA9122@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=jeremy@goop.org \
--cc=keir.fraser@eu.citrix.com \
--cc=linux@eikelenboom.it \
--cc=xen-devel@lists.xensource.com \
--cc=xisisu@gmail.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).