Bug 21924

Summary: kernel does not record correct installed memory when increasing memory size on motherboard
Product: Mageia Reporter: Christian C <bugzzzz>
Component: RPM PackagesAssignee: Kernel and Drivers maintainers <kernel>
Status: RESOLVED OLD QA Contact:
Severity: normal    
Priority: Normal CC: marja11, ouaurelien, tmb
Version: 6   
Target Milestone: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Source RPM: kernel-desktop-4.9.50-1.mga6-1-1.mga6.x86_64.rpm CVE:
Status comment:
Attachments: /var/log/dmesg file
Result of command "dmidecode >dmidecode.bug21924"

Description Christian C 2017-10-23 18:40:48 CEST
Description of problem:
I installed mageia-6 on a MS-7358 MSI motherboard.
The initial memory configuration was :
1 module 1024M DDR2 PC5300
1 module 1024M DDR2 PC5300
1 module 512M DDR2 PC5300
1 module 512M DDR2 PC5300
So I had 3GB of memory available.

Later, I replaced the two 512M modules by two 2048M modules to get 6GB of memory available.
After a check of the memory configuration, I note that the available memory is still 3327624K/3405996K (see dmesg file attached).
But a check with harddrake shows the correct hardware configuration not taken into account by the kernel :
1 module 1024M DDR2 PC5300
1 module 1024M DDR2 PC5300
1 module 2048M DDR2 PC5300
1 module 2048M DDR2 PC5300

A check in the BIOS reveals that the new configuration (above) is correctly detected.

Version-Release number of selected component (if applicable):


How reproducible:
At each boot

Steps to Reproduce:
1. replace two 512M modules by 2048M modules
2. boot and check the memory available in the system
3.
Comment 1 Christian C 2017-10-23 18:44:37 CEST
Created attachment 9749 [details]
/var/log/dmesg file

the /var/log/dmesg file after increasing the memory size on the motherboard
Marja Van Waes 2017-10-24 10:27:12 CEST

CC: (none) => marja11
Assignee: bugsquad => kernel

Comment 2 Marja Van Waes 2017-10-27 19:58:54 CEST
Mass-change status to NEW for all bugs that were filed as UNCONFIRMED between October 9 and now, and that still have that status now.

From now on all newly filed bugs will have the NEW status again, like before, regardless of who files the report.

Status: UNCONFIRMED => NEW
Ever confirmed: 0 => 1

Comment 3 Thomas Backlund 2017-11-01 09:35:04 CET
Can you attach the file dmidecode.bug21924

from the command (as root):

dmidecode >dmidecode.bug21924

CC: (none) => tmb

Comment 4 Christian C 2017-11-01 16:44:01 CET
Created attachment 9770 [details]
Result of command "dmidecode >dmidecode.bug21924"
Comment 5 Christian C 2017-12-26 19:27:28 CET
Any idea how to fix it ?
I really need more memory on this computer.
Comment 6 Marja Van Waes 2017-12-27 08:50:43 CET
(In reply to Christian CHEVALIER from comment #5)
> Any idea how to fix it ?
> I really need more memory on this computer.

This thread:
https://bbs.archlinux.org/viewtopic.php?id=126170
("[SOLVED] Full Amount of RAM Not Detected")
contains some suggestions you could try.
The suggestion that worked for the reporter, was to re-insert his memory:
https://bbs.archlinux.org/viewtopic.php?pid=989803#p989803
Comment 7 Aurelien Oudelet 2020-08-14 16:15:12 CEST
This message is a reminder that Mageia 6 is end of life.

Mageia stopped maintaining and issuing updates for Mageia 6. At that time this bug will be closed as OLD (EOL).

Package Maintainer: If you wish for this bug to remain open because you plan to 
fix it in a currently maintained version, simply change the 'version' to a later 
Mageia version prior to Mageia 6's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we cannot 
be able to fix it before Mageia 6 was end of life.
If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia.

Although we aim to fix as many bugs as possible during every release's lifetime, 
sometimes those efforts are overtaken by events. Often a more recent Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

--
Mageia Bugsquad

CC: (none) => ouaurelien
Status: NEW => RESOLVED
Resolution: (none) => OLD