Bug #1714
memory not reported on solaris 10
| Status: | Resolved | Start date: | 07/03/2012 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 100% | |
| Category: | solaris | |||
| Target version: | 2.3.0 | |||
| For junior contributor: | No |
Description
Hi
On solaris 10u8 SPARC, memory is not reported (screenshot in attachment)
perl/bin/memconf
hostname: RQB00019
Sun Microsystems, Inc. Sun Fire 480R (4 X UltraSPARC-III+ 900MHz)
Logical Logical Logical
MC Bank Bank Bank DIMM Interleave Interleaved
Brd ID num size Status Size Factor with
--- --- ---- ------ ----------- ------ ---------- -----------
A 0 0 512MB no_status 256MB 8-way 0
A 0 1 512MB no_status 256MB 8-way 0
A 0 2 512MB no_status 256MB 8-way 0
A 0 3 512MB no_status 256MB 8-way 0
A 2 0 512MB no_status 256MB 8-way 0
A 2 1 512MB no_status 256MB 8-way 0
A 2 2 512MB no_status 256MB 8-way 0
A 2 3 512MB no_status 256MB 8-way 0
B 1 0 512MB no_status 256MB 8-way 1
B 1 1 512MB no_status 256MB 8-way 1
B 1 2 512MB no_status 256MB 8-way 1
B 1 3 512MB no_status 256MB 8-way 1
B 3 0 512MB no_status 256MB 8-way 1
B 3 1 512MB no_status 256MB 8-way 1
B 3 2 512MB no_status 256MB 8-way 1
B 3 3 512MB no_status 256MB 8-way 1
empty groups: None
total memory = 8192MB (8GB)
Associated revisions
History
#1
Updated by Gonéri Le Bouder 11 months ago
- Status changed from New to Feedback
Hi Nicolas,
What does this command return?
uname -i
#4
Updated by Gonéri Le Bouder 10 months ago
- Status changed from Feedback to In Progress
No, not yet. Sorry.
#7
Updated by Nico LAS 10 months ago
- Status changed from In Progress to Resolved
- % Done changed from 0 to 100
Applied in changeset 102ae407ed6a7711eae08ab7f3652c42036c5f1b.
#8
Updated by Gonéri Le Bouder 10 months ago
- Target version set to 2.3.0
#10
Updated by Gonéri Le Bouder 10 months ago
I did a test for class1, we need to extend the test-suite to cover the other cases too. Do you have such hardware?
#14
Updated by Gonéri Le Bouder 10 months ago
I'm not sure I understand. Is there anything to adjust with the current module?
#15
Updated by Nico LAS 10 months ago
this is a second bug i found in Memory.pm
the bug is : Sun-Fire-V490 is classified on SOLARIS_FIRE_V but this memconf output is like SOLARIS_FIRE
so if machine is a Sun-Fire-V490 we have to launch _getMemories1 instead of _getMemories2
do you prefer one bug report per case of Memory.pm bug?
#16
Updated by Gonéri Le Bouder 10 months ago
Oh ok, can you please open a new bug report and attach the lines than need to be changes?
#18
Updated by Nico LAS 4 months ago
Applied in changeset 102ae407ed6a7711eae08ab7f3652c42036c5f1b.