From: Michael Paesold <mpaesold@gmx.at>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: Don Zickus <dzickus@redhat.com>,
xen-devel Devel <xen-devel@lists.xensource.com>,
Jan Beulich <JBeulich@novell.com>
Subject: Re: Serial console problem with Xen 3.0
Date: Sat, 08 Apr 2006 14:44:09 +0200 [thread overview]
Message-ID: <4437B019.2000004@gmx.at> (raw)
In-Reply-To: <41f19219621fc0c5bcf2815d863d14a7@cl.cam.ac.uk>
Keir Fraser wrote:
>
> On 7 Apr 2006, at 17:51, Keir Fraser wrote:
>
>>> I just wanted to confirm that pnpacpi=off solves my problem and give
>>> me full access over the serial console.
>>>
>>> Should this get an issue in the bugtracker?
>>
>> Yes, it's probably a good thing to gather all this stuff in one place.
>> By the way, I have some fixes already for the IO-APIC checking routine
>> that I mentioned. We're just going to give it a shakedown in Cambridge
>> before putting it in the public repository.
>
> I can confirm that my patch at least fixes the pnpacpi problem that
> you've been seeing. I've also enabled CONFIG_PNP_ACPI by default in our
> -xen0 and -xen defconfig files, so we should get wider feedback on
> issues relating to that config option now.
Great, I am going to pull from xen-unstable after the weekend and test the
changes.
Thanks to Don and Stephen for the "pnpacpi=off" hint.
Best Regards,
Michael Paesold
next prev parent reply other threads:[~2006-04-08 12:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-05 4:40 Serial console problem with Xen 3.0 Amitayu Das
2006-04-07 13:27 ` Stephen C. Tweedie
2006-04-07 13:59 ` Michael Paesold
2006-04-07 14:44 ` Don Zickus
2006-04-07 15:31 ` Keir Fraser
2006-04-07 16:17 ` Michael Paesold
2006-04-07 16:51 ` Keir Fraser
2006-04-08 11:15 ` Keir Fraser
2006-04-08 12:44 ` Michael Paesold [this message]
2006-04-11 15:38 ` Ryan
2006-04-11 15:42 ` Keir Fraser
2006-04-11 16:00 ` Ryan
2006-04-11 16:06 ` Keir Fraser
2006-04-07 14:47 ` Amitayu Das
2006-04-07 17:54 ` Stephen C. Tweedie
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=4437B019.2000004@gmx.at \
--to=mpaesold@gmx.at \
--cc=JBeulich@novell.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=dzickus@redhat.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.