WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

RE: [Xen-devel] Latest pvops hangs on boot

To: "Williams, Mitch A" <mitch.a.williams@xxxxxxxxx>, Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Subject: RE: [Xen-devel] Latest pvops hangs on boot
From: "Williams, Mitch A" <mitch.a.williams@xxxxxxxxx>
Date: Wed, 11 Nov 2009 15:34:24 -0700
Accept-language: en-US
Acceptlanguage: en-US
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Rzeszutek, Wilk <konrad.wilk@xxxxxxxxxx>
Delivery-date: Wed, 11 Nov 2009 14:35:05 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <EA929A9653AAE14F841771FB1DE5A1365FA65FFAB9@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <EA929A9653AAE14F841771FB1DE5A1365FA65FF9FE@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <4AFB328F.5020209@xxxxxxxx> <EA929A9653AAE14F841771FB1DE5A1365FA65FFAB9@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcpjGcOksQh2o2UVRHCDiI0rJkjl2gAAFOUAAAEkKiA=
Thread-topic: [Xen-devel] Latest pvops hangs on boot
Replying to my own email...

>Thanks for the quick replies, guys. I've updated my boot config and am now
>getting much more logging going on, though I'm still lost as to what's
>going on. My latest log file is attached.  The system hangs right in the
>middle of a line of text. On a previous boot, I got a few characters more,
>so it's not perfectly deterministic.
>
>Is there any place these command line options are documented, outside of
>the source? This is the first I've heard of some of these.
>

I started poking through the source, and found that the correct option is 
sync_console, not console_sync. Now that I've done that, I'm finally seeing a 
panic:

[    4.587828] ACPI: Core revision 20090521
[    4.601065]   alloc irq_desc for 1286 on node 0
[    4.605836]   alloc kstat_irqs on node 0
[    4.610014] cpu 0 spinlock event irq 1286
[    4.614274] BUG: unable to handle kernel NULL pointer dereference at (null)
[    4.621455] IP: [<ffffffff814a5b89>] set_cpu_sibling_map+0x116/0x2f9
[    4.628051] PGD 0 
[    4.630296] Oops: 0002 [#1] SMP 
[    4.633753] last sysfs file: 
[    4.636961] CPU 0 
[    4.639204] Modules linked in:
[    4.642490] Pid: 1, comm: swapper Not tainted 2.6.31.5 #4 X8DTN
[    4.648643] RIP: e030:[<ffffffff814a5b89>]  [<ffffffff814a5b89>] 
set_cpu_sibling_map+0x116/0x2f9
[    4.657873] RSP: e02b:ffff8802ed86fe40  EFLAGS: 00010246
[    4.663418] RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000
[    4.670794] RDX: ffffc90000000000 RSI: ffffffff81856100 RDI: 0000000000000000
[    4.678169] RBP: ffff8802ed86fea0 R08: 0000000000000000 R09: ffff8801bfc25e00
[    4.685543] R10: ffff8801bfc25e00 R11: ffff8802ed86fdb0 R12: 0000000000001000
[    4.692919] R13: ffffc90000014980 R14: ffffffffffffffff R15: 0000000000000000
[    4.700296] FS:  0000000000000000(0000) GS:ffffc90000000000(0000) 
knlGS:0000000000000000
[    4.708839] CS:  e033 DS: 0000 ES: 0000 CR0: 000000008005003b
[    4.714819] CR2: 0000000000000000 CR3: 0000000001001000 CR4: 0000000000002660
[    4.728633] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[    4.736008] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[    4.743383] Process swapper (pid: 1, threadinfo ffff8802ed86e000, task 
ffff8801bf078000)
[    4.751920] Stack:
[    4.754172]  ffff8802ed86fe50 0000000000000506 ffff8801bfc3ccc0 
0000000000000000
[    4.761539] <0> 0000000000000506 ffff8801bfc3cd2c 0000000034e8bb78 
ffffffff819a3270
[    4.769581] <0> 0000000000001000 0000000000000000 ffffffffffffffff 
0000000000000000
[    4.778048] Call Trace:
[    4.780740]  [<ffffffff81882433>] xen_smp_prepare_cpus+0x3d/0x134
[    4.787075]  [<ffffffff8100fbb4>] ? xen_spin_lock+0xb/0xd
[    4.792715]  [<ffffffff8187da4f>] kernel_init+0x84/0x1d3
[    4.798270]  [<ffffffff81014daa>] child_rip+0xa/0x20
[    4.803477]  [<ffffffff81013f67>] ? int_ret_from_sys_call+0x7/0x1b
[    4.809900]  [<ffffffff8101471d>] ? retint_restore_args+0x5/0x6
[    4.816062]  [<ffffffff8100e7a5>] ? xen_force_evtchn_callback+0xd/0xf
[    4.822743]  [<ffffffff8100e7a5>] ? xen_force_evtchn_callback+0xd/0xf
[    4.829425]  [<ffffffff81014da0>] ? child_rip+0x0/0x20
[    4.834805] Code: c7 e8 60 21 b8 ff 48 8b 55 a8 3b 05 92 03 3b 00 0f 8c 60 
ff ff ff eb 17 4a 8b 14 fd 90 63 85 81 48 c7 c0 80 e2 00 00 48 8b 04 10 <3e> 0f 
ab 38 49 8b 85 a0 00 00 00 3e 0f ab 18 48 c7 c0 80 49 01 
[    4.854192] RIP  [<ffffffff814a5b89>] set_cpu_sibling_map+0x116/0x2f9
[    4.860864]  RSP <ffff8802ed86fe40>
[    4.864591] CR2: 0000000000000000
[    4.868151] ---[ end trace 4eaa2a86a8e2da22 ]---
[    4.873040] Kernel panic - not syncing: Attempted to kill init!
[    4.879204] Pid: 1, comm: swapper Tainted: G      D    2.6.31.5 #4
[    4.885625] Call Trace:
[    4.888314]  [<ffffffff814a9e70>] panic+0x75/0x130
[    4.893348]  [<ffffffff8100fbb4>] ? xen_spin_lock+0xb/0xd
[    4.898984]  [<ffffffff8104be9e>] do_exit+0x75/0x6fe
[    4.904191]  [<ffffffff814ad0a5>] oops_end+0xdb/0xe3
[    4.909400]  [<ffffffff81034118>] no_context+0x1f1/0x200
[    4.914954]  [<ffffffff810342d3>] __bad_area_nosemaphore+0x1ac/0x1d2
[    4.921551]  [<ffffffff8100922a>] ? hypercall_page+0x22a/0x1006
[    4.927711]  [<ffffffff8100922a>] ? hypercall_page+0x22a/0x1006
[    4.933872]  [<ffffffff8100922a>] ? hypercall_page+0x22a/0x1006
[    4.940035]  [<ffffffff8100e7a5>] ? xen_force_evtchn_callback+0xd/0xf
[    4.946716]  [<ffffffff8100eed2>] ? check_events+0x12/0x20
[    4.952445]  [<ffffffff81034307>] bad_area_nosemaphore+0xe/0x10
[    4.958606]  [<ffffffff814ae5ea>] do_page_fault+0x174/0x2b2
[    4.964422]  [<ffffffff814ac545>] page_fault+0x25/0x30
[    4.969795]  [<ffffffff814a5b89>] ? set_cpu_sibling_map+0x116/0x2f9
[    4.976303]  [<ffffffff81882433>] xen_smp_prepare_cpus+0x3d/0x134
[    4.982638]  [<ffffffff8100fbb4>] ? xen_spin_lock+0xb/0xd
[    4.988280]  [<ffffffff8187da4f>] kernel_init+0x84/0x1d3
[    4.993828]  [<ffffffff81014daa>] child_rip+0xa/0x20
[    4.999025]  [<ffffffff81013f67>] ? int_ret_from_sys_call+0x7/0x1b
[    5.005486]  [<ffffffff8101471d>] ? retint_restore_args+0x5/0x6
[    5.011650]  [<ffffffff8100e7a5>] ? xen_force_evtchn_callback+0xd/0xf
[    5.018332]  [<ffffffff8100e7a5>] ? xen_force_evtchn_callback+0xd/0xf
[    5.025013]  [<ffffffff81014da0>] ? child_rip+0x0/0x20

Complete log is attached.

-Mitch

Attachment: bootlog2.txt
Description: bootlog2.txt

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel