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-users

[Xen-users] Kernel Bug

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Kernel Bug
From: Pedro Rafael Alves Simoes <pedro.a.simoes@xxxxxxxxx>
Date: Thu, 26 Mar 2009 16:53:33 +0000
Delivery-date: Thu, 26 Mar 2009 09:54:15 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type:content-transfer-encoding; bh=u1kGa7WwUyYmhcuXCh14T9DA+60GgLUKbA2iXYC4CPE=; b=JUuO+bpEqsDovLXItUZP8D+sddPDWYUUezaf96wm2sS1z7/Np1+VD9PJIqgFZirgSf q8HyIWZM+jJnMTKPcezYBgq+Rf+JqfNX5YEM1mZOkTCkMzg1V9qQxMGZ1EDu9+zdKCO1 k0cbbzcuuMu7l2VrO4Iqlyu4vnELAXK0M9aN0=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=TREfziplMtVrORHzHLSsxSMfzVsAlq75qw73mf8T52qieFN/fniHaQYk0ofUcikT+7 C9rlHjZCTT2rwM7mfLTPTFv1JdC8yD+Q12FxJ+/WTDYNTROUxIz4JFtEu3hXeygx2eyN FtQoyjCujYG8/q6N9PrRn1qKodIFsJlSv7T7I=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Hello,

I have a Debian Etch host machine with Xen Hypervisor 3.0.3 PAE and
Xen kernel 2.6.18. The machine is a Dell with Intel Xeon dual core and
4gb of RAM. This is my xm list:

Name                                      ID Mem(MiB) VCPUs State   Time(s)
Domain-0                                   0      256     2 r-----     36.0
fe-backup                                  2      768     2 -b----     45.8

After doing xm create -c /etc/xen/guest2 with confile:

kernel = "/boot/vmlinuz-2.6.18-5-xen-686"
ramdisk = "/boot/initrd.img-2.6.18-5-xen-686"
memory = 768
name = "esper"
vcpus = 2
#bootloader = '/usr/lib/xen-3.0.3-1/bin/pygrub'
disk = 
['phy:/dev/virtua/be-backup-disk,hda1,w','phy:/dev/virtua/be-backup-swap,hda2,w']
root = "/dev/hda1 ro"
#extra = "4"

# Network
vif = ['mac=00:16:3E:36:78:F0,bridge=xenbr0']
#dhcp = "on"

the host machine dies. After the reboot, I've checked the
/var/log/syslog and saw this output:

Mar 26 15:42:43 xenserver-backup kernel: ------------[ cut here ]------------
Mar 26 15:42:43 xenserver-backup kernel: kernel BUG at
drivers/xen/core/evtchn.c:481!
Mar 26 15:42:43 xenserver-backup kernel: invalid opcode: 0000 [#1]
Mar 26 15:42:43 xenserver-backup kernel: SMP
Mar 26 15:42:43 xenserver-backup kernel: Modules linked in: tun
xt_physdev iptable_filter ip_tables x_tables bridge netloop button ac
battery ipv6 dm_snapshot
 dm_mirror dm_mod sg loop evdev serio_raw shpchp pci_hotplug psmouse
pcspkr serial_core i2c_i801 i2c_core rtc ext3 jbd mbcache sd_mod
ide_cd cdrom generic mpt
sas mptscsih mptbase scsi_transport_sas scsi_mod uhci_hcd tg3 piix
ide_core ehci_hcd usbcore thermal processor fan
Mar 26 15:42:43 xenserver-backup kernel: CPU:    1
Mar 26 15:42:43 xenserver-backup kernel: EIP:    0061:[<c020c3be>]
Not tainted VLI
Mar 26 15:42:43 xenserver-backup kernel: EFLAGS: 00010046
(2.6.18-5-xen-686 #1)
Mar 26 15:42:43 xenserver-backup kernel: EIP is at retrigger+0x1f/0x35
Mar 26 15:42:43 xenserver-backup kernel: eax: 00000000   ebx: 02080000
  ecx: 00000019   edx: f55f6000
Mar 26 15:42:43 xenserver-backup kernel: esi: c0318460   edi: 0000010a
  ebp: 00000000   esp: c039deb0
Mar 26 15:42:43 xenserver-backup kernel: ds: 007b   es: 007b   ss: 0069
Mar 26 15:42:43 xenserver-backup kernel: Process xenwatch (pid: 11,
ti=c039c000 task=c0d9d000 task.ti=c039c000)
Mar 26 15:42:43 xenserver-backup kernel: Stack: c013b225 c0318460
0000010a c0318488 c013af79 cb3caec0 00000000 00000000
Mar 26 15:42:43 xenserver-backup kernel: cb3caec0 c0217364 00000000
c0217744 c02108d3 00000010 00000000 0000020b
Mar 26 15:42:43 xenserver-backup kernel: 0000020a 00000000 00000000
cd32f376 c02e67a4 d12ea000 00000000 00000002
Mar 26 15:42:43 xenserver-backup kernel: Call Trace:
Mar 26 15:42:43 xenserver-backup kernel: [<c013b225>] check_irq_resend+0x41/0x48
Mar 26 15:42:43 xenserver-backup kernel: [<c013af79>] enable_irq+0x72/0x89
Mar 26 15:42:43 xenserver-backup kernel: [<c0217364>] __netif_up+0xb/0x13
Mar 26 15:42:43 xenserver-backup kernel: [<c0217744>] netif_map+0x247/0x26f
Mar 26 15:42:43 xenserver-backup kernel: [<c02108d3>] xs_talkv+0xe3/0x128
Mar 26 15:42:43 xenserver-backup kernel: [<c0210c1c>] xenbus_read+0x34/0x3b
Mar 26 15:42:43 xenserver-backup kernel: [<c0210fde>] xenbus_scanf+0x18/0x4d
Mar 26 15:42:43 xenserver-backup kernel: [<c0216dd5>]
frontend_changed+0x29f/0x4a8
Mar 26 15:42:43 xenserver-backup kernel: [<c0211fbc>] otherend_changed+0x74/0x79
Mar 26 15:42:43 xenserver-backup kernel: [<c0210756>]
xenwatch_handle_callback+0x12/0x44
Mar 26 15:42:43 xenserver-backup kernel: [<c021119b>]
xenwatch_thread+0x105/0x11b
Mar 26 15:42:43 xenserver-backup kernel: [<c012b6f9>]
autoremove_wake_function+0x0/0x2d
Mar 26 15:42:43 xenserver-backup kernel: [<c0211096>] xenwatch_thread+0x0/0x11b
Mar 26 15:42:43 xenserver-backup kernel: [<c012b62d>] kthread+0xc0/0xeb
Mar 26 15:42:43 xenserver-backup kernel: [<c012b56d>] kthread+0x0/0xeb
Mar 26 15:42:43 xenserver-backup kernel: [<c010293d>]
kernel_thread_helper+0x5/0xb
Mar 26 15:42:43 xenserver-backup kernel: Code: ee 85 f6 75 96 58 5a 5b
5e 5f 5d c3 0f b7 0c 85 40 b8 37 c0 8b 15 84 19 2d c0 85 c9 74 1d 0f
a3 8a 80 08 00 00
19 c0 85 c0 75 08 <0f> 0b e1 01 92 1a 2b c0 f0 0f ab 8a 00 08 00 00 b8
01 00 00 00
Mar 26 15:42:43 xenserver-backup kernel: EIP: [<c020c3be>]
retrigger+0x1f/0x35 SS:ESP 0069:c039deb0

Any idea what was the problem?

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

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] Kernel Bug, Pedro Rafael Alves Simoes <=