From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: "Christopher S. Aker" <caker@theshore.net>
Cc: Ian Campbell <Ian.Campbell@eu.citrix.com>,
Jeremy Fitzhardinge <jeremy@goop.org>,
xen devel <xen-devel@lists.xensource.com>
Subject: Re: 2.6.32.27 dom0 - BUG: unable to handle kernel paging request
Date: Mon, 10 Jan 2011 13:56:10 -0500 [thread overview]
Message-ID: <20110110185610.GC9837@dumpdata.com> (raw)
In-Reply-To: <4517209A-2F8B-41A1-9727-A0E498181135@theshore.net>
On Sun, Jan 09, 2011 at 01:07:26PM -0500, Christopher S. Aker wrote:
> On Jan 4, 2011, at 4:59 PM, Christopher S. Aker wrote:
> >
> > I rebuilt with CONFIG_DEBUG_INFO, and surprisingly it appears valid at the same address:
> >
> > # gdb vmlinux
> > (gdb) list *0xc1022781
> > 0xc1022781 is in vmalloc_sync_all (/build/xen/dom0/pv_ops/2.6.32.27-1-debug/arch/x86/include/asm/pgtable.h:434).
> > 429 #define pud_page(pud) pfn_to_page(pud_val(pud) >> PAGE_SHIFT)
> > 430
> > 431 /* Find an entry in the second-level page table.. */
> > 432 static inline pmd_t *pmd_offset(pud_t *pud, unsigned long address)
> > 433 {
> > 434 return (pmd_t *)pud_page_vaddr(*pud) + pmd_index(address);
> > 435 }
> > 436
> > 437 static inline int pud_large(pud_t pud)
> > 438 {
>
> We hit the BUG again on a third test box -- at least it's fairly easy to reproduce. Has anyone had a chance to poke at this, or have a suggestion for something for me to try/test?
Which test makes it easy to reproduce? Oh wait, you have a whole bunch of guests
pounding. Is it possible to narrow down which type of test is causing this? Or can
you put up the domU guests along with the xm config files to try to reproduce this?
next prev parent reply other threads:[~2011-01-10 18:56 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-30 22:57 2.6.32.27 dom0 - BUG: unable to handle kernel paging request Christopher S. Aker
2010-12-31 1:29 ` Jeremy Fitzhardinge
2010-12-31 17:19 ` Christopher S. Aker
2011-01-02 20:08 ` Christopher S. Aker
2011-01-04 9:16 ` Ian Campbell
2011-01-04 20:30 ` Christopher S. Aker
2011-01-04 20:34 ` Ian Campbell
2011-01-04 21:59 ` Christopher S. Aker
2011-01-09 18:07 ` Christopher S. Aker
2011-01-10 18:56 ` Konrad Rzeszutek Wilk [this message]
2011-01-10 21:49 ` John Weekes
2011-01-15 15:57 ` Christopher S. Aker
2011-01-31 21:07 ` Christopher S. Aker
2011-01-31 21:17 ` Konrad Rzeszutek Wilk
2011-01-31 22:19 ` Jeremy Fitzhardinge
2011-01-31 22:22 ` Jeremy Fitzhardinge
2011-01-31 22:25 ` Jeremy Fitzhardinge
2011-02-14 23:52 ` Christopher S. Aker
2011-02-15 0:19 ` Jeremy Fitzhardinge
2011-02-15 1:15 ` Christopher S. Aker
2011-01-13 14:43 ` Konrad Rzeszutek Wilk
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=20110110185610.GC9837@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=Ian.Campbell@eu.citrix.com \
--cc=caker@theshore.net \
--cc=jeremy@goop.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.