From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: tjaouen <tjaouen@free.fr>
Cc: xen-devel@lists.xensource.com
Subject: Re: Re: kernel BUG at arch/x86/xen/mmu.c:1860!
Date: Fri, 14 Jan 2011 09:47:05 -0500 [thread overview]
Message-ID: <20110114144704.GA7371@dumpdata.com> (raw)
In-Reply-To: <1294928902583-3339844.post@n5.nabble.com>
On Thu, Jan 13, 2011 at 06:28:22AM -0800, tjaouen wrote:
>
> Same issue:
>
> Backup DomU with lvsnapshot ...
Ok. I just got some free time so let me take a look at this.
>
> Linux xencave 2.6.32-5-xen-amd64 #1 SMP Fri Dec 10 17:41:50 UTC 2010 x86_64
> GNU/Linux
>
> Jan 13 04:01:51 xencave kernel: [223872.758977] ------------[ cut here
> ]------------
> Jan 13 04:01:51 xencave kernel: [223872.759006] kernel BUG at
> /build/buildd-linux-2.6_2.6.32-29-amd64-xcs37n/linux-2.6-2.6.32/debian/build/source_amd64_xen/arch/x86/xen/mmu.c:1649!
> Jan 13 04:01:51 xencave kernel: [223872.759047] invalid opcode: 0000 [#2]
> SMP
> Jan 13 04:01:51 xencave kernel: [223872.759076] last sysfs file:
> /sys/devices/virtual/block/dm-30/dm/suspended
> Jan 13 04:01:51 xencave kernel: [223872.759099] CPU 1
> Jan 13 04:01:51 xencave kernel: [223872.759121] Modules linked in:
> dm_snapshot nfs lockd fscache nfs_acl auth_rpcgss sunrpc nf_conntrack_ipv4
> nf_defrag_ipv4 xt_state nf_conntrack xt_physdev iptable_filter ip_tables
> x_tables xen_evtchn xenfs bridge stp coretemp it87 hwmon_vid fuse loop i915
> drm_kms_helper processor acpi_processor drm i2c_algo_bit button video
> snd_pcsp rng_core evdev i2c_i801 serio_raw snd_pcm snd_timer output i2c_core
> snd soundcore snd_page_alloc usbhid hid ext3 jbd mbcache dm_mod raid1 md_mod
> sg sr_mod cdrom sd_mod crc_t10dif ata_generic ata_piix libata scsi_mod
> ehci_hcd uhci_hcd r8169 mii usbcore nls_base thermal fan thermal_sys [last
> unloaded: scsi_wait_scan]
> Jan 13 04:01:51 xencave kernel: [223872.759599] Pid: 9244, comm: dmsetup_env
> Tainted: G D 2.6.32-5-xen-amd64 #1 945GM-S2
> Jan 13 04:01:51 xencave kernel: [223872.759636] RIP:
> e030:[<ffffffff8100c694>] [<ffffffff8100c694>] pin_pagetable_pfn+0x2d/0x36
> Jan 13 04:01:51 xencave kernel: [223872.759683] RSP: e02b:ffff88001d695e08
> EFLAGS: 00010282
> Jan 13 04:01:51 xencave kernel: [223872.759707] RAX: 00000000ffffffea RBX:
> 000000000001e9df RCX: 0000000000000001
> Jan 13 04:01:51 xencave kernel: [223872.759742] RDX: 0000000000000000 RSI:
> 0000000000000001 RDI: ffff88001d695e08
> Jan 13 04:01:51 xencave kernel: [223872.759777] RBP: ffff88001f2b4700 R08:
> 0000000000000ef8 R09: ffffea00006b28c8
> Jan 13 04:01:51 xencave kernel: [223872.759812] R10: 0000000000007ff0 R11:
> ffffea00005858c8 R12: ffff88001a3ee010
> Jan 13 04:01:51 xencave kernel: [223872.759846] R13: ffff8800020a8000 R14:
> ffff880002089530 R15: ffff88001a3ee010
> Jan 13 04:01:51 xencave kernel: [223872.759887] FS: 00007f81d5709700(0000)
> GS:ffff88000308c000(0000) knlGS:0000000000000000
> Jan 13 04:01:51 xencave kernel: [223872.759925] CS: e033 DS: 0000 ES: 0000
> CR0: 000000008005003b
> Jan 13 04:01:51 xencave kernel: [223872.759948] CR2: 000000000043c56a CR3:
> 000000001a38c000 CR4: 0000000000002660
> Jan 13 04:01:51 xencave kernel: [223872.759985] DR0: 0000000000000000 DR1:
> 0000000000000000 DR2: 0000000000000000
> Jan 13 04:01:51 xencave kernel: [223872.760022] DR3: 0000000000000000 DR6:
> 00000000ffff0ff0 DR7: 0000000000000400
> Jan 13 04:01:51 xencave kernel: [223872.760057] Process dmsetup_env (pid:
> 9244, threadinfo ffff88001d694000, task ffff880002089530)
> Jan 13 04:01:51 xencave kernel: [223872.760094] Stack:
> Jan 13 04:01:51 xencave kernel: [223872.760112] 0000000000000000
> 000000000009e90d ffffea00006b28c8 000000000001e9df
> Jan 13 04:01:51 xencave kernel: [223872.760149] <0> ffff88001f2b4700
> ffffffff810cd4a1 ffff88001a3dc000 000000000043c56a
> Jan 13 04:01:51 xencave kernel: [223872.760203] <0> 000000001a3dc000
> ffffffff810cb34c ffff8800020a8000 000000000043c56a
> Jan 13 04:01:51 xencave kernel: [223872.760270] Call Trace:
> Jan 13 04:01:51 xencave kernel: [223872.760295] [<ffffffff810cd4a1>] ?
> __pte_alloc+0x6b/0xc6
> Jan 13 04:01:51 xencave kernel: [223872.760320] [<ffffffff810cb34c>] ?
> pmd_alloc+0x28/0x5b
> Jan 13 04:01:51 xencave kernel: [223872.760344] [<ffffffff810cd5ca>] ?
> handle_mm_fault+0xce/0x80f
> Jan 13 04:01:51 xencave kernel: [223872.760372] [<ffffffff8130cc35>] ?
> page_fault+0x25/0x30
> Jan 13 04:01:51 xencave kernel: [223872.760397] [<ffffffff8130ed96>] ?
> do_page_fault+0x2e0/0x2fc
> Jan 13 04:01:51 xencave kernel: [223872.760422] [<ffffffff8130cc35>] ?
> page_fault+0x25/0x30
> Jan 13 04:01:51 xencave kernel: [223872.760443] 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
> Jan 13 04:01:51 xencave kernel: [223872.760761] RIP [<ffffffff8100c694>]
> pin_pagetable_pfn+0x2d/0x36
> Jan 13 04:01:51 xencave kernel: [223872.760790] RSP <ffff88001d695e08>
> Jan 13 04:01:51 xencave kernel: [223872.761008] ---[ end trace
> b143b5bdb343412e ]---
>
>
> help!
> --
> View this message in context: http://xen.1045712.n5.nabble.com/kernel-BUG-at-arch-x86-xen-mmu-c-1860-tp3318567p3339844.html
> Sent from the Xen - Dev mailing list archive at Nabble.com.
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2011-01-14 14:47 UTC|newest]
Thread overview: 83+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-26 8:16 kernel BUG at arch/x86/xen/mmu.c:1860! Teck Choon Giam
2010-12-27 15:53 ` Konrad Rzeszutek Wilk
2010-12-27 22:14 ` Teck Choon Giam
2010-12-28 10:42 ` Pasi Kärkkäinen
2010-12-28 18:01 ` Teck Choon Giam
2010-12-29 4:25 ` Teck Choon Giam
2010-12-29 4:58 ` Teck Choon Giam
2011-01-14 15:20 ` Konrad Rzeszutek Wilk
2011-01-14 19:25 ` Teck Choon Giam
2011-01-14 19:44 ` Konrad Rzeszutek Wilk
2011-01-14 20:09 ` Teck Choon Giam
2011-01-14 20:32 ` Teck Choon Giam
2011-01-24 1:42 ` Teck Choon Giam
2011-01-24 14:36 ` Konrad Rzeszutek Wilk
2011-01-24 15:56 ` Teck Choon Giam
2011-01-25 14:48 ` Konrad Rzeszutek Wilk
2011-01-26 14:31 ` Konrad Rzeszutek Wilk
2011-01-27 17:17 ` Teck Choon Giam
2011-01-27 20:32 ` Konrad Rzeszutek Wilk
2011-01-27 22:20 ` Teck Choon Giam
2011-02-26 12:03 ` Teck Choon Giam
2011-02-28 16:20 ` Konrad Rzeszutek Wilk
2011-03-01 9:59 ` Teck Choon Giam
2011-03-03 22:16 ` Konrad Rzeszutek Wilk
2011-03-04 5:30 ` Teck Choon Giam
2011-03-04 6:15 ` Fajar A. Nugraha
2011-03-04 6:33 ` Teck Choon Giam
2011-03-08 19:29 ` Konrad Rzeszutek Wilk
2011-03-08 20:10 ` Konrad Rzeszutek Wilk
2011-03-08 20:20 ` Teck Choon Giam
2011-03-08 20:45 ` Guido Hecken
2011-03-08 20:50 ` [SPAM] " tjaouen
2011-03-09 0:06 ` Andreas Olsowski
2011-03-11 18:38 ` benco
2011-03-11 19:59 ` Sander Eikelenboom
2011-03-11 20:29 ` Teck Choon Giam
2011-03-11 20:45 ` Teck Choon Giam
2011-03-11 21:02 ` Sander Eikelenboom
2011-03-11 21:15 ` Teck Choon Giam
2011-03-09 0:43 ` [SPAM] " Konrad Rzeszutek Wilk
2011-03-09 6:58 ` Andreas Olsowski
2011-03-09 15:00 ` Konrad Rzeszutek Wilk
2011-03-09 19:59 ` Andreas Olsowski
2011-03-10 7:20 ` Andreas Olsowski
2011-03-10 13:45 ` Andreas Olsowski
2011-03-11 18:05 ` Konrad Rzeszutek Wilk
2011-03-14 10:25 ` Ian Campbell
2011-03-14 10:36 ` Teck Choon Giam
2011-03-16 15:52 ` [SPAM] Re: kernel BUG at arch/x86/xen/mmu.c:1860! - ideas Konrad Rzeszutek Wilk
2011-03-16 16:26 ` Teck Choon Giam
2011-03-16 16:40 ` Konrad Rzeszutek Wilk
2011-03-24 11:57 ` Konrad Rzeszutek Wilk
2011-03-24 21:28 ` Teck Choon Giam
2011-03-25 3:57 ` Teck Choon Giam
2011-03-27 10:16 ` Teck Choon Giam
2011-03-28 11:37 ` Andreas Olsowski
2011-03-28 12:29 ` Teck Choon Giam
2011-04-05 22:01 ` Dave Hunter
2011-04-05 22:15 ` Teck Choon Giam
2011-04-05 23:20 ` Dave Hunter
2011-04-06 7:53 ` Ian Campbell
2011-04-06 21:52 ` Jeremy Fitzhardinge
2011-04-07 13:16 ` Teck Choon Giam
2011-03-09 0:41 ` kernel BUG at arch/x86/xen/mmu.c:1860! Konrad Rzeszutek Wilk
2011-01-04 15:10 ` Christophe Saout
2011-01-04 15:19 ` Christophe Saout
2011-01-04 15:37 ` benco
2011-01-04 18:40 ` Christophe Saout
2011-01-04 19:32 ` Teck Choon Giam
2011-01-04 19:56 ` benco
2011-01-14 15:22 ` Konrad Rzeszutek Wilk
2011-01-14 15:33 ` Christophe Saout
2011-01-04 23:10 ` Christophe Saout
2011-01-05 10:51 ` Pasi Kärkkäinen
2011-01-05 14:56 ` Teck Choon Giam
2011-01-14 15:24 ` Konrad Rzeszutek Wilk
2011-01-14 19:31 ` Teck Choon Giam
2011-01-04 13:48 ` Ian Campbell
2011-01-04 19:24 ` Teck Choon Giam
2011-01-05 15:30 ` Teck Choon Giam
2011-01-13 14:28 ` tjaouen
2011-01-14 14:47 ` Konrad Rzeszutek Wilk [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-04-15 7:37 Joerg Stephan
2011-04-15 8:54 ` Pasi Kärkkäinen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110114144704.GA7371@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=tjaouen@free.fr \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).