Thread (4 messages) 4 messages, 3 authors, 2000-07-11
  • (off-list ancestor, not in this archive)
  • Re: R5000 oops · Jason Mesker <hidden> · 2000-07-09
  • Re: R5000 oops · Geert Uytterhoeven <geert@linux-m68k.org> · 2000-07-10
  • Re: R5000 oops · <hidden> · 2000-07-10
  • Re: R5000 oops · Geert Uytterhoeven <geert@linux-m68k.org> · 2000-07-11

Re: R5000 oops

From: Geert Uytterhoeven <geert@linux-m68k.org>
Date: 2000-07-10 20:44:31

Possibly related (same subject, not in this thread)

  • 2000-07-09 · R5000 oops · Jason Mesker <hidden>
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
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help