From: thunder7@xs4all.nl
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: Avuton Olrich <avuton@gmail.com>,
linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org
Subject: Re: 2.6.19.2, cp 18gb_file 18gb_file.2 = OOM killer, 100% reproducible
Date: Sun, 21 Jan 2007 16:52:19 +0100 [thread overview]
Message-ID: <20070121155219.GA7413@amd64.of.nowhere> (raw)
In-Reply-To: <Pine.LNX.4.64.0701201602570.4910@p34.internal.lan>
From: Justin Piszcz <jpiszcz@lucidpixels.com>
Date: Sat, Jan 20, 2007 at 04:03:42PM -0500
>
>
> My swap is on, 2GB ram and 2GB of swap on this machine. I can't go back
> to 2.6.17.13 as it does not recognize the NICs in my machine correctly and
> the Alsa Intel HD Audio driver has bugs etc, I guess I am stuck with
> 2.6.19.2 :(
>
Well, if you can't go back, you could always test 2.6.20-rc5. That's why
it's out there :-) It can't be any worse!
Good luck,
Jurriaan
--
It might look like I'm doing nothing, but at the cellular level I'm really
quite busy.
Hans Haas
Debian (Unstable) GNU/Linux 2.6.20-rc5 2x2011 bogomips load 1.97
the Jack Vance Integral Edition: http://www.integralarchive.org
next prev parent reply other threads:[~2007-01-21 15:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-20 20:20 2.6.19.2, cp 18gb_file 18gb_file.2 = OOM killer, 100% reproducible Justin Piszcz
2007-01-20 20:45 ` Avuton Olrich
2007-01-20 21:03 ` Justin Piszcz
2007-01-20 21:24 ` Justin Piszcz
2007-01-21 15:52 ` thunder7 [this message]
2007-01-21 15:54 ` Justin Piszcz
2007-01-26 17:49 ` Adrian Bunk
2007-01-26 17:50 ` Justin Piszcz
2007-01-21 16:48 ` Justin Piszcz
2007-01-21 17:02 ` thunder7
2007-01-21 17:08 ` Justin Piszcz
2007-01-21 17:29 ` 2.6.19.2, cp 18gb_file 18gb_file.2 = OOM killer, 100% reproducible (multi-threaded USB no go) Justin Piszcz
2007-01-22 6:33 ` Greg KH
2007-01-22 10:56 ` Justin Piszcz
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=20070121155219.GA7413@amd64.of.nowhere \
--to=thunder7@xs4all.nl \
--cc=avuton@gmail.com \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@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;
as well as URLs for NNTP newsgroup(s).