From: Yinghai Lu <yinghai@kernel.org>
To: Tvrtko Ursulin <tvrtko.ursulin@sophos.com>
Cc: Avi Kivity <avi@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
KVM list <kvm@vger.kernel.org>,
"Eric W. Biederman" <ebiederm@xmission.com>
Subject: Re: 2.6.35 hangs on early boot in KVM
Date: Wed, 04 Aug 2010 02:05:36 -0700 [thread overview]
Message-ID: <4C592D60.5050309@kernel.org> (raw)
In-Reply-To: <201008040918.58318.tvrtko.ursulin@sophos.com>
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@sophos.com> 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@vger.kernel.org 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
next prev parent reply other threads:[~2010-08-04 9:06 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-03 9:28 2.6.35 hangs on early boot in KVM Tvrtko Ursulin
2010-08-03 9:45 ` Tvrtko Ursulin
2010-08-03 13:53 ` Tvrtko Ursulin
2010-08-03 14:51 ` Avi Kivity
2010-08-03 14:57 ` Tvrtko Ursulin
2010-08-03 15:17 ` Tvrtko Ursulin
2010-08-03 15:31 ` Tvrtko Ursulin
2010-08-03 15:49 ` Borislav Petkov
2010-08-03 16:01 ` Tvrtko Ursulin
2010-08-03 15:59 ` Tvrtko Ursulin
2010-08-03 20:37 ` Eric W. Biederman
2010-08-04 8:09 ` Tvrtko Ursulin
2010-08-03 20:57 ` Yinghai Lu
2010-08-04 8:18 ` Tvrtko Ursulin
2010-08-04 9:05 ` Yinghai Lu [this message]
2010-08-04 9:16 ` Tvrtko Ursulin
2010-08-04 9:19 ` Tvrtko Ursulin
2010-08-04 9:34 ` Yinghai Lu
2010-08-04 9:44 ` Tvrtko Ursulin
2010-08-04 9:36 ` Gleb Natapov
2010-08-04 10:37 ` Eric W. Biederman
2010-08-04 10:46 ` Tvrtko Ursulin
2010-08-04 20:30 ` [PATCH] x86/apic: Map the local apic when parsing the MP table Eric W. Biederman
2010-08-04 21:49 ` Yinghai Lu
2010-08-04 21:58 ` [PATCH 1/2] x86, acpi: merge two register_lapic_address() Yinghai Lu
2010-08-04 22:00 ` [PATCH 2/2] x86: remove early_init_lapic_mapping Yinghai Lu
2010-08-06 0:15 ` [tip:x86/urgent] x86, apic: Map the local apic when parsing the MP table tip-bot for Eric W. Biederman
2010-08-07 0:08 ` Yinghai Lu
2010-08-07 0:15 ` H. Peter Anvin
2010-08-07 0:51 ` Yinghai Lu
2010-08-07 1:08 ` Eric W. Biederman
2010-08-07 1:21 ` H. Peter Anvin
2010-08-07 1:30 ` Yinghai Lu
2010-08-07 2:49 ` Eric W. Biederman
-- strict thread matches above, loose matches on Subject: below --
2010-08-03 22:28 2.6.35 hangs on early boot in KVM Donald Parsons
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=4C592D60.5050309@kernel.org \
--to=yinghai@kernel.org \
--cc=avi@redhat.com \
--cc=ebiederm@xmission.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tvrtko.ursulin@sophos.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox