From: tsbogend@alpha.franken.de (Thomas Bogendoerfer)
To: Ralf Baechle <ralf@linux-mips.org>
Cc: Florian Lohoff <flo@rfc822.org>,
linux-mips@linux-mips.org, debian-mips@lists.debian.org
Subject: Re: Tester with IP27/IP30 needed
Date: Sat, 19 Jan 2008 20:12:41 +0100 [thread overview]
Message-ID: <20080119191240.GA17902@alpha.franken.de> (raw)
In-Reply-To: <20080117151052.GA12457@linux-mips.org>
On Thu, Jan 17, 2008 at 03:10:52PM +0000, Ralf Baechle wrote:
> On Thu, Jan 17, 2008 at 09:27:41AM +0100, Florian Lohoff wrote:
>
> > > this kills my IP28 after a few seconds. If I drop rdhwr or sync the
> > > machine hasn't locked up after running for several minutes. Looks
> > > like we are hiting a strange condition.
> > >
> > > This sort of code could be found in glibc 2.7 all over the place...
> > >
> > > Thomas.
> > >
> > > PS: Using rdhwr_noopt doesn't make a difference...
> >
> > Kills my ip28 after 2 seconds ...
>
> Doesn't harm IP27. I even tried running two copies running in parallel.
IP28 only locks up if spin() spans two I-cache lines. The lockup also
happens if I use a different reserved instruction and skip it via
SIGILL handler. As I don't have a working compiler/assembler for Irix
I couldn't check, if this lockup also happens with Irix.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessary a
good idea. [ RFC1925, 2.3 ]
next prev parent reply other threads:[~2008-01-19 19:12 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-15 11:24 Tester with IP27/IP30 needed Thomas Bogendoerfer
2008-01-15 11:27 ` Florian Lohoff
2008-01-17 0:40 ` Thomas Bogendoerfer
2008-01-17 8:27 ` Florian Lohoff
2008-01-17 10:00 ` Thomas Bogendoerfer
2008-01-17 15:10 ` Ralf Baechle
2008-01-19 19:12 ` Thomas Bogendoerfer [this message]
2008-01-17 11:59 ` Ralf Baechle
2008-01-22 15:20 ` Kumba
2008-01-22 15:49 ` Ralf Baechle
2008-01-26 3:12 ` Kumba
2008-01-26 14:39 ` Thomas Bogendoerfer
2008-02-02 22:08 ` Kumba
2008-02-03 2:16 ` Ralf Baechle
2008-02-03 6:27 ` Florian Lohoff
2008-02-05 7:11 ` Kumba
2008-02-05 12:22 ` Thiemo Seufer
2008-02-06 3:25 ` Kumba
2008-02-06 8:56 ` Florian Lohoff
2008-02-06 14:22 ` Ralf Baechle
2008-02-08 17:23 ` Florian Lohoff
2008-02-08 19:05 ` Thiemo Seufer
2008-02-08 19:29 ` Ralf Baechle
2008-02-07 5:30 ` Kumba
2008-02-05 15:23 ` Ralf Baechle
2008-01-23 8:47 ` peter fuerst
2008-01-15 13:11 ` Ralf Baechle
2008-01-15 13:53 ` Ralf Baechle
2008-01-15 18:18 ` Ralf Baechle
2008-01-16 16:03 ` Ralf Baechle
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=20080119191240.GA17902@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=debian-mips@lists.debian.org \
--cc=flo@rfc822.org \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.org \
/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.