linux-mips
[Top] [All Lists]

Re: R5000 oops

To: Jason Mesker <jasonm@tool.net>
Subject: Re: R5000 oops
From: Geert Uytterhoeven <geert@linux-m68k.org>
Date: Mon, 10 Jul 2000 13:46:17 +0200 (CEST)
Cc: Ralf Baechle <ralf@uni-koblenz.de>, "debian-mips@lists.debian.org" <debian-mips@lists.debian.org>, "linux-mips@fnet.fr" <linux-mips@fnet.fr>, "linux-mips@oss.sgi.com" <linux-mips@oss.sgi.com>, "linux-mips@vger.rutgers.edu" <linux-mips@vger.rutgers.edu>
In-reply-to: <396978F7.A309E715@tool.net>
Sender: owner-linux-mips@oss.sgi.com
On Mon, 10 Jul 2000, Jason Mesker wrote:
> I am running kernel version: 2.4.0 test 3 pre 2.  I am useing wesolows 
> vmlinux-0704b kernel.
> 
> I think I have found the problem though.  I was running the system without 
> swap and with 64Megs of RAM.  I added around 20 megs of swap space and did the
> configure again and it worked fine.  I am actually compiling now and will let 
> the status be known if it completes or not.  As of right now everything looks
> like it is working fine with the swap enabled.

I suspect that's not the problem, though. 64 MB of RAM should not be exhausted
that fast.

I saw lots of similar oopses on the NEC DDB Vrc-5074 with various 2.3.x
kernels. Other people reported similar oopses with other machines. And the
common factor is the R5000.

Gr{oetje,eeting}s,

                                                Geert

--
Geert Uytterhoeven -- Linux/{m68k~Amiga,PPC~CHRP} -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                                            -- Linus Torvalds


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