From: "Jan Beulich" <jbeulich@novell.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>,
Stefan Berger <stefanb@us.ibm.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: No console with xen-3.2
Date: Tue, 13 Nov 2007 17:17:53 +0000 [thread overview]
Message-ID: <4739EA51.76E4.0078.0@novell.com> (raw)
In-Reply-To: <C35F8210.1855A%Keir.Fraser@cl.cam.ac.uk>
>>> Keir Fraser <Keir.Fraser@cl.cam.ac.uk> 13.11.07 17:32 >>>
>Changesets 16215, 16156, 16147 have to be suspected. Could one of you try
>backing those out one by one (cumulatively, not individually) and see if Xen
>springs back to life? My fear is that shifting the location of the boot
>trampoline has screwed us on some boxes. But then again I have no reason to
>think that 0x8c000 isn't a safe place to stick the trampoline...
16215 appears to be innocent - it's sufficiently isolated for reverting alone.
The others I'll try tomorrow, unless Stefan beats me.
In any case - setting a video mode works, so the problem is likely on the
return path from real mode.
Jan
next prev parent reply other threads:[~2007-11-13 17:17 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-13 13:40 No console with xen-3.2 Chuck Short
2007-11-13 15:10 ` Keir Fraser
2007-11-13 15:18 ` Chuck Short
2007-11-13 15:35 ` Keir Fraser
2007-11-13 15:40 ` Chuck Short
2007-11-13 16:15 ` Keir Fraser
2007-11-13 16:33 ` Chuck Short
2007-11-13 15:54 ` Stefan Berger
2007-11-13 15:55 ` Chuck Short
2007-11-13 16:15 ` Jan Beulich
2007-11-13 16:32 ` Keir Fraser
2007-11-13 17:17 ` Jan Beulich [this message]
2007-11-13 18:14 ` Stefan Berger
2007-11-13 18:21 ` Keir Fraser
2007-11-13 19:01 ` Stefan Berger
2007-11-13 19:14 ` Keir Fraser
2007-11-13 19:26 ` Stefan Berger
2007-11-13 19:33 ` Keir Fraser
2007-11-13 20:12 ` Keir Fraser
2007-11-13 20:30 ` Stefan Berger
2007-11-13 20:44 ` Chuck Short
2007-11-14 9:20 ` Jan Beulich
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=4739EA51.76E4.0078.0@novell.com \
--to=jbeulich@novell.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=stefanb@us.ibm.com \
--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.