Bug#600064: linux-image-2.6.32-5-xen-amd64: machine reboots during dom0 bootup if Intel TXT enabled
On Thu, 2010-10-14 at 18:21 +0200, Linus van Geuns wrote:
> On Thu, Oct 14, 2010 at 4:58 PM, Ian Campbell <firstname.lastname@example.org> wrote:
> > On Wed, 2010-10-13 at 12:35 +0200, Linus van Geuns wrote:
> >> Package: linux-2.6
> >> Version: 2.6.32-23
> >> Severity: important
> >> If Intel TXT is enabled in BIOS settings, machine reboots during dom0 kernel startup when used as dom0 with xen-hypervisor-4.0-amd64.
> >> Displays message "Waiting for /dev to be fully populated..", waits some seconds and just reboots.
> >> After disabling Intel TXT, I have not encountered any unexpected reboots so far.. :)
> > Does Debian even support TXT boot in the first place?
> Im talking about the BIOS option "Intel TXT", not about a real
> "trusted" boot environment starting Debian/Xen.
I don't know much (or indeed anything) about TXT but I think I would
recommend leaving the BIOS option turned off unless you have a suitable
> > Does this also happen on bare metal, with either the -xen-amd64 or plain
> > -amd64 kernels?
> > If you add "noreboot" to your hypervisor command line do you get the
> > opportunity to observe any error messages which you are missing due to
> > the reboot?
> There is one additional "error" message after the message "Waiting for
> /Dev to be fully polpulated...":
> "Driver 'pcspkr' is already registered, aborting..". ;-)
> Unable to locate IOAPIC for GSI 2 and 9 is reported as the first
> messages from dom0 kernel, but those messages are also present when
> booting w/o TXT = Enabled setting.
> When I remove the 'quiet' kernel parameter, the mast messages seen are
> sometimes from DRM and from USB otherwise.
> Regards, Linus (no, not that one :-))
Current Noise: Testament - Leave Me Forever
Never try to outstubborn a cat.
-- Lazarus Long, "Time Enough for Love"