From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Bryce Harrington <bryce@osdl.org>
Cc: 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: Sun, 23 Jan 2005 19:27:46 -0800 [thread overview]
Message-ID: <41F46B32.9070904@osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.33.0501221125140.30167-100000@osdlab.pdx.osdl.net>
Bryce Harrington wrote:
> On Fri, 21 Jan 2005, Chris Wright wrote:
>
>>* Bryce Harrington (bryce@osdl.org) wrote:
>>
>>>Well, I'm not having much luck. strace isn't installed on the system
>>>(and is giving errors when trying to compile it). Also, the ssh session
>>>(and sshd) quits whenever I try running the following growfiles command
>>>manually, so I'm having trouble replicating the kernel panic manually.
>>
>>Sounds very much like oom killer gone nuts.
>>
>>
>>># growfiles -W gf14 -b -e 1 -u -i 0 -L 20 -w -l -C 1 -T 10 glseek19 glseek19.2
>>>
>>>Anyway, if anyone wants to investigate this further, I can provide
>>>access to the machine (email me). Otherwise, I'm probably just going to
>>>wait for -rc2 and see if the problem's still there.
>>
>>Wait no longer, it's here ;-)
>
>
> Hmm, still the kernel is going nutso. LTP and everything else on the
> system is getting killed, including the test manager process.
>
> Below's a bit more info scraped from the console. This is from a run on
> RH 9.0. It looks like LTP got through 722 of its 2270 tests before the
> kernel goes postal on it. This time it got through all the growfile
> commands before it died (see bottom of this post), however it looks like
> the same growfile cmd I reported earlier is the one causing the problem.
>
> When I run:
>
> mkfifo gffifo18;
> strace growfiles -b -W gf13 -e 1 -u -i 0 -L 30 -I r -r 1-4096 gffifo18 &> /tmp/growfiles_strace_log.txt
>
> The following happens:
>
> * I get this strace log: http://developer.osdl.org/bryce/growfiles_strace_log.txt
> * The ssh session dies and returns to login prompt
> * A bunch of stuff similar to below is spewed to console
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.
--
~Randy
next prev parent reply other threads:[~2005-01-24 3:36 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 [this message]
2005-01-25 19:12 ` Alexander Nyberg
2005-01-25 18:28 ` Randy.Dunlap
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=41F46B32.9070904@osdl.org \
--to=rddunlap@osdl.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox