All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Kevin D. Kissell" <kevink@mips.com>
To: "Harald Koerfgen" <Harald.Koerfgen@home.ivm.de>,
	"Karsten Merker" <karsten@excalibur.cologne.de>
Cc: <linux-mips@oss.sgi.com>
Subject: Re: Current CVS kernel no-go on R4k Decstation
Date: Mon, 8 Jan 2001 23:33:25 +0100	[thread overview]
Message-ID: <01b401c079c3$095c4740$0deca8c0@Ulysses> (raw)
In-Reply-To: XFMail.791030042838.Harald.Koerfgen@home.ivm.de

> > Similar effect for me (DS5000/150, Checkout @ Sat Jan 6 ~22:30 CET),
> > except that I do not get the "illigal instruction" lines. Harald has the
> > same problem on his /260. It looks like sometime in December 2000
> > something has gone broken in the R4K-support, or are we perhaps
> > triggering a compiler bug in egcs 1.1.2?
>
> I don't think so. This hang appeared in the middle of December and may or
may
> not be related to the MIPS32 patches which were commited then.
Unfortunately I
> haven't had the time to track this down.

If you're referring to the MIPS32 patches that came from the MIPS 2.2 tree,
we generally test those on an R4600 Indy and a couple R5xxx platforms as
a matter of routine.  This is not to say that there might not be some change
to the R4x00 support between 2.2 and 2.4 that interacts pathologically with
the MIPS32 code...

           Kevin K.

WARNING: multiple messages have this Message-ID (diff)
From: "Kevin D. Kissell" <kevink@mips.com>
To: Harald Koerfgen <Harald.Koerfgen@home.ivm.de>,
	Karsten Merker <karsten@excalibur.cologne.de>
Cc: linux-mips@oss.sgi.com
Subject: Re: Current CVS kernel no-go on R4k Decstation
Date: Mon, 8 Jan 2001 23:33:25 +0100	[thread overview]
Message-ID: <01b401c079c3$095c4740$0deca8c0@Ulysses> (raw)
Message-ID: <20010108223325.V-jXK6lzwRQ9Pp8j6Z7rIRtCOCvjauULtcOMvkdSO4E@z> (raw)
In-Reply-To: XFMail.791030042838.Harald.Koerfgen@home.ivm.de

> > Similar effect for me (DS5000/150, Checkout @ Sat Jan 6 ~22:30 CET),
> > except that I do not get the "illigal instruction" lines. Harald has the
> > same problem on his /260. It looks like sometime in December 2000
> > something has gone broken in the R4K-support, or are we perhaps
> > triggering a compiler bug in egcs 1.1.2?
>
> I don't think so. This hang appeared in the middle of December and may or
may
> not be related to the MIPS32 patches which were commited then.
Unfortunately I
> haven't had the time to track this down.

If you're referring to the MIPS32 patches that came from the MIPS 2.2 tree,
we generally test those on an R4600 Indy and a couple R5xxx platforms as
a matter of routine.  This is not to say that there might not be some change
to the R4x00 support between 2.2 and 2.4 that interacts pathologically with
the MIPS32 code...

           Kevin K.

  parent reply	other threads:[~2001-01-08 22:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-08 14:53 Current CVS kernel no-go on R4k Decstation Florian Lohoff
2001-01-08 18:30 ` Karsten Merker
1979-10-30  3:28   ` Harald Koerfgen
2001-01-08 21:53     ` Ralf Baechle
2001-01-08 22:33     ` Kevin D. Kissell [this message]
2001-01-08 22:33       ` Kevin D. Kissell

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='01b401c079c3$095c4740$0deca8c0@Ulysses' \
    --to=kevink@mips.com \
    --cc=Harald.Koerfgen@home.ivm.de \
    --cc=karsten@excalibur.cologne.de \
    --cc=linux-mips@oss.sgi.com \
    /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.