public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephan von Krawczynski <skraw@ithnet.com>
To: Willy Tarreau <willy@w.ods.org>
Cc: marcelo@conectiva.com.br, andrea@suse.de, linux-kernel@vger.kernel.org
Subject: Re: 2.4.22-pre lockups (decoded oops for pre8)
Date: Sun, 3 Aug 2003 11:40:52 +0200	[thread overview]
Message-ID: <20030803114052.731fae3e.skraw@ithnet.com> (raw)
In-Reply-To: <20030803072525.GB679@alpha.home.local>

On Sun, 3 Aug 2003 09:25:25 +0200
Willy Tarreau <willy@w.ods.org> wrote:

> Hi Stephan,
> 
> This is in remove_page_from_hash_queue() at filemap.c:114 :
>     *pprev = next;
> 
> pprev is taken from page->pprev_hash and is considered invalid here
> (4129b0fc). Assuming it has been corrupted earlier, it seems that the only
> files able to touch this either directly or indirectly are :
>   - mm/filemap.c (add_page_to_hash_queue, add_to_page_cache*)
>   - mm/shmem.c (add_to_page_cache_unique)
>   - mm/swap_state.c (idem)

>   - fs/ext3/inode.c and fs/buffer.c (find_or_create_page)

Ext3 is unlikely to be related, the box never saw ext3. Ext2 is only used on
/boot (so very unlikely, too), everything else is reiserfs.


> 
> So the problem may be narrowed down to a few files. Perhaps digging through
> the VM changes since before you had a problem will give you more clues...
> 
> Cheers,
> Willy

Thanks for commenting, the problem really is annoying because I _know_ the box
will freeze, only it takes time, this time 4 days...

Regards,
Stephan


  reply	other threads:[~2003-08-03  9:40 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.55L.0307251040240.12645@freak.distro.conectiva>
     [not found] ` <20030725174517.5b21116d.skraw@ithnet.com>
     [not found]   ` <Pine.LNX.4.55L.0307251545090.14733@freak.distro.conectiva>
2003-08-02 12:27     ` 2.4.22-pre lockups (decoded oops for pre8) Stephan von Krawczynski
2003-08-03  7:25       ` Willy Tarreau
2003-08-03  9:40         ` Stephan von Krawczynski [this message]
2003-08-05 16:40       ` Marcelo Tosatti
2003-08-06  2:37         ` Stephan von Krawczynski
2003-08-06  7:41         ` 2.4.22-pre lockups (now decoded oops for pre10) Stephan von Krawczynski
2003-08-06  8:58           ` Oleg Drokin
2003-08-06  9:09           ` Willy Tarreau
2003-08-06  9:36             ` Stephan von Krawczynski
2003-08-06 12:45               ` Willy Tarreau
2003-08-18 14:23             ` Andrea Arcangeli
2003-08-06 18:15           ` Marcelo Tosatti
2003-08-07  2:14             ` Stephan von Krawczynski
2003-08-07  5:35               ` Oleg Drokin
2003-08-07 12:45               ` Marcelo Tosatti
     [not found]                 ` <3F325198.2010301@namesys.com>
2003-08-07 13:32                   ` Stephan von Krawczynski
2003-08-18 20:29                     ` Mike Fedyk
2003-08-18 20:39                       ` Stephan von Krawczynski
2003-08-18 21:05                         ` [grammar] " Matt Gibson
2003-08-18 21:09                         ` Mike Fedyk
2003-08-07 15:52                 ` Stephan von Krawczynski

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=20030803114052.731fae3e.skraw@ithnet.com \
    --to=skraw@ithnet.com \
    --cc=andrea@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    --cc=willy@w.ods.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