Re: 2.6.35 hangs on early boot in KVM

From: Yinghai Lu
Date: Wed Aug 04 2010 - 05:06:22 EST


On 08/04/2010 01:18 AM, Tvrtko Ursulin wrote:
> On Tuesday 03 Aug 2010 21:57:48 Yinghai Lu wrote:
>> On Tue, Aug 3, 2010 at 8:59 AM, Tvrtko Ursulin
>>
>> <tvrtko.ursulin@xxxxxxxxxx> wrote:
>>> On Tuesday 03 Aug 2010 16:17:20 Tvrtko Ursulin wrote:
>>>> On Tuesday 03 Aug 2010 15:57:03 Tvrtko Ursulin wrote:
>>>>> On Tuesday 03 Aug 2010 15:51:08 Avi Kivity wrote:
>>>>>> On 08/03/2010 12:28 PM, Tvrtko Ursulin wrote:
>>>>>>> I have basically built 2.6.35 with make oldconfig from a working
>>>>>>> 2.6.34. Latter works fine in kvm while 2.6.35 hangs very early. I
>>>>>>> see nothing after grub (have early printk and verbose bootup
>>>>>>> enabled), just a blinking VGA cursor and CPU at 100%.
>>>>>>
>>>>>> Please copy kvm@xxxxxxxxxxxxxxx on kvm issues.
>>>>>>
>>>>>>> CONFIG_PRINTK_TIME=y
>>>>>>
>>>>>> Try disabling this as a workaround.
>>>>>
>>>>> I am in the middle of a bisect run with five builds left to go,
>>>>> currently I have:
>>>>>
>>>>> bad 537b60d17894b7c19a6060feae40299d7109d6e7
>>>>> good 93c9d7f60c0cb7715890b1f9e159da6f4d1f5a65
>>>>
>>>> Bisect is looking good, narrowed it to ten revisions, but I am not sure
>>>> to make it to the end today:
>>>>
>>>> bad cb41838bbc4403f7270a94b93a9a0d9fc9c2e7ea
>>>> good 41d59102e146a4423a490b8eca68a5860af4fe1c
>>>
>>> Bisect points the finger to "x86, ioapic: In mpparse use
>>> mp_register_ioapic" (cf7500c0ea133d66f8449d86392d83f840102632), so I am
>>> copying Eric. No idea whether this commit is solely to blame or it is a
>>> combined interaction with KVM, but I am sure you guys will know.
>>>
>>> If you want me to test something else please shout.
>>
>> please try attached patch, to see if it help.
>
> No luck (no visible difference, no output on VGA or serial console). (Btw
> there is a typo in pin_2_irq_leagcy so that you do not push it directly).

can you try current tip with
earlyprintk=ttyS0,115200 or console=uart8250,io,0x3f8,115200?

Thanks

Yinghai
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/