Bug#614400: linux-image-2.6.32-5-xen-amd64: Kernel Crash when initiating lvcreate or lvremove actions
Package: linux-2.6
Version: 2.6.32-30
Severity: important
Tags: upstream
-- Package-specific info:
** Version:
Linux version 2.6.32-5-xen-amd64 (Debian 2.6.32-30) (ben@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Wed Jan 12 05:46:49 UTC 2011
** Command line:
placeholder root=/dev/mapper/svd--xen-root ro bootkbd=de quiet
** Not tainted
** Kernel log:
[ 15.386844] XENBUS: Unable to read cpu state
[ 15.386923] XENBUS: Unable to read cpu state
[ 15.387002] XENBUS: Unable to read cpu state
[ 15.387077] XENBUS: Unable to read cpu state
[ 15.387151] XENBUS: Unable to read cpu state
[ 15.387240] XENBUS: Unable to read cpu state
[ 15.387318] XENBUS: Unable to read cpu state
[ 15.387436] XENBUS: Unable to read cpu state
[ 17.344354] lp: driver loaded but no devices found
[ 17.359176] ppdev: user-space parallel port driver
[ 17.563552] Bridge firewalling registered
[ 17.637327] bonding: bond0: Warning: the permanent HWaddr of eth0 - 00:25:90:1d:2f:ba - is still in use by bond0. Set the HWaddr of eth0 to a different address to avoid conflicts.
[ 17.637340] bonding: bond0: releasing active interface eth0
[ 17.891097] bonding: bond0: Removing an active aggregator
[ 17.891105] bonding: bond0: releasing active interface eth1
[ 18.306195] ADDRCONF(NETDEV_UP): pbond0: link is not ready
[ 18.340291] bonding: pbond0: enslaving eth0 as a backup interface with a down link.
[ 18.388221] bonding: pbond0: enslaving eth1 as a backup interface with a down link.
[ 18.598457] Ebtables v2.0 registered
[ 18.654382] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 18.696050] ip6_tables: (C) 2000-2006 Netfilter Core Team
[ 19.407044] lo: Disabled Privacy Extensions
[ 20.590251] igb: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
[ 20.608443] bonding: pbond0: link status up for interface eth0, enabling it in 0 ms.
[ 20.608448] bonding: pbond0: link status definitely up for interface eth0.
[ 20.610569] ADDRCONF(NETDEV_CHANGE): pbond0: link becomes ready
[ 20.852133] igb: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
[ 20.904417] bonding: pbond0: link status up for interface eth1, enabling it in 200 ms.
[ 21.103392] bonding: pbond0: link status definitely up for interface eth1.
[ 21.425038] device pbond0 entered promiscuous mode
[ 21.425044] device eth0 entered promiscuous mode
[ 21.425128] device eth1 entered promiscuous mode
[ 21.444654] CPU0 attaching NULL sched-domain.
[ 21.444660] CPU1 attaching NULL sched-domain.
[ 21.444663] CPU2 attaching NULL sched-domain.
[ 21.444666] CPU3 attaching NULL sched-domain.
[ 21.444669] CPU4 attaching NULL sched-domain.
[ 21.444672] CPU5 attaching NULL sched-domain.
[ 21.444675] CPU6 attaching NULL sched-domain.
[ 21.444678] CPU7 attaching NULL sched-domain.
[ 21.447566] bond0: port 1(pbond0) entering forwarding state
[ 21.479755] CPU0 attaching sched-domain:
[ 21.479758] domain 0: span 0-7 level CPU
[ 21.479761] groups: 0 1 2 3 4 5 6 7
[ 21.479772] CPU1 attaching sched-domain:
[ 21.479774] domain 0: span 0-7 level CPU
[ 21.479776] groups: 1 2 3 4 5 6 7 0
[ 21.479785] CPU2 attaching sched-domain:
[ 21.479787] domain 0: span 0-7 level CPU
[ 21.479789] groups: 2 3 4 5 6 7 0 1
[ 21.479798] CPU3 attaching sched-domain:
[ 21.479800] domain 0: span 0-7 level CPU
[ 21.479803] groups: 3 4 5 6 7 0 1 2
[ 21.479812] CPU4 attaching sched-domain:
[ 21.479814] domain 0: span 0-7 level CPU
[ 21.479816] groups: 4 5 6 7 0 1 2 3
[ 21.479825] CPU5 attaching sched-domain:
[ 21.479827] domain 0: span 0-7 level CPU
[ 21.479829] groups: 5 6 7 0 1 2 3 4
[ 21.479838] CPU6 attaching sched-domain:
[ 21.479840] domain 0: span 0-7 level CPU
[ 21.479842] groups: 6 7 0 1 2 3 4 5
[ 21.479851] CPU7 attaching sched-domain:
[ 21.479853] domain 0: span 0-7 level CPU
[ 21.479856] groups: 7 0 1 2 3 4 5 6
[ 23.149533] pbond0: received packet with own address as source address
[ 23.453559] pbond0: received packet with own address as source address
[ 23.560897] pbond0: received packet with own address as source address
[ 23.560935] pbond0: received packet with own address as source address
[ 23.580242] pbond0: received packet with own address as source address
[ 23.591635] pbond0: received packet with own address as source address
[ 23.811365] pbond0: received packet with own address as source address
[ 23.811382] pbond0: received packet with own address as source address
[ 24.064896] pbond0: received packet with own address as source address
[ 24.065010] pbond0: received packet with own address as source address
[ 27.047316] alloc irq_desc for 2226 on node -1
[ 27.047320] alloc kstat_irqs on node -1
[ 27.238611] device vif1.0 entered promiscuous mode
[ 27.242454] bond0: port 2(vif1.0) entering forwarding state
[ 27.266928] alloc irq_desc for 2225 on node -1
[ 27.266931] alloc kstat_irqs on node -1
[ 27.288264] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
[ 27.289132] CONFIG_NF_CT_ACCT is deprecated and will be removed soon. Please use
[ 27.289135] nf_conntrack.acct=1 kernel parameter, acct=1 nf_conntrack module option or
[ 27.289138] sysctl net.netfilter.nf_conntrack_acct=1 to enable it.
[ 27.295724] physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore.
[ 27.310668] physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore.
[ 27.313442] physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore.
[ 27.313449] physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore.
[ 27.807743] blkback: ring-ref 8, event-channel 8, protocol 1 (x86_64-abi)
[ 27.807782] alloc irq_desc for 2224 on node -1
[ 27.807784] alloc kstat_irqs on node -1
[ 27.822009] blkback: ring-ref 9, event-channel 9, protocol 1 (x86_64-abi)
[ 27.822027] alloc irq_desc for 2223 on node -1
[ 27.822029] alloc kstat_irqs on node -1
[ 27.845195] alloc irq_desc for 2222 on node -1
[ 27.845197] alloc kstat_irqs on node -1
[ 31.271373] pbond0: no IPv6 routers present
[ 32.383491] bond0: no IPv6 routers present
[ 37.631446] vif1.0: no IPv6 routers present
** Model information
sys_vendor: Supermicro
product_name: X8DT3
product_version: 1234567890
chassis_vendor: Supermicro
chassis_version: 1234567890
bios_vendor: American Megatrends Inc.
bios_version: 2.0a
board_vendor: Supermicro
board_name: X8DT3
board_version: 2.0
** Loaded modules:
Module Size Used by
xt_tcpudp 2319 1
nf_conntrack_ipv4 9833 2
nf_defrag_ipv4 1139 1 nf_conntrack_ipv4
xt_state 1303 2
nf_conntrack 46519 2 nf_conntrack_ipv4,xt_state
xt_physdev 1508 4
ip6table_filter 2384 0
ip6_tables 15075 1 ip6table_filter
iptable_filter 2258 1
ip_tables 13899 1 iptable_filter
ebtable_nat 1588 0
ebtables 13933 1 ebtable_nat
x_tables 12845 6 xt_tcpudp,xt_state,xt_physdev,ip6_tables,ip_tables,ebtables
bridge 39662 0
stp 1440 1 bridge
parport_pc 18855 0
ppdev 5030 0
lp 7462 0
parport 27954 3 parport_pc,ppdev,lp
cpufreq_powersave 902 0
cpufreq_stats 2659 0
cpufreq_userspace 1992 0
cpufreq_conservative 5162 0
xen_evtchn 4339 2
xenfs 9600 1
fuse 50625 1
bonding 74103 0
ext2 52969 1
loop 11799 0
i2c_i801 7830 0
i2c_core 15712 1 i2c_i801
psmouse 49777 0
pcspkr 1699 0
serio_raw 3752 0
evdev 7352 11
ioatdma 34876 48
button 4650 0
processor 35941 0
acpi_processor 5087 1 processor,[permanent]
ext3 106502 5
jbd 37085 1 ext3
mbcache 5050 2 ext2,ext3
dm_snapshot 18481 6
dm_mod 53754 51 dm_snapshot
sg 18760 0
sr_mod 12602 0
cdrom 29415 1 sr_mod
sd_mod 29873 3
crc_t10dif 1276 1 sd_mod
usbhid 33276 0
hid 63225 1 usbhid
uhci_hcd 18521 0
ahci 32374 0
ehci_hcd 31151 0
libata 133632 1 ahci
usbcore 122034 4 usbhid,uhci_hcd,ehci_hcd
nls_base 6377 1 usbcore
aacraid 59763 2
scsi_mod 122133 5 sg,sr_mod,sd_mod,libata,aacraid
thermal 11674 0
igb 77991 0
thermal_sys 11942 2 processor,thermal
dca 3761 2 ioatdma,igb
** Network interface configuration:
auto lo
iface lo inet loopback
auto bond0
iface bond0 inet static
up /sbin/ifenslave bond0 eth0 eth1
down /sbin/ifenslave -d bond0 eth0 eth1
address 192.168.161.223
netmask 255.255.255.0
network 192.168.161.0
gateway 192.168.161.115
bond_miimon 100
bond_downdelay 200
bond_updelay 200
** Network status:
*** IP interfaces and addresses:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master pbond0 state UP qlen 1000
link/ether 00:25:90:1d:2f:ba brd ff:ff:ff:ff:ff:ff
3: eth1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master pbond0 state UP qlen 1000
link/ether 00:25:90:1d:2f:ba brd ff:ff:ff:ff:ff:ff
4: pbond0: <BROADCAST,MULTICAST,PROMISC,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP
link/ether 00:25:90:1d:2f:ba brd ff:ff:ff:ff:ff:ff
inet6 fe80::225:90ff:fe1d:2fba/64 scope link
valid_lft forever preferred_lft forever
5: bond0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN
link/ether 00:25:90:1d:2f:ba brd ff:ff:ff:ff:ff:ff
inet 192.168.161.223/24 brd 192.168.161.255 scope global bond0
inet6 fe80::225:90ff:fe1d:2fba/64 scope link
valid_lft forever preferred_lft forever
7: vif1.0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 32
link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
inet6 fe80::fcff:ffff:feff:ffff/64 scope link
valid_lft forever preferred_lft forever
*** Device statistics:
Inter-| Receive | Transmit
face |bytes packets errs drop fifo frame compressed multicast|bytes packets errs drop fifo colls carrier compressed
lo: 560 8 0 0 0 0 0 0 560 8 0 0 0 0 0 0
eth0: 1262544 7623 0 0 0 0 0 4957 684252 5535 0 0 0 0 0 0
eth1: 1065613 8523 0 0 0 0 0 5689 881946 5177 0 0 0 0 0 0
pbond0: 2328157 16146 0 0 0 0 0 10646 1566198 10712 0 0 0 0 0 0
bond0: 795180 6745 0 0 0 0 0 5369 151186 1217 0 0 0 0 0 0
vif1.0: 325734 815 0 0 0 0 0 0 1119314 6090 0 9 0 0 0 0
*** Protocol statistics:
Ip:
4097 total packets received
0 forwarded
0 incoming packets discarded
2169 incoming packets delivered
1085 requests sent out
4 reassemblies required
2 packets reassembled ok
2 fragments received ok
4 fragments created
Icmp:
2 ICMP messages received
0 input ICMP message failed.
ICMP input histogram:
echo replies: 2
8 ICMP messages sent
0 ICMP messages failed
ICMP output histogram:
destination unreachable: 6
echo request: 2
IcmpMsg:
InType0: 2
OutType3: 6
OutType8: 2
Tcp:
3 active connections openings
2 passive connection openings
0 failed connection attempts
0 connection resets received
2 connections established
1291 segments received
1022 segments send out
0 segments retransmited
0 bad segments received.
3 resets sent
Udp:
78 packets received
6 packets to unknown port received.
0 packet receive errors
50 packets sent
UdpLite:
TcpExt:
2 TCP sockets finished time wait in fast timer
29 delayed acks sent
3 packets directly queued to recvmsg prequeue.
1 bytes directly received in process context from prequeue
336 packet headers predicted
405 acknowledgments not containing data payload received
1 predicted acknowledgments
IpExt:
InMcastPkts: 52
OutMcastPkts: 29
InBcastPkts: 792
InOctets: 671253
OutOctets: 129873
InMcastOctets: 11173
OutMcastOctets: 5094
InBcastOctets: 102272
*** Device features:
bond0: 0x111833
bonding_masters:
-- System Information:
Debian Release: 6.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-5-xen-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages linux-image-2.6.32-5-xen-amd64 depends on:
ii debconf [debconf-2.0] 1.5.36.1 Debian configuration management sy
ii initramfs-tools 0.98.8 tools for generating an initramfs
ii linux-base 2.6.32-30 Linux image base package
ii module-init-tools 3.12-1 tools for managing Linux kernel mo
Versions of packages linux-image-2.6.32-5-xen-amd64 recommends:
ii firmware-linux-free 2.6.32-30 Binary firmware for various driver
Versions of packages linux-image-2.6.32-5-xen-amd64 suggests:
pn grub <none> (no description available)
pn linux-doc-2.6.32 <none> (no description available)
Versions of packages linux-image-2.6.32-5-xen-amd64 is related to:
pn firmware-bnx2 <none> (no description available)
pn firmware-bnx2x <none> (no description available)
pn firmware-ipw2x00 <none> (no description available)
pn firmware-ivtv <none> (no description available)
pn firmware-iwlwifi <none> (no description available)
pn firmware-linux <none> (no description available)
pn firmware-linux-nonfree <none> (no description available)
pn firmware-qlogic <none> (no description available)
pn firmware-ralink <none> (no description available)
ii xen-hypervisor-4.0-amd64 [xen 4.0.1-2 The Xen Hypervisor on AMD64
-- debconf information:
linux-image-2.6.32-5-xen-amd64/postinst/ignoring-do-bootloader-2.6.32-5-xen-amd64:
linux-image-2.6.32-5-xen-amd64/prerm/removing-running-kernel-2.6.32-5-xen-amd64: true
linux-image-2.6.32-5-xen-amd64/postinst/depmod-error-initrd-2.6.32-5-xen-amd64: false
linux-image-2.6.32-5-xen-amd64/postinst/missing-firmware-2.6.32-5-xen-amd64:
Creating and afterwards deleting snapshots of logical volumes crashes the system.
I can do the following commands only twice, max. three times, before the server crashes.
lvcreate -s -L 10G some_vg/some_lv -n snap_some_vg_some_lv lvremove /dev/some_vg/some_lv -f
Here ist the output of /var/log/messages
Result:
---------------------------------------------------------------------------------------------------
Message from syslogd@svd-xen at Feb 21 14:32:33 ...
kernel:[22916.840309] ------------[ cut here ]------------
Message from syslogd@svd-xen at Feb 21 14:32:33 ...
kernel:[22916.840323] invalid opcode: 0000 [#2] SMP
Message from syslogd@svd-xen at Feb 21 14:32:33 ...
kernel:[22916.840329] last sysfs file: /sys/devices/pci0000:00/0000:00:1f.2/host1/target1:0:0/1:0:0:0/block/sdb/sdb1/alignment_offset
Message from syslogd@svd-xen at Feb 21 14:32:33 ...
kernel:[22916.840488] Stack:
Message from syslogd@svd-xen at Feb 21 14:32:33 ...
kernel:[22916.840512] Call Trace:
Message from syslogd@svd-xen at Feb 21 14:32:33 ...
kernel:[22916.840549] Code: ec 28 89 3c 24 48 89 f7 e8 a2 fd ff ff 48 89 e7 48 89 44 24 08 be 01 00 00 00 31 d2 41 ba f0 7f 00 00 e8 b0 cc ff ff 85 c0 74 04 <0f> 0b eb fe 48 83 c4 28 c3 55 49 89 ca 48 89 d5 40 88 f1 48 89
---------------------------------------------------------------------------------------------------
Here some lines from syslog:
--------------------------------------------------------------------------------------------------
Feb 21 14:44:33 svd-xen kernel: [23636.279456] CPU 4:
Feb 21 14:44:33 svd-xen kernel: [23636.279458] Modules linked in: xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 xt_state nf_conntrack xt_physdev ip6table_filter ip6_tables iptable_filter ip_tables ebtable_nat ebtables x_tables bridge stp parport_pc ppdev lp parport cpufreq_powersave cpufreq_stats cpufreq_userspace cpufreq_conservative xen_evtchn xenfs fuse bonding ext2 loop evdev i2c_i801 psmouse i2c_core pcspkr serio_raw ioatdma button processor acpi_processor ext3 jbd mbcache dm_snapshot dm_mod sg sr_mod cdrom sd_mod crc_t10dif usbhid hid uhci_hcd ahci ehci_hcd libata usbcore nls_base aacraid scsi_mod thermal igb dca thermal_sys [last unloaded: scsi_wait_scan]
Feb 21 14:44:33 svd-xen kernel: [23636.279508] Pid: 6881, comm: udisks-dm-expor Tainted: G D 2.6.32-5-xen-amd64 #1 X8DT3
Feb 21 14:44:33 svd-xen kernel: [23636.279510] RIP: e030:[<ffffffff8130cb1b>] [<ffffffff8130cb1b>] _spin_lock+0x18/0x1b Feb 21 14:44:33 svd-xen kernel: [23636.279516] RSP: e02b:ffff88059ad21b10 EFLAGS: 00000297 Feb 21 14:44:33 svd-xen kernel: [23636.279518] RAX: 0000000000000027 RBX: ffff88059ad21b28 RCX: ffff88059ad21b68 Feb 21 14:44:33 svd-xen kernel: [23636.279520] RDX: 0000000000000026 RSI: 0000000000000200 RDI: ffff8805dc0db180 Feb 21 14:44:33 svd-xen kernel: [23636.279522] RBP: 0000000000000200 R08: 0000000000000008 R09: ffffffff814eb870 Feb 21 14:44:33 svd-xen kernel: [23636.279524] R10: 000000000000000b R11: 00000000000186a0 R12: ffff8805dc0db100 Feb 21 14:44:33 svd-xen kernel: [23636.279526] R13: 000000000000c580 R14: ffff88059ad21b28 R15: ffffffff814eb830 Feb 21 14:44:33 svd-xen kernel: [23636.279531] FS: 00007feca22657a0(0000) GS:ffff88001c6c2000(0000) knlGS:0000000000000000 Feb 21 14:44:33 svd-xen kernel: [23636.279533] CS: e033 DS: 0000 ES: 0000 CR0: 00000000
8005003b Feb 21 14:44:33 svd-xen kernel: [23636.279535] CR2: 00007feca1c043c0 CR3: 0000000001001000 CR4: 0000000000002660 Feb 21 14:44:33 svd-xen kernel: [23636.279537] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Feb 21 14:44:33 svd-xen kernel: [23636.279539] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 Feb 21 14:44:33 svd-xen kernel: [23636.279541] Call Trace:
Feb 21 14:44:33 svd-xen kernel: [23636.279545] [<ffffffff8100dd87>] ? xen_exit_mmap+0xf8/0x136 Feb 21 14:44:33 svd-xen kernel: [23636.279548] [<ffffffff810d1208>] ? exit_mmap+0x5a/0x148 Feb 21 14:44:33 svd-xen kernel: [23636.279551] [<ffffffff8104cb09>] ? mmput+0x3c/0xdf Feb 21 14:44:33 svd-xen kernel: [23636.279554] [<ffffffff81050702>] ? exit_mm+0x102/0x10d Feb 21 14:44:33 svd-xen kernel: [23636.279557] [<ffffffff8130ca72>] ? _spin_lock_irq+0x7/0x22 Feb 21 14:44:33 svd-xen kernel: [23636.279560] [<ffffffff81052127>] ? do_exit+0x1f8/0x6c6 Feb 21 14:44:33 svd-xen kernel: [23636.279564] [<ffffffff8100ecf2>] ? check_events+0x12/0x20 Feb 21 14:44:33 svd-xen kernel: [23636.279567] [<ffffffff8130d9dd>] ? oops_end+0xaf/0xb4 Feb 21 14:44:33 svd-xen kernel: [23636.279570] [<ffffffff810135f0>] ? do_invalid_op+0x8b/0x95 Feb 21 14:44:33 svd-xen kernel: [23636.279573] [<ffffffff8100c694>] ? pin_pagetable_pfn+0x2d/0x36 Feb 21 14:44:33 svd-xen kernel: [23636.279576] [<ffffffff81
0baf07>] ? __alloc_pages_nodemask+0x11c/0x5f5
Feb 21 14:44:33 svd-xen kernel: [23636.279579] [<ffffffff8101293b>] ? invalid_op+0x1b/0x20 Feb 21 14:44:33 svd-xen kernel: [23636.279582] [<ffffffff8100c694>] ? pin_pagetable_pfn+0x2d/0x36 Feb 21 14:44:33 svd-xen kernel: [23636.279585] [<ffffffff8100c690>] ? pin_pagetable_pfn+0x29/0x36 Feb 21 14:44:33 svd-xen kernel: [23636.279588] [<ffffffff810cd4e2>] ? __pte_alloc+0x6b/0xc6 Feb 21 14:44:33 svd-xen kernel: [23636.279591] [<ffffffff810cb394>] ? pmd_alloc+0x28/0x5b Feb 21 14:44:33 svd-xen kernel: [23636.279594] [<ffffffff810cd60b>] ? handle_mm_fault+0xce/0x80f Feb 21 14:44:33 svd-xen kernel: [23636.279597] [<ffffffff8102ddc0>] ? pvclock_clocksource_read+0x3a/0x8b
Feb 21 14:44:33 svd-xen kernel: [23636.279600] [<ffffffff8130f016>] ? do_page_fault+0x2e0/0x2fc Feb 21 14:44:33 svd-xen kernel: [23636.279603] [<ffffffff8130ceb5>] ? page_fault+0x25/0x30
--------------------------------------------------------------------------------------------------
Possible Solution:
As of the Xen-devel mailinglist, these two patches should fix the problem,
they have been integrated in xen/stable-2.6.32.x branch for arround 5 Month:
b2464c422fb44275deeb5770b668351860f68e0e "x86: hold mm->page_table_lock while doing vmalloc_sync"
a8bf92faf72dba6e0dd2130256cb81c3e68f672b "vmalloc: eagerly clear ptes on vunmap"
Reply to: