Summary: | sys-kernel/hardened-sources-3.2.11 - beam: page allocation failure: order:1, mode:0x20 or swapper: page allocation failure: order:1, mode:0x20 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | cyberbat <cyberbat83> |
Component: | [OLD] Core system | Assignee: | The Gentoo Linux Hardened Kernel Team (OBSOLETE) <hardened-kernel+disabled> |
Status: | RESOLVED OBSOLETE | ||
Severity: | normal | CC: | hardened, kernel, pageexec |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
.config
full dmesg .config diff |
Description
cyberbat
2012-05-24 18:50:24 UTC
Created attachment 312983 [details]
full dmesg
This is probably pax related. Can you turn off pax and see if the problem goes away. I'm cc-ing upstream too. (In reply to comment #2) > This is probably pax related. Can you turn off pax and see if the problem > goes away. I'm cc-ing upstream too. i don't see how PaX is related to this OOM ;). just give your VM enough memory. Created attachment 313091 [details]
.config diff
I'm not sure that it's because of memory amount. Before upgrade everything was ok. I have played with highmem optuions in kernel (turn highmem off, change processor type, and so on see .config diff. I have 512MB on my VPS) and errors gone away. But I'm not sure what option made it.
(In reply to comment #4) > I'm not sure that it's because of memory amount. well, strictly speaking it wasn't 'not enough memory' in general, but 'no big enough contiguous free memory'. thing is, i still think the memory allocated to your VM was on the edge and you were just lucky before to not hit this fragmentation problem (what was your previous kernel version btw?). I have never such problem. There was no grow of load on VDS and according to htop I have near 50% of RAM (128 of 256) and 100% of swap (512) free. I've used hardened-sources 3.2.2-r1 before. I have to repeat that after making changes described in comment 4 I have no error at all. 3.2.11 has been off the tree for a while. If this is a problem with any kernel on the tree, please reopen. |