xfs
[Top] [All Lists]

Re: kernel crash 2.6.31.14-0.1-xen from openSUSE 11.2

To: xfs@xxxxxxxxxxx
Subject: Re: kernel crash 2.6.31.14-0.1-xen from openSUSE 11.2
From: Michael Monnerie <michael.monnerie@xxxxxxxxxxxxxxxxxxx>
Date: Mon, 11 Oct 2010 06:57:55 +0200
Cc: Dave Chinner <david@xxxxxxxxxxxxx>
In-reply-to: <20101010015628.GL4681@dastard>
Organization: it-management http://it-management.at
References: <201010092355.17240@xxxxxx> <20101010015628.GL4681@dastard>
User-agent: KMail/1.13.5 (Linux/2.6.34.7-0.3-desktop; KDE/4.4.4; x86_64; ; )
On Sonntag, 10. Oktober 2010 Dave Chinner wrote:
> > [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
> 
>                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> 
> 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.....

Thanks. So what? Didn't we have this before? I sent a mail on May 21, 
2010, with subject "kernel crash: scheduling while atomic". Eric Sandeen 
said "I'm guessing you blew the stack".

So what should I do about it? I think I read about a patch that should 
fix this. Seems Novell/openSUSE didn't backport it, so could someone 
please guide me where to find it? And I guess I should report upstream, 
right?

-- 
mit freundlichen Grüssen,
Michael Monnerie, Ing. BSc

it-management Internet Services
http://proteger.at [gesprochen: Prot-e-schee]
Tel: 0660 / 415 65 31

****** Aktuelles Radiointerview! ******
http://www.it-podcast.at/aktuelle-sendung.html

// Wir haben im Moment zwei Häuser zu verkaufen:
// http://zmi.at/langegg/
// http://zmi.at/haus2009/

Attachment: signature.asc
Description: This is a digitally signed message part.

<Prev in Thread] Current Thread [Next in Thread>