Re: Re: pv_ops dom0 USB fixed

[Jeremy Fitzhardinge <jeremy@goop.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