From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: "Nadolski, Ed" <Ed.Nadolski@lsi.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
"Xen-devel@lists.xensource.com" <Xen-devel@lists.xensource.com>
Subject: Re: dom0 hang in xen-4.0.0-rc5 - possible acpi issue? [WAS: Using xen-unstable, dom0 hangs during boot]
Date: Tue, 16 Mar 2010 08:52:34 -0400 [thread overview]
Message-ID: <20100316125233.GB25340@phenom.dumpdata.com> (raw)
In-Reply-To: <8115AF16522A3D4383C1FF753036713F9B3222B2@cosmail01.lsi.com>
>
> Everything seems to work if I specify acpi_skip_timer_override in grub.conf. I think I may be seeing the following issue:
>
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/272247?comments=all
> System freezes during boot, unless I hold a key down
> Ubuntu >> "linux" package >> Bugs >> Bug #272247
>
> > The problem behind this seems not limited to a certain controller
> > chip, but related to ACPI BIOS definitions. The IRQ0 override
> > defines to which interrupt number the timer interrupt is supposed
> > to be routed. Most BIOS define a route to IRQ2, so the timer
> > source (hpet in most cases) has to deliver an IRQ2 whenever a
> > timer expires. The problem is, that this is not always correct
> > (either hpet does not use IRQ2 or IRQ2 is not enabled on the
> > chipset). So as soon as all CPUs go into sleep there is no
> > timer irq to wake them up. To solve this automatically one
> > would need documentation about the chipsets pci config space
> > which is often secret.
Do you have the MCP67 chipset?
> >
> > Workaround for affected systems: Use of "acpi_skip_timer_override"
> > as kernel command line option. Sometimes "nohpet" or "acpi=noirq"
> > have been reported to work, too."
>
>
> Is there a way that I can verify that this is the issue?
Yes. You need to boot the pv-ops under bare-metal so that we can be sure
this is not a Xen hypervisor problem, but the pv-ops kernel having an
issue.
Please provide the serial output with debugging turned on (debug initcall_debug
apic=debug).
Thanks.
next prev parent reply other threads:[~2010-03-16 12:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-25 22:18 Using xen-unstable, dom0 hangs during boot Nadolski, Ed
2010-02-25 23:11 ` Jeremy Fitzhardinge
2010-02-26 13:33 ` Nadolski, Ed
2010-02-26 14:46 ` Pasi Kärkkäinen
2010-02-26 20:40 ` Nadolski, Ed
2010-02-28 23:47 ` Nadolski, Ed
2010-03-01 15:10 ` Konrad Rzeszutek Wilk
2010-03-02 19:23 ` dom0 hang in xen-4.0.0-rc5 - possible acpi issue? [WAS: Using xen-unstable, dom0 hangs during boot] Nadolski, Ed
2010-03-03 18:18 ` Konrad Rzeszutek Wilk
2010-03-15 14:59 ` Nadolski, Ed
2010-03-16 12:52 ` Konrad Rzeszutek Wilk [this message]
2010-03-17 16:34 ` Nadolski, Ed
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=20100316125233.GB25340@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=Ed.Nadolski@lsi.com \
--cc=Xen-devel@lists.xensource.com \
--cc=jeremy@goop.org \
/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.