linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Andy Whitcroft <apw@shadowen.org>
To: Martin Bligh <mbligh@google.com>
Cc: Andrew Morton <akpm@osdl.org>,
	linuxppc64-dev@ozlabs.org, Badari Pulavarty <pbadari@us.ibm.com>,
	lkml <linux-kernel@vger.kernel.org>,
	ak@suse.de
Subject: Re: 2.6.17-rc2-mm1
Date: Mon, 01 May 2006 19:32:35 +0100	[thread overview]
Message-ID: <44565443.3020000@shadowen.org> (raw)
In-Reply-To: <44564BEC.1040803@google.com>

Martin Bligh wrote:
> Badari Pulavarty wrote:
> 
>> On Mon, 2006-05-01 at 10:26 -0700, Martin Bligh wrote:
>>
>>>> I ran mtest01 multiple times with various options on my 4-way AMD64
>>>> box.
>>>> So far couldn't reproduce the problem (2.6.17-rc3-mm1).
>>>>
>>>> Are there any special config or test options you are testing with ?
>>>
>>>
>>> Config is here:
>>>
>>> http://ftp.kernel.org/pub/linux/kernel/people/mbligh/config/abat/amd64
>>>
>>> It's just doing "runalltests", I think.
>>
>>
>>
>> FWIW, I tried your config file on my 4-way AMD64 (melody) box and ran
>> latest "mtest01" fine.
>>
>> I am now trying runalltests. I guess, its time to bi-sect :(
> 
> 
> There was a panic on PPC64 during LTP too, but it seems to have gone
> away with rc3-mm1. Not sure if it was really fixed, or just intermittent.
> 
> http://test.kernel.org/abat/29675/debug/console.log

I think its more intermittant than gone.  I've got another machine which
runs the same tests, and she threw a very similar failure on 2.6.18-rc3-mm1.

-apw

  reply	other threads:[~2006-05-01 18:32 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-27 16:47 2.6.17-rc2-mm1 Martin Bligh
2006-04-28  8:20 ` 2.6.17-rc2-mm1 Andrew Morton
2006-05-01 14:24   ` 2.6.17-rc2-mm1 Martin J. Bligh
2006-05-01 17:07     ` 2.6.17-rc2-mm1 Andrew Morton
2006-05-01 17:14       ` 2.6.17-rc2-mm1 Martin Bligh
2006-05-01 17:19       ` 2.6.17-rc2-mm1 Badari Pulavarty
2006-05-01 17:26         ` 2.6.17-rc2-mm1 Martin Bligh
2006-05-01 17:55           ` 2.6.17-rc2-mm1 Badari Pulavarty
2006-05-01 17:57             ` 2.6.17-rc2-mm1 Martin Bligh
2006-05-01 18:32               ` Andy Whitcroft [this message]
2006-05-01 23:29                 ` 2.6.17-rc2-mm1 Badari Pulavarty
2006-05-01 18:34     ` 2.6.17-rc2-mm1 Andi Kleen
2006-05-02 13:20       ` 2.6.17-rc2-mm1 Andy Whitcroft
  -- strict thread matches above, loose matches on Subject: below --
2006-04-27 16:50 2.6.17-rc2-mm1 Martin Bligh
2006-04-27 16:54 2.6.17-rc2-mm1 Martin Bligh

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=44565443.3020000@shadowen.org \
    --to=apw@shadowen.org \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc64-dev@ozlabs.org \
    --cc=mbligh@google.com \
    --cc=pbadari@us.ibm.com \
    /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;
as well as URLs for NNTP newsgroup(s).