From: Robert Love <rml@tech9.net>
To: "Alexandre P. Nunes" <alex@PolesApart.dhs.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: 2.4.19-pre10-ac2 bug in page_alloc.c:131
Date: 27 Jun 2002 14:31:54 -0400 [thread overview]
Message-ID: <1025202738.1084.12.camel@icbm> (raw)
In-Reply-To: <3D1B5982.60008@PolesApart.dhs.org>
On Thu, 2002-06-27 at 14:29, Alexandre P. Nunes wrote:
> The user (oops, that is me) was using
> preempt-kernel-rml-2.4.19-pre10-ac2-1, by the time of the report.
Ah try preempt-kernel-rml-2.4.19-pre10-ac2-2 which has the bit lock
safing William mentioned.
Robert Love
next prev parent reply other threads:[~2002-06-27 18:35 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-23 1:13 PROBLEM: 2.4.19-pre10-ac2 bug in page_alloc.c:131 Alexandre Pereira Nunes
2002-06-23 11:07 ` Diego Calleja
2002-06-23 11:40 ` Alexandre Pereira Nunes
2002-06-26 20:47 ` William Lee Irwin III
2002-06-26 21:00 ` Bongani
2002-06-26 21:45 ` khromy
2002-06-26 21:54 ` Robert Love
2002-06-26 22:12 ` Bongani
2002-06-26 22:08 ` Robert Love
2002-06-27 0:54 ` William Lee Irwin III
2002-06-27 15:40 ` Robert Love
2002-06-27 15:47 ` William Lee Irwin III
2002-06-27 18:29 ` Alexandre P. Nunes
2002-06-27 18:31 ` Robert Love [this message]
2002-06-27 18:53 ` Alexandre P. Nunes
2002-06-27 20:05 ` J Sloan
2002-06-27 20:23 ` 2.4.19-rc1 + O(1) scheduler Alexandre P. Nunes
2002-06-27 20:37 ` J Sloan
2002-06-27 20:39 ` Robert Love
[not found] <200206231945.27717.markus_schoder@yahoo.de>
2002-06-24 12:23 ` PROBLEM: 2.4.19-pre10-ac2 bug in page_alloc.c:131 Alexandre P. Nunes
2002-06-24 14:17 ` Alan Cox
2002-06-24 15:06 ` Alexandre P. Nunes
2002-06-24 15:04 ` David S. Miller
2002-06-24 16:47 ` Alexandre P. Nunes
2002-07-01 2:18 ` Pavel Machek
2002-07-02 1:39 ` Horst von Brand
2002-07-02 16:29 ` Bill Davidsen
2002-07-02 17:04 ` Alexandre P. Nunes
2002-07-02 23:25 ` Matthias Andree
2002-06-24 15:18 ` Zwane Mwaikambo
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=1025202738.1084.12.camel@icbm \
--to=rml@tech9.net \
--cc=alex@PolesApart.dhs.org \
--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