From: Michael Monnerie <michael.monnerie@is.it-management.at>
To: xfs@oss.sgi.com
Cc: Christoph Hellwig <hch@infradead.org>
Subject: Re: xfs stack overrun, unable to handle kernel paging request
Date: Fri, 15 Apr 2011 08:11:16 +0200 [thread overview]
Message-ID: <201104150811.16971@zmi.at> (raw)
In-Reply-To: <20110415060202.GA32250@infradead.org>
[-- Attachment #1.1: Type: Text/Plain, Size: 910 bytes --]
On Freitag, 15. April 2011 Christoph Hellwig wrote:
> That's still without the commits I pointed out to avoid direct
> reclaim hitting the filesystem, right? Unfortunately the stack
> trace is truncate so it's not possible to spot where it originated,
> but I suspect it's the cause for this one as well.
Yes, it's an older server that's going to be replaced by OpenSUSE 11.4
anyway. And this crash is seldom enough that I am not urged to update
all our servers.
I think I copied all the lines that were visible. I was wondering why
the output was so short.
--
mit freundlichen Grüssen,
Michael Monnerie, Ing. BSc
it-management Internet Services: Protéger
http://proteger.at [gesprochen: Prot-e-schee]
Tel: +43 660 / 415 6531
// ****** Radiointerview zum Thema Spam ******
// http://www.it-podcast.at/archiv.html#podcast-100716
//
// Haus zu verkaufen: http://zmi.at/langegg/
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 121 bytes --]
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2011-04-15 6:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-15 4:31 xfs stack overrun, unable to handle kernel paging request Michael Monnerie
2011-04-15 6:02 ` Christoph Hellwig
2011-04-15 6:11 ` Michael Monnerie [this message]
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=201104150811.16971@zmi.at \
--to=michael.monnerie@is.it-management.at \
--cc=hch@infradead.org \
--cc=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