Kernel BUG at drivers/xen/core/evtchn.c:481
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
xen-source (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: xen-image-
Using Gutsy with Ubuntu kernel xen-image-
I've now seen it crash like this twice (doesn't happen every time). See dmesg output below.
Result of this is a machine that doesn't work and must be rebooted.
[ 42.182170] device vif1.0 entered promiscuous mode
[ 42.182186] audit(119141403
[ 42.185784] ADDRCONF(
[ 50.160007] xenbr0: no IPv6 routers present
[ 53.372088] ----------- [cut here ] --------- [please bite here ] ---------
[ 53.372098] Kernel BUG at drivers/
[ 53.372102] invalid opcode: 0000 [1] SMP
[ 53.372106] CPU 1
[ 53.372108] Modules linked in: af_packet loop ppdev tun ip6table_filter ip6_tables iptable_raw xt_comment xt_policy xt_multiport ipt_ULOG ipt_TTL ipt_ttl ipt_TOS ipt_tos ipt_TCPMSS ipt_SAME ipt_REJECT ipt_REDIRECT ipt_recent ipt_owner ipt_NETMAP ipt_MASQUERADE ipt_LOG ipt_iprange ipt_hashlimit ipt_ECN ipt_ecn ipt_CLUSTERIP ipt_ah ipt_addrtype ip_nat_tftp ip_nat_snmp_basic ip_nat_pptp ip_nat_irc ip_nat_h323 ip_nat_ftp ip_nat_amanda ip_conntrack_tftp ip_conntrack_pptp ip_conntrack_
[ 53.372211] Pid: 21, comm: xenwatch Not tainted 2.6.19-
[ 53.372215] RIP: e030:[<
[ 53.372227] RSP: e02b:ffff880001
[ 53.372231] RAX: 0000000000000000 RBX: 0000000000008800 RCX: ffffffffff578000
[ 53.372235] RDX: 000000000000001f RSI: ffff880001ac7cd0 RDI: 0000000000000110
[ 53.372239] RBP: 0000000000000110 R08: 0000000000000000 R09: 0000000000000001
[ 53.372244] R10: ffff8800758da2c0 R11: ffffffff8038fce0 R12: ffffffff80544080
[ 53.372249] R13: ffffffff805440bc R14: 0000000000000000 R15: ffff880001ac7da0
[ 53.372257] FS: 000000000000000
[ 53.372261] CS: e033 DS: 0000 ES: 0000 CR0: 000000008005003b
[ 53.372264] CR2: 0000000000000000 CR3: 000000006c5ce000 CR4: 0000000000000660
[ 53.372269] Process xenwatch (pid: 21, threadinfo ffff880001ac6000, task ffff880001b00180)
[ 53.372273] Stack: ffffffff802b70c0 ffff88000131b500 ffff88000131b500 0000000000000000
[ 53.372282] 000000000000020b 0000000000000008 ffffffff803a0cec 0000000000000000
[ 53.372289] ffffffff803a121e ffff880001ac7e7c 0000000000000000 0000000000000000
[ 53.372295] Call Trace:
[ 53.372301] [<ffffffff802b7
[ 53.372314] [<ffffffff803a0
[ 53.372320] [<ffffffff803a1
[ 53.372336] [<ffffffff80268
[ 53.372342] [<ffffffff80398
[ 53.372347] [<ffffffff80427
[ 53.372362] [<ffffffff802a2
[ 53.372368] [<ffffffff803a0
[ 53.372388] [<ffffffff80396
[ 53.372394] [<ffffffff802a2
[ 53.372400] [<ffffffff80395
[ 53.372406] [<ffffffff80396
[ 53.372413] [<ffffffff802a2
[ 53.372421] [<ffffffff802a2
[ 53.372428] [<ffffffff80236
[ 53.372435] [<ffffffff8022a
[ 53.372444] [<ffffffff80266
[ 53.372450] [<ffffffff802a2
[ 53.372469] [<ffffffff80236
[ 53.372475] [<ffffffff80266
[ 53.372482]
[ 53.372484]
[ 53.372485] Code: 0f 0b 68 11 34 46 80 c2 e1 01 f0 0f ab 91 00 08 00 00 b8 01
[ 53.372500] RIP [<ffffffff8038f
[ 53.372507] RSP <ffff880001ac7d38>
[ 53.372510] <6>Capability LSM initialized
Got the same on kernel 2.6.19-4-server #2 SMP i686. Here's what I did: prolo1: ~$ sudo xm create /etc/xen/ sysadmin. cfg sysadmin. cfg". prolo1: ~$ sudo xm list prolo1: ~$ sudo /etc/init.d/xend prolo1: ~$ sudo /etc/init. d/xendomains restart save).. .Error: Device 0 not connected d/xendomains: line 264: 5217 Terminated watchdog_xm shutdown 1 xen/core/ evtchn. c:481! vector+ 0x3e/0x50 resend+ 0x61/0x70 irq+0xc5/ 0xd0 0x26f/0x2e0 0x1fd/0x520 changed+ 0xaf/0xc0 handle_ callback+ 0x1a/0x60 thread+ 0x11d/0x130 thread_ helper+ 0x7/0x10 ======= ======= == vector+ 0x3e/0x50 SS:ESP 0069:ed7bfe60
shuerlimann@
Using config file "/etc/xen/
Started domain sysadmin
shuerlimann@
Name ID Mem(MiB) VCPUs State Time(s)
Domain-0 0 1893 2 r----- 39.1
sysadmin 2 128 1 r----- 4.1
shuerlimann@
xend xendomains
shuerlimann@
Shutting down Xen domains: sysadmin(
SHUTDOWN_ALL .All domains terminated
/etc/init.
Restoring Xen domains: sysadminl prolo1 kernel: [ 1100.910599] ------------[ cut here ]------------
prolo1 kernel: [ 1100.910983] kernel BUG at drivers/
prolo1 kernel: [ 1100.911218] invalid opcode: 0000 [#1]
prolo1 kernel: [ 1100.911426] SMP
prolo1 kernel: [ 1100.912389] CPU: 1
prolo1 kernel: [ 1100.912391] EIP: 0061:[<c0247cce>] Not tainted VLI
prolo1 kernel: [ 1100.912394] EFLAGS: 00010046 (2.6.19-4-server #2)
prolo1 kernel: [ 1100.913007] EIP is at retrigger_
prolo1 kernel: [ 1100.913223] eax: 00000000 ebx: 02080000 ecx: f5746000 edx: 00000017
prolo1 kernel: [ 1100.913330] esi: c03dd900 edi: 0000010a ebp: 00000000 esp: ed7bfe60
prolo1 kernel: [ 1100.913436] ds: 007b es: 007b ss: 0069
prolo1 kernel: [ 1100.913524] Process xenwatch (pid: 13, ti=ed7be000 task=c14fb560 task.ti=ed7be000)
prolo1 kernel: [ 1100.913632] Stack: c014b691 c03dd900 0000010a c03dd928 c014b355 c0131aee 00000000 00000001
prolo1 kernel: [ 1100.913820] 00000001 e5890c00 00000000 ed7bfefc e5890c00 c0257ecb 00000000 c025834f
prolo1 kernel: [ 1100.914203] e5890800 e5890c00 e6cb9ba0 00000002 00000000 00000000 ed7bfefc ed7bfec0
prolo1 kernel: [ 1100.914601] Call Trace:
prolo1 kernel: [ 1100.915824] [<c014b691>] check_irq_
prolo1 kernel: [ 1100.916293] [<c014b355>] enable_
prolo1 kernel: [ 1100.916751] [<c0257ecb>] __netif_up+0xb/0x20
prolo1 kernel: [ 1100.917839] [<c025834f>] netif_map+
prolo1 kernel: [ 1100.918907] [<c02573bd>] maybe_connect+
prolo1 kernel: [ 1100.919994] [<c024f2cf>] otherend_
prolo1 kernel: [ 1100.921066] [<c024d28a>] xenwatch_
prolo1 kernel: [ 1100.922160] [<c024e00d>] xenwatch_
prolo1 kernel: [ 1100.923242] [<c0135336>] kthread+0xf6/0x100
prolo1 kernel: [ 1100.923637] [<c0105367>] kernel_
prolo1 kernel: [ 1100.923908] =======
prolo1 kernel: [ 1100.924142] Code: b8 01 00 00 00 c3 8d b4 26 00 00 00 00 0f b7 d0 0f a3 91 80 08 00 00 19 c0 85 c0 74 0e f0 0f ab 91 00 08 00 00 b8 01 00 00 00 c3 <0f> 0b e1 01 e9 8f 32 c0 eb e8 90 8d b4 26 00 00 00 00 0f b7 04
prolo1 kernel: [ 1100.925282] EIP: [<c0247cce>] retrigger_
webmaster1Error: Restore failed
Usa...