ARM kirkwood: 1 Gb memory 25% unusable due to vmalloc region overlap
I updated my Qnap TS-212 with 256 Mb memory to a new TS-221 with 1 Gb memory.
On booting, I see that a large chunk of that new memory is not used by linux:
[ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Initializing cgroup subsys cpuset [ 0.000000] Initializing cgroup subsys cpu [ 0.000000] Initializing cgroup subsys cpuacct [ 0.000000] Linux version 3.14-2-kirkwood ([email protected]) (gcc version 4.8.3 (Debian 4.8.3-7) ) #1 Debian 3.14.15-2 (2014-08-09) [ 0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=00053977 [ 0.000000] CPU: VIVT data cache, VIVT instruction cache [ 0.000000] Machine: QNAP TS-119/TS-219 [ 0.000000] Ignoring unrecognised tag 0x41000403 [ 0.000000] Truncating RAM at 20000000-3fffffff to -2f7fffff (vmalloc region overlap).
Whoops!
[ 0.000000] Memory policy: Data cache writeback [ 0.000000] On node 0 totalpages: 194560 [ 0.000000] free_area_init_node: node 0, pgdat c05af874, node_mem_map ef20b000 [ 0.000000] DMA zone: 1520 pages used for memmap [ 0.000000] DMA zone: 0 pages reserved [ 0.000000] DMA zone: 194560 pages, LIFO batch:31 [ 0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768 [ 0.000000] pcpu-alloc: [0] 0 [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 193040 [ 0.000000] Kernel command line: console=ttyS0,115200 root=/dev/ram initrd=0xa00000,0x900000 ramdisk=34816 [ 0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes) [ 0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) [ 0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) [ 0.000000] Memory: 755820K/778240K available (3869K kernel code, 352K rwdata, 1412K rodata, 202K init, 417K bss, 22420K reserved) [ 0.000000] Virtual kernel memory layout: [ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB) [ 0.000000] fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB) [ 0.000000] vmalloc : 0xf0000000 - 0xff000000 ( 240 MB) [ 0.000000] lowmem : 0xc0000000 - 0xef800000 ( 760 MB) [ 0.000000] modules : 0xbf000000 - 0xc0000000 ( 16 MB) [ 0.000000] .text : 0xc0008000 - 0xc053097c (5283 kB) [ 0.000000] .init : 0xc0531000 - 0xc0563b34 ( 203 kB) [ 0.000000] .data : 0xc0564000 - 0xc05bc128 ( 353 kB) [ 0.000000] .bss : 0xc05bc128 - 0xc06246c4 ( 418 kB) [ 0.000000] NR_IRQS:114
As far as I've been able to determine, this config is used in the debian linux-image-3.14-2-kirkwood package:
CONFIG_ARCH_KIRKWOOD=yCONFIG_PCI=yCONFIG_UACCESS_WITH_MEMCPY=yCONFIG_ZBOOT_ROM_TEXT=0x0CONFIG_ZBOOT_ROM_BSS=0x0CONFIG_ARM_APPENDED_DTB=yCONFIG_ARM_ATAG_DTB_COMPAT=yCONFIG_CMDLINE=""CONFIG_KEXEC=yCONFIG_ATAGS_PROC=yCONFIG_FPE_NWFPE=yCONFIG_MACH_D2NET_V2=yCONFIG_MACH_DOCKSTAR=yCONFIG_MACH_ESATA_SHEEVAPLUG=yCONFIG_MACH_GURUPLUG=yCONFIG_MACH_INETSPACE_V2=yCONFIG_MACH_MV88F6281GTW_GE=yCONFIG_MACH_NET2BIG_V2=yCONFIG_MACH_NET5BIG_V2=yCONFIG_MACH_NETSPACE_MAX_V2=yCONFIG_MACH_NETSPACE_V2=yCONFIG_MACH_OPENRD_BASE=yCONFIG_MACH_OPENRD_CLIENT=yCONFIG_MACH_OPENRD_ULTIMATE=yCONFIG_MACH_RD88F6192_NAS=yCONFIG_MACH_RD88F6281=yCONFIG_MACH_SHEEVAPLUG=yCONFIG_MACH_T5325=yCONFIG_MACH_TS219=yCONFIG_MACH_TS41X=yCONFIG_ARCH_KIRKWOOD_DT=yCONFIG_MACH_DLINK_KIRKWOOD_DT=yCONFIG_MACH_DOCKSTAR_DT=yCONFIG_MACH_DREAMPLUG_DT=yCONFIG_MACH_GOFLEXNET_DT=yCONFIG_MACH_GURUPLUG_DT=yCONFIG_MACH_IB62X0_DT=yCONFIG_MACH_ICONNECT_DT=yCONFIG_MACH_INETSPACE_V2_DT=yCONFIG_MACH_IOMEGA_IX2_200_DT=yCONFIG_MACH_KM_KIRKWOOD_DT=yCONFIG_MACH_LSXL_DT=yCONFIG_MACH_MPLCEC4_DT=yCONFIG_MACH_NETSPACE_LITE_V2_DT=yCONFIG_MACH_NETSPACE_MAX_V2_DT=yCONFIG_MACH_NETSPACE_MINI_V2_DT=yCONFIG_MACH_NETSPACE_V2_DT=yCONFIG_MACH_OPENBLOCKS_A6_DT=yCONFIG_MACH_TOPKICK_DT=yCONFIG_MACH_TS219_DT=yCONFIG_ARM_THUMB=yCONFIG_ACORN_PARTITION=yCONFIG_ACORN_PARTITION_ICS=yCONFIG_ACORN_PARTITION_RISCIX=yCONFIG_OSF_PARTITION=yCONFIG_AMIGA_PARTITION=yCONFIG_ATARI_PARTITION=yCONFIG_MAC_PARTITION=yCONFIG_BSD_DISKLABEL=yCONFIG_MINIX_SUBPARTITION=yCONFIG_SOLARIS_X86_PARTITION=yCONFIG_UNIXWARE_DISKLABEL=yCONFIG_LDM_PARTITION=yCONFIG_SGI_PARTITION=yCONFIG_ULTRIX_PARTITION=yCONFIG_SUN_PARTITION=yCONFIG_ATA=mCONFIG_SATA_AHCI=mCONFIG_ATA_SFF=yCONFIG_SATA_MV=mCONFIG_BT_HCIBCM203X=mCONFIG_BT_HCIBPA10X=mCONFIG_BT_HCIBFUSB=mCONFIG_BT_HCIVHCI=mCONFIG_CPU_IDLE=yCONFIG_CRYPTO_DEV_MV_CESA=mCONFIG_DMADEVICES=yCONFIG_MV_XOR=yCONFIG_GPIO_SYSFS=yCONFIG_SENSORS_GPIO_FAN=mCONFIG_I2C=yCONFIG_I2C_CHARDEV=yCONFIG_I2C_MV64XXX=yCONFIG_GAMEPORT=mCONFIG_INPUT_JOYSTICK=yCONFIG_KEYBOARD_GPIO=mCONFIG_INPUT_TOUCHSCREEN=yCONFIG_ISDN=yCONFIG_ISDN_CAPI=mCONFIG_ISDN_DRV_AVMB1_VERBOSE_REASON=yCONFIG_ISDN_CAPI_MIDDLEWARE=yCONFIG_ISDN_CAPI_CAPI20=mCONFIG_ISDN_CAPI_CAPIDRV=mCONFIG_CAPI_AVM=yCONFIG_ISDN_DRV_AVMB1_B1PCI=mCONFIG_ISDN_DRV_AVMB1_B1PCIV4=yCONFIG_ISDN_DRV_AVMB1_B1PCMCIA=mCONFIG_ISDN_DRV_AVMB1_AVM_CS=mCONFIG_ISDN_DRV_AVMB1_T1PCI=mCONFIG_ISDN_DRV_AVMB1_C4=mCONFIG_CAPI_EICON=yCONFIG_ISDN_DIVAS=mCONFIG_ISDN_DIVAS_BRIPCI=yCONFIG_ISDN_DIVAS_PRIPCI=yCONFIG_ISDN_DIVAS_DIVACAPI=mCONFIG_ISDN_DIVAS_USERIDI=mCONFIG_ISDN_DIVAS_MAINT=mCONFIG_LEDS_GPIO=yCONFIG_LEDS_NS2=mCONFIG_LEDS_NETXBIG=mCONFIG_LEDS_TRIGGER_TIMER=yCONFIG_LEDS_TRIGGER_DEFAULT_ON=yCONFIG_MMC=mCONFIG_MMC_BLOCK=mCONFIG_MMC_MVSDIO=mCONFIG_MTD=yCONFIG_MTD_CMDLINE_PARTS=yCONFIG_MTD_OF_PARTS=yCONFIG_MTD_BLOCK=yCONFIG_FTL=mCONFIG_NFTL=mCONFIG_MTD_CFI=yCONFIG_MTD_JEDECPROBE=yCONFIG_MTD_CFI_ADV_OPTIONS=yCONFIG_MTD_CFI_NOSWAP=yCONFIG_MTD_CFI_GEOMETRY=yCONFIG_MTD_MAP_BANK_WIDTH_1=yCONFIG_MTD_MAP_BANK_WIDTH_2=yCONFIG_MTD_MAP_BANK_WIDTH_4=yCONFIG_MTD_CFI_I1=yCONFIG_MTD_CFI_I2=yCONFIG_MTD_CFI_I4=yCONFIG_MTD_CFI_INTELEXT=yCONFIG_MTD_CFI_AMDSTD=mCONFIG_MTD_CFI_STAA=mCONFIG_MTD_M25P80=yCONFIG_MTD_PHYSMAP_OF=yCONFIG_MTD_NAND=yCONFIG_MTD_NAND_ORION=yCONFIG_MTD_UBI=yCONFIG_MV643XX_ETH=mCONFIG_MVMDIO=mCONFIG_MWIFIEX=mCONFIG_MWIFIEX_SDIO=mCONFIG_PROC_DEVICETREE=yCONFIG_POWER_RESET_QNAP=yCONFIG_POWER_RESET_RESTART=yCONFIG_RTC_DRV_S35390A=yCONFIG_RTC_DRV_MV=yCONFIG_SPI_ORION=yCONFIG_FB_XGI=mCONFIG_KIRKWOOD_THERMAL=mCONFIG_SERIAL_OF_PLATFORM=yCONFIG_SERIAL_8250=yCONFIG_SERIAL_8250_CONSOLE=yCONFIG_SERIAL_8250_NR_UARTS=4CONFIG_SERIAL_8250_RUNTIME_UARTS=2CONFIG_USB_SUPPORT=yCONFIG_USB=mCONFIG_USB_ATM=mCONFIG_USB_SPEEDTOUCH=mCONFIG_USB_EHCI_HCD=mCONFIG_USB_EHCI_HCD_ORION=yCONFIG_USB_OHCI_HCD=mCONFIG_USB_UHCI_HCD=mCONFIG_USB_SL811_HCD=mCONFIG_FB=mCONFIG_FRAMEBUFFER_CONSOLE=mCONFIG_ORION_WATCHDOG=mCONFIG_BINFMT_AOUT=mCONFIG_JFFS2_FS=yCONFIG_UBIFS_FS=yCONFIG_CC_OPTIMIZE_FOR_SIZE=yCONFIG_FLATMEM_MANUAL=yCONFIG_ATM=mCONFIG_HAMRADIO=yCONFIG_AX25=mCONFIG_NETROM=mCONFIG_ROSE=mCONFIG_SND_SOC=mCONFIG_SND_KIRKWOOD_SOC=mCONFIG_SND_KIRKWOOD_SOC_OPENRD=mCONFIG_SND_KIRKWOOD_SOC_T5325=mCONFIG_MACH_DB88F6281_BP=y
Is there something I can tweak in this config to make all memory usable or any other way to solve this? I can test new kernels, I have a working serial console cable installed in the TS-221.
Thanks,
Jurriaan
Quoted 17 lines · Jurriaan
I updated my Qnap TS-212 with 256 Mb memory to a new TS-221 with 1 Gb memory.
On booting, I see that a large chunk of that new memory is not used by linux:
[ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Initializing cgroup subsys cpuset [ 0.000000] Initializing cgroup subsys cpu [ 0.000000] Initializing cgroup subsys cpuacct [ 0.000000] Linux version 3.14-2-kirkwood ([email protected]) (gcc version 4.8.3 (Debian 4.8.3-7) ) #1 Debian 3.14.15-2 (2014-08-09) [ 0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=00053977 [ 0.000000] CPU: VIVT data cache, VIVT instruction cache [ 0.000000] Machine: QNAP TS-119/TS-219 [ 0.000000] Ignoring unrecognised tag 0x41000403 [ 0.000000] Truncating RAM at 20000000-3fffffff to -2f7fffff (vmalloc region overlap).
Quoted 1 line
Whoops!
You can either enable highmem (which has been available on ARM for ages now, there's little excuse not to use it) or reduce the available userspace virtual memory by enabling VMSPLIT_2G.
Signature · 2 lines
FTTC broadband for 0.8mile line: currently at 9.5Mbps down 400kbps up according to speedtest.net.
From: Russell King - ARM Linux <[email protected]>
Date: Sat, Sep 06, 2014 at 07:29:16PM +0100
Quoted 18 lines · Jurriaan
Quoted 17 lines
I updated my Qnap TS-212 with 256 Mb memory to a new TS-221 with 1 Gb memory.
On booting, I see that a large chunk of that new memory is not used by linux:
[ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Initializing cgroup subsys cpuset [ 0.000000] Initializing cgroup subsys cpu [ 0.000000] Initializing cgroup subsys cpuacct [ 0.000000] Linux version 3.14-2-kirkwood ([email protected]) (gcc version 4.8.3 (Debian 4.8.3-7) ) #1 Debian 3.14.15-2 (2014-08-09) [ 0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=00053977 [ 0.000000] CPU: VIVT data cache, VIVT instruction cache [ 0.000000] Machine: QNAP TS-119/TS-219 [ 0.000000] Ignoring unrecognised tag 0x41000403 [ 0.000000] Truncating RAM at 20000000-3fffffff to -2f7fffff (vmalloc region overlap).
Quoted 6 lines
Quoted 1 line
Whoops!
You can either enable highmem (which has been available on ARM for ages now, there's little excuse not to use it) or reduce the available userspace virtual memory by enabling
VMSPLIT_2G.
Thanks, CONFIG_HIGHMEM=y did the trick:
[ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Initializing cgroup subsys cpuset [ 0.000000] Initializing cgroup subsys cpu [ 0.000000] Initializing cgroup subsys cpuacct [ 0.000000] Linux version 3.14.15-kirkwood (root@qnap) (gcc version 4.9.1 (Debian 4.9.1-12) ) #1 Sun Sep 7 12:36:56 CEST 2014 [ 0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=00053977 [ 0.000000] CPU: VIVT data cache, VIVT instruction cache [ 0.000000] Machine: QNAP TS-119/TS-219 [ 0.000000] Ignoring unrecognised tag 0x41000403 [ 0.000000] Memory policy: Data cache writeback [ 0.000000] On node 0 totalpages: 262144 [ 0.000000] free_area_init_node: node 0, pgdat c05a78b4, node_mem_map eeffa000 [ 0.000000] DMA zone: 1520 pages used for memmap [ 0.000000] DMA zone: 0 pages reserved [ 0.000000] DMA zone: 194560 pages, LIFO batch:31 [ 0.000000] HighMem zone: 528 pages used for memmap [ 0.000000] HighMem zone: 67584 pages, LIFO batch:15 [ 0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768 [ 0.000000] pcpu-alloc: [0] 0 [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 260624 [ 0.000000] Kernel command line: console=ttyS0,115200 root=/dev/ram initrd=0xa00000,0x900000 ramdisk=34816 [ 0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes) [ 0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) [ 0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) [ 0.000000] Memory: 1024056K/1048576K available (3849K kernel code, 353K rwdata, 1396K rodata, 202K init, 428K bss, 24520K reserved, 270336K highmem) [ 0.000000] Virtual kernel memory layout: [ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB) [ 0.000000] fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB) [ 0.000000] vmalloc : 0xf0000000 - 0xff000000 ( 240 MB) [ 0.000000] lowmem : 0xc0000000 - 0xef800000 ( 760 MB) [ 0.000000] pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB) [ 0.000000] modules : 0xbf000000 - 0xbfe00000 ( 14 MB) [ 0.000000] .text : 0xc0008000 - 0xc05278a4 (5247 kB) [ 0.000000] .init : 0xc0528000 - 0xc055aa1c ( 203 kB) [ 0.000000] .data : 0xc055c000 - 0xc05b4448 ( 354 kB) [ 0.000000] .bss : 0xc05b4448 - 0xc061f5e4 ( 429 kB) [ 0.000000] NR_IRQS:114
Kind regards,
Jurriaan