All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Cc: linux-mips@linux-mips.org
Subject: Re: Tester with IP27/IP30 needed
Date: Tue, 15 Jan 2008 18:18:12 +0000	[thread overview]
Message-ID: <20080115181812.GA14816@linux-mips.org> (raw)
In-Reply-To: <20080115135300.GB5189@linux-mips.org>

On Tue, Jan 15, 2008 at 01:53:00PM +0000, Ralf Baechle wrote:

> > > we are facing a strange problem with lenny/sid chroots on IP28. The
> > > machine locks up after issuing a few ls/ps commands in a chroot
> > > bash. This only happens with a lenny/sid chroot, but not with etch.
> > > The major difference is probably the updare to glibc2.7. Since
> > > IP28 isn't really a nice R10k machine, it would be good, if someone
> > > with a working IP27/IP30 could try a lenny/sid chroot and tell us,
> > > if it's working/not working.
> > 
> > Which CPU revision do you hit these problems on?
> 
> On IRC Thomas said it's rev 2.5.
> 
> R10000 upto version 2.6 has a broken store conditional so needs
> R10000_LLSC_WAR enabled.  The sympthom is that SC succeed even though
> it should have failed so for example two multiple competing CPUs can
> take a spinlock.  There is an erratum for this one.
> 
> Another bug is when a rdhwr $29 opcode is encountered in a branch delay
> slot.  This will result in the CPU stopping execution of instructions
> but an NMI can recover it.  For emulation performance reasons gcc no
> longer places rdhwr $29 in delay slots, so this one is no longer
> encountered in C code but still could be in assembler code.  This one
> isn't covered by any errata.
> 
> There seem to be more funnies but to the best I can say they were never
> officially documented in errata either.

So I tested the rootfs provided by Florian and more or less as expected
it immediately took out the 2 CPU R10000 v2.7 Origin I was testing on.
Seems like only one CPU stopped, as the machine was pinging and reacts
to NMIs.  So could well be the effect I observed ages ago when trying to
convert to glibc 2.4.

  Ralf

  reply	other threads:[~2008-01-15 18:18 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
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 [this message]
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=20080115181812.GA14816@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=linux-mips@linux-mips.org \
    --cc=tsbogend@alpha.franken.de \
    /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.