From: tsbogend@alpha.franken.de (Thomas Bogendoerfer)
To: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
Cc: ralf@linux-mips.org, linux-mips@linux-mips.org, sam@catalyst.net.nz
Subject: Re: Kernel issues on R4000/R4000 SC and MC
Date: Thu, 1 Feb 2007 11:36:18 +0100 [thread overview]
Message-ID: <20070201103618.GA25843@alpha.franken.de> (raw)
In-Reply-To: <20070201.190717.55145997.nemoto@toshiba-tops.co.jp>
On Thu, Feb 01, 2007 at 07:07:17PM +0900, Atsushi Nemoto wrote:
> On Wed, 31 Jan 2007 13:09:26 +0000, Ralf Baechle <ralf@linux-mips.org> wrote:
> > Anyway, the issue boiled up again last week and was supposedly fixed for
> > linux-2.6.17-rc7 which I've just merged. I'd like to ask somebody with
> > one of the affected CPUs to test this. Below Nick Piggin's test program.
>
> What is the expected output of the test program?
I can confirm, that it kills R4400SC/MC machines. I saw some
"detected softlock" messages. With just one zero page (CPU without VCE)
everything is fine
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessary a
good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2007-02-01 10:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-31 13:09 Kernel issues on R4000/R4000 SC and MC Ralf Baechle
2007-02-01 10:07 ` Atsushi Nemoto
2007-02-01 10:36 ` Thomas Bogendoerfer [this message]
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=20070201103618.GA25843@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=anemo@mba.ocn.ne.jp \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.org \
--cc=sam@catalyst.net.nz \
/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