From: Chris Bainbridge <chris.bainbridge@gmail.com>
To: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: can't boot dom0
Date: Wed, 5 Oct 2005 19:32:17 +0100 [thread overview]
Message-ID: <623652d50510051132t2399d058m@mail.gmail.com> (raw)
In-Reply-To: <983B408465C04C49B0344D51FA21C7553E74FC@trudi.bpmmail.local>
On 05/10/05, Stephan Böni <boeni@bpm.ch> wrote:
> Well, i have the same problem with scsi and fc devices. It seams that
> this release is very very buggy at the moment.
Argghhhhhhhhhh! What is going on? If I enable smp it works! Using a
uniprocessor p4 with hyperthreading... huh? My best guess.. smp
enables some kind of different interrupt handling, and the cpu is
stuck waiting for an interrupt when probing the ata port? hmmm. Let's
test.
uniprocessor w/wo msi: fails
uniprocessor w acpi: fails
uniprocessor w msi+acpi+preempt: fails
uniprocessor+apic+ioapic+msi: can't compile :
drivers/built-in.o(.text+0x7022): In function `get_new_vector'::
undefined reference to `interrupt
uniprocessor+apic+ioapic: ok
uniprocessor+apic: fails
Ah-ha! So it looks like you need CONFIG_X86_UP_IOAPIC or SMP to get it working.
Bug 1) xen with non apic kernel is broken
Bug 2) compile error with CONFIG_PCI_MSI
next prev parent reply other threads:[~2005-10-05 18:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-05 15:15 AW: can't boot dom0 Stephan Böni
2005-10-05 18:32 ` Chris Bainbridge [this message]
2005-10-05 21:56 ` Keir Fraser
2005-10-06 7:58 ` Chris Bainbridge
2005-10-06 9:15 ` Keir Fraser
-- strict thread matches above, loose matches on Subject: below --
2005-10-05 14:55 Chris Bainbridge
2005-10-05 15:13 ` Chris Bainbridge
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=623652d50510051132t2399d058m@mail.gmail.com \
--to=chris.bainbridge@gmail.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.