From mboxrd@z Thu Jan 1 00:00:00 1970 From: Killian De Volder Subject: Re: Crashing DomU Date: Wed, 11 Nov 2009 09:08:57 +0100 Message-ID: <4AFA7119.4090108@scarlet.be> References: <4AF9E19C.2060900@scarlet.be> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0484273554==" Return-path: In-Reply-To: <4AF9E19C.2060900@scarlet.be> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org This is a multi-part message in MIME format. --===============0484273554== Content-Type: multipart/alternative; boundary="------------090902010706010408050900" This is a multi-part message in MIME format. --------------090902010706010408050900 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit After removing some things from my .config (of witch PCI support) xen now seems to boot. > Good day, > > I'm experiencing a crashing domU kernel (during bootup) > A person on IRC redirected me to the devel mailing list as it might > well be a bug. > > Below you can find the information about the crash, and versions used. > (Used .config for domU is attached.) > > If you have any questions, feel free to ask. > > Greetings, > Killian > > Xen Hypervision Version: 3.4.1 > DomU kernel: Vanilla-sources 2.6.31.6 > DomO kernel: Linux xen 2.6.18-xen-r12 > CPU: SMP x86_64 AMD Athlon(tm) 64 X2 Dual Core Processor 4400+ > > Xen config file: > > kernel = "/boot/domU/net_vmlinuz" > memory = 128 > name = "net" > vcpus = 2 > vif = [ 'bridge=lan' ] > disk = [ > 'phy:vg/net_root,xvda1,w', > 'phy:vg/net_tmp,xvda2,w', > 'phy:vg/net_var,xvda3,w', > 'phy:vg/net_usr,xvda4,w', > 'phy:vg/net_log,xvda5,w', > 'phy:vg/net_swap,xvda6,w', > 'phy:vg/net_proxy_cache,xvda7,w', > ] > > root = "/dev/xvda1 ro" > extra="console=hvc0 earlyprintk=xen" > on_crash='preserve > > Crash report: > rip: ffffffff811f22b0 write_console+0x43 > flags: 00001246 i z p > rsp: ffffffff8142dc60 > rax: ffffffff81654000 rcx: 000000000000003d rdx: 0000000000000008 > rbx: ffffffff8147d360 rsi: ffffffff813e21be rdi: 0000000000000000 > rbp: 0000000000000008 r8: ffffffff815b5570 r9: ffffffff815358c5 > r10: 0000000000000010 r11: ffffffff815b5930 r12: ffffffff813e21be > r13: 0000000000000008 r14: ffff880000000000 r15: 0000000000000000 > cs: e033 ss: e02b ds: 0000 es: 0000 > fs: 0000 @ 0000000000000000 > gs: 0000 @ ffffffff814a0000/0000000000000000 > Code (instr addr ffffffff811f22b0) > 00 48 83 f8 ff 75 25 80 3d 59 a3 2a 00 00 48 8b 05 a8 b0 33 00 <48> 8b > 40 48 75 11 44 89 fa 48 b9 > > > Stack: > 000000000000003d ffffffff815b5930 0000000000000000 ffffffff811f22b0 > 000000010000e030 0000000000010046 ffffffff8142dca8 000000000000e02b > ffffffff8117c89f 0000002100000008 ffffffff8147d360 000000000000003d > 00000000000003a5 ffffffff8149be18 ffffffff815358c5 ffffffff8142dda8 > > Call Trace: > [] write_console+0x43 <-- > [] write_console+0x43 > [] vsnprintf+0x7b3 > [] xenboot_write_console+0x45 > [] __call_console_drivers+0x64 > [] release_console_sem+0x10e > [] vprintk+0x2e3 > [] __raw_callee_save_xen_restore_fl+0x11 > [] __raw_callee_save_xen_restore_fl+0x11 > [] __raw_callee_save_xen_irq_disable+0x11 > [] __raw_callee_save_xen_restore_fl+0x11 > [] printk+0x4e > [] printk+0x4e > [] mark_bootmem_node+0xa8 > [] e820_register_active_regions+0x5a > [] early_res_to_bootmem+0x56 > [] initmem_init+0x8c > [] setup_arch+0x508 > [] _spin_unlock_irqrestore+0xc > [] clockevents_register_notifier+0x39 > [] start_kernel+0x7e > ------------------------------------------------------------------------ > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel > --------------090902010706010408050900 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable After removing some things from my .config (of witch PCI support) xen now seems to boot.
Good day,

I'm experiencing a crashing domU kernel (during bootup)
A person on IRC redirected me to the devel mailing list as it might well be a bug.

Below you can find the information about the crash, and versions used.
(Used .config for domU is attached.)

If you have any questions, feel free to ask.

Greetings,
Killian

Xen Hypervision Version: 3.4.1
DomU kernel: Vanilla-sources 2.6.31.6
DomO kernel: Linux xen 2.6.18-xen-r12
CPU: SMP x86_64 AMD Athlon(tm) 64 X2 Dual Core Processor 4400+

Xen config file:

kernel =3D "/boot/domU/net_vmlinuz"
memory =3D 128
name =3D "net"
vcpus =3D 2
vif =3D [ 'bridge=3Dlan' ]
disk =3D [
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 'phy:vg/net_root,xvda1,w',
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 'phy:vg/net_tmp,xvda2,w',
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 'phy:vg/net_var,xvda3,w',
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 'phy:vg/net_usr,xvda4,w',
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 'phy:vg/net_log,xvda5,w',
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 'phy:vg/net_swap,xvda6,w',
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 'phy:vg/net_proxy_cache,xvda7,w',
]

root =3D "/dev/xvda1 ro"
extra=3D"console=3Dhvc0 earlyprintk=3Dxen"
on_crash=3D'preserve

Crash report:
rip: ffffffff811f22b0 write_console+0x43
flags: 00001246 i z p
rsp: ffffffff8142dc60
rax: ffffffff81654000=C2=A0=C2=A0=C2=A0 rcx: 000000000000003d=C2=A0=C2=A0= =C2=A0 rdx: 0000000000000008
rbx: ffffffff8147d360=C2=A0=C2=A0=C2=A0 rsi: ffffffff813e21be=C2=A0=C2=A0= =C2=A0 rdi: 0000000000000000
rbp: 0000000000000008=C2=A0=C2=A0=C2=A0=C2=A0 r8: ffffffff815b5570=C2=A0=C2= =A0=C2=A0=C2=A0 r9: ffffffff815358c5
r10: 0000000000000010=C2=A0=C2=A0=C2=A0 r11: ffffffff815b5930=C2=A0=C2=A0= =C2=A0 r12: ffffffff813e21be
r13: 0000000000000008=C2=A0=C2=A0=C2=A0 r14: ffff880000000000=C2=A0=C2=A0= =C2=A0 r15: 0000000000000000
cs: e033=C2=A0=C2=A0=C2=A0=C2=A0 ss: e02b=C2=A0=C2=A0=C2=A0=C2=A0 ds: 000= 0=C2=A0=C2=A0=C2=A0=C2=A0 es: 0000
fs: 0000 @ 0000000000000000
gs: 0000 @ ffffffff814a0000/0000000000000000
Code (instr addr ffffffff811f22b0)
00 48 83 f8 ff 75 25 80 3d 59 a3 2a 00 00 48 8b 05 a8 b0 33 00 <48> 8b 40 48 75 11 44 89 fa 48 b9


Stack:
000000000000003d ffffffff815b5930 0000000000000000 ffffffff811f22b0
000000010000e030 0000000000010046 ffffffff8142dca8 000000000000e02b
ffffffff8117c89f 0000002100000008 ffffffff8147d360 000000000000003d
00000000000003a5 ffffffff8149be18 ffffffff815358c5 ffffffff8142dda8

Call Trace:
=C2=A0[<ffffffff811f22b0>] write_console+0x43=C2=A0 <--
=C2=A0[<ffffffff811f22b0>] write_console+0x43
=C2=A0[<ffffffff8117c89f>] vsnprintf+0x7b3
=C2=A0[<ffffffff811f245b>] xenboot_write_console+0x45
=C2=A0[<ffffffff8104ec35>] __call_console_drivers+0x64
=C2=A0[<ffffffff8104f04a>] release_console_sem+0x10e
=C2=A0[<ffffffff8104f5bf>] vprintk+0x2e3
=C2=A0[<ffffffff810269f3>] __raw_callee_save_xen_restore_fl+0x11
=C2=A0[<ffffffff810269f3>] __raw_callee_save_xen_restore_fl+0x11
=C2=A0[<ffffffff81026a11>] __raw_callee_save_xen_irq_disable+0x11
=C2=A0[<ffffffff810269f3>] __raw_callee_save_xen_restore_fl+0x11
=C2=A0[<ffffffff813095b8>] printk+0x4e
=C2=A0[<ffffffff813095b8>] printk+0x4e
=C2=A0[<ffffffff814c2f36>] mark_bootmem_node+0xa8
=C2=A0[<ffffffff814b7135>] e820_register_active_regions+0x5a
=C2=A0[<ffffffff814b71a4>] early_res_to_bootmem+0x56
=C2=A0[<ffffffff814bf48b>] initmem_init+0x8c
=C2=A0[<ffffffff814b60b4>] setup_arch+0x508
=C2=A0[<ffffffff8130afe3>] _spin_unlock_irqrestore+0xc
=C2=A0[<ffffffff810681fb>] clockevents_register_notifier+0x39
=C2=A0[<ffffffff814b32ee>] start_kernel+0x7e

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

--------------090902010706010408050900-- --===============0484273554== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel --===============0484273554==--