From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Shaun Reitan <mailinglists@unix-scripts.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: Re: kernel BUG at mm/swapfile.c:2527!
Date: Fri, 16 Sep 2011 04:24:56 -0400 [thread overview]
Message-ID: <20110916082456.GA884@phenom.oracle.com> (raw)
In-Reply-To: <j4tl2j$cm2$1@dough.gmane.org>
On Thu, Sep 15, 2011 at 12:52:42PM -0700, Shaun Reitan wrote:
> I can just about reproduce this bug on the fly, a PCI compliance
> scan seams to be triggering it every time. Let me know what you
> guys need!
How do I reproduce it? Is the PCI compliance easily available? Is
there any chance we can get access to the physical box to figure
out what is happening?
>
> ~Shaun
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2011-09-16 8:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-15 18:56 kernel BUG at mm/swapfile.c:2527! Shaun Reitan
2011-09-15 19:52 ` Shaun Reitan
2011-09-16 8:24 ` Konrad Rzeszutek Wilk [this message]
2011-09-16 16:52 ` Shaun Reitan
2011-09-20 4:33 ` Shaun Reitan
2011-09-22 11:06 ` Konrad Rzeszutek Wilk
-- strict thread matches above, loose matches on Subject: below --
2011-09-19 16:30 Kent Hoxsey
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=20110916082456.GA884@phenom.oracle.com \
--to=konrad.wilk@oracle.com \
--cc=mailinglists@unix-scripts.com \
--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.