Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: tsbogend@alpha.franken.de (Thomas Bogendoerfer)
To: Florian Lohoff <flo@rfc822.org>
Cc: linux-mips@linux-mips.org, debian-mips@lists.debian.org
Subject: Re: Tester with IP27/IP30 needed
Date: Thu, 17 Jan 2008 01:40:54 +0100	[thread overview]
Message-ID: <20080117004054.GA12051@alpha.franken.de> (raw)
In-Reply-To: <20080115112719.GB7920@paradigm.rfc822.org>

On Tue, Jan 15, 2008 at 12:27:19PM +0100, Florian Lohoff wrote:
> Simple testcase for me is:

now even simpler:

----------------------------------------------------------------------
void spin(void *a0)
{
	while (1) {
		asm volatile(
		"    .set mips3       \n"
		"    sync             \n"
		"1:  ll $5, 0($4)     \n"
		"    sc $3, 0($4)     \n"
		"    beqz $3, 1b      \n"
		"    .word 0x7c03e83b \n" /* rdhwr */
		"    lw $3, 0($4)     \n"
		"    nop              \n"
		);
	}
}

int main()
{
	int a;

	spin(&a);
}
----------------------------------------------------------------------

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...

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessary a
good idea.                                                [ RFC1925, 2.3 ]

  reply	other threads:[~2008-01-17  0:41 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 [this message]
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
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=20080117004054.GA12051@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=debian-mips@lists.debian.org \
    --cc=flo@rfc822.org \
    --cc=linux-mips@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox