From: Giovanni Bellac <giovannib1979@ymail.com>
To: xen-devel@lists.xensource.com
Subject: 2.6.32.22 (amd64) domU Kernel doesnt boot - kernel panic
Date: Tue, 21 Sep 2010 10:02:53 +0000 (GMT) [thread overview]
Message-ID: <181628.18427.qm@web29720.mail.ird.yahoo.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 7507 bytes --]
Hello
I have used my 2.6.32.20 config and compiled now a 2.6.32.22 from kernel.org.
2.6.32.22 has the important security fix (local user can be root with a
exploit).
When booting up the domU with the new kernel, it hangs here:
[7061459.971314] installing Xen timer for CPU 0
[7061459.971338] BUG: unable to handle kernel NULL pointer dereference at (null)
[7061459.971347] IP: [<(null)>] (null)
[7061459.971353] PGD 0
[7061459.971357] Thread overran stack, or stack corrupted
[7061459.971362] Oops: 0010 [#1] SMP
[7061459.971368] last sysfs file:
[7061459.971372] CPU 0
[7061459.971377] Modules linked in:
[7061459.971383] Pid: 0, comm: swapper Not tainted 2.6.32.22 #1
[7061459.971389] RIP: e030:[<0000000000000000>] [<(null)>] (null)
[7061459.971395] RSP: e02b:ffffffff81805da0 EFLAGS: 00010082
[7061459.971400] RAX: ffffffff81b62a50 RBX: 0000000000000000 RCX:
00000000000002
00
[7061459.971407] RDX: 0000000000000000 RSI: ffffffff81b434a8 RDI:
00000000000000
00
[7061459.971413] RBP: ffffffff81805db8 R08: ffff88007fc18080 R09:
ffffffff818937
30
[7061459.971420] R10: ffffffff81893750 R11: 0000000000000001 R12:
ffffffff818272
40
[7061459.971426] R13: ffff88007fc1b000 R14: 0000000000000000 R15:
ffffffff818272
a4
[7061459.971438] FS: 0000000000000000(0000) GS:ffff880001fd6000(0000)
knlGS:000
0000000000000
[7061459.971445] CS: e033 DS: 0000 ES: 0000 CR0: 000000008005003b
[7061459.971450] CR2: 0000000000000000 CR3: 0000000001001000 CR4:
00000000000026
60
[7061459.971457] DR0: 0000000000000000 DR1: 0000000000000000 DR2:
00000000000000
00
[7061459.971464] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7:
00000000000004
00
[7061459.971471] Process swapper (pid: 0, threadinfo ffffffff81804000, task
ffff
ffff818979f0)
[7061459.971478] Stack:
[7061459.971481] ffffffff8107cac5 0000000000000000 00000000ffffffda
ffffffff818
05dd8
[7061459.971490] <0> ffffffff8107caa5 ffffffff815a94b1 ffffffff81827240
ffffffff
81805e18
[7061459.971502] <0> ffffffff8107c009 0000000000000200 ffff88007fc1b000
00000000
fffffff4
[7061459.971515] Call Trace:
[7061459.971525] [<ffffffff8107cac5>] ? default_enable+0x1a/0x28
[7061459.971533] [<ffffffff8107caa5>] default_startup+0x19/0x1f
[7061459.971542] [<ffffffff815a94b1>] ? _spin_lock_irqsave+0x19/0x32
[7061459.971550] [<ffffffff8107c009>] __setup_irq+0x197/0x2cf
[7061459.971558] [<ffffffff8100e05f>] ? xen_timer_interrupt+0x0/0x182
[7061459.971565] [<ffffffff8107c22d>] request_threaded_irq+0xec/0x12b
[7061459.971575] [<ffffffff812b278c>] bind_virq_to_irqhandler+0x13f/0x163
[7061459.971582] [<ffffffff8100e05f>] ? xen_timer_interrupt+0x0/0x182
[7061459.971589] [<ffffffff8100e01a>] xen_setup_timer+0x59/0x9e
[7061459.971598] [<ffffffff8198d5a3>] xen_time_init+0xb7/0xc0
[7061459.971604] [<ffffffff8198da27>] x86_late_time_init+0xa/0x11
[7061459.971612] [<ffffffff81989c2f>] start_kernel+0x2fe/0x385
[7061459.971618] [<ffffffff819892bf>] x86_64_start_reservations+0xaa/0xae
[7061459.971626] [<ffffffff8198cad2>] xen_start_kernel+0x541/0x548
[7061459.971631] Code: Bad RIP value.
[7061459.971641] RIP [<(null)>] (null)
[7061459.971646] RSP <ffffffff81805da0>
[7061459.971650] CR2: 0000000000000000
[7061459.971660] ---[ end trace 4eaa2a86a8e2da22 ]---
[7061459.971665] Kernel panic - not syncing: Attempted to kill the idle task!
[7061459.971671] Pid: 0, comm: swapper Tainted: G D 2.6.32.22 #1
[7061459.971676] Call Trace:
[7061459.971682] [<ffffffff815a7537>] panic+0xa0/0x158
[7061459.971688] [<ffffffff815a7656>] ? printk+0x67/0x69
[7061459.971696] [<ffffffff81055e60>] ? blocking_notifier_call_chain+0xf/0x11
[7061459.971705] [<ffffffff81042b76>] do_exit+0x79/0x6c9
[7061459.971711] [<ffffffff815aa492>] oops_end+0xb9/0xc1
[7061459.971718] [<ffffffff8102aeed>] no_context+0x1ea/0x1f9
[7061459.971724] [<ffffffff8102b0b5>] __bad_area_nosemaphore+0x1b9/0x1df
[7061459.971733] [<ffffffff8108ec17>] ? __alloc_pages_nodemask+0x11a/0x5e7
[7061459.971741] [<ffffffff8100dd01>] ? xen_force_evtchn_callback+0xd/0xf
[7061459.971747] [<ffffffff8100e352>] ? check_events+0x12/0x20
[7061459.971754] [<ffffffff8102b0e9>] bad_area_nosemaphore+0xe/0x10
[7061459.971761] [<ffffffff815ab98a>] do_page_fault+0x1a0/0x2d6
[7061459.971768] [<ffffffff815a9975>] page_fault+0x25/0x30
[7061459.971775] [<ffffffff8107cac5>] ? default_enable+0x1a/0x28
[7061459.971782] [<ffffffff8107caa5>] default_startup+0x19/0x1f
[7061459.971788] [<ffffffff815a94b1>] ? _spin_lock_irqsave+0x19/0x32
[7061459.971795] [<ffffffff8107c009>] __setup_irq+0x197/0x2cf
[7061459.971801] [<ffffffff8100e05f>] ? xen_timer_interrupt+0x0/0x182
[7061459.971808] [<ffffffff8107c22d>] request_threaded_irq+0xec/0x12b
[7061459.971815] [<ffffffff812b278c>] bind_virq_to_irqhandler+0x13f/0x163
[7061460.172264] [<ffffffff8100e05f>] ? xen_timer_interrupt+0x0/0x182
[7061460.172273] [<ffffffff8100e01a>] xen_setup_timer+0x59/0x9e
[7061460.172283] [<ffffffff8198d5a3>] xen_time_init+0xb7/0xc0
[7061460.172290] [<ffffffff8198da27>] x86_late_time_init+0xa/0x11
[7061460.172297] [<ffffffff81989c2f>] start_kernel+0x2fe/0x385
[7061460.172304] [<ffffffff819892bf>] x86_64_start_reservations+0xaa/0xae
[7061460.172311] [<ffffffff8198cad2>] xen_start_kernel+0x541/0x548
dom0 is XEN 3.4.3 selfcompiled on Debian Lenny amd64.
Hardware is Supermicro Board with XEON E5506 CPU.
Best regards
Gio
[-- Attachment #1.2: Type: text/html, Size: 18610 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next reply other threads:[~2010-09-21 10:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-21 10:02 Giovanni Bellac [this message]
2010-09-21 13:51 ` 2.6.32.22 (amd64) domU Kernel doesnt boot - kernel panic Konrad Rzeszutek Wilk
2010-09-21 15:44 ` William Pitcock
2010-09-21 15:48 ` Jeremy Fitzhardinge
2010-09-21 16:03 ` Jeremy Fitzhardinge
2010-09-22 22:48 ` Jeremy Fitzhardinge
2010-09-23 16:18 ` AW: " Giovanni Bellac
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=181628.18427.qm@web29720.mail.ird.yahoo.com \
--to=giovannib1979@ymail.com \
--cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.