Hi all.
Today I work a lot on a server and, after a shutdown and a startup of a
vm guest, I receive a "kernel crash".
I'm using debian etch for amd64:
srv-xen:~# uname -a
Linux srv-xen 2.6.18-4-xen-vserver-amd64 #1 SMP Fri May 4 03:26:45 UTC
2007 x86_64 GNU/Linux
My server are a Xeon (2 core + 2 HT). Here It's only the first one:
srv-xen:~# cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 15
model : 6
model name : Intel(R) Xeon(TM) CPU 2.66GHz
stepping : 4
cpu MHz : 2660.110
cache size : 2048 KB
physical id : 0
siblings : 1
core id : 0
cpu cores : 1
fpu : yes
fpu_exception : yes
cpuid level : 6
wp : yes
flags : fpu tsc msr pae mce cx8 apic mtrr mca cmov pat pse36
clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall nx lm constant_tsc
pni monitor ds_cpl vmx est cid cx16 xtpr lahf_lm
bogomips : 6652.62
clflush size : 64
cache_alignment : 128
address sizes : 36 bits physical, 48 bits virtual
power management:
This is the log found on kern.log:
Jun 2 18:01:06 srv-xen kernel: device vif7.0 entered promiscuous mode
Jun 2 18:01:06 srv-xen kernel: audit(1180800066.039:24): dev=vif7.0
prom=256 old_prom=0 auid=4294967295
Jun 2 18:01:06 srv-xen kernel: ADDRCONF(NETDEV_UP): vif7.0: link is not
ready
Jun 2 18:01:06 srv-xen kernel: device vif7.1 entered promiscuous mode
Jun 2 18:01:06 srv-xen kernel: audit(1180800066.127:25): dev=vif7.1
prom=256 old_prom=0 auid=4294967295
Jun 2 18:01:06 srv-xen kernel: ADDRCONF(NETDEV_UP): vif7.1: link is not
ready
Jun 2 18:01:07 srv-xen kernel: ADDRCONF(NETDEV_CHANGE): vif7.0: link
becomes ready
Jun 2 18:01:07 srv-xen kernel: ----------- [cut here ] ---------
[please bite here ] ---------
Jun 2 18:01:07 srv-xen kernel: Kernel BUG at drivers/xen/core/evtchn.c:481
Jun 2 18:01:07 srv-xen kernel: invalid opcode: 0000 [1] SMP
Jun 2 18:01:07 srv-xen kernel: CPU 3
Jun 2 18:01:07 srv-xen kernel: Modules linked in: ip_nat_h323
ip_conntrack_h323 ip_nat_irc ip_conntrack_irc ip_nat_tftp
ip_conntrack_tftp ip_nat_sip ip_conntrack_sip ip_nat_ftp
ip_conntrack_ftp iptabl
e_mangle ipt_MASQUERADE iptable_nat ip_nat ipt_LOG ipt_REJECT xt_state
ip_conntrack iptable_filter ip_tables nfnetlink xt_tcpudp xt_physdev
x_tables nfs bridge netloop nfsd exportfs lockd nfs_acl sunrpc
button ac battery ipv6 dm_snapshot dm_mirror dm_mod loop tsdev i2c_i801
shpchp pci_hotplug i2c_core serial_core psmouse serio_raw pcspkr evdev
ext3 jbd mbcache raid1 md_mod ide_generic ide_cd cdrom sd_mo
d piix 8139too generic e100 ide_core ata_piix libata scsi_mod ehci_hcd
uhci_hcd 8139cp mii e1000 fan
Jun 2 18:01:07 srv-xen kernel: Pid: 21, comm: xenwatch Not tainted
2.6.18-4-xen-vserver-amd64 #1
Jun 2 18:01:07 srv-xen kernel: RIP: e030:[<ffffffff8036d28f>]
[<ffffffff8036d28f>] retrigger+0x26/0x3e
Jun 2 18:01:07 srv-xen kernel: RSP: e02b:ffff880074505d88 EFLAGS: 00010046
Jun 2 18:01:07 srv-xen kernel: RAX: 0000000000000000 RBX:
0000000000008880 RCX: ffffffffff578000
Jun 2 18:01:07 srv-xen kernel: RDX: 0000000000000020 RSI:
ffff880074505d30 RDI: 0000000000000111
Jun 2 18:01:07 srv-xen kernel: RBP: ffffffff804dcd00 R08:
00000000000000f7 R09: ffff8800744baa80
Jun 2 18:01:07 srv-xen kernel: R10: ffff880061ec2580 R11:
ffffffff8036d269 R12: 0000000000000111
Jun 2 18:01:07 srv-xen kernel: R13: ffffffff804dcd3c R14:
0000000000000000 R15: 0000000000000009
Jun 2 18:01:07 srv-xen kernel: FS: 00002b4d4228eae0(0000)
GS:ffffffff804d3180(0000) knlGS:0000000000000000
Jun 2 18:01:07 srv-xen kernel: CS: e033 DS: 0000 ES: 0000
Jun 2 18:01:07 srv-xen kernel: Process xenwatch (pid: 21[#0],
threadinfo ffff880074504000, task ffff8800744ed080)
Jun 2 18:01:07 srv-xen kernel: Stack: ffffffff802aadb8
ffff88005a8c9500 ffff88005a8c9500 0000000000000000
Jun 2 18:01:07 srv-xen kernel: ffff880074505de0 000000000000040d
ffffffff80379dfa 0000000000000000
Jun 2 18:01:07 srv-xen kernel: ffffffff8037a272 ffff880074505ea4
Jun 2 18:01:07 srv-xen kernel: Call Trace:
Jun 2 18:01:07 srv-xen kernel: [<ffffffff802aadb8>] enable_irq+0x9d/0xbc
Jun 2 18:01:07 srv-xen kernel: [<ffffffff80379dfa>] __netif_up+0xc/0x15
Jun 2 18:01:07 srv-xen kernel: [<ffffffff8037a272>] netif_map+0x2a6/0x2d8
Jun 2 18:01:07 srv-xen kernel: [<ffffffff80372a7c>]
xenwatch_thread+0x0/0x145
Jun 2 18:01:07 srv-xen kernel: [<ffffffff80372a7c>]
xenwatch_thread+0x0/0x145
Jun 2 18:01:07 srv-xen kernel: [<ffffffff803745bc>]
frontend_changed+0x2ba/0x4f9
Jun 2 18:01:07 srv-xen kernel: [<ffffffff80372a7c>]
xenwatch_thread+0x0/0x145
Jun 2 18:01:07 srv-xen kernel: [<ffffffff80293243>]
keventd_create_kthread+0x0/0x64
Jun 2 18:01:07 srv-xen kernel: [<ffffffff80371e8a>]
xenwatch_handle_callback+0x15/0x48
Jun 2 18:01:07 srv-xen kernel: [<ffffffff80372ba9>]
xenwatch_thread+0x12d/0x145
Jun 2 18:01:07 srv-xen kernel: [<ffffffff80293409>]
autoremove_wake_function+0x0/0x2e
Jun 2 18:01:07 srv-xen kernel: [<ffffffff80293243>]
keventd_create_kthread+0x0/0x64
Jun 2 18:01:07 srv-xen kernel: [<ffffffff80372a7c>]
xenwatch_thread+0x0/0x145
Jun 2 18:01:07 srv-xen kernel: [<ffffffff80234393>] kthread+0xd4/0x107
Jun 2 18:01:07 srv-xen kernel: [<ffffffff8025f694>] child_rip+0xa/0x12
Jun 2 18:01:07 srv-xen kernel: [<ffffffff80293243>]
keventd_create_kthread+0x0/0x64
Jun 2 18:01:07 srv-xen kernel: [<ffffffff8024b263>] worker_thread+0x0/0x122
Jun 2 18:01:07 srv-xen kernel: [<ffffffff8024b263>] worker_thread+0x0/0x122
Jun 2 18:01:07 srv-xen kernel: [<ffffffff802342bf>] kthread+0x0/0x107
Jun 2 18:01:07 srv-xen kernel: [<ffffffff8025f68a>] child_rip+0x0/0x12
Jun 2 18:01:07 srv-xen kernel:
Jun 2 18:01:07 srv-xen kernel:
Jun 2 18:01:07 srv-xen kernel: Code: 0f 0b 68 f0 b4 42 80 c2 e1 01 f0
0f ab 91 00 08 00 00 b8 01
Jun 2 18:01:07 srv-xen kernel: RIP [<ffffffff8036d28f>]
retrigger+0x26/0x3e
Jun 2 18:01:07 srv-xen kernel: RSP <ffff880074505d88>
And now? :)
Thanks,
Michele
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
| 
Home