From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Alexander Nyberg <alexn@dsv.su.se>
Cc: Bryce Harrington <bryce@osdl.org>, Chris Wright <chrisw@osdl.org>,
dev@osdl.org, linux-kernel@vger.kernel.org,
stp-devel@lists.sourceforge.net
Subject: Re: Kernel 2.6.11-rc1/2 goes Postal on LTP
Date: Tue, 25 Jan 2005 10:28:00 -0800 [thread overview]
Message-ID: <41F68FB0.7080808@osdl.org> (raw)
In-Reply-To: <1106680321.705.52.camel@boxen>
Alexander Nyberg wrote:
>>Similar for me, easy to reproduce (3 times today).
>>Here's a kernel messages log, with 32 processes killed,
>>mostly hotplug, but also bash (2x), runltp, & some daemons.
>>
>>I could not login and do anything else, but I could/did
>>SysRq-T, P, M, S, U, B to reboot. These are also in the log.
>>
>>log:
>>http://developer.osdl.org/rddunlap/oom/oom_kill.txt
>>
>>config:
>>http://developer.osdl.org/rddunlap/oom/config-2611rc2
>>
>>on P4-UP, 1 GB RAM.
>>
>
>
> I saw this aswell. Appears to be the pipe leak cause it doesn't go nuts
> with the patch at the bottom from Linus.
I expected that as well, but I haven't rerun it to confirm.
I'm going on the the nptl test next....
Thanks,
--
~Randy
next prev parent reply other threads:[~2005-01-25 19:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.58.0410011536060.2403@ppc970.osdl.org>
2005-01-19 0:19 ` LTP Results for 2.6.x and 2.4.x Bryce Harrington
2005-01-21 19:27 ` Kernel Panic with LTP on 2.6.11-rc1 (was Re: LTP Results for 2.6.x and 2.4.x) Bryce Harrington
2005-01-21 23:35 ` Andrew Morton
2005-01-21 23:33 ` [Dev] " Chris Wright
2005-01-22 1:08 ` Bryce Harrington
2005-01-22 3:11 ` [LTP] " Bryce Harrington
2005-01-22 5:05 ` Chris Wright
2005-01-22 20:14 ` Kernel 2.6.11-rc1/2 goes Postal on LTP Bryce Harrington
2005-01-23 22:20 ` Randy.Dunlap
2005-01-24 3:27 ` Randy.Dunlap
2005-01-25 19:12 ` Alexander Nyberg
2005-01-25 18:28 ` Randy.Dunlap [this message]
2005-01-21 23:41 ` Kernel Panic with LTP on 2.6.11-rc1 (was Re: LTP Results for 2.6.x and 2.4.x) William Lee Irwin III
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=41F68FB0.7080808@osdl.org \
--to=rddunlap@osdl.org \
--cc=alexn@dsv.su.se \
--cc=bryce@osdl.org \
--cc=chrisw@osdl.org \
--cc=dev@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stp-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.