for the record: the "oom bug" turned out to be user generated. a *lot* of
small scripts were started, triggering oom again and again, user error.
the source of the problem is still pppd and the discussion continues as a
debian bugreport:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=299875
Coywolf Qi Hunt wrote:
> I do "grep check-route.sh oom_2.6.11.3.txt | wc" and it shows 4365
duh, good catch! really!
> lines, which means there're 4365 that script processes running, from
> pid 4260 to12747, mostly with pretty low points, 123.
> Based on this points, suppose each script consumes
On Thu, 17 Mar 2005 02:27:29 +0100, Christian Kujau <[EMAIL PROTECTED]> wrote:
> hello again,
>
> unfortunately i've hit OOM again, this time with "#define DEBUG" enabled
> in mm/oom_kill.c:
>
> http://nerdbynature.de/bits/sheep/2.6.11/oom/oom_2.6.11.3.txt
>
> by "Mar 16 18:32" pppd died again a
Andrew Morton wrote:
>
> Some application went berzerk, used up all the swap and then oomed the box.
>
> You could perhaps run `top -d1' then hit M so the output is sorted by
> bloatiness, then try to catch the culprit.
i've already done that. as OOM happens when i am not around, i did that
with
Christian Kujau <[EMAIL PROTECTED]> wrote:
>
> unfortunately i've hit OOM again, this time with "#define DEBUG" enabled
> in mm/oom_kill.c:
>
> http://nerdbynature.de/bits/sheep/2.6.11/oom/oom_2.6.11.3.txt
>
> by "Mar 16 18:32" pppd died again and OOM kicked in 30min later.
> (there are a *lo
hello again,
unfortunately i've hit OOM again, this time with "#define DEBUG" enabled
in mm/oom_kill.c:
http://nerdbynature.de/bits/sheep/2.6.11/oom/oom_2.6.11.3.txt
by "Mar 16 18:32" pppd died again and OOM kicked in 30min later.
(there are a *lot* messages of a shell script named "check-route.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mauricio Lin wrote:
>>>
>>>Did this problem start from 2.6.11-rc2-bk10?
>>
>>i noticed it first at 2.6.11, then again with 2.6.11-rc5-bk2. suspecting
>>pppd to be the culprit to chew up all RAM after being terminated by my ISP
>>once a day - i just hav
Hi Christian,
On Fri, 11 Mar 2005 16:09:24 +0100, Christian Kujau <[EMAIL PROTECTED]> wrote:
> Mauricio Lin wrote:
> > Hi Christian,
> >
> > I would like to know what are the kernel versions this problem happened.
> >
> > Did this problem start from 2.6.11-rc2-bk10?
>
> i noticed it first at 2.6.
hi again,
i had to wait for my pppoe session to be terminated by the remote peer
[1], and now it happened again with 2.6.11-rc5-bk2:
http://nerdbynature.de/bits/sheep/2.6.11/oom/oom_2.6.11-rc5-bk2_2.txt
http://nerdbynature.de/bits/sheep/2.6.11/oom/lsmod_2.6.11-rc5-bk2
http://nerdbynature.de/bits/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Coywolf Qi Hunt wrote:
> In file mm/oom_kill.c, uncomment line 24: /* #define DEBUG */.
> And next time when oom happens again, we'll see the badness.
oh, good hint. will do this before the next reboot (in a few hours i guess)
thanks,
Christian.
-
Mauricio Lin wrote:
> Hi Christian,
>
> I would like to know what are the kernel versions this problem happened.
>
> Did this problem start from 2.6.11-rc2-bk10?
i noticed it first at 2.6.11, then again with 2.6.11-rc5-bk2. suspecting
pppd to be the culprit to chew up all RAM after being termina
In file mm/oom_kill.c, uncomment line 24: /* #define DEBUG */.
And next time when oom happens again, we'll see the badness.
--coywolf
On Tue, 08 Mar 2005 16:21:21 +0100, Christian Kujau <[EMAIL PROTECTED]> wrote:
> hallo list,
>
> today my machine went out out memory and noticing it several hou
Hi Christian,
I would like to know what are the kernel versions this problem happened.
Did this problem start from 2.6.11-rc2-bk10?
BR,
Mauricio Lin.
On Thu, 10 Mar 2005 16:12:27 +0100, Christian Kujau <[EMAIL PROTECTED]> wrote:
> ok,
>
> as "promised", it the OOM happened again with the same
On Fri, Mar 11, 2005 at 02:14:14AM +0100, Christian Kujau wrote:
> Andrew Morton wrote:
> > Christian Kujau <[EMAIL PROTECTED]> wrote:
> >
> >>i was going to compile 2.6.11-rc5-bk4, to sort out the "bad" kernel.
> >>compiling went fine. ok, finished some email, ok, suddenly my swap was
> >>used up
Andrew Morton wrote:
> Christian Kujau <[EMAIL PROTECTED]> wrote:
>
>>i was going to compile 2.6.11-rc5-bk4, to sort out the "bad" kernel.
>>compiling went fine. ok, finished some email, ok, suddenly my swap was
>>used up again, and no memory left - uh oh! OOM again, with 2.6.11-rc5-bk2!
>
>
> W
Christian Kujau <[EMAIL PROTECTED]> wrote:
>
> i was going to compile 2.6.11-rc5-bk4, to sort out the "bad" kernel.
> compiling went fine. ok, finished some email, ok, suddenly my swap was
> used up again, and no memory left - uh oh! OOM again, with 2.6.11-rc5-bk2!
Well if you ran out of swap then
ok,
as "promised", it the OOM happened again with the same plain 2.6.11,
details here.
http://nerdbynature.de/bits/sheep/2.6.11/oom/oom_2.6.11_2.txt
the following is a quite long, but please read on
(if anyone is reading at all :))
this time it happened at 08:01, and i could image some heavy cr
Mauricio Lin wrote:
> Hi Christian,
>
> I found the 2.6.11-rc3 patch. The oom killer modification from
> Arcangeli was included in 2.6.11-rc3. Right? So this is correct, so
> the problem is not related to Arcangeli modification.
>
> Does anyone have idea?
hi Mauricio,
thank you for your answers
Hi Christian,
I found the 2.6.11-rc3 patch. The oom killer modification from
Arcangeli was included in 2.6.11-rc3. Right? So this is correct, so
the problem is not related to Arcangeli modification.
Does anyone have idea?
BR,
Mauricio Lin.
On Wed, 9 Mar 2005 09:18:31 -0400, Mauricio Lin <[EMAI
...replying to myself: it happened again!
switched back to 2.6.11-rc5-bk2, details will follow.
thanks,
Christian.
--
BOFH excuse #311:
transient bus protocol violation
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More m
Hi Christian,
Could you check the mm/oom_kill.c for your kernel 2.6.11-rc3?
During the 2.6.11-rc development, the oom killer was changed by Andrea
Arcangeli. I do not remember exactly which was the version that this
modification was included, perhaps in kernel 2.6.11-rc4.
Now this oom killer mod
hallo list,
today my machine went out out memory and noticing it several hours after
the first OOM message in the log, i wonder
1) why this happened at all and
2) why almost every service was killed despite the clever algorithms
documented in mm/oom_kill.c.
the first oom message went
22 matches
Mail list logo
