linux-mips-fnet
[Top] [All Lists]

Re: 2.1.131 strikes back!

To: linux-mips@fnet.fr
Subject: Re: 2.1.131 strikes back!
From: "Houten K.H.C. van (Karel)" <K.H.C.vanHouten@research.kpn.com>
Date: Tue, 19 Jan 1999 19:03:41 +0100
Cc: K.H.C.vanHouten@research.kpn.com
In-reply-to: "Your message of Mon, 18 Jan 1999 22:33:59 +0100." <XFMail.990118223359.Harald.Koerfgen@home.ivm.de>
Reply-to: K.H.C.vanHouten@research.kpn.com
Hi Harald,

Harald Koerfgen wrote:
> Hi all,
> 
> it looks like I found the annoying bug which made 2.1.131 unstable:
> 
> [root@192 /proc]# uname -a
> Linux 192.168.0.3 2.1.131 #2 Mon Jan 18 18:58:22 MET 1999 mips unknown
> [root@192 /proc]# uptime
>  10:15pm  up 40 min,  5 users,  load average: 17.58, 18.15, 17.53
> 
> This is on my DECstation 5000/260 running two "make -j 10 netboot" in
> parallel on two kernel source trees. I booted in single user mode, started
> inetd manually and opened four telnet sessions :-).
> 
> The bug was simple but not necessary obvious: duplicate labels in
> r2300_misc.S and r4k_misc.S which, although not declared as such, were
> global.
> 
> Quick'n'dirty fix: rename those labels.
> 
> Please apply the attached patch to r2300_misc.S and experience the
> wonderful world of linux-2.1.131 :-).
> 
> [As a side note for the not so experienced reader:
>    cd .../linux/arch/mips/kernel
>    patch r2300_misc.S <patch-r2300_misc]

I'm sorry to report, my 260 is still unstable with 2.1.131, even after
that patch.
The first time it died at ntpdate, and was not pingable anymore.

The next time I booted single user, started inetd, and unpacked
a tar file. While starting 'top', it died again.

Back to 2.1.121....

Regards,
-- 
Karel van Houten

----------------------------------------------------------
The box said "Requires Windows 95 or better."
I can't understand why it won't work on my Linux computer. 
----------------------------------------------------------


<Prev in Thread] Current Thread [Next in Thread>