Bug#615048: marked as done (base: After removing lvm snapshot got kernel BUG at /build/.../source_amd64_xen/arch/x86/xen/mmu.c:1649!)

2011-10-30 Thread Debian Bug Tracking System
Your message dated Sun, 30 Oct 2011 16:04:00 +0100
with message-id <20111030150400.gb18...@wavehammer.waldi.eu.org>
and subject line Fixed upstream
has caused the Debian Bug report #613634,
regarding base: After removing lvm snapshot got kernel BUG at 
/build/.../source_amd64_xen/arch/x86/xen/mmu.c:1649!
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
613634: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=613634
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: base
Severity: normal




Problems's started after changing version of Debian from Lenny to Squeeze.
I'm using Xen with virtual hosts on LVM volumes.
I make a snapshot of LVM volume and dump it to a file.
After it I'm tring to remove snapshot.
The operation fails and generates kernel error.
After the error one of cpus is used in 100%.
Neither shutdown(reboot) nor use many other command because seems like the 
system is high load or hung up.
The same is on two other machines (I've got two HP DL360g5 and one DL380g7).



Feb 25 03:32:05 xen3 kernel: [400058.329748] [ cut here 
]
Feb 25 03:32:05 xen3 kernel: [400058.329785] kernel BUG at 
/build/buildd-linux-2.6_2.6.32-30-amd64-d4MbNM/linux-2.6-2.6.32/debian/build/s
ource_amd64_xen/arch/x86/xen/mmu.c:1649!
Feb 25 03:32:05 xen3 kernel: [400058.329857] invalid opcode:  [#1] SMP
Feb 25 03:32:05 xen3 kernel: [400058.329900] last sysfs file: 
/sys/devices/pci:00/:00:01.0/:05:00.0/cciss0/c0d0/block/cciss!c
0d0/cciss!c0d0p2/size
Feb 25 03:32:05 xen3 kernel: [400058.329965] CPU 1
Feb 25 03:32:05 xen3 kernel: [400058.330001] Modules linked in: dm_snapshot nfs 
lockd fscache nfs_acl auth_rpcgss sunrpc tun ip6table_fil
ter ip6_tables ebtable_nat ebtables cpufreq_stats cpufreq_powersave 
cpufreq_conservative cpufreq_userspace xen_evtchn xenfs binfmt_misc f
use bridge stp ipt_REJECT xt_state xt_physdev xt_tcpudp iptable_filter 
iptable_mangle iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack n
f_defrag_ipv4 ip_tables x_tables loop psmouse joydev evdev hpwdt hpilo pcspkr 
serio_raw container power_meter button processor acpi_proce
ssor ext3 jbd mbcache dm_mod sg sr_mod cdrom ata_generic usbhid hid ata_piix 
uhci_hcd libata ehci_hcd usbcore nls_base cciss bnx2 scsi_mo
d thermal thermal_sys [last unloaded: scsi_wait_scan]
Feb 25 03:32:05 xen3 kernel: [400058.330706] Pid: 20284, comm: udisks-dm-expor 
Not tainted 2.6.32-5-xen-amd64 #1 ProLiant DL380 G7
Feb 25 03:32:05 xen3 kernel: [400058.330765] RIP: e030:[]  
[] pin_pagetable_pfn+0x2d/0x36
Feb 25 03:32:05 xen3 kernel: [400058.330827] RSP: e02b:880256c53e08  
EFLAGS: 00010282
Feb 25 03:32:05 xen3 kernel: [400058.330860] RAX: ffea RBX: 
00115e50 RCX: 0001
Feb 25 03:32:05 xen3 kernel: [400058.330916] RDX:  RSI: 
0001 RDI: 880256c53e08
Feb 25 03:32:05 xen3 kernel: [400058.330976] RBP: 8802e8885780 R08: 
0280 R09: ea0003cca180
Feb 25 03:32:05 xen3 kernel: [400058.331032] R10: 7ff0 R11: 
0f7a1030 R12: 880114dc10a0
Feb 25 03:32:05 xen3 kernel: [400058.331089] R13: 88011c1465c0 R14: 
8802e6e946a0 R15: 880114dc10a0
Feb 25 03:32:05 xen3 kernel: [400058.331149] FS:  7f9b42e6f7a0() 
GS:88000f78f000() knlGS:
Feb 25 03:32:05 xen3 kernel: [400058.331211] CS:  e033 DS:  ES:  CR0: 
8005003b
Feb 25 03:32:05 xen3 kernel: [400058.331249] CR2: 7f9b428143c0 CR3: 
000105534000 CR4: 2660
Feb 25 03:32:05 xen3 kernel: [400058.331304] DR0:  DR1: 
 DR2: 
Feb 25 03:32:05 xen3 kernel: [400058.331357] DR3:  DR6: 
0ff0 DR7: 0400
Feb 25 03:32:05 xen3 kernel: [400058.331421] Process udisks-dm-expor (pid: 
20284, threadinfo 880256c52000, task 8802e6e946a0)
Feb 25 03:32:05 xen3 kernel: [400058.331482] Stack:
Feb 25 03:32:05 xen3 kernel: [400058.331513]   0020de50 
ea0003cca180 00115e50
Feb 25 03:32:05 xen3 kernel: [400058.331579] <0> 8802e8885780 
810cd4e2 8801334d8368 7f9b428143c0
Feb 25 03:32:05 xen3 kernel: [400058.331661] <0> 0001334d8000 
810cb394 88011c1465c0 7f9b428143c0
Feb 25 03:32:05 xen3 kernel: [400058.331764] Call Trace:
Feb 25 03:32:05 xen3 kernel: [400058.331764] Call Trace:
Feb 25 03:32:05 xen3 kernel: [400058.331803]  [] ? 
__pte_alloc+0x6b/0xc6
Feb 25 03:32:05 xen3 kernel: [400058.331847]  [] ? 
pmd_alloc+0x28/0x5b
Feb 25 03:32:05 xen3 kernel: [400058.331888]

Bug#615048: marked as done (base: After removing lvm snapshot got kernel BUG at /build/.../source_amd64_xen/arch/x86/xen/mmu.c:1649!)

2011-06-14 Thread Debian Bug Tracking System
Your message dated Tue, 14 Jun 2011 08:00:54 +
with message-id 
and subject line Bug#613634: fixed in linux-2.6 2.6.32-35
has caused the Debian Bug report #613634,
regarding base: After removing lvm snapshot got kernel BUG at 
/build/.../source_amd64_xen/arch/x86/xen/mmu.c:1649!
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
613634: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=613634
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: base
Severity: normal




Problems's started after changing version of Debian from Lenny to Squeeze.
I'm using Xen with virtual hosts on LVM volumes.
I make a snapshot of LVM volume and dump it to a file.
After it I'm tring to remove snapshot.
The operation fails and generates kernel error.
After the error one of cpus is used in 100%.
Neither shutdown(reboot) nor use many other command because seems like the 
system is high load or hung up.
The same is on two other machines (I've got two HP DL360g5 and one DL380g7).



Feb 25 03:32:05 xen3 kernel: [400058.329748] [ cut here 
]
Feb 25 03:32:05 xen3 kernel: [400058.329785] kernel BUG at 
/build/buildd-linux-2.6_2.6.32-30-amd64-d4MbNM/linux-2.6-2.6.32/debian/build/s
ource_amd64_xen/arch/x86/xen/mmu.c:1649!
Feb 25 03:32:05 xen3 kernel: [400058.329857] invalid opcode:  [#1] SMP
Feb 25 03:32:05 xen3 kernel: [400058.329900] last sysfs file: 
/sys/devices/pci:00/:00:01.0/:05:00.0/cciss0/c0d0/block/cciss!c
0d0/cciss!c0d0p2/size
Feb 25 03:32:05 xen3 kernel: [400058.329965] CPU 1
Feb 25 03:32:05 xen3 kernel: [400058.330001] Modules linked in: dm_snapshot nfs 
lockd fscache nfs_acl auth_rpcgss sunrpc tun ip6table_fil
ter ip6_tables ebtable_nat ebtables cpufreq_stats cpufreq_powersave 
cpufreq_conservative cpufreq_userspace xen_evtchn xenfs binfmt_misc f
use bridge stp ipt_REJECT xt_state xt_physdev xt_tcpudp iptable_filter 
iptable_mangle iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack n
f_defrag_ipv4 ip_tables x_tables loop psmouse joydev evdev hpwdt hpilo pcspkr 
serio_raw container power_meter button processor acpi_proce
ssor ext3 jbd mbcache dm_mod sg sr_mod cdrom ata_generic usbhid hid ata_piix 
uhci_hcd libata ehci_hcd usbcore nls_base cciss bnx2 scsi_mo
d thermal thermal_sys [last unloaded: scsi_wait_scan]
Feb 25 03:32:05 xen3 kernel: [400058.330706] Pid: 20284, comm: udisks-dm-expor 
Not tainted 2.6.32-5-xen-amd64 #1 ProLiant DL380 G7
Feb 25 03:32:05 xen3 kernel: [400058.330765] RIP: e030:[]  
[] pin_pagetable_pfn+0x2d/0x36
Feb 25 03:32:05 xen3 kernel: [400058.330827] RSP: e02b:880256c53e08  
EFLAGS: 00010282
Feb 25 03:32:05 xen3 kernel: [400058.330860] RAX: ffea RBX: 
00115e50 RCX: 0001
Feb 25 03:32:05 xen3 kernel: [400058.330916] RDX:  RSI: 
0001 RDI: 880256c53e08
Feb 25 03:32:05 xen3 kernel: [400058.330976] RBP: 8802e8885780 R08: 
0280 R09: ea0003cca180
Feb 25 03:32:05 xen3 kernel: [400058.331032] R10: 7ff0 R11: 
0f7a1030 R12: 880114dc10a0
Feb 25 03:32:05 xen3 kernel: [400058.331089] R13: 88011c1465c0 R14: 
8802e6e946a0 R15: 880114dc10a0
Feb 25 03:32:05 xen3 kernel: [400058.331149] FS:  7f9b42e6f7a0() 
GS:88000f78f000() knlGS:
Feb 25 03:32:05 xen3 kernel: [400058.331211] CS:  e033 DS:  ES:  CR0: 
8005003b
Feb 25 03:32:05 xen3 kernel: [400058.331249] CR2: 7f9b428143c0 CR3: 
000105534000 CR4: 2660
Feb 25 03:32:05 xen3 kernel: [400058.331304] DR0:  DR1: 
 DR2: 
Feb 25 03:32:05 xen3 kernel: [400058.331357] DR3:  DR6: 
0ff0 DR7: 0400
Feb 25 03:32:05 xen3 kernel: [400058.331421] Process udisks-dm-expor (pid: 
20284, threadinfo 880256c52000, task 8802e6e946a0)
Feb 25 03:32:05 xen3 kernel: [400058.331482] Stack:
Feb 25 03:32:05 xen3 kernel: [400058.331513]   0020de50 
ea0003cca180 00115e50
Feb 25 03:32:05 xen3 kernel: [400058.331579] <0> 8802e8885780 
810cd4e2 8801334d8368 7f9b428143c0
Feb 25 03:32:05 xen3 kernel: [400058.331661] <0> 0001334d8000 
810cb394 88011c1465c0 7f9b428143c0
Feb 25 03:32:05 xen3 kernel: [400058.331764] Call Trace:
Feb 25 03:32:05 xen3 kernel: [400058.331764] Call Trace:
Feb 25 03:32:05 xen3 kernel: [400058.331803]  [] ? 
__pte_alloc+0x6b/0xc6
Feb 25 03:32:05 xen3 kernel: [400058.331847]  [] ? 
pmd_alloc+0x28/0x5b
Feb 25 03:32:05 xen3 kernel: [400058.331888]  [] ? 
handle_mm_faul

Bug#615048: marked as done (base: After removing lvm snapshot got kernel BUG at /build/.../source_amd64_xen/arch/x86/xen/mmu.c:1649!)

2011-05-04 Thread Debian Bug Tracking System
Your message dated Wed, 04 May 2011 20:07:36 +
with message-id 
and subject line Bug#614400: fixed in linux-2.6 2.6.32-34
has caused the Debian Bug report #614400,
regarding base: After removing lvm snapshot got kernel BUG at 
/build/.../source_amd64_xen/arch/x86/xen/mmu.c:1649!
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
614400: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=614400
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: base
Severity: normal




Problems's started after changing version of Debian from Lenny to Squeeze.
I'm using Xen with virtual hosts on LVM volumes.
I make a snapshot of LVM volume and dump it to a file.
After it I'm tring to remove snapshot.
The operation fails and generates kernel error.
After the error one of cpus is used in 100%.
Neither shutdown(reboot) nor use many other command because seems like the 
system is high load or hung up.
The same is on two other machines (I've got two HP DL360g5 and one DL380g7).



Feb 25 03:32:05 xen3 kernel: [400058.329748] [ cut here 
]
Feb 25 03:32:05 xen3 kernel: [400058.329785] kernel BUG at 
/build/buildd-linux-2.6_2.6.32-30-amd64-d4MbNM/linux-2.6-2.6.32/debian/build/s
ource_amd64_xen/arch/x86/xen/mmu.c:1649!
Feb 25 03:32:05 xen3 kernel: [400058.329857] invalid opcode:  [#1] SMP
Feb 25 03:32:05 xen3 kernel: [400058.329900] last sysfs file: 
/sys/devices/pci:00/:00:01.0/:05:00.0/cciss0/c0d0/block/cciss!c
0d0/cciss!c0d0p2/size
Feb 25 03:32:05 xen3 kernel: [400058.329965] CPU 1
Feb 25 03:32:05 xen3 kernel: [400058.330001] Modules linked in: dm_snapshot nfs 
lockd fscache nfs_acl auth_rpcgss sunrpc tun ip6table_fil
ter ip6_tables ebtable_nat ebtables cpufreq_stats cpufreq_powersave 
cpufreq_conservative cpufreq_userspace xen_evtchn xenfs binfmt_misc f
use bridge stp ipt_REJECT xt_state xt_physdev xt_tcpudp iptable_filter 
iptable_mangle iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack n
f_defrag_ipv4 ip_tables x_tables loop psmouse joydev evdev hpwdt hpilo pcspkr 
serio_raw container power_meter button processor acpi_proce
ssor ext3 jbd mbcache dm_mod sg sr_mod cdrom ata_generic usbhid hid ata_piix 
uhci_hcd libata ehci_hcd usbcore nls_base cciss bnx2 scsi_mo
d thermal thermal_sys [last unloaded: scsi_wait_scan]
Feb 25 03:32:05 xen3 kernel: [400058.330706] Pid: 20284, comm: udisks-dm-expor 
Not tainted 2.6.32-5-xen-amd64 #1 ProLiant DL380 G7
Feb 25 03:32:05 xen3 kernel: [400058.330765] RIP: e030:[]  
[] pin_pagetable_pfn+0x2d/0x36
Feb 25 03:32:05 xen3 kernel: [400058.330827] RSP: e02b:880256c53e08  
EFLAGS: 00010282
Feb 25 03:32:05 xen3 kernel: [400058.330860] RAX: ffea RBX: 
00115e50 RCX: 0001
Feb 25 03:32:05 xen3 kernel: [400058.330916] RDX:  RSI: 
0001 RDI: 880256c53e08
Feb 25 03:32:05 xen3 kernel: [400058.330976] RBP: 8802e8885780 R08: 
0280 R09: ea0003cca180
Feb 25 03:32:05 xen3 kernel: [400058.331032] R10: 7ff0 R11: 
0f7a1030 R12: 880114dc10a0
Feb 25 03:32:05 xen3 kernel: [400058.331089] R13: 88011c1465c0 R14: 
8802e6e946a0 R15: 880114dc10a0
Feb 25 03:32:05 xen3 kernel: [400058.331149] FS:  7f9b42e6f7a0() 
GS:88000f78f000() knlGS:
Feb 25 03:32:05 xen3 kernel: [400058.331211] CS:  e033 DS:  ES:  CR0: 
8005003b
Feb 25 03:32:05 xen3 kernel: [400058.331249] CR2: 7f9b428143c0 CR3: 
000105534000 CR4: 2660
Feb 25 03:32:05 xen3 kernel: [400058.331304] DR0:  DR1: 
 DR2: 
Feb 25 03:32:05 xen3 kernel: [400058.331357] DR3:  DR6: 
0ff0 DR7: 0400
Feb 25 03:32:05 xen3 kernel: [400058.331421] Process udisks-dm-expor (pid: 
20284, threadinfo 880256c52000, task 8802e6e946a0)
Feb 25 03:32:05 xen3 kernel: [400058.331482] Stack:
Feb 25 03:32:05 xen3 kernel: [400058.331513]   0020de50 
ea0003cca180 00115e50
Feb 25 03:32:05 xen3 kernel: [400058.331579] <0> 8802e8885780 
810cd4e2 8801334d8368 7f9b428143c0
Feb 25 03:32:05 xen3 kernel: [400058.331661] <0> 0001334d8000 
810cb394 88011c1465c0 7f9b428143c0
Feb 25 03:32:05 xen3 kernel: [400058.331764] Call Trace:
Feb 25 03:32:05 xen3 kernel: [400058.331764] Call Trace:
Feb 25 03:32:05 xen3 kernel: [400058.331803]  [] ? 
__pte_alloc+0x6b/0xc6
Feb 25 03:32:05 xen3 kernel: [400058.331847]  [] ? 
pmd_alloc+0x28/0x5b
Feb 25 03:32:05 xen3 kernel: [400058.331888]  [] ? 
handle_mm_faul

Bug#615048: marked as done (base: After removing lvm snapshot got kernel BUG at /build/.../source_amd64_xen/arch/x86/xen/mmu.c:1649!)

2011-05-04 Thread Debian Bug Tracking System
Your message dated Wed, 04 May 2011 20:07:36 +
with message-id 
and subject line Bug#613634: fixed in linux-2.6 2.6.32-34
has caused the Debian Bug report #613634,
regarding base: After removing lvm snapshot got kernel BUG at 
/build/.../source_amd64_xen/arch/x86/xen/mmu.c:1649!
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
613634: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=613634
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: base
Severity: normal




Problems's started after changing version of Debian from Lenny to Squeeze.
I'm using Xen with virtual hosts on LVM volumes.
I make a snapshot of LVM volume and dump it to a file.
After it I'm tring to remove snapshot.
The operation fails and generates kernel error.
After the error one of cpus is used in 100%.
Neither shutdown(reboot) nor use many other command because seems like the 
system is high load or hung up.
The same is on two other machines (I've got two HP DL360g5 and one DL380g7).



Feb 25 03:32:05 xen3 kernel: [400058.329748] [ cut here 
]
Feb 25 03:32:05 xen3 kernel: [400058.329785] kernel BUG at 
/build/buildd-linux-2.6_2.6.32-30-amd64-d4MbNM/linux-2.6-2.6.32/debian/build/s
ource_amd64_xen/arch/x86/xen/mmu.c:1649!
Feb 25 03:32:05 xen3 kernel: [400058.329857] invalid opcode:  [#1] SMP
Feb 25 03:32:05 xen3 kernel: [400058.329900] last sysfs file: 
/sys/devices/pci:00/:00:01.0/:05:00.0/cciss0/c0d0/block/cciss!c
0d0/cciss!c0d0p2/size
Feb 25 03:32:05 xen3 kernel: [400058.329965] CPU 1
Feb 25 03:32:05 xen3 kernel: [400058.330001] Modules linked in: dm_snapshot nfs 
lockd fscache nfs_acl auth_rpcgss sunrpc tun ip6table_fil
ter ip6_tables ebtable_nat ebtables cpufreq_stats cpufreq_powersave 
cpufreq_conservative cpufreq_userspace xen_evtchn xenfs binfmt_misc f
use bridge stp ipt_REJECT xt_state xt_physdev xt_tcpudp iptable_filter 
iptable_mangle iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack n
f_defrag_ipv4 ip_tables x_tables loop psmouse joydev evdev hpwdt hpilo pcspkr 
serio_raw container power_meter button processor acpi_proce
ssor ext3 jbd mbcache dm_mod sg sr_mod cdrom ata_generic usbhid hid ata_piix 
uhci_hcd libata ehci_hcd usbcore nls_base cciss bnx2 scsi_mo
d thermal thermal_sys [last unloaded: scsi_wait_scan]
Feb 25 03:32:05 xen3 kernel: [400058.330706] Pid: 20284, comm: udisks-dm-expor 
Not tainted 2.6.32-5-xen-amd64 #1 ProLiant DL380 G7
Feb 25 03:32:05 xen3 kernel: [400058.330765] RIP: e030:[]  
[] pin_pagetable_pfn+0x2d/0x36
Feb 25 03:32:05 xen3 kernel: [400058.330827] RSP: e02b:880256c53e08  
EFLAGS: 00010282
Feb 25 03:32:05 xen3 kernel: [400058.330860] RAX: ffea RBX: 
00115e50 RCX: 0001
Feb 25 03:32:05 xen3 kernel: [400058.330916] RDX:  RSI: 
0001 RDI: 880256c53e08
Feb 25 03:32:05 xen3 kernel: [400058.330976] RBP: 8802e8885780 R08: 
0280 R09: ea0003cca180
Feb 25 03:32:05 xen3 kernel: [400058.331032] R10: 7ff0 R11: 
0f7a1030 R12: 880114dc10a0
Feb 25 03:32:05 xen3 kernel: [400058.331089] R13: 88011c1465c0 R14: 
8802e6e946a0 R15: 880114dc10a0
Feb 25 03:32:05 xen3 kernel: [400058.331149] FS:  7f9b42e6f7a0() 
GS:88000f78f000() knlGS:
Feb 25 03:32:05 xen3 kernel: [400058.331211] CS:  e033 DS:  ES:  CR0: 
8005003b
Feb 25 03:32:05 xen3 kernel: [400058.331249] CR2: 7f9b428143c0 CR3: 
000105534000 CR4: 2660
Feb 25 03:32:05 xen3 kernel: [400058.331304] DR0:  DR1: 
 DR2: 
Feb 25 03:32:05 xen3 kernel: [400058.331357] DR3:  DR6: 
0ff0 DR7: 0400
Feb 25 03:32:05 xen3 kernel: [400058.331421] Process udisks-dm-expor (pid: 
20284, threadinfo 880256c52000, task 8802e6e946a0)
Feb 25 03:32:05 xen3 kernel: [400058.331482] Stack:
Feb 25 03:32:05 xen3 kernel: [400058.331513]   0020de50 
ea0003cca180 00115e50
Feb 25 03:32:05 xen3 kernel: [400058.331579] <0> 8802e8885780 
810cd4e2 8801334d8368 7f9b428143c0
Feb 25 03:32:05 xen3 kernel: [400058.331661] <0> 0001334d8000 
810cb394 88011c1465c0 7f9b428143c0
Feb 25 03:32:05 xen3 kernel: [400058.331764] Call Trace:
Feb 25 03:32:05 xen3 kernel: [400058.331764] Call Trace:
Feb 25 03:32:05 xen3 kernel: [400058.331803]  [] ? 
__pte_alloc+0x6b/0xc6
Feb 25 03:32:05 xen3 kernel: [400058.331847]  [] ? 
pmd_alloc+0x28/0x5b
Feb 25 03:32:05 xen3 kernel: [400058.331888]  [] ? 
handle_mm_faul