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:
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
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
>
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 and OOM kicked
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
t around, i did that
with "ps":
http://lkml.org/lkml/2005/3/12/88
http://nerdbynature.de/bits/sheep/2.6.11/oom/daily_stats-2.6.11-rc5-bk2.log.gz
> But it would be better to have some app which prints the N most
> memory-hungry processes every second and simply scrolls that up the screen.
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"
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
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.sh
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 *lot* messages
:
http://lkml.org/lkml/2005/3/12/88
http://nerdbynature.de/bits/sheep/2.6.11/oom/daily_stats-2.6.11-rc5-bk2.log.gz
But it would be better to have some app which prints the N most
memory-hungry processes every second and simply scrolls that up the screen.
I'm not aware of such a thing
-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
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
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.11, then again
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
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
as away and no heavy
> tasks were scheduled:
>
> http://nerdbynature.de/bits/sheep/2.6.11/oom/oom_2.6.11.txt
>
> mysqld got killed by the oom killer, so i have to suspect mysql for being
> the reason for oom here, even that i know that mysqld is running all day
> long. severa
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 so
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 cron jobs
were going on. but as i said: it did not happen
:
http://nerdbynature.de/bits/sheep/2.6.11/oom/oom_2.6.11.txt
mysqld got killed by the oom killer, so i have to suspect mysql for being
the reason for oom here, even that i know that mysqld is running all day
long. several other tasks got killed, but Free swap stays at 0kB and the
oom killer kills
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 terminated
-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.
-
hed 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 yes, the oom-killer will visit you.
> >
> > Why did you run out of swapspace?
>
> h
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
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!
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
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
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 yes
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!
Well if you ran
, and no memory left - uh oh! OOM again, with 2.6.11-rc5-bk2!
Well if you ran out of swap then yes, the oom-killer will visit you.
Why did you run out of swapspace?
hm, if i only knew. i don't know how long it took the other night to go
from normal to OOM. but today, with 2.6.11-rc5-bk2 (well
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
s killed despite the clever algorithms
> > documented in mm/oom_kill.c.
> >
> > the first oom message went to the syslog at 01:27, i was away and no heavy
> > tasks were scheduled:
> >
> > http://nerdbynature.de/bits/sheep/2.6.11/oom/oom_2.6.11.txt
>
...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
, i was away and no heavy
> tasks were scheduled:
>
> http://nerdbynature.de/bits/sheep/2.6.11/oom/oom_2.6.11.txt
>
> mysqld got killed by the oom killer, so i have to suspect mysql for being
> the reason for oom here, even that i know that mysqld is running all day
> long. severa
:
http://nerdbynature.de/bits/sheep/2.6.11/oom/oom_2.6.11.txt
mysqld got killed by the oom killer, so i have to suspect mysql for being
the reason for oom here, even that i know that mysqld is running all day
long. several other tasks got killed, but Free swap stays at 0kB and the
oom killer
...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
was away and no heavy
tasks were scheduled:
http://nerdbynature.de/bits/sheep/2.6.11/oom/oom_2.6.11.txt
mysqld got killed by the oom killer, so i have to suspect mysql for being
the reason for oom here, even that i know that mysqld is running all day
long. several other tasks got killed
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, but
to the syslog at 01:27, i was away and no heavy
tasks were scheduled:
http://nerdbynature.de/bits/sheep/2.6.11/oom/oom_2.6.11.txt
mysqld got killed by the oom killer, so i have to suspect mysql for being
the reason for oom here, even that i know that mysqld is running all day
long. several other
to the syslog at 01:27, i was away and no heavy
tasks were scheduled:
http://nerdbynature.de/bits/sheep/2.6.11/oom/oom_2.6.11.txt
mysqld got killed by the oom killer, so i have to suspect mysql for being
the reason for oom here, even that i know that mysqld is running all day
long. several other
43 matches
Mail list logo
