Kurt Roeckx wrote:
It's running linux-image-2.6.32-5-amd64 2.6.32-45
Note that this has nothing to do with vserver, just that people
seeing it and reported it so far happened to run that version.
Hm. page allocation failure usually means that (some particular
kind of) memory has been
On Tue, Jul 10, 2012 at 02:44:25PM -0500, Jonathan Nieder wrote:
However, you are using r8169 here, not e1000.
I think the network driver itself is not related to the problem,
it's just that it wants RAM and can't get any.
Any leads towards
finding the resource hog, source of
merge 495919 477377
tags 477377 + moreinfo
quit
Kurt Roeckx wrote:
You might also want to look at #477377
Ok, merging optimistically. But we don't maintain the lenny kernels;
has this been reproduced in squeeze, too?
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
On Mon, Jul 09, 2012 at 09:16:03PM -0500, Jonathan Nieder wrote:
merge 495919 477377
tags 477377 + moreinfo
quit
Kurt Roeckx wrote:
You might also want to look at #477377
Ok, merging optimistically. But we don't maintain the lenny kernels;
has this been reproduced in squeeze, too?
Kurt Roeckx wrote:
It has been seen on homer during debconf, or at least something
that looks very simular to it. The machine was also doing around
50 MB/s.
Ok, thanks. What kernel was homer running? Do you have corresponding
logs? (A trace of the page allocation failure plus a log of the
5 matches
Mail list logo
