From: David Woodhouse <dwmw2@infradead.org>
To: Lukasz Trabinski <lukasz@trabinski.net>
Cc: Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
linux-kernel@vger.kernel.org, riel@redhat.com
Subject: Re: Linux 2.4.25-pre6
Date: Wed, 21 Jan 2004 11:07:09 +0000 [thread overview]
Message-ID: <1074683229.16045.122.camel@imladris.demon.co.uk> (raw)
In-Reply-To: <Pine.LNX.4.58LT.0401210746350.2482@lt.wsisiz.edu.pl>
On Wed, 2004-01-21 at 07:47 +0100, Lukasz Trabinski wrote:
> Here is:
> http://lukasz.eu.org/ksymoops.txt
Some weirdness in there. This is init, for example. Apparently in R
state (as are 260-odd other processes), and:
>>EIP; c02d5d38 <contig_page_data+298/3b8> <=====
Trace; c0106cfc <setup_frame+11c/210>
Trace; c0115ba8 <schedule_timeout+58/b0>
Trace; c013849c <__get_free_pages+1c/20>
Trace; c0115b30 <process_timeout+0/20>
Trace; c014be47 <pipe_poll+37/80>
Trace; c015315d <do_select+12d/250>
>From what I can tell, there are many people waiting on the inode_lock,
because kswapd has taken it and then taken a page fault....
Trace; c0130018 <filemap_nopage+f8/220>
Trace; c01148f0 <do_page_fault+0/5e4>
Trace; c01077f0 <error_code+34/3c>
Trace; c0158fb7 <refile_inode+47/a0>
Trace; c012d7a2 <__remove_inode_page+82/90>
I wonder if one of the lists is corrupt. I'd like to know _precisely_
what's at refile_inode+47 in your build. Please could you run 'gdb
vmlinux' and tell it 'disass refile_inode'. Then save the original
vmlinux somewhere, run 'make CFLAGS_inode.o=-g SUBDIRS=fs vmlinux', load
it in GDB again and repeat the disassembly, followed by 'list
*0xc0158fb7'?
I assume this is a clean 2.4.25-pre6 build with no other patches or
modules?
--
dwmw2
next prev parent reply other threads:[~2004-01-21 11:08 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-16 14:11 Marcelo Tosatti
2004-01-16 15:34 ` Maciej Soltysiak
2004-01-16 15:52 ` [PATCH 2.6] " Maciej Soltysiak
2004-01-16 18:14 ` Mike Fedyk
2004-01-16 18:25 ` [PATCH 2.6 FIXED] " Maciej Soltysiak
2004-01-20 21:25 ` Lukasz Trabinski
2004-01-20 21:41 ` Marcelo Tosatti
2004-01-21 6:47 ` Lukasz Trabinski
2004-01-21 10:53 ` Marcelo Tosatti
2004-01-21 11:28 ` Lukasz Trabinski
2004-01-21 11:54 ` David Woodhouse
2004-01-21 16:07 ` Lukasz Trabinski
2004-01-21 20:12 ` Marcelo Tosatti
2004-01-28 15:04 ` David Woodhouse
2004-01-28 17:03 ` Lukasz Trabinski
2004-02-02 22:24 ` Lukasz Trabinski
[not found] ` <Pine.LNX.4.58L.0401220929450.18938@logos.cnet>
[not found] ` <Pine.LNX.4.58LT.0401221248560.11640@oceanic.wsisiz.edu.pl>
[not found] ` <Pine.LNX.4.58L.0401221014510.18938@logos.cnet>
[not found] ` <Pine.LNX.4.58LT.0401221334070.2772@oceanic.wsisiz.edu.pl>
2004-02-04 13:26 ` Marcelo Tosatti
2004-02-04 18:45 ` Lukasz Trabinski
2004-02-04 23:20 ` Lukasz Trabinski
2004-01-21 11:01 ` Marcelo Tosatti
2004-01-21 11:07 ` David Woodhouse [this message]
2004-01-25 0:40 ` [2.4 patch] fix via-ircc.c .text.exit error Adrian Bunk
2004-01-26 19:28 ` Jean Tourrilhes
2004-01-26 21:01 ` Adrian Bunk
2004-01-26 21:02 ` David S. Miller
2004-01-26 21:42 ` Jean Tourrilhes
2004-01-26 22:11 ` Jean Tourrilhes
2004-01-20 22:02 Linux 2.4.25-pre6 Xose Vazquez Perez
2004-01-21 6:49 ` Lukasz Trabinski
2004-01-29 14:12 Samium Gromoff
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=1074683229.16045.122.camel@imladris.demon.co.uk \
--to=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukasz@trabinski.net \
--cc=marcelo.tosatti@cyclades.com \
--cc=riel@redhat.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
all inboxes | Powered by JetHome®