From: Ralf Hildebrandt <Ralf.Hildebrandt@charite.de>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.4.21-pre3-ac4 oops in free_pages_ok
Date: Fri, 17 Jan 2003 08:47:13 +0100 [thread overview]
Message-ID: <20030117074713.GF12788@charite.de> (raw)
In-Reply-To: <3E27044C.4010308@tupshin.com>
* Tupshin Harper <tupshin@tupshin.com>:
> There are multiple other threads about this problem recently. One
> started by me, as well as a few others.
> The consensus is that it's a problem in the ac tree, and is not present
> in 2.4.21-pre3.
Yep.
> Some people seem to avoid the problem by disabling highmem, but this
> doesn't work for me. Quota has been mentioned as a possible culprit, but
> disabling that also doesn't help me.
Correct. I use neither himem nor quotas, still it crashes.
> The ac changes to mm/shmem.c are
> still a possibility, though one reporter seems to have tried that
> without any success.
Yup, I tried that. No go.
> The remaining candidate that has been mentioned to
> me is the buffer cache changes in the ac tree, this seems moderately
> likely. I don't see any obvious way to break out those changes from
> Alan's large ac4 patch, so I emailed him hoping to get a patch free of
> those changes, but I haven't heard back yet(it's been 9 hours
> already...how dare he ignore me ;-).
--
Ralf Hildebrandt (Im Auftrag des Referat V a) Ralf.Hildebrandt@charite.de
Charite Campus Mitte Tel. +49 (0)30-450 570-155
Referat V a - Kommunikationsnetze - Fax. +49 (0)30-450 570-916
"The report of my death was an exaggeration."
-Mark Twain, After reading his own obituary, June 2, 1897
next prev parent reply other threads:[~2003-01-17 7:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-16 16:28 2.4.21-pre3-ac4 oops in free_pages_ok Phil Oester
2003-01-16 19:13 ` Tupshin Harper
2003-01-17 7:47 ` Ralf Hildebrandt [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-18 0:05 Bryan Andersen
2003-01-19 11:01 ` Bryan Andersen
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=20030117074713.GF12788@charite.de \
--to=ralf.hildebrandt@charite.de \
--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