From: "Houten K.H.C. van (Karel)" <vhouten@kpn.com>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: "Houten K.H.C. van (Karel)" <vhouten@kpn.com>, linux-mips@oss.sgi.com
Subject: Re: FPU interrupt handler
Date: Mon, 26 Nov 2001 15:07:54 +0100 [thread overview]
Message-ID: <200111261407.PAA11348@sparta.research.kpn.com> (raw)
In-Reply-To: Your message of "Mon, 26 Nov 2001 14:50:13 +0100." <Pine.GSO.3.96.1011126142508.21598H-100000@delta.ds2.pg.gda.pl>
Hi Maciej,
> Hmm, for R3k gcc 2.95.3 + binutils 2.11.2 as available at my site seem to
> be rock solid.
>
> For R4k you need binutils 2.11.92, as there is a problem with dla/la
> expansion in the Ulf's patch for .mips3+. That actually can be fixed in
> 2.11.2 easily but I was going to switch to 2.11.92 anyway, as it has more
> MIPS/Linux support integrated and 2.12 is supposedly soon to be released.
> Unfortunately 2.11.92 is not as stable as 2.11.2 due to generic ELF code
> problems, but I'm trying to track changes and spot a more stable snapshot.
I'm using the RedHat 7.1 packages from oss:
binutils-2.11.92.0.10-1.mips.rpm
gcc-2.96-99.1.mips.rpm
> > Some kernels don't start-up, others hang just before forking init,
> > and all have problems with my serial console.
>
> Well, I'm very happy with a /240 running a 2.4.14 snapshot dated
> 20011123. For a /260 I need a small, but critical bugfix I'm sending to
> the list right now. I wonder how was it possible for the bug to remain
> uncovered for so long as it's absolutely lethal and often triggered (I've
> only got my /260 recently and it wasn't even running a few minutes
> continuously before the fix).
My 'main' mips box at home is a /260. I sometimes test things out on
a /240, but I don't have access to other boxes.
> I can't comment other models.
>
> > When I get a recent kernel running again, I would love to update my
> > DECStation Linux Website with newer instructions and a new root FS.
>
> I may upload binaries of my kernels to my site if they are to be useful
> -- they are fully monolithic (but with kmod support) due to historical
> reasons. Only IPv6 is modular due to its unstability -- it freezes the
> system immediately on my /240 and splashes a bunch of suspicious messages
> on my /260 (weird, but no time to debug). They only support /240 and /260
> due to CONFIG_CPU_HAS_WB unset.
Yes please. I hope to get a new disk this week, so I can build a
stable development server...
Thanks a lot,
--
Karel van Houten
----------------------------------------------------------
The box said "Requires Windows 95 or better."
I can't understand why it won't work on my Linux computer.
----------------------------------------------------------
next prev parent reply other threads:[~2001-11-26 15:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-25 8:23 FPU interrupt handler William Lee Irwin III
2001-11-26 11:57 ` Maciej W. Rozycki
2001-11-26 12:19 ` Houten K.H.C. van (Karel)
2001-11-26 13:50 ` Maciej W. Rozycki
2001-11-26 14:07 ` Houten K.H.C. van (Karel) [this message]
2001-11-26 16:20 ` Maciej W. Rozycki
2001-11-27 17:35 ` Maciej W. Rozycki
2001-11-26 13:24 ` Ralf Baechle
2001-11-26 16:10 ` Maciej W. Rozycki
2001-11-27 1:17 ` Ralf Baechle
2001-11-26 14:48 ` William Lee Irwin III
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=200111261407.PAA11348@sparta.research.kpn.com \
--to=vhouten@kpn.com \
--cc=linux-mips@oss.sgi.com \
--cc=macro@ds2.pg.gda.pl \
/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.