From: Eric Sandeen <sandeen@sandeen.net>
To: Dave Chinner <david@fromorbit.com>
Cc: Michael Monnerie <michael.monnerie@is.it-management.at>, xfs@oss.sgi.com
Subject: Re: kernel crash 2.6.31.14-0.1-xen from openSUSE 11.2
Date: Wed, 13 Oct 2010 17:07:56 -0500 [thread overview]
Message-ID: <4CB62DBC.9060808@sandeen.net> (raw)
In-Reply-To: <20101010015628.GL4681@dastard>
On 10/09/2010 08:56 PM, Dave Chinner wrote:
> On Sat, Oct 09, 2010 at 11:55:16PM +0200, Michael Monnerie wrote:
>> I just had a bug in one VM, and don't know if this is XFS related, but it seems so.
>>
>> [1172140.926859] BUG: unable to handle kernel paging request at 00000003d03dd178
>> [1172140.926877] IP: [<ffffffff80034872>] dequeue_task+0x72/0x110
>> [1172140.926897] PGD 1b54b067 PUD 0
>> [1172140.926897] Thread overran stack, or stack corrupted
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Awesome, that's the 2nd time in like 4 years I've seen that stack canary
I put in actually be useful ;)
-Eric
> The stack trace shows pdflush doing writeback, and way down the
> stack doing a memory allocation that triggered direct reclaim, which
> caused writeback to occur, which blew the stack.....
>
> Cheers,
>
> Dave.
>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-10-13 22:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-09 21:55 kernel crash 2.6.31.14-0.1-xen from openSUSE 11.2 Michael Monnerie
2010-10-10 1:56 ` Dave Chinner
2010-10-11 4:57 ` Michael Monnerie
2010-10-13 22:07 ` Eric Sandeen [this message]
2010-10-14 5:18 ` Michael Monnerie
2010-10-15 9:13 ` Michael Monnerie
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=4CB62DBC.9060808@sandeen.net \
--to=sandeen@sandeen.net \
--cc=david@fromorbit.com \
--cc=michael.monnerie@is.it-management.at \
--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 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.