From: Chris Wright <chrisw@osdl.org>
To: Andrew Morton <akpm@osdl.org>
Cc: Bryce Harrington <bryce@osdl.org>,
dev@osdl.org, ltp-list@lists.sourceforge.net,
linux-kernel@vger.kernel.org, stp-devel@lists.sourceforge.net
Subject: Re: [Dev] Re: Kernel Panic with LTP on 2.6.11-rc1 (was Re: LTP Results for 2.6.x and 2.4.x)
Date: Fri, 21 Jan 2005 15:33:08 -0800 [thread overview]
Message-ID: <20050121153308.I24171@build.pdx.osdl.net> (raw)
In-Reply-To: <20050121153520.6a7c08dd.akpm@osdl.org>; from akpm@osdl.org on Fri, Jan 21, 2005 at 03:35:20PM -0800
* Andrew Morton (akpm@osdl.org) wrote:
> Bryce Harrington <bryce@osdl.org> wrote:
> I am unable to find the oops trace amongst all that stuff. Help?
>
> (It would have been handy to include it in the bug report, actually)
Yes, it would. Or at least some better granularity leading up to the
problem. I ran growfiles locally on 2.6.11-rc-bk and didn't have any
problem. Could you strace growfiles and see what it was doing when it
killed the machine?
thanks,
-chris
--
Linux Security Modules http://lsm.immunix.org http://lsm.bkbits.net
next prev parent reply other threads:[~2005-01-21 23:40 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 ` Chris Wright [this message]
2005-01-22 1:08 ` [Dev] " 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
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=20050121153308.I24171@build.pdx.osdl.net \
--to=chrisw@osdl.org \
--cc=akpm@osdl.org \
--cc=bryce@osdl.org \
--cc=dev@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ltp-list@lists.sourceforge.net \
--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
Powered by JetHome