From: Tony Vroon <tony@linx.net>
To: Tejun Heo <tj@kernel.org>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
Rusty Russell <rusty@rustcorp.com.au>,
Christoph Lameter <cl@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>, "H. Peter Anvin" <hpa@zytor.com>
Subject: 2.6.31-09194-g0d9df25 Early boot exception
Date: Sun, 27 Sep 2009 13:49:57 +0100 [thread overview]
Message-ID: <1254055797.2756.1.camel@localhost> (raw)
In-Reply-To: <4ABAC2F1.3020302@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 1915 bytes --]
On Thu, 2009-09-24 at 09:53 +0900, Tejun Heo wrote:
> Add PCPU_SETUP_BUG() macro which prints out enough information about
> the parameters. As the macro still puts separate BUG() for each
> check, it won't lose any information even on the situations where only
> the program counter can be retrieved.
On Thu, 2009-09-24 at 21:49 +0900, Tejun Heo wrote:
> Warn and dump stack when percpu allocation fails.
Thank you Tejun, both patches applied, more information is now visible:
ACPI: INT_SRC_OVR (bus 0 bus_irq 15 global_irq 15 high edge)
Using ACPI (MADT) for SMP configuration information
ACPI: HPET id: 0x10de8201 base: 0xfed00000
SMP: allowing 12 CPUs, 0 hotplug CPUs
Allocating PCI resources starting at b00000000 (gap: b0000000:30000000)
NR_CPUS: 12 nr_cpumask_bits:12 nr_cpu_ids:12 nr_node_ids:2
PERCPU: Embedded 23 pages/cpu @ffff880028200000 s73176 r0 d21032 u262144
PERCPU: failed to initialize, unit_map[cpu] == NR_CPUS
PERCPU: cpu_possible_mask=fff
pcpu-alloc: s73176 r0 d21032 u262144 alloc=1*2097152
pcpu-alloc: [0] 00 01 02 03 04 05 -- -- [1] 06 07 08 09 10 11 -- --
PANIC: early exception 06 rip 10:ffffffff81597feb error 0 cr2 d0fff6
Pid: 0, comm: swapper Not tainted 2.6.31-09194-g0d9df25-dirty #1
Call Trace:
[<ffffffff81582195>] early_idt_handler+0x55/0x68
[<ffffffff81597feb>] ? pcpu_setup_first_chunk+0x472/0x769
[<ffffffff81597feb>] ? pcpu_setup_first_chunk+0x472/0x769
[<ffffffff815987e8>] pcpu_embed_first_chunk+0x1e2/0x241
[<ffffffff8158b51d>] ? pcpu_fc_alloc+0x0/0xac
[<ffffffff8158b4fe>] ? pcpu_fc_free+0x0/0x1f
[<ffffffff8158b33f>] setup_per_cpu_areas+0x65/0x219
[<ffffffff815829df>] start_kernel+0x124/0x2c5
[<ffffffff81582272>] x86_64_start_reservations+0x82/0x86
[<ffffffff8158235a>] x86_64_start_kernel+0xe4/0xeb
RIP pcpu_setup_first_chunk+0x472/0x769
If you would like the vmlinux image again, let me know.
Regards,
Tony V.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2009-09-27 12:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-24 0:53 [PATCH] percpu: make pcpu_setup_first_chunk() failures more verbose Tejun Heo
2009-09-24 12:49 ` [PATCH] percpu: make allocation " Tejun Heo
2009-09-27 12:49 ` Tony Vroon [this message]
2009-09-28 16:19 ` [PATCH] percpu: fix unit_map[] verification in pcpu_setup_first_chunk() Tejun Heo
2009-09-28 16:25 ` Christoph Lameter
2009-09-28 16:35 ` Tejun Heo
2009-09-28 16:38 ` Tejun Heo
2009-09-28 16:40 ` Christoph Lameter
2009-09-28 16:53 ` Tejun Heo
2009-09-28 22:07 ` Tony Vroon
2009-09-29 0:15 ` Tejun Heo
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=1254055797.2756.1.camel@localhost \
--to=tony@linx.net \
--cc=cl@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rusty@rustcorp.com.au \
--cc=tj@kernel.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