From: Sander Eikelenboom <linux@eikelenboom.it>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: xen-devel <xen-devel@lists.xen.org>, linux-kernel@vger.kernel.org
Subject: Re: 3.8.0-rc0 on xen-unstable: RCU Stall during boot as dom0 kernel after IOAPIC
Date: Mon, 17 Dec 2012 15:58:30 +0100 [thread overview]
Message-ID: <357884620.20121217155830@eikelenboom.it> (raw)
In-Reply-To: <20121216173824.GA4518@phenom.dumpdata.com>
Sunday, December 16, 2012, 6:38:24 PM, you wrote:
> On Fri, Dec 14, 2012 at 04:55:57PM +0100, Sander Eikelenboom wrote:
>> Hi Konrad,
>>
>> I just tried to boot a 3.8.0-rc0 kernel (last commit: 7313264b899bbf3988841296265a6e0e8a7b6521) as dom0 on my machine with current xen-unstable.
> Yeah, saw it over the Dec 11->Dec 12 merges and was out on
> vacation during that time (just got back).
> Did you by any chance try to do a git bisect to narrow down
> which merge it was?
Hi Konrad,
I tried to bisect, but did not succeed so far. But somehow i have the feeling it is at least partly .config related.
After make a new clone, and by hand trying to bisecting down, i came back to v3.7, but that also didn't boot.
So i will see if i can do it the other way around :S
--
Sander
> Thanks!
>> The boot stalls:
>>
>> [ 0.000000] ACPI: PM-Timer IO Port: 0x808
>> [ 0.000000] ACPI: Local APIC address 0xfee00000
>> [ 0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
>> [ 0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
>> [ 0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x02] enabled)
>> [ 0.000000] ACPI: LAPIC (acpi_id[0x04] lapic_id[0x03] enabled)
>> [ 0.000000] ACPI: LAPIC (acpi_id[0x05] lapic_id[0x04] enabled)
>> [ 0.000000] ACPI: LAPIC (acpi_id[0x06] lapic_id[0x05] enabled)
>> [ 0.000000] ACPI: IOAPIC (id[0x06] address[0xfec00000] gsi_base[0])
>> [ 0.000000] IOAPIC[0]: apic_id 6, version 33, address 0xfec00000, GSI 0-23
>> [ 0.000000] ACPI: IOAPIC (id[0x07] address[0xfec20000] gsi_base[24])
>> [ 0.000000] IOAPIC[1]: apic_id 7, version 33, address 0xfec20000, GSI 24-
>> [ 64.598628] INFO: rcu_preempt detected stalls on CPUs/tasks:
>> [ 64.598676] 0: (1 GPs behind) idle=aed/140000000000000/0 drain=5 . timer not pending
>> [ 64.598683] (detected by 1, t=18004 jiffies, g=18446744073709551414, c=18446744073709551413, q=162)
>> [ 64.598692] sending NMI to all CPUs:
>> [ 64.598716] xen: vector 0x2 is not implemented
>>
>>
>> Perhaps an interesting line is the incomplete (no end of range, and it stalls there some time before the kernel reports the stall itself:
>> [ 0.000000] IOAPIC[1]: apic_id 7, version 33, address 0xfec20000, GSI 24-
>>
>>
>> The exact seem config with 3.7.0 as kernel works fine.
>> Complete serial log is attached.
>>
>> --
>>
>> Sander
>>
>>
next prev parent reply other threads:[~2012-12-17 14:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-14 15:55 3.8.0-rc0 on xen-unstable: RCU Stall during boot as dom0 kernel after IOAPIC Sander Eikelenboom
2012-12-16 17:38 ` Konrad Rzeszutek Wilk
2012-12-16 19:42 ` Sander Eikelenboom
2012-12-17 14:58 ` Sander Eikelenboom [this message]
2012-12-17 20:32 ` Sander Eikelenboom
2012-12-17 20:46 ` Konrad Rzeszutek Wilk
2012-12-17 21:12 ` Konrad Rzeszutek Wilk
2012-12-17 21:35 ` Sander Eikelenboom
2012-12-18 1:12 ` Konrad Rzeszutek Wilk
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=357884620.20121217155830@eikelenboom.it \
--to=linux@eikelenboom.it \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xen-devel@lists.xen.org \
/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