From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: "Pasi Kärkkäinen" <pasik@iki.fi>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Andi Reinbrech <andi.reinbrech@darwinistic.com>
Subject: Re: Kernel 3 Crashes on 4.2 unstable
Date: Tue, 2 Aug 2011 13:23:05 -0400 [thread overview]
Message-ID: <20110802172304.GX11133@dumpdata.com> (raw)
In-Reply-To: <20110802171644.GJ32373@reaktio.net>
On Tue, Aug 02, 2011 at 08:16:44PM +0300, Pasi Kärkkäinen wrote:
> On Tue, Aug 02, 2011 at 12:25:32PM -0400, Konrad Rzeszutek Wilk wrote:
> > >
> > > Will dig a bit deeper. I saw that page also has very detailed
> > > instructions for a custom kernel, I will try and tune a little and
> > > compile a few versions. I have a feeling it may very well be
> > > graphics related. Will feed back here when I have details.
> > >
> > > I have extensive C and hardware/embedded knowledge and would love to
> > > get a bit more involved in Xen. Hopefully I can contribute, however
> > > small, here and there :-)
> >
> > Awesome. Not sure if the 'earlyprintk=xenboot' is mentioned in the Wiki but
> > that one is quite useful.
>
> Hmm.. what's the difference between "earlyprintk=xen" and "earlyprintk=xenboot" ?
It has the same effect:
#ifdef CONFIG_HVC_XEN
if (!strncmp(buf, "xen", 3))
early_console_register(&xenboot_console, keep);
#endif
Just doing 'earlyprintk=xen' is enough. Not sure why I actually have 'xenboot' ..hmm
>
> -- Pasi
prev parent reply other threads:[~2011-08-02 17:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-31 19:07 Kernel 3 Crashes on 4.2 unstable Andi Reinbrech
2011-08-01 1:45 ` Pasi Kärkkäinen
2011-08-01 18:59 ` Andi Reinbrech
2011-08-02 16:25 ` Konrad Rzeszutek Wilk
2011-08-02 17:16 ` Pasi Kärkkäinen
2011-08-02 17:23 ` Konrad Rzeszutek Wilk [this message]
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=20110802172304.GX11133@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=andi.reinbrech@darwinistic.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 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.