Re: Swap strangeness using 2.4.5pre2aa1
On Thu, 24 May 2001, G. Hugh Song wrote: > My Alpha/LInux UP2000 SMP with 1GB memory is running kernel > The following is the output from "free" > = > total used free sharedbuffers cached > Mem: 10231281015640 7488 0544 948976 > -/+ buffers/cache: 66120 957008 > Swap: 10219361021936 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/ http://www.conectiva.com/ http://distro.conectiva.com/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Swap strangeness using 2.4.5pre2aa1
On Thu, May 24, 2001 at 03:16:48AM +0900, G. Hugh Song wrote: > The following is the output from "free" > = > total used free sharedbuffers > cached > Mem: 10231281015640 7488 0544 > 948976 > -/+ buffers/cache: 66120 957008 > Swap: 10219361021936 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. > I think I should back down to Kernel 2.2.20pre2aa1. definitely a good idea until somebody fixes the VM in mainline. Andrea - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
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 sharedbuffers cached Mem: 10231281015640 7488 0544 948976 -/+ buffers/cache: 66120 957008 Swap: 10219361021936 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 R1872 1.0 0.0 0:02 top 5 root 12 0 00 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 00 0 SW 0 0.0 0.0 0:00 keventd 3 root 20 19 00 0 SWN 0 0.0 0.0 0:01 ksoftirqd_CP 4 root 20 19 00 0 SWN 0 0.0 0.0 0:00 ksoftirqd_CP 6 root 12 0 00 0 SW 0 0.0 0.0 0:00 kreclaimd 7 root 12 0 00 0 SW 0 0.0 0.0 0:00 bdflush 8 root 12 0 00 0 SW 0 0.0 0.0 1:03 kupdated 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 9608 8 S 0 0.0 0.0 0:06 klogd 227 root 12 0 1368 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. -- 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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
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 sharedbuffers cached Mem: 10231281015640 7488 0544 948976 -/+ buffers/cache: 66120 957008 Swap: 10219361021936 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 R1872 1.0 0.0 0:02 top 5 root 12 0 00 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 00 0 SW 0 0.0 0.0 0:00 keventd 3 root 20 19 00 0 SWN 0 0.0 0.0 0:01 ksoftirqd_CP 4 root 20 19 00 0 SWN 0 0.0 0.0 0:00 ksoftirqd_CP 6 root 12 0 00 0 SW 0 0.0 0.0 0:00 kreclaimd 7 root 12 0 00 0 SW 0 0.0 0.0 0:00 bdflush 8 root 12 0 00 0 SW 0 0.0 0.0 1:03 kupdated 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 9608 8 S 0 0.0 0.0 0:06 klogd 227 root 12 0 1368 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. -- 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 - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Swap strangeness using 2.4.5pre2aa1
On Thu, May 24, 2001 at 03:16:48AM +0900, G. Hugh Song wrote: The following is the output from free = total used free sharedbuffers cached Mem: 10231281015640 7488 0544 948976 -/+ buffers/cache: 66120 957008 Swap: 10219361021936 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. I think I should back down to Kernel 2.2.20pre2aa1. definitely a good idea until somebody fixes the VM in mainline. Andrea - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Swap strangeness using 2.4.5pre2aa1
On Thu, 24 May 2001, G. Hugh Song wrote: My Alpha/LInux UP2000 SMP with 1GB memory is running kernel The following is the output from free = total used free sharedbuffers cached Mem: 10231281015640 7488 0544 948976 -/+ buffers/cache: 66120 957008 Swap: 10219361021936 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/ http://www.conectiva.com/ http://distro.conectiva.com/ - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.4.5pre2aa1 panic during boot
On Mon, May 21, 2001 at 01:59:25AM +0900, root wrote: > Andrea told us that he will not care for anything > compiled with gcc-2.95 or version lower than that. I said I don't care about bugreport of alpha kernel crashes if the _alpha_ kernel was compiled with gcc 2.95.*. 2.95 is fine on the x86, but it's broken on the alpha. In short: x86 2.4 kernels -> use 2.95.[34] or egcs 1.1.2 (I use 2.95.4 from the gcc_2_95_branch of CVS) alpha 2.4 kernel-> use egcs 1.1.2 or 2.96 with some houndred of patches (I personally still use the egcs 1.1.2) > However, it seems that this kernel panic has anything > to do with gcc-2.95. Please try to reproduce with egcs 1.1.2 to be sure. > Anyway, gcc-2.95 is still the official release of gcc. > Even SuSE-7.1 has this version only. I wish SuSE puts x86 and alpha are completly different issues with regard to the compiler. I never heard of problems with 2.95.4 on x86 and I would never replace 2.95.4 from the gcc_2_95_branch for the latest 2.96 on my x86 boxes, I'd instead try again gcc 3.0 after the inline asm fixes for "+=" constranints on local variables are done. Andrea - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
2.4.5pre2aa1 panic during boot
The attached .config file created a working kernel for 2.4.2. Now, with the one compiled from 2.4.5pre2aa1, it only gives kernel panic during boot with the following message: Kernel panic: Attempted to kill the idel task In idle task -- not syncing This happened on LX164 with AlphaBIOS running SuSE-7.0, gcc-2.95.2-136. Almost identical .config file created a working kernel for UP2000 SMP. So, what is wrong with LX164? Should I dump this old ALpha now? Andrea told us that he will not care for anything compiled with gcc-2.95 or version lower than that. However, it seems that this kernel panic has anything to do with gcc-2.95. Anyway, gcc-2.95 is still the official release of gcc. Even SuSE-7.1 has this version only. I wish SuSE puts something higher than 2.95 in their web site somewhere. Best regards, Hugh # # Automatically generated make config: don't edit # CONFIG_ALPHA=y # CONFIG_UID16 is not set CONFIG_RWSEM_GENERIC_SPINLOCK=y # # Code maturity level options # CONFIG_EXPERIMENTAL=y # # Loadable module support # CONFIG_MODULES=y CONFIG_MODVERSIONS=y CONFIG_KMOD=y # # General setup # # CONFIG_ALPHA_GENERIC is not set # CONFIG_ALPHA_ALCOR is not set # CONFIG_ALPHA_XL is not set # CONFIG_ALPHA_BOOK1 is not set # CONFIG_ALPHA_AVANTI is not set # CONFIG_ALPHA_CABRIOLET is not set # CONFIG_ALPHA_DP264 is not set # CONFIG_ALPHA_EB164 is not set # CONFIG_ALPHA_EB64P is not set # CONFIG_ALPHA_EB66 is not set # CONFIG_ALPHA_EB66P is not set # CONFIG_ALPHA_EIGER is not set # CONFIG_ALPHA_JENSEN is not set CONFIG_ALPHA_LX164=y # CONFIG_ALPHA_MIATA is not set # CONFIG_ALPHA_MIKASA is not set # CONFIG_ALPHA_NAUTILUS is not set # CONFIG_ALPHA_NONAME is not set # CONFIG_ALPHA_NORITAKE is not set # CONFIG_ALPHA_PC164 is not set # CONFIG_ALPHA_P2K is not set # CONFIG_ALPHA_RAWHIDE is not set # CONFIG_ALPHA_RUFFIAN is not set # CONFIG_ALPHA_RX164 is not set # CONFIG_ALPHA_SX164 is not set # CONFIG_ALPHA_SABLE is not set # CONFIG_ALPHA_TAKARA is not set # CONFIG_ALPHA_TITAN is not set # CONFIG_ALPHA_WILDFIRE is not set CONFIG_ISA=y CONFIG_EISA=y # CONFIG_SBUS is not set # CONFIG_MCA is not set CONFIG_PCI=y CONFIG_ALPHA_EV5=y CONFIG_ALPHA_CIA=y CONFIG_ALPHA_PYXIS=y # CONFIG_ALPHA_SRM is not set CONFIG_DISCONTIGMEM=y CONFIG_NUMA=y CONFIG_NUMA_SCHED=y # CONFIG_ALPHA_LARGE_VMALLOC is not set CONFIG_PCI_NAMES=y # CONFIG_HOTPLUG is not set # CONFIG_PCMCIA is not set CONFIG_NET=y CONFIG_SYSVIPC=y CONFIG_BSD_PROCESS_ACCT=y CONFIG_SYSCTL=y CONFIG_KCORE_ELF=y # CONFIG_KCORE_AOUT is not set CONFIG_BINFMT_AOUT=y CONFIG_BINFMT_ELF=y CONFIG_BINFMT_MISC=y # CONFIG_BINFMT_EM86 is not set # # Parallel port support # CONFIG_PARPORT=y CONFIG_PARPORT_PC=y CONFIG_PARPORT_PC_FIFO=y # CONFIG_PARPORT_PC_SUPERIO is not set # CONFIG_PARPORT_AMIGA is not set # CONFIG_PARPORT_MFC3 is not set # CONFIG_PARPORT_ATARI is not set # CONFIG_PARPORT_SUNBPP is not set # CONFIG_PARPORT_OTHER is not set CONFIG_PARPORT_1284=y # # Memory Technology Devices (MTD) # # CONFIG_MTD is not set # # Plug and Play configuration # CONFIG_PNP=y CONFIG_ISAPNP=y # # Block devices # CONFIG_BLK_DEV_FD=y # CONFIG_BLK_DEV_XD is not set # CONFIG_PARIDE is not set # CONFIG_BLK_CPQ_DA is not set # CONFIG_BLK_CPQ_CISS_DA is not set # CONFIG_BLK_DEV_DAC960 is not set CONFIG_BLK_DEV_LOOP=y CONFIG_BLK_DEV_NBD=m # CONFIG_BLK_DEV_RAM is not set # # Multi-device support (RAID and LVM) # CONFIG_MD=y # CONFIG_BLK_DEV_MD is not set CONFIG_BLK_DEV_LVM=y # # Networking options # CONFIG_PACKET=y # CONFIG_PACKET_MMAP is not set CONFIG_NETLINK=y CONFIG_RTNETLINK=y CONFIG_NETLINK_DEV=y # CONFIG_NETFILTER is not set # CONFIG_FILTER is not set CONFIG_UNIX=y CONFIG_INET=y # CONFIG_IP_MULTICAST is not set # CONFIG_IP_ADVANCED_ROUTER is not set # CONFIG_IP_PNP is not set # CONFIG_NET_IPIP is not set # CONFIG_NET_IPGRE is not set # CONFIG_ARPD is not set # CONFIG_INET_ECN is not set CONFIG_SYN_COOKIES=y # CONFIG_IPV6 is not set # CONFIG_KHTTPD is not set # CONFIG_ATM is not set # # # # CONFIG_IPX is not set # CONFIG_ATALK is not set # CONFIG_DECNET is not set # CONFIG_BRIDGE is not set # CONFIG_X25 is not set # CONFIG_LAPB is not set # CONFIG_LLC is not set # CONFIG_NET_DIVERT is not set # CONFIG_ECONET is not set # CONFIG_WAN_ROUTER is not set CONFIG_NET_FASTROUTE=y # CONFIG_NET_HW_FLOWCONTROL is not set # # QoS and/or fair queueing # # CONFIG_NET_SCHED is not set # # ATA/IDE/MFM/RLL support # CONFIG_IDE=y # # IDE, ATA and ATAPI Block devices # CONFIG_BLK_DEV_IDE=y # # Please see Documentation/ide.txt for help/info on IDE drives # # CONFIG_BLK_DEV_HD_IDE is not set # CONFIG_BLK_DEV_HD is not set CONFIG_BLK_DEV_IDEDISK=y # CONFIG_IDEDISK_MULTI_MODE is not set # CONFIG_BLK_DEV_IDEDISK_VENDOR is not set # CONFIG_BLK_DEV_COMMERIAL is not set CONFIG_BLK_DEV_IDECD=y # CONFIG_BLK_DEV_IDETAPE is not set # CONFIG_BLK_DEV_IDEFLOPPY is not set # CONFIG_BLK_DEV_IDESCSI is not set # # IDE chipset support/bugfixes # # CONFIG_BLK_DEV_CMD640 is not set # CONFIG_BLK_DEV_ISAPNP is not set
2.4.5pre2aa1 panic during boot
The attached .config file created a working kernel for 2.4.2. Now, with the one compiled from 2.4.5pre2aa1, it only gives kernel panic during boot with the following message: Kernel panic: Attempted to kill the idel task In idle task -- not syncing This happened on LX164 with AlphaBIOS running SuSE-7.0, gcc-2.95.2-136. Almost identical .config file created a working kernel for UP2000 SMP. So, what is wrong with LX164? Should I dump this old ALpha now? Andrea told us that he will not care for anything compiled with gcc-2.95 or version lower than that. However, it seems that this kernel panic has anything to do with gcc-2.95. Anyway, gcc-2.95 is still the official release of gcc. Even SuSE-7.1 has this version only. I wish SuSE puts something higher than 2.95 in their web site somewhere. Best regards, Hugh # # Automatically generated make config: don't edit # CONFIG_ALPHA=y # CONFIG_UID16 is not set CONFIG_RWSEM_GENERIC_SPINLOCK=y # # Code maturity level options # CONFIG_EXPERIMENTAL=y # # Loadable module support # CONFIG_MODULES=y CONFIG_MODVERSIONS=y CONFIG_KMOD=y # # General setup # # CONFIG_ALPHA_GENERIC is not set # CONFIG_ALPHA_ALCOR is not set # CONFIG_ALPHA_XL is not set # CONFIG_ALPHA_BOOK1 is not set # CONFIG_ALPHA_AVANTI is not set # CONFIG_ALPHA_CABRIOLET is not set # CONFIG_ALPHA_DP264 is not set # CONFIG_ALPHA_EB164 is not set # CONFIG_ALPHA_EB64P is not set # CONFIG_ALPHA_EB66 is not set # CONFIG_ALPHA_EB66P is not set # CONFIG_ALPHA_EIGER is not set # CONFIG_ALPHA_JENSEN is not set CONFIG_ALPHA_LX164=y # CONFIG_ALPHA_MIATA is not set # CONFIG_ALPHA_MIKASA is not set # CONFIG_ALPHA_NAUTILUS is not set # CONFIG_ALPHA_NONAME is not set # CONFIG_ALPHA_NORITAKE is not set # CONFIG_ALPHA_PC164 is not set # CONFIG_ALPHA_P2K is not set # CONFIG_ALPHA_RAWHIDE is not set # CONFIG_ALPHA_RUFFIAN is not set # CONFIG_ALPHA_RX164 is not set # CONFIG_ALPHA_SX164 is not set # CONFIG_ALPHA_SABLE is not set # CONFIG_ALPHA_TAKARA is not set # CONFIG_ALPHA_TITAN is not set # CONFIG_ALPHA_WILDFIRE is not set CONFIG_ISA=y CONFIG_EISA=y # CONFIG_SBUS is not set # CONFIG_MCA is not set CONFIG_PCI=y CONFIG_ALPHA_EV5=y CONFIG_ALPHA_CIA=y CONFIG_ALPHA_PYXIS=y # CONFIG_ALPHA_SRM is not set CONFIG_DISCONTIGMEM=y CONFIG_NUMA=y CONFIG_NUMA_SCHED=y # CONFIG_ALPHA_LARGE_VMALLOC is not set CONFIG_PCI_NAMES=y # CONFIG_HOTPLUG is not set # CONFIG_PCMCIA is not set CONFIG_NET=y CONFIG_SYSVIPC=y CONFIG_BSD_PROCESS_ACCT=y CONFIG_SYSCTL=y CONFIG_KCORE_ELF=y # CONFIG_KCORE_AOUT is not set CONFIG_BINFMT_AOUT=y CONFIG_BINFMT_ELF=y CONFIG_BINFMT_MISC=y # CONFIG_BINFMT_EM86 is not set # # Parallel port support # CONFIG_PARPORT=y CONFIG_PARPORT_PC=y CONFIG_PARPORT_PC_FIFO=y # CONFIG_PARPORT_PC_SUPERIO is not set # CONFIG_PARPORT_AMIGA is not set # CONFIG_PARPORT_MFC3 is not set # CONFIG_PARPORT_ATARI is not set # CONFIG_PARPORT_SUNBPP is not set # CONFIG_PARPORT_OTHER is not set CONFIG_PARPORT_1284=y # # Memory Technology Devices (MTD) # # CONFIG_MTD is not set # # Plug and Play configuration # CONFIG_PNP=y CONFIG_ISAPNP=y # # Block devices # CONFIG_BLK_DEV_FD=y # CONFIG_BLK_DEV_XD is not set # CONFIG_PARIDE is not set # CONFIG_BLK_CPQ_DA is not set # CONFIG_BLK_CPQ_CISS_DA is not set # CONFIG_BLK_DEV_DAC960 is not set CONFIG_BLK_DEV_LOOP=y CONFIG_BLK_DEV_NBD=m # CONFIG_BLK_DEV_RAM is not set # # Multi-device support (RAID and LVM) # CONFIG_MD=y # CONFIG_BLK_DEV_MD is not set CONFIG_BLK_DEV_LVM=y # # Networking options # CONFIG_PACKET=y # CONFIG_PACKET_MMAP is not set CONFIG_NETLINK=y CONFIG_RTNETLINK=y CONFIG_NETLINK_DEV=y # CONFIG_NETFILTER is not set # CONFIG_FILTER is not set CONFIG_UNIX=y CONFIG_INET=y # CONFIG_IP_MULTICAST is not set # CONFIG_IP_ADVANCED_ROUTER is not set # CONFIG_IP_PNP is not set # CONFIG_NET_IPIP is not set # CONFIG_NET_IPGRE is not set # CONFIG_ARPD is not set # CONFIG_INET_ECN is not set CONFIG_SYN_COOKIES=y # CONFIG_IPV6 is not set # CONFIG_KHTTPD is not set # CONFIG_ATM is not set # # # # CONFIG_IPX is not set # CONFIG_ATALK is not set # CONFIG_DECNET is not set # CONFIG_BRIDGE is not set # CONFIG_X25 is not set # CONFIG_LAPB is not set # CONFIG_LLC is not set # CONFIG_NET_DIVERT is not set # CONFIG_ECONET is not set # CONFIG_WAN_ROUTER is not set CONFIG_NET_FASTROUTE=y # CONFIG_NET_HW_FLOWCONTROL is not set # # QoS and/or fair queueing # # CONFIG_NET_SCHED is not set # # ATA/IDE/MFM/RLL support # CONFIG_IDE=y # # IDE, ATA and ATAPI Block devices # CONFIG_BLK_DEV_IDE=y # # Please see Documentation/ide.txt for help/info on IDE drives # # CONFIG_BLK_DEV_HD_IDE is not set # CONFIG_BLK_DEV_HD is not set CONFIG_BLK_DEV_IDEDISK=y # CONFIG_IDEDISK_MULTI_MODE is not set # CONFIG_BLK_DEV_IDEDISK_VENDOR is not set # CONFIG_BLK_DEV_COMMERIAL is not set CONFIG_BLK_DEV_IDECD=y # CONFIG_BLK_DEV_IDETAPE is not set # CONFIG_BLK_DEV_IDEFLOPPY is not set # CONFIG_BLK_DEV_IDESCSI is not set # # IDE chipset support/bugfixes # # CONFIG_BLK_DEV_CMD640 is not set # CONFIG_BLK_DEV_ISAPNP is not set
Re: 2.4.5pre2aa1 panic during boot
On Mon, May 21, 2001 at 01:59:25AM +0900, root wrote: Andrea told us that he will not care for anything compiled with gcc-2.95 or version lower than that. I said I don't care about bugreport of alpha kernel crashes if the _alpha_ kernel was compiled with gcc 2.95.*. 2.95 is fine on the x86, but it's broken on the alpha. In short: x86 2.4 kernels - use 2.95.[34] or egcs 1.1.2 (I use 2.95.4 from the gcc_2_95_branch of CVS) alpha 2.4 kernel- use egcs 1.1.2 or 2.96 with some houndred of patches (I personally still use the egcs 1.1.2) However, it seems that this kernel panic has anything to do with gcc-2.95. Please try to reproduce with egcs 1.1.2 to be sure. Anyway, gcc-2.95 is still the official release of gcc. Even SuSE-7.1 has this version only. I wish SuSE puts x86 and alpha are completly different issues with regard to the compiler. I never heard of problems with 2.95.4 on x86 and I would never replace 2.95.4 from the gcc_2_95_branch for the latest 2.96 on my x86 boxes, I'd instead try again gcc 3.0 after the inline asm fixes for += constranints on local variables are done. Andrea - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.4.5pre2aa1
On Wednesday 16 May 2001 09:52, Andrea Arcangeli babbled: > > These descriptions are very helpful. Are they available somewhere > personally, I wish all kernel announcements were as nice as this. Kudos to Andrea. -- Douglas J. Hunley (Linux User #174778) http://hunley.homeip.net/ http://linux.nf/http://www.kicq.org/ And on the 8th day God said, "OK Murphy, you take over." - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.4.5pre2aa1
On Tue, May 15, 2001 at 08:42:03PM -0300, Rik van Riel wrote: > On Tue, 15 May 2001, Andrea Arcangeli wrote: > > > Detailed description of 2.4.5pre2aa1 follows. > > > 00_buffer-2 > > > > Reschedule during oom while allocating buffers, still getblk > > can deadlock with oom but this will hide it pretty well as > > it won't loop in a tight loop anymore. > > These descriptions are very helpful. Are they available somewhere I'm happy to hear that. > for all your (recent) patches? Almost everything was shortly described in my last emails. Those descriptions are available also as .log into my ftp area. Andrea - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.4.5pre2aa1
On Tue, May 15, 2001 at 08:42:03PM -0300, Rik van Riel wrote: On Tue, 15 May 2001, Andrea Arcangeli wrote: Detailed description of 2.4.5pre2aa1 follows. 00_buffer-2 Reschedule during oom while allocating buffers, still getblk can deadlock with oom but this will hide it pretty well as it won't loop in a tight loop anymore. These descriptions are very helpful. Are they available somewhere I'm happy to hear that. for all your (recent) patches? Almost everything was shortly described in my last emails. Those descriptions are available also as .log into my ftp area. Andrea - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.4.5pre2aa1
On Wednesday 16 May 2001 09:52, Andrea Arcangeli babbled: These descriptions are very helpful. Are they available somewhere personally, I wish all kernel announcements were as nice as this. Kudos to Andrea. -- Douglas J. Hunley (Linux User #174778) http://hunley.homeip.net/ http://linux.nf/http://www.kicq.org/ And on the 8th day God said, OK Murphy, you take over. - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.4.5pre2aa1
On Tue, 15 May 2001, Andrea Arcangeli wrote: > Detailed description of 2.4.5pre2aa1 follows. > 00_buffer-2 > > Reschedule during oom while allocating buffers, still getblk > can deadlock with oom but this will hide it pretty well as > it won't loop in a tight loop anymore. These descriptions are very helpful. Are they available somewhere for all your (recent) patches? regards, Rik -- Virtual memory is like a game you can't win; However, without VM there's truly nothing to lose... http://www.surriel.com/ http://distro.conectiva.com/ Send all your spam to [EMAIL PROTECTED] (spam digging piggy) - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
2.4.5pre2aa1
Detailed description of 2.4.5pre2aa1 follows. --- 00_alpha-illegal-irq-1 Be verbose for MAX_ILLEGAL_IRQS times if an invalid irq number is getting run. (debugging) 00_alpha-ksyms-1 Export a few alpha-arch symbols needed by modules. (recommended to avoid compilation troubles) 00_alpha-large-vmalloc-1 Drop the CONFIG_LARGE_VMALLOC selection from the arch/alpha/config.in, the large-vmalloc feature is racy and it can destabilize the machine, fixing it isn't worthwhile because nobody needs more than 8Gigabytes of ram in vmalloc memory, not even tux on the 256G boxes will ever need that. (recommended) 00_alpha-modrace-1 Fix alpha races between module insmod/rmmod and the page fault fixmap lookup. (recommended) 00_alpha-numa-10 Fully support wildfire machines with all kind of NUMA memory configuration, plus it optimizes the allocation on per node basis to boost the performance on the NUMA boxes. Right now CONFIG_WILDFIRE needs to be selected to take advantage of this feature. (CONFIG_GENERIC + CONFIG_DISCONTIGMEM=y and CONFIG_NUMA=y will work fine as well but it won't take advantage of the new feature. It also fixes many memory management bit in the core linux allocator in the common code, mostly to avoid wasting static memory. (recommended) 00_alpha-sched-yield-1 Fixes SCHED_YIELD on the alpha arch for UP compiles. (recommended) 00_alpha-show_stack-1 Implements the show_stack() call used often by some common code, mostly to allow compilation, things like tux needs it. (nice to have) 00_alpha-tlb-page-sym-1 Drops a not necessary export on the alpha port. (recommended) 00_buffer-2 Reschedule during oom while allocating buffers, still getblk can deadlock with oom but this will hide it pretty well as it won't loop in a tight loop anymore. (recommended) 00_cachelinealigned-in-smp-1 Moves the pagecache_lock and the VM pagemap_lru_lock in two different L1 cachelines to avoid contention, mostly useful on the alpha where the spinlocks uses load locked store conditional loops (and we don't want to loop). (nice to have) 00_copy-user-lat-2 Put the rechedule points into copy-user calls, with lots of cache large read/writes could otherwise _never_ reschedule once until they returns to userspace. (recommended) 00_cpus_allowed-1 Fixes a bug in the cpu affinity in-kernel API, bug was fatal for ksoftirqd. (recommended) 00_double-buffer-pass-1 Avoids looping two times for no good reason into the lru lists of the buffer cache (the double loop was an unreliable hack from the prehistory that survided 'till today). (nice to have) 00_exception-table-1 Avoids a compilation warning when compiling without modules. (very minor thing) 00_highmem-deadlock-3 Fixes an highmem deadlock using a reserved pool for the bounce buffers. (recommended) 00_highmem-debug-1 Allows people with x86 machines with less than 1G of ram to test the highmem code. (debugging) 00_ia32-bootmem-corruption-1 Fixes the x86 boot stage to finish initializing all the reserved memory before starting allocating memory. (recommended) 00_ipv6-null-oops-1 Fixes null pointer oops. (recommended) 00_jens-loop-noop-nobounce-1 Skips the bounces with the null transfer function. (nice to have) 00_ksoftirqd-4 Avoids 1/HZ latency for the softirq if the softirq is marked again pending when do_softirq() finished and the machine is otherwise idle, it also fixes the case of a softirq re-marking itself runnable by delegating to the scheduler the balance of the softirq load like if it would be an normal task. (nice to have) 00_kupdate-large-interval-1 Allows to set large interval for the kupdate runs, this is useful on the laptops, instead of sigstopping ksoftirqd it's nicer to set a large interval for example of the order of one hour (do that at your own risk of course, doing that is not recommended unless you know what you're doing). (nice to have) 00_lvm-0.9.1_beta7-4 Updates to the lvmbeta7 with fixes for the lv hardsectsize estimantion based on the max hardsectsize of the underlying pv, plus it has some other tons of fixes and it is a must have for the 64bit archs as the IOP silenty changed for those platforms. (recommended) 00_max_readahead-1 Increases the max_readahead to allow
2.4.5pre2aa1
Detailed description of 2.4.5pre2aa1 follows. --- 00_alpha-illegal-irq-1 Be verbose for MAX_ILLEGAL_IRQS times if an invalid irq number is getting run. (debugging) 00_alpha-ksyms-1 Export a few alpha-arch symbols needed by modules. (recommended to avoid compilation troubles) 00_alpha-large-vmalloc-1 Drop the CONFIG_LARGE_VMALLOC selection from the arch/alpha/config.in, the large-vmalloc feature is racy and it can destabilize the machine, fixing it isn't worthwhile because nobody needs more than 8Gigabytes of ram in vmalloc memory, not even tux on the 256G boxes will ever need that. (recommended) 00_alpha-modrace-1 Fix alpha races between module insmod/rmmod and the page fault fixmap lookup. (recommended) 00_alpha-numa-10 Fully support wildfire machines with all kind of NUMA memory configuration, plus it optimizes the allocation on per node basis to boost the performance on the NUMA boxes. Right now CONFIG_WILDFIRE needs to be selected to take advantage of this feature. (CONFIG_GENERIC + CONFIG_DISCONTIGMEM=y and CONFIG_NUMA=y will work fine as well but it won't take advantage of the new feature. It also fixes many memory management bit in the core linux allocator in the common code, mostly to avoid wasting static memory. (recommended) 00_alpha-sched-yield-1 Fixes SCHED_YIELD on the alpha arch for UP compiles. (recommended) 00_alpha-show_stack-1 Implements the show_stack() call used often by some common code, mostly to allow compilation, things like tux needs it. (nice to have) 00_alpha-tlb-page-sym-1 Drops a not necessary export on the alpha port. (recommended) 00_buffer-2 Reschedule during oom while allocating buffers, still getblk can deadlock with oom but this will hide it pretty well as it won't loop in a tight loop anymore. (recommended) 00_cachelinealigned-in-smp-1 Moves the pagecache_lock and the VM pagemap_lru_lock in two different L1 cachelines to avoid contention, mostly useful on the alpha where the spinlocks uses load locked store conditional loops (and we don't want to loop). (nice to have) 00_copy-user-lat-2 Put the rechedule points into copy-user calls, with lots of cache large read/writes could otherwise _never_ reschedule once until they returns to userspace. (recommended) 00_cpus_allowed-1 Fixes a bug in the cpu affinity in-kernel API, bug was fatal for ksoftirqd. (recommended) 00_double-buffer-pass-1 Avoids looping two times for no good reason into the lru lists of the buffer cache (the double loop was an unreliable hack from the prehistory that survided 'till today). (nice to have) 00_exception-table-1 Avoids a compilation warning when compiling without modules. (very minor thing) 00_highmem-deadlock-3 Fixes an highmem deadlock using a reserved pool for the bounce buffers. (recommended) 00_highmem-debug-1 Allows people with x86 machines with less than 1G of ram to test the highmem code. (debugging) 00_ia32-bootmem-corruption-1 Fixes the x86 boot stage to finish initializing all the reserved memory before starting allocating memory. (recommended) 00_ipv6-null-oops-1 Fixes null pointer oops. (recommended) 00_jens-loop-noop-nobounce-1 Skips the bounces with the null transfer function. (nice to have) 00_ksoftirqd-4 Avoids 1/HZ latency for the softirq if the softirq is marked again pending when do_softirq() finished and the machine is otherwise idle, it also fixes the case of a softirq re-marking itself runnable by delegating to the scheduler the balance of the softirq load like if it would be an normal task. (nice to have) 00_kupdate-large-interval-1 Allows to set large interval for the kupdate runs, this is useful on the laptops, instead of sigstopping ksoftirqd it's nicer to set a large interval for example of the order of one hour (do that at your own risk of course, doing that is not recommended unless you know what you're doing). (nice to have) 00_lvm-0.9.1_beta7-4 Updates to the lvmbeta7 with fixes for the lv hardsectsize estimantion based on the max hardsectsize of the underlying pv, plus it has some other tons of fixes and it is a must have for the 64bit archs as the IOP silenty changed for those platforms. (recommended) 00_max_readahead-1 Increases the max_readahead to allow
Re: 2.4.5pre2aa1
On Tue, 15 May 2001, Andrea Arcangeli wrote: Detailed description of 2.4.5pre2aa1 follows. 00_buffer-2 Reschedule during oom while allocating buffers, still getblk can deadlock with oom but this will hide it pretty well as it won't loop in a tight loop anymore. These descriptions are very helpful. Are they available somewhere for all your (recent) patches? regards, Rik -- Virtual memory is like a game you can't win; However, without VM there's truly nothing to lose... http://www.surriel.com/ http://distro.conectiva.com/ Send all your spam to [EMAIL PROTECTED] (spam digging piggy) - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
