From: Andrew Morton <andrewm@uow.edu.au>
To: Henry <henry@borg.metroweb.co.za>
Cc: linux-kernel@vger.kernel.org
Subject: Re: OOPS (kswapd) in 2.4.5 and 2.4.6
Date: Sat, 07 Jul 2001 18:07:30 +1000 [thread overview]
Message-ID: <3B46C342.A27D6C50@uow.edu.au> (raw)
In-Reply-To: <01070516412506.06182@borg> <3B457835.F06E49CF@uow.edu.au>, <3B457835.F06E49CF@uow.edu.au> <01070708085101.00793@borg>
Henry wrote:
>
> ...
> So far, so good. There has not been a single oops on the two principle
> servers I patched.
>
> uptime1: 8:04am up 18:22, 1 user, load average: 0.09, 0.15, 0.11
> uptime2: 8:04am up 18:25, 1 user, load average: 0.15, 0.20, 0.15
OK, that looks good.
> Andrew my china, you are the _MAN_!
Not only that - I have great legs!
> We should know by monday afternoon
> (the monday morning/midday crunch should provide some valuable
> feedback).
I wonder why it only affects you. Is the drive which holds
your swap partition running in PIO mode? `hdparm' will tell
you. If it is, then that could easily cause the page to come
unlocked before brw_page() has finished touching the buffer
ring. Then all it takes is a parallel try_to_free_buffers
on the other CPU.
There's a similar bug in __block_write_full_page(). I'll
send a patch...
-
next prev parent reply other threads:[~2001-07-07 8:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-05 14:03 OOPS (kswapd) in 2.4.5 and 2.4.6 Henry
2001-07-05 16:53 ` Wayne Whitney
2001-07-05 17:09 ` Henry
2001-07-06 5:59 ` Henry
2001-07-06 8:35 ` Andrew Morton
2001-07-06 10:31 ` Henry
2001-07-07 6:03 ` Henry
2001-07-07 8:07 ` Andrew Morton [this message]
2001-07-07 9:33 ` Henry
2001-07-07 9:54 ` Andrew Morton
2001-07-08 11:08 ` Henry
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=3B46C342.A27D6C50@uow.edu.au \
--to=andrewm@uow.edu.au \
--cc=henry@borg.metroweb.co.za \
--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