xen-devel
Re: [Xen-devel] Re: Panic on boot on Sun Blade 6270
On Fri, Mar 12, 2010 at 1:44 PM, Pasi Kärkkäinen <pasik@xxxxxx> wrote:
>> Also, is it expected that
>> the default .hg tree xen will *just work* on a SLES distro by running
>> install.sh or do you need a bunch of SuSE specific patches?
>>
>
> The default hg tree should work.
Thanks for the tips Pasi.. I guess I did pretty much that, but I just
did a 'make dist' and built everything including the 2.6.18 kernel, I
moved everything to the test machine and ran 'sh ./install.sh' and
added a grub line to boot the new xen:
title Xen-3.4.3-rc1.dan -- SUSE Linux Enterprise Server 11 -
2.6.27.19-5 (xen).dan
root (hd0,0)
kernel /xen-3.4.3-rc4-pre.gz crashkernel=128M@16M iommu=1
loglvl=all guest_loglvl=all console=vga,com1 com1=auto
module /vmlinuz-2.6.27.19-5-xen.dan root=/dev/dm-5
resume=/dev/dm-2 splash=silent showopts console=ttyS0,115200 quiet
module /initrd-2.6.27.19-5-xen.dan
so it should use the new hypervisor (xen-3.4.3-rc4-pre.gz) but the
original SLES 11 kernel /vmlinuz-2.6.27.19-5-xen.dan ( the stock
kernel with a couple of printks thrown in).
This boots to the kernel, but then it locks up the machine when it
tries to bring the networking up:
Mounting local file systems...
/proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
debugfs on /sys/kernel/debug type debugfs (rw)
udev on /dev type tmpfs (rw)
devpts on /dev/pts type devpts (rw,mode=0620,gid=5)
/dev/mapper/ddf1_disk1_part1 on /boot type ext2 (rw,acl,user_xattr)
/dev/mapper/ddf1_disk1_part3 on /temp type ext3 (rw,acl,user_xattr) done
Setting current sysctl status from /etc/sysctl.conf done
Enabling syn flood protection done
Disabling IP forwarding done
done
Loading fuse module done
Mounting fuse control filesystem done
Activating remaining swap-devices in /etc/fstab... done
Creating /var/log/boot.msg done
Setting up linker cache (/etc/ld.so.cache) using ldconfig done
ATTENTION: You have modified /etc/resolv.conf. Leaving it untouched...
You can find my version in /etc/resolv.conf.netconfig ...
ATTENTION: You have modified /etc/yp.conf. Leaving it untouched...
You can find my version in /etc/yp.conf.netconfig ...
Setting up hostname 'sunblade1' done
Setting up NIS domainname 'adax.co.uk' done
Setting up loopback interface lo
lo IP address: 127.0.0.1/8
IP address: 127.0.0.2/8
Bridge firewalling registered
After about 5 minutes of sitting there it crashed:
BUG: unable to handle kernel NULL pointer dereference at 0000000000000008
IP: [<ffffffff8020e9cb>] profile_pc+0x30/0x3d
PGD 0
Oops: 0000 [1] SMP
last sysfs file: /sys/devices/pci0000:00/0000:00:1e.0/0000:20:05.0/class
CPU 0
Modules linked in: bridge(N) stp(N) fuse(N) ext2(N) loop(N) rtc_cmos(N) i2c_i80)
Supported: No
Pid: 92, comm: kswapd0 Tainted: G 2.6.27.19-5-xen.dan #5
RIP: e030:[<ffffffff8020e9cb>] [<ffffffff8020e9cb>] profile_pc+0x30/0x3d
RSP: e02b:ffffffff80783db8 EFLAGS: 00010002
RAX: 0000000000000000 RBX: ffffffff8049077c RCX: ffffffff8067e320
RDX: ffff880081fa5000 RSI: 0000000000000400 RDI: ffffffff8049077c
RBP: ffffffff80783dc8 R08: 0000000000000c31 R09: ffff8803d8608878
R10: ffffffff80783d38 R11: 000000000000000c R12: ffff8803d860b838
R13: ffffffff80774020 R14: 00000000006187a6 R15: ffff880002719000
FS: 00007fde48ab66f0(0000) GS:ffffffff80785080(0000) knlGS:0000000000000000
CS: e033 DS: 0000 ES: 0000
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Process kswapd0 (pid: 92, threadinfo ffff8803d860a000, task ffff8803d8608840)
Stack: ffff8803d860b838 0000000000000001 ffffffff80783de8 ffffffff8024da1a
0000000000000000 0000000000000020 ffffffff80783e98 ffffffff8020e987
ffffffff80490942 ffffffff806b7108 ffffffff807e9700 ffffffff80774000
Call Trace:
[<ffffffff8024da1a>] profile_tick+0x5f/0x7d
[<ffffffff8020e987>] timer_interrupt+0x436/0x44a
[<ffffffff80270594>] handle_IRQ_event+0x50/0x9c
[<ffffffff80271757>] handle_percpu_irq+0x45/0x73
[<ffffffff8020d8e3>] do_IRQ+0x4a/0x92
[<ffffffff803dbce8>] evtchn_do_upcall+0x1a9/0x275
[<ffffffff8020bcae>] do_hypervisor_callback+0x1e/0x30
[<ffffffff8049077c>] _read_unlock_irqrestore+0x58/0x59
DWARF2 unwinder stuck at _read_unlock_irqrestore+0x58/0x59
Leftover inexact backtrace:
[<ffffffffa012c8a7>] ? dm_get_table+0x35/0x3d [dm_mod]
[<ffffffffa012ca10>] ? __split_bio+0x1e/0x47f [dm_mod]
[<ffffffff802837ac>] ? __set_page_dirty_nobuffers+0x12/0x18d
[<ffffffff802a691d>] ? __mem_cgroup_uncharge_common+0x10/0x163
[<ffffffff802896ae>] ? __dec_zone_state+0x9/0x77
[<ffffffff80490942>] ? _spin_lock_irq+0xc/0x71
[<ffffffff804902f4>] ? __down_read+0x1a/0x120
[<ffffffff8027f2ae>] ? mempool_alloc_slab+0x16/0x18
[<ffffffffa012d056>] ? dm_request+0x13d/0x15f [dm_mod]
[<ffffffff8033d1c0>] ? generic_make_request+0x39c/0x3df
[<ffffffff802d282a>] ? bvec_alloc_bs+0x86/0xad
[<ffffffff802d2780>] ? bio_init+0xd/0x31
[<ffffffff802d28a1>] ? bio_alloc_bioset+0x50/0x97
[<ffffffff804909b9>] ? _spin_lock_irqsave+0x12/0x96
[<ffffffff8033d2ce>] ? submit_bio+0xcb/0xd4
[<ffffffff8029c3ba>] ? swap_writepage+0xf6/0x103
[<ffffffff80287748>] ? shrink_page_list+0x37b/0x5f3
[<ffffffff8021d359>] ? ptep_clear_flush_young+0x7c/0x8b
[<ffffffff80286829>] ? __isolate_lru_page+0x9/0x62
[<ffffffff802869e8>] ? isolate_lru_pages+0x166/0x210
[<ffffffff80287b90>] ? shrink_inactive_list+0x1d0/0x51d
[<ffffffff80287fe8>] ? shrink_zone+0x10b/0x12e
[<ffffffff802885f1>] ? kswapd+0x3f3/0x583
[<ffffffff80286a92>] ? isolate_pages_global+0x0/0x39
[<ffffffff8024860a>] ? autoremove_wake_function+0x0/0x3d
[<ffffffff802881fe>] ? kswapd+0x0/0x583
[<ffffffff802480bf>] ? kthread+0x4e/0x7b
[<ffffffff8020bef9>] ? child_rip+0xa/0x11
[<ffffffff80248071>] ? kthread+0x0/0x7b
[<ffffffff8020beef>] ? child_rip+0x0/0x11
Code: 54 53 e8 89 ca ff ff f6 87 88 00 00 00 03 48 8b 9f 80 00 00 00 49 89 fc 7
RIP [<ffffffff8020e9cb>] profile_pc+0x30/0x3d
RSP <ffffffff80783db8>
CR2: 0000000000000008
---[ end trace a2b3d37002a3cae5 ]---
Kernel panic - not syncing: Aiee, killing interrupt handler!
------------[ cut here ]------------
WARNING: at kernel/smp.c:331 smp_call_function_mask+0x5a/0x1e1()
Modules linked in: bridge(N) stp(N) fuse(N) ext2(N) loop(N) rtc_cmos(N) i2c_i80)
Is there some difference in the network configuration or something
that could cause this?
thanks
dan
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- [Xen-devel] Panic on boot on Sun Blade 6270, Dan Gora
- [Xen-devel] Re: Panic on boot on Sun Blade 6270, Dan Gora
- RE: [Xen-devel] Re: Panic on boot on Sun Blade 6270, Jiang, Yunhong
- Re: [Xen-devel] Re: Panic on boot on Sun Blade 6270, Keir Fraser
- Re: [Xen-devel] Re: Panic on boot on Sun Blade 6270, Dan Gora
- Re: [Xen-devel] Re: Panic on boot on Sun Blade 6270, Dan Gora
- Re: [Xen-devel] Re: Panic on boot on Sun Blade 6270, Pasi Kärkkäinen
- Re: [Xen-devel] Re: Panic on boot on Sun Blade 6270,
Dan Gora <=
- Re: [Xen-devel] Re: Panic on boot on Sun Blade 6270, Jan Beulich
- Re: [Xen-devel] Re: Panic on boot on Sun Blade 6270, Dan Gora
- Re: [Xen-devel] Re: Panic on boot on Sun Blade 6270, Jan Beulich
- Re: [Xen-devel] Re: Panic on boot on Sun Blade 6270, Dan Gora
- Re: [Xen-devel] Re: Panic on boot on Sun Blade 6270, Jan Beulich
- Re: [Xen-devel] Re: Panic on boot on Sun Blade 6270, Dan Gora
Re: [Xen-devel] Panic on boot on Sun Blade 6270, Keir Fraser
|
|
|