From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Bainbridge Subject: Re: can't boot dom0 Date: Wed, 5 Oct 2005 19:32:17 +0100 Message-ID: <623652d50510051132t2399d058m@mail.gmail.com> References: <983B408465C04C49B0344D51FA21C7553E74FC@trudi.bpmmail.local> Reply-To: Chris Bainbridge Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <983B408465C04C49B0344D51FA21C7553E74FC@trudi.bpmmail.local> Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel List-Id: xen-devel@lists.xenproject.org On 05/10/05, Stephan B=F6ni 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 work= ing. Bug 1) xen with non apic kernel is broken Bug 2) compile error with CONFIG_PCI_MSI