[Xen-users] Kernel BUG at drivers/xen/blkback/blkback.c:555

["Ulrich Windl" <ulrich.windl@xxxxxxxxxxxxxxxxxxxx>]

Hi,

when playing with the "dom0_mem=" Boot parameter, I get panics with a reason 
like 
this:
"(XEN) Domain 0 allocation is too small for kernel image."

When the Dom0 finally booted, I got a panic, possibly related to tight memory:
Starting xend ----------- [cut here ] --------- [please bite here ] ---------
Kernel BUG at drivers/xen/blkback/blkback.c:555
invalid opcode: 0000 [1] SMP
last sysfs file: /class/net/vif0.5/ifindex
CPU 0
Modules linked in: blkbk netbk netloop af_packet button battery ac sr_mod 
ip6t_REJECT xt_tcpudp ipt_REJECT xt_state iptable_mangle iptable_nat ip_nat 
iptable_filter ip6table_mangle ip_conntrack nfnetlink ip_tables ip6table_filter 
ip6_tables x_tables ipv6 loop usb_storage usbhid hw_random ide_cd cdrom 
i2c_amd8111 i2c_amd756 ohci_hcd i2c_core usbcore e1000 shpchp pci_hotplug 
reiserfs 
dm_snapshot dm_mod fan thermal processor sg mptsas mptscsih mptbase 
scsi_transport_sas amd74xx sd_mod scsi_mod ide_disk ide_core
Pid: 3908, comm: modprobe Not tainted 2.6.16.21-0.25-xen #1
RIP: e030:[<ffffffff8808e0d1>] <ffffffff8808e0d1>{:blkbk:blkif_init+209}
RSP: e02b:ffff88000fcade58  EFLAGS: 00010246
RAX: 0000000000000000 RBX: ffffffff8032dea0 RCX: 0000000000005486
RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffffffff8032aa9c
RBP: ffffffff88284100 R08: ffffffff803a3340 R09: ffffffff88284100
R10: 0000000000000001 R11: 0000000000000000 R12: ffffffff8032de60
R13: ffffffff88284100 R14: ffff880008888488 R15: ffffc20000c65380
FS:  00002b13072976d0(0000) GS:ffffffff80421000(0000) knlGS:0000000000000000
CS:  e033 DS: 0000 ES: 0000
Process modprobe (pid: 3908, threadinfo ffff88000fcac000, task ffff88000076a840)
Stack: ffffffff8032de60 ffffffff8014591c 0000000000000000 ffffffff00000016
       ffff88000076a840 0000000000000000 000000000fcade88 0000000000000000
       0000000000000000 0000000000000000
Call Trace: <ffffffff8014591c>{sys_init_module+5615}
       <ffffffff8010aa6a>{system_call+134} <ffffffff8010a9e4>{system_call+0}

Code: 0f 0b 68 7d 16 28 88 c2 2b 02 48 2b 15 ce cb 35 f8 48 b8 b7
RIP <ffffffff8808e0d1>{:blkbk:blkif_init+209} RSP <ffff88000fcade58>
 /etc/init.d/xend: line 68:  3908 Segmentation fault      modprobe blkbk 
2>/dev/null
<7>usb-storage: device scan complete
Setting mem allocation to 262144 kiB
Bridge firewalling registered
eth0 renamed to peth0
veth0 renamed to eth0
[...]

Processed by ksymoops it looks like this (System is SLES10 on a 4 CPU x86_64):

