Hi all,
I just wrote a post in my blog about Linux (2.6.35 on x86_64) oopsing
and hanging when allocating huge amounts of RAM. There are a couple of
plain C programs in the post that did the job pretty well. You may want
to try them yourselves. Or maybe suggest reasons why this happens at
On 05/17/2012 08:56 PM, Shlomi Fish wrote:
Oh wait! You're using kernel-2.6.35.4 - not kernel 3.5.x (which does not exist
yet). That's a really old version. Is it an up-to-date distribution kernel? If
so - you can report it to your distributor. If not - you should upgrade.
Of course I should
Hi Eli,
On Thu, 17 May 2012 20:48:59 +0300
Shlomi Fish shlo...@shlomifish.org wrote:
Hi Eli,
On Thu, 17 May 2012 19:34:12 +0300
Eli Billauer e...@billauer.co.il wrote:
Hi all,
I just wrote a post in my blog about Linux (2.6.35 on x86_64) oopsing
and hanging when allocating huge
Hi Eli,
On Thu, 17 May 2012 19:34:12 +0300
Eli Billauer e...@billauer.co.il wrote:
Hi all,
I just wrote a post in my blog about Linux (2.6.35 on x86_64) oopsing
and hanging when allocating huge amounts of RAM. There are a couple of
plain C programs in the post that did the job pretty
On Thu, May 17, 2012 at 09:31:16PM +0300, Eli Billauer wrote:
On 05/17/2012 08:56 PM, Shlomi Fish wrote:
Oh wait! You're using kernel-2.6.35.4 - not kernel 3.5.x (which does not
exist
yet). That's a really old version. Is it an up-to-date distribution kernel?
If
so - you can report it to
On 05/17/2012 10:23 PM, Tzafrir Cohen wrote:
I may consider upgrading to a kernel 2.6.35 which has gone through a
long phase of "bug fixes only" but I understand there is no such around
at the moment. What I call a vintage kernel.
You obviously have a beefy system with
