Swap strangeness using 2.4.5pre2aa1
My Alpha/LInux UP2000 SMP with 1GB memory is running kernel 2.4.5pre2aa1.
I have been observing some strangeness with Swap usage quite recently (in fact since 2.4.4). Unfortunately, the kernel was made using gcc-2.95.2-136.alpha.rpm provided by SuSE-7.0.
The following is the output from "free"
=========================================================================
total used free shared buffers
cached
Mem: 1023128 1015640 7488 0 544
948976
-/+ buffers/cache: 66120 957008
Swap: 1021936 1021936 0
==========================================================================
And the following is the output from "top"
===========================================================================
3:09am up 3 days, 5:49, 7 users, load average: 1.60, 2.02, 3.05
82 processes: 79 sleeping, 3 running, 0 zombie, 0 stopped
CPU states: 0.1% user, 4.0% system, 80.3% nice, 15.4% idle Mem: 1023128K av, 1016128K used, 7000K free, 0K shrd, 736K
buff
Swap: 1021936K av, 1021936K used, 0K free 948968K
cached
PID USER PRI NI SIZE RSS SHARE STAT LIB %CPU %MEM TIME
COMMAND
9555 sekim 20 10 437M 345M 345M R N 108M 90.4 17.2 1881m
full.ax
9547 sekim 18 10 95624 24M 792 R N 13M 75.8 1.2 1424m
optcon.ax
21133 hugh 16 0 1976 1976 1648 R 1872 1.0 0.0 0:02 top
5 root 12 0 0 0 0 SW 0 0.4 0.0 151:52
kswapd
1 root 12 0 128 104 104 S 16 0.0 0.0 0:44 init
2 root 12 0 0 0 0 SW 0 0.0 0.0 0:00
keventd
3 root 20 19 0 0 0 SWN 0 0.0 0.0 0:01
ksoftirqd_CP
4 root 20 19 0 0 0 SWN 0 0.0 0.0 0:00
ksoftirqd_CP
6 root 12 0 0 0 0 SW 0 0.0 0.0 0:00
kreclaimd
7 root 12 0 0 0 0 SW 0 0.0 0.0 0:00
bdflush
8 root 12 0 0 0 0 SW 0 0.0 0.0 1:03kupdated
159 bin 12 0 216 136 136 S 128 0.0 0.0 2:31
portmap
183 root 12 0 272 168 168 S 120 0.0 0.0 4:25
syslogd
187 root 12 0 960 8 8 S 0 0.0 0.0 0:06 klogd 227 root 12 0 136 8 8 S 0 0.0 0.0 0:00
rpc.rquotad
......
=============================================================================
At this point, the mouse movement crawls down at an unacceptable level. I
cannot understand that the above showing of 0 free space of swap space although the sum of all memeory usages is far less than 1GB.
I understand that free swap space may become close to 0 and stay there for
a while once it ever reached down close to zero. However, it should back
up some nonzero number if the situation is cleared.
Please tell me whether something is wrong or not with the kernel. If so,
I think I should back down to Kernel 2.2.20pre2aa1.
Thank you very much.
Signature · 8 lines
G. Hugh Song Assoc. Professor Office: +82-62-970-2210 fax: -3156 handphone: +82-16-608-2210 Email: [email protected] Department of Information and Communications Kwangju Institute of Science and Technology 1 Oryong-dong, Buk-gu, Gwangju, 500-712 South KOREA
Quoted 9 lines · G. Hugh Song
The following is the output from "free"
=========================================================================
total used free shared buffers
cached
Mem: 1023128 1015640 7488 0 544
948976
-/+ buffers/cache: 66120 957008
Swap: 1021936 1021936 0
==========================================================================
I get the same with egcs. To me it sounds broken VM (I shouldn't have changed anything that can confuse the VM so this should be reproducible with 2.4.5pre5 vanilla and infact you also said you reproduced previously in 2.4.4).
Is it possible you booted with 'mem=something'? It seems to me that when I boot with 'mem=something' the VM bad beahaviour become more visible.
Quoted 1 line
I think I should back down to Kernel 2.2.20pre2aa1.
definitely a good idea until somebody fixes the VM in mainline.
Andrea
Quoted 6 lines · G. Hugh Song
My Alpha/LInux UP2000 SMP with 1GB memory is running kernel
The following is the output from "free"
=========================================================================total used free shared buffers cached Mem: 1023128 1015640 7488 0 544 948976
Quoted 8 lines
-/+ buffers/cache: 66120 957008
Swap: 1021936 1021936 0
==========================================================================I understand that free swap space may become close to 0 and stay there for a while once it ever reached down close to zero. However, it should back up some nonzero number if the situation is cleared.
Something is wrong with the 2.4 VM. As of yet, it cannot reclaim swap space once it is full. This is pretty much the next thing on my TODO list, right after the worst highmem lockups and balancing issues have been fixed.
Watch http://www.surriel.com/patches/ closely, swap reclaiming is next on my TODO list ;)
regards,
Rik
--
Linux MM bugzilla: http://linux-mm.org/bugzilla.shtml
Virtual memory is like a game you can't win; However, without VM there's truly nothing to lose...
http://www.surriel.com/
2.4.5 does not link on Ruffian (alpha)
In reply to G. Hugh SongHi,
I just tried to compile 2.4.5 on a Ruffian. With CPU selection "generic" it fails when linking the kernel (see below). With CPU=Ruffian, it compiles and links fine. Haven't tried booting yet, 'cause the machine is some 20 miles away from here.
What more can I provide/do to help?
Cheers,
Ingo
-------------
ld -r -o kernel.o entry.o traps.o process.o osf_sys.o irq.o irq_alpha.o signal.
o setup.o ptrace.o time.o semaphore.o alpha_ksyms.o irq_i8259.o irq_srm.o es1888
.o smc37c669.o smc37c93x.o ns87312.o pci.o pci_iommu.o core_apecs.o core_cia.o c
ore_irongate.o core_lca.o core_mcpcia.o core_polaris.o core_t2.o core_tsunami.o
core_titan.o sys_alcor.o sys_cabriolet.o sys_dp264.o sys_eb64p.o sys_eiger.o sys
_jensen.o sys_miata.o sys_mikasa.o sys_nautilus.o sys_titan.o sys_noritake.o sys
_rawhide.o sys_ruffian.o sys_rx164.o sys_sable.o sys_sio.o sys_sx164.o sys_takar
a.o sys_wildfire.o core_wildfire.o irq_pyxis.o
sys_dp264.o: In function `tsunami_inb':sys_dp264.c(.text+0x440): multiple definition of tsunami_inb' core_tsunami.o(.text+0x500):core_tsunami.c: first defined here sys_dp264.o: In function clipper_map_irq':sys_dp264.c(.text+0x480): multiple definition of tsunami_inw' core_tsunami.o(.text+0x540):core_tsunami.c: first defined here sys_dp264.o: In function tsunami_inl':sys_dp264.c(.text+0x4c0): multiple definition of tsunami_inl' core_tsunami.o(.text+0x580):core_tsunami.c: first defined here sys_dp264.o: In function tsunami_outb':sys_dp264.c(.text+0x460): multiple definition of tsunami_outb' core_tsunami.o(.text+0x520):core_tsunami.c: first defined here sys_dp264.o: In function tsunami_outw':sys_dp264.c(.text+0x4a0): multiple definition of tsunami_outw' core_tsunami.o(.text+0x560):core_tsunami.c: first defined here sys_dp264.o: In function dp264_init_pci':sys_dp264.c(.text+0x4e0): multiple definition of tsunami_outl' core_tsunami.o(.text+0x5a0):core_tsunami.c: first defined here sys_dp264.o: In function tsunami_readb':sys_dp264.c(.text+0x540): multiple definition of tsunami_readb' core_tsunami.o(.text+0x600):core_tsunami.c: first defined here sys_dp264.o: In function tsunami_readw':sys_dp264.c(.text+0x560): multiple definition of tsunami_readw' core_tsunami.o(.text+0x620):core_tsunami.c: first defined here sys_dp264.o: In function webbrick_init_arch':sys_dp264.c(.text+0x580): multiple definition of tsunami_readl' core_tsunami.o(.text+0x640):core_tsunami.c: first defined here sys_dp264.o: In function tsunami_readq':sys_dp264.c(.text+0x5a0): multiple definition of tsunami_readq' core_tsunami.o(.text+0x660):core_tsunami.c: first defined here sys_dp264.o: In function tsunami_writeb':sys_dp264.c(.text+0x5c0): multiple definition of tsunami_writeb' core_tsunami.o(.text+0x680):core_tsunami.c: first defined here sys_dp264.o: In function tsunami_writew':sys_dp264.c(.text+0x5e0): multiple definition of tsunami_writew' core_tsunami.o(.text+0x6a0):core_tsunami.c: first defined here sys_dp264.o: In function tsunami_writel':sys_dp264.c(.text+0x600): multiple definition of tsunami_writel' core_tsunami.o(.text+0x6c0):core_tsunami.c: first defined here sys_dp264.o: In function tsunami_writeq':sys_dp264.c(.text+0x620): multiple definition of tsunami_writeq' core_tsunami.o(.text+0x6e0):core_tsunami.c: first defined here sys_dp264.o: In function tsunami_ioremap':sys_dp264.c(.text+0x500): multiple definition of tsunami_ioremap' core_tsunami.o(.text+0x5c0):core_tsunami.c: first defined here sys_dp264.o: In function monet_init_pci':sys_dp264.c(.text+0x520): multiple definition of `tsunami_is_ioaddr' core_tsunami.o(.text+0x5e0):core_tsunami.c: first defined here make[1]: *** [kernel.o] Error 1
make[1]: Leaving directory `/usr/src/linux-2.4.5/arch/alpha/kernel'
make: *** [_dir_arch/alpha/kernel] Error 2
Re: 2.4.5 does not link on Ruffian (alpha)
In reply to G. Hugh SongQuoted 43 lines · Ingo T. Storm
sys_dp264.o: In function `tsunami_inb':
sys_dp264.c(.text+0x440): multiple definition oftsunami_inb' core_tsunami.o(.text+0x500):core_tsunami.c: first defined here sys_dp264.o: In functionclipper_map_irq':sys_dp264.c(.text+0x480): multiple definition oftsunami_inw' core_tsunami.o(.text+0x540):core_tsunami.c: first defined here sys_dp264.o: In functiontsunami_inl':sys_dp264.c(.text+0x4c0): multiple definition oftsunami_inl' core_tsunami.o(.text+0x580):core_tsunami.c: first defined here sys_dp264.o: In functiontsunami_outb':sys_dp264.c(.text+0x460): multiple definition oftsunami_outb' core_tsunami.o(.text+0x520):core_tsunami.c: first defined here sys_dp264.o: In functiontsunami_outw':sys_dp264.c(.text+0x4a0): multiple definition oftsunami_outw' core_tsunami.o(.text+0x560):core_tsunami.c: first defined here sys_dp264.o: In functiondp264_init_pci':sys_dp264.c(.text+0x4e0): multiple definition oftsunami_outl' core_tsunami.o(.text+0x5a0):core_tsunami.c: first defined here sys_dp264.o: In functiontsunami_readb':sys_dp264.c(.text+0x540): multiple definition oftsunami_readb' core_tsunami.o(.text+0x600):core_tsunami.c: first defined here sys_dp264.o: In functiontsunami_readw':sys_dp264.c(.text+0x560): multiple definition oftsunami_readw' core_tsunami.o(.text+0x620):core_tsunami.c: first defined here sys_dp264.o: In functionwebbrick_init_arch':sys_dp264.c(.text+0x580): multiple definition oftsunami_readl' core_tsunami.o(.text+0x640):core_tsunami.c: first defined here sys_dp264.o: In functiontsunami_readq':sys_dp264.c(.text+0x5a0): multiple definition oftsunami_readq' core_tsunami.o(.text+0x660):core_tsunami.c: first defined here sys_dp264.o: In functiontsunami_writeb':sys_dp264.c(.text+0x5c0): multiple definition oftsunami_writeb' core_tsunami.o(.text+0x680):core_tsunami.c: first defined here sys_dp264.o: In functiontsunami_writew':sys_dp264.c(.text+0x5e0): multiple definition oftsunami_writew' core_tsunami.o(.text+0x6a0):core_tsunami.c: first defined here sys_dp264.o: In functiontsunami_writel':sys_dp264.c(.text+0x600): multiple definition oftsunami_writel' core_tsunami.o(.text+0x6c0):core_tsunami.c: first defined here sys_dp264.o: In functiontsunami_writeq':sys_dp264.c(.text+0x620): multiple definition oftsunami_writeq' core_tsunami.o(.text+0x6e0):core_tsunami.c: first defined here sys_dp264.o: In functiontsunami_ioremap':
Quoted 8 lines
sys_dp264.c(.text+0x500): multiple definition oftsunami_ioremap' core_tsunami.o(.text+0x5c0):core_tsunami.c: first defined here sys_dp264.o: In functionmonet_init_pci':sys_dp264.c(.text+0x520): multiple definition of `tsunami_is_ioaddr' core_tsunami.o(.text+0x5e0):core_tsunami.c: first defined here make[1]: *** [kernel.o] Error 1
make[1]: Leaving directory `/usr/src/linux-2.4.5/arch/alpha/kernel'
make: *** [_dir_arch/alpha/kernel] Error 2
I got exactly the above when compiling for dp264 so I sent to Linus a patch to fix those compile problems, now I suspect my fix broke the generic compile :(, I will check that.
Andrea
Re: [PATCH] Re: 2.4.5 does not link on Ruffian (alpha)
In reply to G. Hugh SongIt should note, though, that -not- using CONFIG_ALPHA_GENERIC seems to have a detrimental effect on my machines, in 2.4.5 vanilla.
When built with CONFIG_ALPHA_NAUTILUS, my UP1000's IDE totally fails. It probes the drives ok, on boot, but a logic hang occurs where no more boot progress can be made. All I get are "hda: lost interrupt" messages. I am booting w/ aboot 0.7a from SRM, -without- the srm-as-bootloader kernel config option. These problems go away when using the generic MDK alpha kernel, which is based on Alan's '2.4.4-ac' patchkit, and uses CONFIG_ALPHA_GENERIC.
A very similar problem occurs on my new test alpha, a miata. With CONFIG_ALPHA_MIATA, IDE fails with "hda: lost interrupt" as above, but additionally, the keyboard is no longer recognized. Again, with MDK(ac) kernel, things work fine.
After wondering for a while what magic was in the 'ac' patchkit, I realized that my build needed CONFIG_ALPHA_GENERIC to work. Tested that theory... sure enough, I can boot 2.4.5-vanilla no problems now.
Signature · 3 lines
Jeff Garzik | Disbelief, that's why you fail. Building 1024 | MandrakeSoft |
[PATCH] Re: 2.4.5 does not link on Ruffian (alpha)
In reply to G. Hugh SongQuoted 15 lines · Ingo T. Storm
I just tried to compile 2.4.5 on a Ruffian. With CPU selection "generic" it fails when linking the kernel (see below). With CPU=Ruffian, it compiles and links fine. Haven't tried booting yet, 'cause the machine is some 20 miles away from here.
ld -r -o kernel.o entry.o traps.o process.o osf_sys.o irq.o irq_alpha.o signal.
o setup.o ptrace.o time.o semaphore.o alpha_ksyms.o irq_i8259.o irq_srm.o es1888
.o smc37c669.o smc37c93x.o ns87312.o pci.o pci_iommu.o core_apecs.o core_cia.o c
ore_irongate.o core_lca.o core_mcpcia.o core_polaris.o core_t2.o core_tsunami.o
core_titan.o sys_alcor.o sys_cabriolet.o sys_dp264.o sys_eb64p.o sys_eiger.o sys
Quoted 8 lines
_jensen.o sys_miata.o sys_mikasa.o sys_nautilus.o sys_titan.o sys_noritake.o sys
_rawhide.o sys_ruffian.o sys_rx164.o sys_sable.o sys_sio.o sys_sx164.osys_takar
a.o sys_wildfire.o core_wildfire.o irq_pyxis.o
sys_dp264.o: In function `tsunami_inb':sys_dp264.c(.text+0x440): multiple definition of `tsunami_inb' core_tsunami.o(.text+0x500):core_tsunami.c: first defined here
I used the attached patch to fix the problem.
(note the tty.h changes are unrelated... they are preparing for when sched.h no longer includes tty.h, fixing a nasty include loop)
Signature · 3 lines
Jeff Garzik | Disbelief, that's why you fail. Building 1024 | MandrakeSoft |
Index: arch/alpha/kernel/process.c
===================================================================
RCS file: /cvsroot/gkernel/linux_2_4/arch/alpha/kernel/process.c,v retrieving revision 1.1.1.14
alpha/kernel/process.c +1 -0
@@ -28,6 +28,7 @@#include <linux/mman.h> #include <linux/elfcore.h> #include <linux/reboot.h> +#include <linux/tty.h> #include <linux/console.h> #include <asm/reg.h>
Index: arch/alpha/kernel/sys_dp264.c
===================================================================
RCS file: /cvsroot/gkernel/linux_2_4/arch/alpha/kernel/sys_dp264.c,v retrieving revision 1.1.1.10
alpha/kernel/sys_dp264.c +1 -1
@@ -16,7 +16,7 @@#include <linux/pci.h> #include <linux/init.h> -#define __EXTERN_INLINE inline +#define __EXTERN_INLINE extern inline#include <asm/io.h> #include <asm/core_tsunami.h> #undef __EXTERN_INLINE
Index: arch/alpha/kernel/sys_sio.c
===================================================================
RCS file: /cvsroot/gkernel/linux_2_4/arch/alpha/kernel/sys_sio.c,v retrieving revision 1.1.1.2
alpha/kernel/sys_sio.c +1 -0
@@ -17,6 +17,7 @@#include <linux/sched.h> #include <linux/pci.h> #include <linux/init.h> +#include <linux/tty.h> #include <asm/compiler.h> #include <asm/ptrace.h>
Re: 2.4.5 does not link on Ruffian (alpha)
In reply to G. Hugh SongQuoted 3 lines · Andrea Arcangeli
I got exactly the above when compiling for dp264 so I sent to Linus a patch to fix those compile problems, now I suspect my fix broke the generic compile :(, I will check that.
2.4.5aa1 compiles fine, but 2.4.5 doesn't, don't know why yet. Please backout this patch from 2.4.5 for now, this should be the right thing to do in the long run:
arch/alpha/kernel/sys_dp264.c +5 -2
@@ -16,15 +16,18 @@#include <linux/pci.h> #include <linux/init.h> +#define __EXTERN_INLINE inline +#include <asm/io.h> +#include <asm/core_tsunami.h> +#undef __EXTERN_INLINE +#include <asm/ptrace.h> #include <asm/system.h> #include <asm/dma.h> #include <asm/irq.h> #include <asm/bitops.h> #include <asm/mmu_context.h> -#include <asm/io.h> #include <asm/pgtable.h> -#include <asm/core_tsunami.h> #include <asm/hwrpb.h> #include "proto.h"
Now I will start a robot that will tell me in some hour of computations which of the patches in my tree actually makes me to need the above patch to compile both generic and dp264 correctly. After I localized the offender patch it should be very easy to found why I need the above and 2.4.5 doesn't.
Andrea
Re: 2.4.5 does not link on Ruffian (alpha)
In reply to G. Hugh Songarch/alpha/kernel/sys_dp264.c Wed May 23 02:43:49 2001 line 23
Quoted 12 lines · Andrea Arcangeli
diff -urN
alpha/arch/alpha/kernel/sys_dp264.calpha-1/arch/alpha/kernel/sys_dp264.carch/alpha/kernel/sys_dp264.c Wed May 23 02:43:49 2001 renamed from arch/alpha/kernel/sys_dp264.c Sun Apr 1 01:17:07 2001 +5
-0@@ -16,15 +16,18 @@ #include <linux/pci.h> #include <linux/init.h> +#define __EXTERN_INLINE inline +#include <asm/io.h> +#include <asm/core_tsunami.h> +#undef __EXTERN_INLINE +
Why is "__EXTERN_INLINE" defined as "inline" not "extern inline"?
I simply added "extern" and things started working (as noted in my previous message in this thread)..
Signature · 3 lines
Jeff Garzik | Disbelief, that's why you fail. Building 1024 | MandrakeSoft |
Re: 2.4.5 does not link on Ruffian (alpha)
In reply to G. Hugh SongQuoted 8 lines · Jeff Garzik
Quoted 7 lines · Andrea Arcangeli
diff -urN
alpha/arch/alpha/kernel/sys_dp264.calpha-1/arch/alpha/kernel/sys_dp264.carch/alpha/kernel/sys_dp264.c Wed May 23 02:43:49 2001 renamed from arch/alpha/kernel/sys_dp264.c Sun Apr 1 01:17:07 2001 +0
-0@@ -16,15 +16,18 @@ #include <linux/pci.h> #include <linux/init.h>
Quoted 7 lines
arch/alpha/kernel/sys_dp264.c Wed May 23 02:43:49 2001 line 23
Quoted 5 lines
arch/alpha/kernel/sys_dp264.c Wed May 23 02:43:49 2001 renamed from arch/alpha/kernel/sys_dp264.c Sun Apr 1 01:17:07 2001 +5
-0+#define __EXTERN_INLINE inline +#include <asm/io.h> +#include <asm/core_tsunami.h> +#undef __EXTERN_INLINE +Why is "
__EXTERN_INLINE" defined as "inline" not "extern inline"?
because it must be implemented somewhere for the alpha_mv pointer to functions and for some reason they are not implemented by core_tsunami.c in my tree (but they are in mainline and that's right).
Quoted 2 lines
I simply added "extern" and things started working (as noted in my previous message in this thread)..
defining it as `extern inline' is completly equivalent to backing out the patch I posted, see core_tsunami.h:
#ifndef __EXTERN_INLINE
#define __EXTERN_INLINE extern inline
#define __IO_EXTERN_INLINE
#endif
Of course your patch works like a charm too. A cleaner fix is to backout my patch because core_tsunami.h will define it to `extern inline' atuomatically.
Tomorrow I'll go through the log generated by the script that did the binary search for me while I was out to find out what patch in my tree caused me to write the posted patch to get all compilations right.
Andrea
Re: 2.4.5 does not link on Ruffian (alpha)
In reply to G. Hugh SongQuoted 1 line · Andrea Arcangeli
caused me to write the posted patch to get all compilations right.
The reason I needed that patch is that I was not using 2.4.5aa1 but a corrupted tree (I'm been fooled by an hardlink during developement), it was just two lines away from the real one.
So this is the fix for all 2.4.5 based trees (ac1 and aa1 included) to get generic and dp264 compililations right:
arch/alpha/kernel/sys_dp264.c +2 -5
@@ -16,18 +16,15 @@#include <linux/pci.h> #include <linux/init.h> -#define __EXTERN_INLINE inline -#include <asm/io.h> -#include <asm/core_tsunami.h> -#undef __EXTERN_INLINE -#include <asm/ptrace.h> #include <asm/system.h> #include <asm/dma.h> #include <asm/irq.h> #include <asm/bitops.h> #include <asm/mmu_context.h> +#include <asm/io.h> #include <asm/pgtable.h> +#include <asm/core_tsunami.h> #include <asm/hwrpb.h> #include "proto.h"
Sorry about that.
Andrea
Re: 2.4.5 does not link on Ruffian (alpha)
In reply to G. Hugh SongQuoted 9 lines · Andrea Arcangeli
Quoted 1 line · Andrea Arcangeli
caused me to write the posted patch to get all compilations right.
The reason I needed that patch is that I was not using 2.4.5aa1 but a corrupted tree (I'm been fooled by an hardlink during developement), it was just two lines away from the real one.
So this is the fix for all 2.4.5 based trees (ac1 and aa1 included) to get generic and dp264 compililations right:
woops, the dp264 compilation wasn't right yet, this additional patch is needed too.
arch/alpha/kernel/core_tsunami.c renamed from arch/alpha/kernel/core_tsunami.c.~1~ +2 -1
@@ -11,7 +11,6 @@#include <linux/pci.h> #include <linux/sched.h> #include <linux/init.h> -#include <linux/bootmem.h> #include <asm/ptrace.h> #include <asm/system.h>
@@ -21,6 +20,8 @@#include <asm/io.h> #include <asm/core_tsunami.h> #undef __EXTERN_INLINE + +#include <linux/bootmem.h> #include "proto.h" #include "pci_impl.h"
the bootmem include was the one that broke the __EXTERN_INLINE logic for dp264.
Andrea
Re: 2.4.5 does not link on Ruffian (alpha)
In reply to G. Hugh SongFrom: "Andrea Arcangeli" <[email protected]>
Quoted 8 lines · Andrea Arcangeli
Quoted 7 lines · Andrea Arcangeli
Quoted 1 line
caused me to write the posted patch to get all compilations right.
The reason I needed that patch is that I was not using 2.4.5aa1 but a corrupted tree (I'm been fooled by an hardlink during developement), it was just two lines away from the real one.
Quoted 6 lines
Quoted 2 lines
So this is the fix for all 2.4.5 based trees (ac1 and aa1 included) to get generic and dp264 compililations right:
woops, the dp264 compilation wasn't right yet, this additional patch is needed too.
2.4.5aa1 broke on my ruffian, now it works beautifully, now i just gotta check if it boots :)
Magnus Naeslund
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Programmer/Networker [|] Magnus Naeslund
PGP Key: http://www.genline.nu/mag_pgp.txt
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Re: [PATCH] Re: 2.4.5 does not link on Ruffian (alpha)
In reply to G. Hugh SongQuoted 1 line · Jeff Garzik
When built with
CONFIG_ALPHA_NAUTILUS, my UP1000's IDE totally fails.
Mine doesn't.
Quoted 2 lines
I am booting w/ aboot 0.7a from SRM, -without- the srm-as-bootloader kernel config option.
That is the error.
r~
Re: [PATCH] Re: 2.4.5 does not link on Ruffian (alpha)
In reply to G. Hugh SongQuoted 9 lines · Richard Henderson
Quoted 1 line · Jeff Garzik
When built with
CONFIG_ALPHA_NAUTILUS, my UP1000's IDE totally fails.Mine doesn't.
Quoted 2 lines
I am booting w/ aboot 0.7a from SRM, -without- the srm-as-bootloader kernel config option.
That is the error.
Ok, thanks.
FWIW the documentation seems to imply that the option is necessary only when directly booting from SRM, i.e.. no bootloader is involved at all. It uses the example of MILO's presence or absence as indicating the need for this option.
So... is it safe to always enable this option, with a little hacking perhaps? :)
Regards,
Jeff
Quoted 20 lines
Using SRM as bootloader
CONFIG_ALPHA_SRM
There are two different types of booting firmware on Alphas: SRM, which is command line driven, and ARC, which uses menus and arrow keys. Details about the Linux/Alpha booting process are contained in the Linux/Alpha FAQ, accessible on the WWW from
http://www.alphalinux.org .The usual way to load Linux on an Alpha machine is to use MILO (a bootloader that lets you pass command line parameters to the kernel just like lilo does for the x86 architecture) which can be loaded either from ARC or can be installed directly as a permanent firmware replacement from floppy (which requires changing a certain jumper on the motherboard). If you want to do either of these, say N here. If MILO doesn't work on your system (true for Jensen motherboards), you can bypass it altogether and boot Linux directly from an SRM console; say Y here in order to do that. Note that you won't be able to boot from an IDE disk using SRM.
If unsure, say N.
Signature · 3 lines
Jeff Garzik | Disbelief, that's why you fail. Building 1024 | MandrakeSoft |
Re: [PATCH] Re: 2.4.5 does not link on Ruffian (alpha)
In reply to G. Hugh SongQuoted 2 lines · Jeff Garzik
FWIW the documentation seems to imply that the option is necessary only when directly booting from SRM, i.e.. no bootloader is involved at all.
Err, well, you can't have _no_ bootloader.
Quoted 2 lines
It uses the example of MILO's presence or absence as indicating the need for this option.
Exactly. aboot doesn't substitute.
Quoted 2 lines
So... is it safe to always enable this option, with a little hacking perhaps? :)
Well, yes, it is obviously possible. The generic config does what you want. You just need to permanently enable some of that configury.
r~