Did the limits for RAM on Home edition get changed with SFOS 16.05.2 MR2? I'm only seeing 4GB after update. Still only showing 4GB after rolling back to SFOS 16.05.1 MR-1. I was seeing 6GB usable before upgrade.
Mine's brand new and i ran clean across 2 full passes in memtest. I always run memory/stability tests before relying on a new system.
And as i mentioned booting the system to any other linux distro shows 8G of ram. Bios shows 8 G of ram. dmidecode shows 2 x 4G.
My only guess would be something in the kernel changed how it deals with memory. it's basically like i don't even have a second stick of memory.
Was there a kernel update between 16.05-MR1 and MR2? Does it fall back to a previous kernel if you tell it to use MR1 again or is that only switch the userland OS
Maybe the kernel can't map the second dimm due to the ram=6G, but that's only a guess.
Has anyone using a single 8G dimm reported the same issue?
Just in case it's CI323 related mine's brand new barebones from newegg, I installed memory and SSD.
Memory: https://www.newegg.com/Product/Product.aspx?Item=N82E16820191523
SSD: https://www.newegg.com/Product/Product.aspx?Item=N82E16820173150
CI323: https://www.newegg.com/Product/Product.aspx?Item=N82E16856173128
The bios version is below
# dmidecode | grep Version: | head -1
Version: B301P019
I am running this on Zotac ZBOX CI320 nano
Processor Intel N3150 quad-core 1.6GHz, up to 2.08GHz
Chipset Intel
System Memory 2 x 4GB 204-pin DDR3L-1600 SO-DIMM - 8GB
Graphics Engine Intel HD Graphics
Video Output HDMI, DisplayPort, VGA
60GB SSD
Sophos Firmware Version SFOS 16.05.2 MR-2
console> system diagnostics show memory
MemTotal: 3967252 kB
MemFree: 499704 kB
MemAvailable: 1649264 kB
Buffers: 235264 kB
Cached: 958352 kB
SwapCached: 0 kB
Active: 2937140 kB
Inactive: 325828 kB
Active(anon): 2121120 kB
Inactive(anon): 41352 kB
Active(file): 816020 kB
Inactive(file): 284476 kB
Unevictable: 0 kB
Mlocked: 0 kB
SwapTotal: 1993256 kB
SwapFree: 1993256 kB
Dirty: 812 kB
Writeback: 0 kB
AnonPages: 2069028 kB
Mapped: 136532 kB
Shmem: 93444 kB
Slab: 129392 kB
SReclaimable: 78884 kB
SUnreclaim: 50508 kB
KernelStack: 4976 kB
PageTables: 20220 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
WritebackTmp: 0 kB
CommitLimit: 3976880 kB
Committed_AS: 4840900 kB
VmallocTotal: 34359738367 kB
VmallocUsed: 5700 kB
VmallocChunk: 34359695108 kB
DirectMap4k: 9220 kB
DirectMap2M: 4106240 kB
console>
================================
console> system diagnostics show cpu
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 76
model name : Intel(R) Celeron(R) CPU N3150 @ 1.60GHz
stepping : 3
microcode : 0x34f
cpu MHz : 1599.956
cache size : 1024 KB
physical id : 0
siblings : 4
core id : 0
cpu cores : 4
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 11
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes rdrand lahf_lm 3dnowprefetch ida arat epb dtherm tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms
bogomips : 3199.91
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
processor : 1
vendor_id : GenuineIntel
cpu family : 6
model : 76
model name : Intel(R) Celeron(R) CPU N3150 @ 1.60GHz
stepping : 3
microcode : 0x34f
cpu MHz : 1599.956
cache size : 1024 KB
physical id : 0
siblings : 4
core id : 1
cpu cores : 4
apicid : 2
initial apicid : 2
fpu : yes
fpu_exception : yes
cpuid level : 11
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes rdrand lahf_lm 3dnowprefetch ida arat epb dtherm tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms
bogomips : 3199.91
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
processor : 2
vendor_id : GenuineIntel
cpu family : 6
model : 76
model name : Intel(R) Celeron(R) CPU N3150 @ 1.60GHz
stepping : 3
microcode : 0x34f
cpu MHz : 1599.956
cache size : 1024 KB
physical id : 0
siblings : 4
core id : 2
cpu cores : 4
apicid : 4
initial apicid : 4
fpu : yes
fpu_exception : yes
cpuid level : 11
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes rdrand lahf_lm 3dnowprefetch ida arat epb dtherm tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms
bogomips : 3199.91
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
processor : 3
vendor_id : GenuineIntel
cpu family : 6
model : 76
model name : Intel(R) Celeron(R) CPU N3150 @ 1.60GHz
stepping : 3
microcode : 0x34f
cpu MHz : 1599.956
cache size : 1024 KB
physical id : 0
siblings : 4
core id : 3
cpu cores : 4
apicid : 6
initial apicid : 6
fpu : yes
fpu_exception : yes
cpuid level : 11
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes rdrand lahf_lm 3dnowprefetch ida arat epb dtherm tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms
bogomips : 3199.91
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
console>
Kevin Brierly said:Has anyone using a single 8G dimm reported the same issue?
Yes ... see previous post here.
Single 8GB and seeing same issue.
I dug thru my syslog.log and grabbed memory and kernel command line across all boots since initial install
It did see 8G before the mem=6G was added to boot options even on the MR-2 kernel.
You can also see my attempt to go back to MR-1 to no avail on getting back 6-8G, but the mem=6G option is there.
The timestamp on my license file is Mar 8th 14:21 if that helps at all
Also i looked up the mem= kernel option. This MIGHT be a physical address space collision.
I personally believe this is directly tied to the addition of the mem=6G on people with certain hardware.
mem=nn[KMG] [KNL,BOOT] Force usage of a specific amount of memory
Amount of memory to be used when the kernel is not able
to see the whole system memory or for test.
[X86] Work as limiting max address. Use together
with memmap= to avoid physical address space collisions.
Without memmap= PCI devices could be placed at addresses
belonging to unused RAM.
Mar 8 20:05:28 (none) user.info kernel: [ 0.000000] Command line: auto BOOT_IMAGE=16_05_1139 zd=/dev/sda ro ro quiet console=tty0 console=ttyS0,38400n8 ZD=80 SM=0Mar 8 20:05:28 (none) user.warn kernel: [ 0.000000] Memory: 8075208K/8296108K available (5864K kernel code, 812K rwdata, 2152K rodata, 1336K init, 564K bss, 220900K reserved)Mar 8 20:23:45 (none) user.info kernel: [ 0.000000] Command line: auto BOOT_IMAGE=16_05_1139 zd=/dev/sda ro ro quiet console=tty0 console=ttyS0,38400n8 ZD=80 SM=0Mar 8 20:23:45 (none) user.warn kernel: [ 0.000000] Memory: 8075208K/8296108K available (5864K kernel code, 812K rwdata, 2152K rodata, 1336K init, 564K bss, 220900K reserved)Mar 8 14:29:43 (none) user.info kernel: [ 0.000000] Command line: auto BOOT_IMAGE=16_05_1139 zd=/dev/sda ro ro quiet console=tty0 console=ttyS0,38400n8 ZD=80 SM=0Mar 8 14:29:43 (none) user.warn kernel: [ 0.000000] Memory: 8075208K/8296108K available (5864K kernel code, 812K rwdata, 2152K rodata, 1336K init, 564K bss, 220900K reserved)Mar 8 14:40:16 (none) user.info kernel: [ 0.000000] Command line: auto BOOT_IMAGE=16_05_2160 zd=/dev/sda ro ro quiet console=tty0 console=ttyS0,38400n8 ZD=80 SM=0Mar 8 14:40:16 (none) user.warn kernel: [ 0.000000] Memory: 8075208K/8296108K available (5864K kernel code, 812K rwdata, 2152K rodata, 1336K init, 564K bss, 220900K reserved)Mar 8 14:42:55 (none) user.info kernel: [ 0.000000] Command line: auto BOOT_IMAGE=16_05_2160 zd=/dev/sda ro ro quiet console=tty0 console=ttyS0,38400n8 ZD=80 SM=0Mar 8 14:42:55 (none) user.warn kernel: [ 0.000000] Memory: 8075208K/8296108K available (5864K kernel code, 812K rwdata, 2152K rodata, 1336K init, 564K bss, 220900K reserved)Mar 8 14:44:07 (none) user.info kernel: [ 0.000000] Command line: auto BOOT_IMAGE=16_05_2160 console=tty0 console=ttyS0,38400n8 quiet maxcpus=4 mem=6G ZD=80 SM=0Mar 8 14:44:07 (none) user.warn kernel: [ 0.000000] Memory: 3952648K/4101804K available (5864K kernel code, 812K rwdata, 2152K rodata, 1336K init, 564K bss, 149156K reserved)Mar 8 17:35:56 (none) user.info kernel: [ 0.000000] Command line: auto BOOT_IMAGE=16_05_2160 console=tty0 console=ttyS0,38400n8 quiet maxcpus=4 mem=6G ZD=80 SM=0Mar 8 17:35:56 (none) user.warn kernel: [ 0.000000] Memory: 3952648K/4101804K available (5864K kernel code, 812K rwdata, 2152K rodata, 1336K init, 564K bss, 149156K reserved)Mar 8 17:38:43 (none) user.info kernel: [ 0.000000] Command line: auto BOOT_IMAGE=16_05_2160 console=tty0 console=ttyS0,38400n8 quiet maxcpus=4 mem=6G ZD=80 SM=0Mar 8 17:38:43 (none) user.warn kernel: [ 0.000000] Memory: 3952648K/4101804K available (5864K kernel code, 812K rwdata, 2152K rodata, 1336K init, 564K bss, 149156K reserved)Mar 8 20:02:51 (none) user.info kernel: [ 0.000000] Command line: auto BOOT_IMAGE=16_05_2160 console=tty0 console=ttyS0,38400n8 quiet maxcpus=4 mem=6G ZD=80 SM=0Mar 8 20:02:51 (none) user.warn kernel: [ 0.000000] Memory: 3952648K/4101804K available (5864K kernel code, 812K rwdata, 2152K rodata, 1336K init, 564K bss, 149156K reserved)Mar 8 20:08:18 (none) user.info kernel: [ 0.000000] Command line: auto BOOT_IMAGE=16_05_1139 console=tty0 console=ttyS0,38400n8 quiet maxcpus=4 mem=6G ZD=80 SM=0Mar 8 20:08:18 (none) user.warn kernel: [ 0.000000] Memory: 3952648K/4101804K available (5864K kernel code, 812K rwdata, 2152K rodata, 1336K init, 564K bss, 149156K reserved)Mar 8 20:12:43 (none) user.info kernel: [ 0.000000] Command line: auto BOOT_IMAGE=16_05_2160 console=tty0 console=ttyS0,38400n8 quiet maxcpus=4 mem=6G ZD=80 SM=0Mar 8 20:12:44 (none) user.warn kernel: [ 0.000000] Memory: 3952648K/4101804K available (5864K kernel code, 812K rwdata, 2152K rodata, 1336K init, 564K bss, 149156K reserved)
I also think it being an pci device collision could explain why some are seeing different amounts of available memory than others.
It would depends on where the PCI devices map into the system at.
^^^THISDavidWilliams1 said:Just to put it out there ...
This has all the symptoms of a licensing issue.
Given that the problem remains after rolling back to MR-1. It doesn't appear to be in the OS. It smells like the licenses were modified, 'downgraded', upon applying the MR-2 update.
Not everyone's memory sticks go bad suddenly as soon as they updated. Sachin usually gives sound advice but running memory tests or changing ram sticks where one is 4GB and other is 2GB is frankly absurd.
Do a configuration backup. Try to do a fresh install and use the free 30 day license with a new account. It will more than likely show full memory. Install your home license and see if the memory drops. If it does, licensing is bad... if it doesn't, import your current backup, if the memory drops, MR2 configuration is bad. If everything still works then XG engineers have no idea what they are doing as usual.
Ofcourse we shouldn't have to go through all these hoops to prove to sophos that their code was changed somewhere by someone[:#]
Check my previous post with the syslog kernel command lines and memory. It pretty much proves to me that what is doing this is the mem=6G option that was added to the kernel options.
Going back to MR1 didn't work because the mem=6G option was still present on that boot.
So yes it is a "licensing" issue in the fact that they are trying to limit home users to 6G, The problem is that somehow that memory limit is causing the kernel to map out large chunks of memory that were previously available without the mem=6G
Is that option mem=6G on 16.01.x firmwares? I'll try and do an install to see if no ones checked yet.