From: torvalds@transmeta.com (Linus Torvalds)
To: linux-kernel@vger.kernel.org
Subject: Re: pre6 BUG oops
Date: Wed, 31 Oct 2001 18:19:31 +0000 (UTC) [thread overview]
Message-ID: <9rpfbj$vrn$1@penguin.transmeta.com> (raw)
In-Reply-To: <3BE03401.406B8585@mandrakesoft.com> <20011031.094112.125896630.davem@redhat.com>
In article <20011031.094112.125896630.davem@redhat.com>,
David S. Miller <davem@redhat.com> wrote:
> From: Jeff Garzik <jgarzik@mandrakesoft.com>
> Date: Wed, 31 Oct 2001 12:25:21 -0500
>
> 2.4.14-pre6 on UP alpha, newly reformatted and reinstalled :)
>
> Machine was nowhere near OOM, and no other adverse messages appeared in
> dmesg. An rpm build and an rpm install were running in parallel.
>
>Hmmm... the oops suggests that truncate_complete_page() gets a page
>not in the page cache. The page count should be at least 2 when
>it gets passed there.
Indeed. Looks like somebody removed the page from the page cache
without removing it from the inode queue.
Which sounds rather impossible, as the two are always done together.
Maybe it's just the page count that is buggered, and we free it too
early as a result. Is this the same machine that had interesting
trouble before?
Linus
next prev parent reply other threads:[~2001-10-31 18:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-31 17:25 pre6 BUG oops Jeff Garzik
2001-10-31 17:41 ` David S. Miller
2001-10-31 18:19 ` Linus Torvalds [this message]
2001-10-31 18:30 ` Jeff Garzik
2001-10-31 19:53 ` Linus Torvalds
2001-10-31 21:48 ` 2.4.13 (and 2.4.5) performance drops under load and does not recover David Lang
2001-10-31 23:22 ` David Lang
2001-11-01 21:37 ` David Lang
2001-11-01 22:12 ` ip tables performace problem was " David Lang
2001-11-03 20:46 ` pre6 BUG oops Richard Henderson
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='9rpfbj$vrn$1@penguin.transmeta.com' \
--to=torvalds@transmeta.com \
--cc=linux-kernel@vger.kernel.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