From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: Re: pv_ops dom0 USB fixed Date: Thu, 11 Dec 2008 10:17:41 -0800 Message-ID: <49415945.3030508@goop.org> References: <4940210C.1060401@goop.org> <1e16a9ed0812101448i52a39946o528c74effa2690ab@mail.gmail.com> <4940C98D.6070004@goop.org> <1e16a9ed0812110850odff8f56h836b7187ad0c64b0@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1e16a9ed0812110850odff8f56h836b7187ad0c64b0@mail.gmail.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: deshantm@gmail.com Cc: Xen-devel , Aviv Grafi List-Id: xen-devel@lists.xenproject.org Todd Deshane wrote: >> Well, for a start, disable MSI for now (pci=nomsi on the kernel command >> line). I haven't done any MSI support yet. >> >> In the nosmp boot, something seems amiss with interrupt routing. nomsi may >> help there as well, but I'll need to have a closer look at the code to work >> out what's really going wrong here. Hm, its probably: >> [ 0.000000] ACPI: Skipping IOAPIC probe due to 'noapic' option. >> >> I guess nosmp implies noapic? Anyway, we don't do well without ioapics at >> present... >> >> J >> >> > The pci=nomsi helped a lot. > > I have booting (at least almost) > > Again two logs attached. This time the without nosmp does better. > > Gets to a checking battery state line then it seems to stop. > What normally happens next? Looks like its pretty close to the end of the boot sequence; is that where it would normally print the login prompt? Is the machine on the network at that point? Can you log in remotely? > The nosmp does the same as last time, a initramfs prompt followed by > ATA trying... > Yes, that's going to be non-functional; none of the hardware interrupts have been set up properly, so none of the drivers are going to see the interrupts they're expecting. > I will try to disable some of the init scripts or try single user mode to > see if I can get a normal prompt. > I think it might just be a matter of getting your devices set up properly or something. > Might not have much time to work on it over the next couple days... > Thanks for testing this. Your logs have lots of valuable stuff in them. J