From: "Stephen C. Tweedie" <sct@redhat.com>
To: Steffen Persvold <sp@scali.no>
Cc: "Stephen C. Tweedie" <sct@redhat.com>,
Andrew Morton <akpm@zip.com.au>,
lkml <linux-kernel@vger.kernel.org>,
nfs list <nfs@lists.sourceforge.net>,
ext2-devel@lists.sourceforge.net
Subject: Re: [Ext2-devel] Re: 2.4.9 kernel crash
Date: Thu, 6 Dec 2001 18:50:27 +0000 [thread overview]
Message-ID: <20011206185027.O2029@redhat.com> (raw)
In-Reply-To: <3C077FF8.AFBD8DB8@scali.no> <3C07E905.DF30E497@zip.com.au> <20011204003350.L2857@redhat.com> <3C0FB84A.76D8C003@scali.no>
In-Reply-To: <3C0FB84A.76D8C003@scali.no>; from sp@scali.no on Thu, Dec 06, 2001 at 07:26:18PM +0100
Hi,
On Thu, Dec 06, 2001 at 07:26:18PM +0100, Steffen Persvold wrote:
> So what could this be then ?
> VFS: Busy inodes after unmount. Self-destruct in 5 seconds. Have a nice day...
This one is a little unfamiliary, but the oops:
> Call Trace: [<c0150eb6>] prune_dcache [kernel] 0xf6
> [<c01357a5>] page_launder [kernel] 0x8f5
> [<c01512a1>] shrink_dcache_memory [kernel] 0x21
> [<c0135bab>] do_try_to_free_pages [kernel] 0x1b
> [<c0135c35>] kswapd [kernel] 0x55
> [<c0105000>] stext [kernel] 0x0
> [<c0105866>] kernel_thread [kernel] 0x26
> [<c0135be0>] kswapd [kernel] 0x0
has been reported before, even on much more recent kernels, and even
without ext3 loaded. So basically I've no idea what's behind it.
Cheers,
Stephen
next prev parent reply other threads:[~2001-12-06 18:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-30 12:47 2.4.9 kernel crash Steffen Persvold
2001-11-30 20:16 ` Andrew Morton
2001-12-03 19:10 ` [NFS] " Stephen Walton
2001-12-04 0:32 ` [Ext2-devel] " Stephen C. Tweedie
2001-12-04 0:33 ` [Ext2-devel] " Stephen C. Tweedie
2001-12-06 18:26 ` Steffen Persvold
2001-12-06 18:50 ` Stephen C. Tweedie [this message]
2001-12-06 20:52 ` [NFS] " Ragnar Kjørstad
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=20011206185027.O2029@redhat.com \
--to=sct@redhat.com \
--cc=akpm@zip.com.au \
--cc=ext2-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=nfs@lists.sourceforge.net \
--cc=sp@scali.no \
/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.