From: Stan Hoeppner <stan@hardwarefreak.com>
To: Linda Walsh <xfs@tlinx.org>
Cc: xfs-oss <xfs@oss.sgi.com>
Subject: Re: xfsdump -OOM triggering 'soft' kernel panic...
Date: Sun, 03 Feb 2013 09:39:44 -0600 [thread overview]
Message-ID: <510E84C0.40601@hardwarefreak.com> (raw)
In-Reply-To: <510DED3D.702@tlinx.org>
On 2/2/2013 10:53 PM, Linda Walsh wrote:
> Feb 2 06:18:28 Ishtar kernel: [990738.011852] xfsdump: page allocation
> failure: order:4, mode:0xc0d0
> Feb 2 06:18:28 Ishtar kernel: [990738.011856] Pid: 14882, comm: xfsdump
> Tainted: G O 3.7.1-Isht-Van #1
Your kernel is tainted, albeit by a GPL (or compatible) licensed module.
Any idea which module? You may need to reproduce this with a
non-tainted kernel before anyone would run with it.
--
Stan
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-02-03 15:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-03 3:49 xfsdump showing system problems -- ? ideas? Linda Walsh
2013-02-03 4:53 ` xfsdump -OOM triggering 'soft' kernel panic Linda Walsh
2013-02-03 15:39 ` Stan Hoeppner [this message]
2013-02-03 23:17 ` xfsdump showing system problems -- ? ideas? Dave Chinner
2013-02-04 1:49 ` Linda Walsh
2013-02-04 9:01 ` xfsdump fix tested... level 0's on all partitions: no problems Linda Walsh
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=510E84C0.40601@hardwarefreak.com \
--to=stan@hardwarefreak.com \
--cc=xfs@oss.sgi.com \
--cc=xfs@tlinx.org \
/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