From: Philipp Rumpf <prumpf@parcelfarce.linux.theplanet.co.uk>
To: Daniel Phillips <phillips@innominate.de>
Cc: Mark Hindley <mh15@st-andrews.ac.uk>, linux-kernel@vger.kernel.org
Subject: Re: 2.4.0 kernel paging error
Date: Wed, 10 Jan 2001 18:47:09 +0000 [thread overview]
Message-ID: <20010110184709.F21944@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <l03130302b681de2fd7a0@[138.251.135.28]> <3A5C93E9.A96EF8AE@innominate.de>
In-Reply-To: <3A5C93E9.A96EF8AE@innominate.de>; from phillips@innominate.de on Wed, Jan 10, 2001 at 05:55:05PM +0100
On Wed, Jan 10, 2001 at 05:55:05PM +0100, Daniel Phillips wrote:
> Mark Hindley wrote:
> > I am running 2.4.0 final. I got the following failed paging request which
> > produced a complete freeze.
> >
> > As you can see it was precipitated by cron starting to run some
> > housekeeping stuff overnight.
> >
> > Has anyone else had prblems?
>
> It looks real. It was executing this line of clear_inode in fs/inode.c:
>
> 380 if (inode->i_sb && inode->i_sb->s_op && inode->i_sb->s_op->clear_inode)
> ^^^^^^^^^^^^^
> and it blew up here ----->
> Unable to handle kernel paging request at virtual address c4870840
I'm pretty sure this is a vmalloc/module address, which would mean ->s_op
points to a module that has been unloaded. This sounds consistent with the
"cron starting to run some housekeeping stuff" above.
Mark, which file systems are you using ?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-10 18:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-10 9:39 2.4.0 kernel paging error Mark Hindley
2001-01-10 16:55 ` Daniel Phillips
2001-01-10 18:47 ` Philipp Rumpf [this message]
2001-01-11 8:23 ` Mark Hindley
2001-01-11 8:32 ` Keith Owens
-- strict thread matches above, loose matches on Subject: below --
2001-01-10 10:04 anders.karlsson
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=20010110184709.F21944@parcelfarce.linux.theplanet.co.uk \
--to=prumpf@parcelfarce.linux.theplanet.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mh15@st-andrews.ac.uk \
--cc=phillips@innominate.de \
/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.