64-bit kernel
I don't know if anymore has a interest in the 64-bit kernel, but I just found this bug (see patch below).
It would be nice to know, how many are interested in the 64-bit kernel and who actually got something running.
So please rise you voice.
/Carsten
Index: include/asm-mips64/exception.h
===================================================================
RCS file:/home/repository/sw/linux-2.4.18/include/asm-mips64/exception.h,v retrieving revision 1.1.1.1
diff -u -r1.1.1.1 exception.h
--- include/asm-mips64/exception.h 4 Mar 2002 11:13:25 -0000
1.1.1.1
+++ include/asm-mips64/exception.h 18 Jun 2002 12:18:40 -0000
@@ -28,7 +28,7 @@
.macro __build_clear_fpe
cfc1 a1, fcr31
- li a2, ~(0x3f << 13)
+ li a2, ~(0x3f << 12)
and a2, a1
ctc1 a2, fcr31STI
--
_ _ ____ ___ Carsten Langgaard Mailto:[email protected] |\ /|||___)(___ MIPS Denmark Direct: +45 4486 5527 | \/ ||| ____) Lautrupvang 4B Switch: +45 4486 5555 TECHNOLOGIES 2750 Ballerup Fax...: +45 4486 5556 Denmark http://www.mips.com
Quoted 6 lines · Carsten Langgaard
I don't know if anymore has a interest in the 64-bit kernel, but I just found this bug (see patch below).
It would be nice to know, how many are interested in the 64-bit kernel and who actually got something running.
So please rise you voice.
Been running 64-bit stuff here, but nothing even remotely fpu intensive. It's quite possible we'd never run into this case.
-Justin
Quoted 9 lines · Justin Carlson
Quoted 5 lines · Carsten Langgaard
I don't know if anymore has a interest in the 64-bit kernel, but I just found this bug (see patch below).
It would be nice to know, how many are interested in the 64-bit kernel and who actually got something running.
So please rise you voice.Been running 64-bit stuff here, but nothing even remotely fpu intensive. It's quite possible we'd never run into this case.
At this time probably most 64-bit kernels are running on a certain 64-bit CPU with it's hardware fp disabled so nobody ever saw this one.
Ralf
I'm trying to compile glibc natively using my 64-bit kernel, but it fails with the following message:
Out of Memory: Killed process 641 (qmgr).
Out of Memory: Killed process 642 (tlsmgr). Out of Memory: Killed process 378 (portmap). Out of Memory: Killed process 9363 (cc1).
Out of Memory: Killed process 9363 (cc1).
So there may be a memory leak problem in 64-bit kernel. Has anyone seen this ?
/Carsten
Quoted 9 lines · Ralf Baechle
Quoted 7 lines · Justin Carlson
Quoted 5 lines · Carsten Langgaard
I don't know if anymore has a interest in the 64-bit kernel, but I just found this bug (see patch below).
It would be nice to know, how many are interested in the 64-bit kernel and who actually got something running.
So please rise you voice.
Quoted 7 lines
Quoted 2 lines
Been running 64-bit stuff here, but nothing even remotely fpu intensive. It's quite possible we'd never run into this case.
At this time probably most 64-bit kernels are running on a certain 64-bit CPU with it's hardware fp disabled so nobody ever saw this one.
Ralf
--
_ _ ____ ___ Carsten Langgaard Mailto:[email protected] |\ /|||___)(___ MIPS Denmark Direct: +45 4486 5527 | \/ ||| ____) Lautrupvang 4B Switch: +45 4486 5555 TECHNOLOGIES 2750 Ballerup Fax...: +45 4486 5556 Denmark http://www.mips.com
Quoted 11 lines · Carsten Langgaard
I'm trying to compile glibc natively using my 64-bit kernel, but it fails with the following message:
Out of Memory: Killed process 641 (qmgr).
Out of Memory: Killed process 642 (tlsmgr). Out of Memory: Killed process 378 (portmap). Out of Memory: Killed process 9363 (cc1).
Out of Memory: Killed process 9363 (cc1).So there may be a memory leak problem in 64-bit kernel. Has anyone seen this ?
No. The entire Redhat 7.0 stuff I built was done exclusivly on a 64-bit kernel (with 2GB RAM however ...) and no such problem ever, even after long uptimes.
Ralf
Quoted 6 lines · Carsten Langgaard
I don't know if anymore has a interest in the 64-bit kernel, but I just found this bug (see patch below).
It would be nice to know, how many are interested in the 64-bit kernel and who actually got something running.
So please rise you voice.
Actually I think there is an increased interestes to 64bit kernel with the recent introduction of RM7K and bcm1250 CPUs.
If 64bit kernel gets mature, I think two years down the road we will see mid-range CPUs edging into that domain as well.
(Jun is raising his voice....)
Jun
Quoted 33 lines
/Carsten
Index:
include/asm-mips64/exception.h
===================================================================
RCS file:/home/repository/sw/linux-2.4.18/include/asm-mips64/exception.h,vretrieving revision 1.1.1.1
diff -u -r1.1.1.1exception.h
---include/asm-mips64/exception.h4 Mar 2002 11:13:25 -0000
1.1.1.1
+++include/asm-mips64/exception.h18 Jun 2002 12:18:40 -0000(quoted diff) +1
-2@@ -28,7 +28,7 @@ .macro __build_clear_fpe cfc1 a1, fcr31 - li a2, ~(0x3f << 13) + li a2, ~(0x3f << 12) and a2, a1 ctc1 a2, fcr31 STI --_ _ ____ ___ Carsten Langgaard Mailto:[email protected] |\ /|||___)(___ MIPS Denmark Direct: +45 4486 5527 | \/ ||| ____) Lautrupvang 4B Switch: +45 4486 5555 TECHNOLOGIES 2750 Ballerup Fax...: +45 4486 5556 Denmark http://www.mips.com
Quoted 5 lines · Carsten Langgaard
I don't know if anymore has a interest in the 64-bit kernel, but I just found this bug (see patch below).
It would be nice to know, how many are interested in the 64-bit kernel and who actually got something running.
So please rise you voice.
More and more systems run into the limits of system memory so once it's practically unavoidable. Take the existence of highmem as a proof for it.
Ralf
Quoted 7 lines · Carsten Langgaard
X-Mailer: Mozilla 4.77 [en] (X11; U; SunOS 5.8 sun4u)
I don't know if anymore has a interest in the 64-bit kernel, but I just found this bug (see patch below).
It would be nice to know, how many are interested in the 64-bit kernel and who actually got something running.
So please rise you voice.
The patch is ok but please do not send inline patches with Mozilla - it does bad things like converting tabs to spaces and wordwrapping to patches.
Ralf