Oct 23 15:35:21 rkdvmso4 kernel: Kernel BUG at drivers/xen/blkback/blkback.c:555
Oct 23 15:35:21 rkdvmso4 kernel: CPU 0
Oct 23 15:35:21 rkdvmso4 kernel: Pid: 3908, comm: modprobe Not tainted 
2.6.16.21-
0.25-xen #1
Oct 23 15:35:21 rkdvmso4 kernel: RIP: e030:[<ffffffff8808e0d1>] 
<ffffffff8808e0d1>{:blkbk:blkif_init+209}
Using defaults from ksymoops -t elf64-x86-64 -a i386:x86-64
Oct 23 15:35:21 rkdvmso4 kernel: RSP: e02b:ffff88000fcade58  EFLAGS: 00010246
Oct 23 15:35:21 rkdvmso4 kernel: RAX: 0000000000000000 RBX: ffffffff8032dea0 
RCX: 
0000000000005486
Oct 23 15:35:21 rkdvmso4 kernel: RDX: 0000000000000000 RSI: 0000000000000000 
RDI: 
ffffffff8032aa9c
Oct 23 15:35:21 rkdvmso4 kernel: RBP: ffffffff88284100 R08: ffffffff803a3340 
R09: 
ffffffff88284100
Oct 23 15:35:21 rkdvmso4 kernel: R10: 0000000000000001 R11: 0000000000000000 
R12: 
ffffffff8032de60
Oct 23 15:35:21 rkdvmso4 kernel: R13: ffffffff88284100 R14: ffff880008888488 
R15: 
ffffc20000c65380
Oct 23 15:35:21 rkdvmso4 kernel: FS:  00002b13072976d0(0000) 
GS:ffffffff80421000(0000) knlGS:0000000000000000
Oct 23 15:35:21 rkdvmso4 kernel: CS:  e033 DS: 0000 ES: 0000
Oct 23 15:35:21 rkdvmso4 kernel: Stack: ffffffff8032de60 ffffffff8014591c 
0000000000000000 ffffffff00000016
Oct 23 15:35:21 rkdvmso4 kernel:        ffff88000076a840 0000000000000000 
000000000fcade88 0000000000000000
Oct 23 15:35:21 rkdvmso4 kernel:        0000000000000000 0000000000000000
Oct 23 15:35:21 rkdvmso4 kernel: Call Trace: 
<ffffffff8014591c>{sys_init_module+5615}
Oct 23 15:35:21 rkdvmso4 kernel:        <ffffffff8010aa6a>{system_call+134} 
<ffffffff8010a9e4>{system_call+0}
Oct 23 15:35:21 rkdvmso4 kernel: Code: 0f 0b 68 7d 16 28 88 c2 2b 02 48 2b 15 
ce 
cb 35 f8 48 b8 b7


>>RIP; ffffffff8808e0d1 <_end+7c290d1/7f19b000>   <=====

>>RBX; ffffffff8032dea0 <notify_mutex+0/20>
>>RDI; ffffffff8032aa9c <logbuf_lock+0/4>
>>RBP; ffffffff88284100 <_end+7e1f100/7f19b000>
>>R08; ffffffff803a3340 <__log_buf+0/40000>
>>R09; ffffffff88284100 <_end+7e1f100/7f19b000>
>>R12; ffffffff8032de60 <module_mutex+0/20>
>>R13; ffffffff88284100 <_end+7e1f100/7f19b000>
>>R14; ffff880008888488 <__start___xen_guest+ffff8800084b151e/ffffffff7fd29096>
>>R15; ffffc20000c65380 <__start___xen_guest+ffffc2000088e416/ffffffff7fd29096>

Trace; ffffffff8014591c <sys_init_module+15ef/1795>
Trace; ffffffff8010aa6a <system_call+86/8b>

Code;  ffffffff8808e0d1 <_end+7c290d1/7f19b000>
0000000000000000 <_RIP>:
Code;  ffffffff8808e0d1 <_end+7c290d1/7f19b000>   <=====
   0:   0f 0b                     ud2a      <=====
Code;  ffffffff8808e0d3 <_end+7c290d3/7f19b000>
   2:   68 7d 16 28 88            pushq  $0xffffffff8828167d
Code;  ffffffff8808e0d8 <_end+7c290d8/7f19b000>
   7:   c2 2b 02                  retq   $0x22b
Code;  ffffffff8808e0db <_end+7c290db/7f19b000>
   a:   48 2b 15 ce cb 35 f8      sub    -130692146(%rip),%rdx        # 
fffffffff835cbdf <_RIP+0xfffffffff835cbdf>
Code;  ffffffff8808e0e2 <_end+7c290e2/7f19b000>
  11:   48 b8 b7 00 00 00 00      mov    $0xb7,%rax
Code;  ffffffff8808e0e9 <_end+7c290e9/7f19b000>
  18:   00 00 00

Oct 23 15:35:26 rkdvmso4 kernel: e1000: peth0: e1000_watchdog: NIC Link is Up 
1000 
Mbps Full Duplex

3 warnings issued.  Results may not be reliable.


Is this know already?


Regards,
Ulrich


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