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:
[<ffffffff811f22b0>] write_console+0x43 <--
[<ffffffff811f22b0>] write_console+0x43
[<ffffffff8117c89f>] vsnprintf+0x7b3
[<ffffffff811f245b>] xenboot_write_console+0x45
[<ffffffff8104ec35>] __call_console_drivers+0x64
[<ffffffff8104f04a>] release_console_sem+0x10e
[<ffffffff8104f5bf>] vprintk+0x2e3
[<ffffffff810269f3>] __raw_callee_save_xen_restore_fl+0x11
[<ffffffff810269f3>] __raw_callee_save_xen_restore_fl+0x11
[<ffffffff81026a11>] __raw_callee_save_xen_irq_disable+0x11
[<ffffffff810269f3>] __raw_callee_save_xen_restore_fl+0x11
[<ffffffff813095b8>] printk+0x4e
[<ffffffff813095b8>] printk+0x4e
[<ffffffff814c2f36>] mark_bootmem_node+0xa8
[<ffffffff814b7135>] e820_register_active_regions+0x5a
[<ffffffff814b71a4>] early_res_to_bootmem+0x56
[<ffffffff814bf48b>] initmem_init+0x8c
[<ffffffff814b60b4>] setup_arch+0x508
[<ffffffff8130afe3>] _spin_unlock_irqrestore+0xc
[<ffffffff810681fb>] clockevents_register_notifier+0x39
[<ffffffff814b32ee>] start_kernel+0x7e
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
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: > [<ffffffff811f22b0>] write_console+0x43 <-- > [<ffffffff811f22b0>] write_console+0x43 > [<ffffffff8117c89f>] vsnprintf+0x7b3 > [<ffffffff811f245b>] xenboot_write_console+0x45 > [<ffffffff8104ec35>] __call_console_drivers+0x64 > [<ffffffff8104f04a>] release_console_sem+0x10e > [<ffffffff8104f5bf>] vprintk+0x2e3 > [<ffffffff810269f3>] __raw_callee_save_xen_restore_fl+0x11 > [<ffffffff810269f3>] __raw_callee_save_xen_restore_fl+0x11 > [<ffffffff81026a11>] __raw_callee_save_xen_irq_disable+0x11 > [<ffffffff810269f3>] __raw_callee_save_xen_restore_fl+0x11 > [<ffffffff813095b8>] printk+0x4e > [<ffffffff813095b8>] printk+0x4e > [<ffffffff814c2f36>] mark_bootmem_node+0xa8 > [<ffffffff814b7135>] e820_register_active_regions+0x5a > [<ffffffff814b71a4>] early_res_to_bootmem+0x56 > [<ffffffff814bf48b>] initmem_init+0x8c > [<ffffffff814b60b4>] setup_arch+0x508 > [<ffffffff8130afe3>] _spin_unlock_irqrestore+0xc > [<ffffffff810681fb>] clockevents_register_notifier+0x39 > [<ffffffff814b32ee>] start_kernel+0x7e > ------------------------------------------------------------------------ > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On Wed, Nov 11, 2009 at 09:08:57AM +0100, Killian De Volder wrote:> After removing some things from my .config (of witch PCI support) xen now > seems to boot. >What was the option causing the crash? -- Pasi _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
I''m not entirely certain, if you wish i could seek out the option.> On Wed, Nov 11, 2009 at 09:08:57AM +0100, Killian De Volder wrote: > >> After removing some things from my .config (of witch PCI support) xen now >> seems to boot. >> >> > > What was the option causing the crash? > > -- Pasi > > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On Wed, Nov 11, 2009 at 04:04:51PM +0100, Killian De Volder wrote:> I''m not entirely certain, if you wish i could seek out the option.Please do. Earlier you mention that the kernel you built is Vanilla 2.6.31.6 - where did you get it from? What git branch is it from? Thanks. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
I tried this version: http://www.kernel.org/pub/linux/kernel/v2.6/testing/linux-2.6.32-rc6.tar.bz2 And several other, i played some with the settings i changed, but cannot reproduce. (And I don''t really have a lot of time left to look for this.) Must be some sort of weird "your not suppose to do this" kind of bugs and/or weird combination. My config probably wasn''t sane. If anyone feels like tracking down a low priority bug (since it''s probably something weird), have fun :p> > >> On Wed, Nov 11, 2009 at 04:04:51PM +0100, Killian De Volder wrote: >> >>> I''m not entirely certain, if you wish i could seek out the option. >>> >> >> Please do. >> >> Earlier you mention that the kernel you built is Vanilla 2.6.31.6 - where >> did you get it from? What git branch is it from? >> >> Thanks. >> >> _______________________________________________ >> Xen-devel mailing list >> Xen-devel@lists.xensource.com >> http://lists.xensource.com/xen-devel >> >> >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On Wed, Nov 11, 2009 at 07:03:22PM +0100, Killian De Volder wrote:> > I tried this version: > http://www.kernel.org/pub/linux/kernel/v2.6/testing/linux-2.6.32-rc6.tar.bz2Aaahh.. There is the problem. The upstream version is a bit out-dated compared to the Jeremy''s git tree. Take a look here: http://wiki.xensource.com/xenwiki/XenParavirtOps _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On 11/11/09 07:04, Killian De Volder wrote:> I''m not entirely certain, if you wish i could seek out the option.It would be helpful to isolate it. Mainline kernels should work as domU without any other patches. Its possible there''s a bugfix in xen.git should should be in mainline. J>> On Wed, Nov 11, 2009 at 09:08:57AM +0100, Killian De Volder wrote: >> >>> After removing some things from my .config (of witch PCI support) xen now >>> seems to boot. >>> >>> >> >> What was the option causing the crash? >> >> -- Pasi >> >> >> > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel