search

michalpolkowski / alt-f

Automatically exported from code.google.com/p/alt-f
0 stars 0 forks source link

to many user.warn kernel #136

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Go to system log, and read the log

What is the expected output? What do you see instead?
I never encounter this kind of log in RC2
http://pastie.org/7122601

What Alt-F version are you using? Have you flashed it?
RC3, flased

What is the box hardware revision level? A1, B1 or C1? (look at the label
at the box bottom)
C1

What is your disk configuration? Standard, RAID (what level)...
Standard

What operating system are you using on your computer? Using what browser?
latest Firefox, latest OSX

Original issue reported on code.google.com by zero1...@gmail.com on 26 Mar 2013 at 11:28

GoogleCodeExporter commented 9 years ago 
This used to be a "frequent" warning, when there are many memory-demanding apps 
running.

I remember researching this, and the outcome was that is was a inocuos warning 
message.
There was a patch to avoid the kernel spitting the warning, but it was not 
accepted for inclusion.

I hope that the move to a more recent kernel, and a different memory allocator 
(SLUB instead of SLAB),
will make this vanish for ever.
But the main kernel developers are not very worried with low memory equipped 
computers (embedded), so it is not guaranteed the issue will disappears.

For future reference, I enclose a log of it when testing Transmission-2.80 
during heavy downloading.
In this case, the constant flood of new packets from different sources, with 
long TTL, should be the cause of the warning.
In other cases, such as running Python or PHP based apps, the huge code size 
requirement should be the reason.

Not closing just for future reference against the new kernel, but no action 
will be taken.

Original comment by whoami.j...@gmail.com on 29 Jun 2013 at 5:58

Attachments: