From: Bernd Schubert <bernd.schubert@itwm.fraunhofer.de>
To: Dave Chinner <david@fromorbit.com>
Cc: linux-xfs@oss.sgi.com
Subject: Re: 3.9.0: general protection fault
Date: Mon, 06 May 2013 14:47:31 +0200 [thread overview]
Message-ID: <5187A663.707@itwm.fraunhofer.de> (raw)
In-Reply-To: <20130506122844.GL19978@dastard>
On 05/06/2013 02:28 PM, Dave Chinner wrote:
> On Mon, May 06, 2013 at 10:14:22AM +0200, Bernd Schubert wrote:
>> And anpther protection fault, this time with 3.9.0. Always happens
>> on one of the servers. Its ECC memory, so I don't suspect a faulty
>> memory bank. Going to fsck now-
>
> http://xfs.org/index.php/XFS_FAQ#Q:_What_information_should_I_include_when_reporting_a_problem.3F
Isn't that a bit overhead? And I can't provide /proc/meminfo and others,
as this issue causes a kernel panic a few traces later.
>
>>
>>> [303340.514052] general protection fault: 0000 [#1] SMP DEBUG_PAGEALLOC
>>> [303340.517913] Modules linked in: fhgfs(O) fhgfs_client_opentk(O)
>
> Kernel tainted with out of tree modules. Can you reproduce the
> problem with them?
The modules are unused, as this is the server side. I disabled client
packages now and will re-run. But I really think that we should look for
memory/list corruption outside of fhgfs. Also very unlikely that always
only xfs would suffer, as there is also running ext4 for fhgfs meta data.
Also, it took from Friday evening till this morning to run into the
crash, so the next occurance might take some time. And I think tracing
xfs is out of question, as I need the disk space to store data (the
client side is running our stress test suite).
Cheers,
Bernd
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-05-06 12:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-02 14:45 3.8.7: general protection fault Bernd Schubert
2013-05-06 8:14 ` 3.9.0: " Bernd Schubert
2013-05-06 9:40 ` Bernd Schubert
2013-05-06 12:28 ` Dave Chinner
2013-05-06 12:47 ` Bernd Schubert [this message]
2013-05-07 1:12 ` Dave Chinner
2013-05-07 11:18 ` Bernd Schubert
2013-05-07 22:07 ` Dave Chinner
2013-05-08 17:48 ` Bernd Schubert
2013-05-09 0:41 ` Dave Chinner
2013-05-10 10:19 ` Bernd Schubert
2013-05-10 13:33 ` Eric Sandeen
2013-05-11 0:12 ` Dave Chinner
2013-06-03 16:39 ` Bernd Schubert
2013-05-09 7:16 ` Stan Hoeppner
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=5187A663.707@itwm.fraunhofer.de \
--to=bernd.schubert@itwm.fraunhofer.de \
--cc=david@fromorbit.com \
--cc=linux-xfs@oss.sgi.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