Re: Tester with IP27/IP30 needed

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 ]


-- 
To UNSUBSCRIBE, email to debian-mips-REQUESTlists.debian.org
with a subject of "unsubscribe". Trouble? Contact
listmasterlists.debian.org

On Sat, Jan 19, 2008 at 08:12:41PM +0100, Thomas
Bogendoerfer wrote:
> 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.

My IP30 isn't killed by it. The program just waits forever
but I can
easily terminate it with Ctrl+C.
 
> 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.

I have access to Irix (but need to replace the monitor) but
no lookup :-(

Jens


-- 
To UNSUBSCRIBE, email to debian-mips-REQUESTlists.debian.org
with a subject of "unsubscribe". Trouble? Contact
listmasterlists.debian.org