From: Dave Hansen <haveblue@us.ibm.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Andrew Morton <akpm@digeo.com>,
lkml <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: 2.5.41-mm2
Date: Wed, 09 Oct 2002 23:44:17 -0700 [thread overview]
Message-ID: <3DA521C1.2060707@us.ibm.com> (raw)
In-Reply-To: Pine.LNX.4.44.0210100841280.4384-100000@localhost.localdomain
Ingo Molnar wrote:
> On Wed, 9 Oct 2002, Andrew Morton wrote:
>
>> Ingo's original per-cpu-pages patch was said to be mainly beneficial
>> for web-serving type things, but no specweb testing has been possible
>> for a week or two due to oopses in the timer code.
>
> i sent my latest timer patch to Dave Hansen but have not heard back since.
> I've attached the latest patch, this kernel also printks a bit more when
> it sees invalid timer usage.
>
> in any case, the oops Dave was seeing i believe was fixed by Linus (the
> PgUp fix), and it was in the keyboard code. If there's anything else still
> going on then the attached patch should either fix it or provide further
> clues.
Sorry, I haven't had a chance to test it yet. The Specweb setup likes
to eat ethernet cards and I haven't put in replacements yet. I'll try
and get some time in on it tomorrow.
--
Dave Hansen
haveblue@us.ibm.com
WARNING: multiple messages have this Message-ID (diff)
From: Dave Hansen <haveblue@us.ibm.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Andrew Morton <akpm@digeo.com>,
lkml <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: 2.5.41-mm2
Date: Wed, 09 Oct 2002 23:44:17 -0700 [thread overview]
Message-ID: <3DA521C1.2060707@us.ibm.com> (raw)
In-Reply-To: Pine.LNX.4.44.0210100841280.4384-100000@localhost.localdomain
Ingo Molnar wrote:
> On Wed, 9 Oct 2002, Andrew Morton wrote:
>
>> Ingo's original per-cpu-pages patch was said to be mainly beneficial
>> for web-serving type things, but no specweb testing has been possible
>> for a week or two due to oopses in the timer code.
>
> i sent my latest timer patch to Dave Hansen but have not heard back since.
> I've attached the latest patch, this kernel also printks a bit more when
> it sees invalid timer usage.
>
> in any case, the oops Dave was seeing i believe was fixed by Linus (the
> PgUp fix), and it was in the keyboard code. If there's anything else still
> going on then the attached patch should either fix it or provide further
> clues.
Sorry, I haven't had a chance to test it yet. The Specweb setup likes
to eat ethernet cards and I haven't put in replacements yet. I'll try
and get some time in on it tomorrow.
--
Dave Hansen
haveblue@us.ibm.com
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/
next prev parent reply other threads:[~2002-10-10 6:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-10 5:40 2.5.41-mm2 Andrew Morton
2002-10-10 5:40 ` 2.5.41-mm2 Andrew Morton
2002-10-10 5:59 ` 2.5.41-mm2 David S. Miller
2002-10-10 5:59 ` 2.5.41-mm2 David S. Miller
2002-10-10 6:45 ` 2.5.41-mm2 Ingo Molnar
2002-10-10 6:45 ` 2.5.41-mm2 Ingo Molnar
2002-10-10 6:44 ` Dave Hansen [this message]
2002-10-10 6:44 ` 2.5.41-mm2 Dave Hansen
2002-10-11 4:32 ` 2.5.41-mm2 Dave Hansen
2002-10-11 5:30 ` 2.5.41-mm2 Ingo Molnar
2002-10-10 8:18 ` 2.5.41-mm2 William Lee Irwin III
2002-10-10 8:18 ` 2.5.41-mm2 William Lee Irwin III
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=3DA521C1.2060707@us.ibm.com \
--to=haveblue@us.ibm.com \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@elte.hu \
/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.