From: William Lee Irwin III <wli@holomorphy.com>
To: Micah Anderson <micah@riseup.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: 2.6.6 grinds to a halt with moderate I/O
Date: Tue, 15 Jun 2004 11:30:18 -0700 [thread overview]
Message-ID: <20040615183018.GC1444@holomorphy.com> (raw)
In-Reply-To: <20040615181908.GC22650@riseup.net>
At some point in the past, I wrote:
>> Thanks for the bugreport. I'm going to file this in the Debian BTS
>> after I get the FPU fixes out. Could you send along a dmesg
>> (/var/log/dmesg on Debian) and /proc/meminfo and /proc/cpuinfo at some
>> point when you can log into the box? I'll also try to reproduce this.
On Tue, Jun 15, 2004 at 01:19:08PM -0500, Micah Anderson wrote:
> I am not sure why this would be filed in the Debian BTS, yes the
> underlying OS is Debian, but this is not a Debian Kernel, it is a
> vanilla 2.6.6 kernel that I compiled by hand.
The debian kernel team is migrating Debian's 2.6 as close to mainline
as is possible within policy guidelines, so it'll be applicable to it
hopefully in the next 24 hours.
On Tue, Jun 15, 2004 at 01:19:08PM -0500, Micah Anderson wrote:
> Please find attached the dmesg and the /proc/meminfo, the
> /proc/cpuinfo was already included in the original email.
Okay, thanks. I'll do some testing of copying large files shortly.
-- wli
next prev parent reply other threads:[~2004-06-15 18:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-15 15:47 PROBLEM: 2.6.6 grinds to a halt with moderate I/O Micah Anderson
2004-06-15 16:00 ` William Lee Irwin III
2004-06-15 18:19 ` Micah Anderson
2004-06-15 18:30 ` William Lee Irwin III [this message]
2004-06-16 7:43 ` Philippe Gramoullé
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=20040615183018.GC1444@holomorphy.com \
--to=wli@holomorphy.com \
--cc=linux-kernel@vger.kernel.org \
--cc=micah@riseup.net \
/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