lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Sat, 20 Jan 2007 16:03:42 -0500 (EST)
From:	Justin Piszcz <jpiszcz@...idpixels.com>
To:	Avuton Olrich <avuton@...il.com>
cc:	linux-kernel@...r.kernel.org, linux-raid@...r.kernel.org
Subject: Re: 2.6.19.2, cp 18gb_file 18gb_file.2 = OOM killer, 100% reproducible



On Sat, 20 Jan 2007, Avuton Olrich wrote:

> On 1/20/07, Justin Piszcz <jpiszcz@...idpixels.com> wrote:
> > Perhaps its time to back to a stable (2.6.17.13 kernel)?
> >
> > Anyway, when I run a cp 18gb_file 18gb_file.2 on a dual raptor sw raid1
> > partition, the OOM killer goes into effect and kills almost all my
> > processes.
> >
> > Completely 100% reproducible.
> >
> > Does 2.6.19.2 have some of memory allocation bug as well?
> 
> I had been seeing something similar (also with 2.6.19.2), but it's not
> outputting anything to dmesg, so I was waiting for something to happen
> before I reported it. It's mostly the same thing, but I've only seen
> it happen when copying something large (2+ GB) over NFS. Interactivity
> completely goes away and lockups last 10-15 seconds a piece. Then
> realized I turned the swap off, so I turned it on and didn't lockup
> any longer.
> -- 
> avuton
> --
> Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
> 
> 

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 :(

Justin.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