Why lsdev and lscfg shows only 0 MB Memory!
Ali Albayrak
lsdev and lsconfig both say that my 43P has 0 MB of memory:
% lscfg -lmem0
DEVICE LOCATION DESCRIPTION
mem0 00-00 Memory
% lsdev -Ccmemory
mem0 Available 00-00 Memory
L2cache0 Available 00-00 L2 Cache
However bootinfo gives correct value:
% bootinfo -r
65536
Can anyone explain this? Machine has AIX 4 installed.
-Ali-
--
Ali Albayrak <a...@elma.fi>
ELMA OY - Electronic Trading http://www.elma.fi/
tel(direct): +358 0 47855613 tel(mobile): +358 40 5116160
tel(center): +358 0 478555 fax: +358 0 47855600
kke...@austin.ibm.com
"lsattr -El mem0" will show the total amount of memory like the
bootinfo command.
In article <31466E98...@caldera.com>, Kevin Gee <ge...@caldera.com> writes:
> Ali Albayrak wrote:
> >
> > Hi,
> > lsdev and lsconfig both say that my 43P has 0 MB of memory:
> > % lscfg -lmem0
> > DEVICE LOCATION DESCRIPTION
> >
> > mem0 00-00 Memory
> > % lsdev -Ccmemory
> > mem0 Available 00-00 Memory
> > L2cache0 Available 00-00 L2 Cache
> >
> > However bootinfo gives correct value:
> > % bootinfo -r
> > 65536
> >
> > Can anyone explain this? Machine has AIX 4 installed.
>
> First of all, neither of these commands is saying that you have 0Mb
> of memory; 00-00 is an address (i.e., the planar). Certain models
> at AIX 4.1.* have a slightly modified Predefined Object Database, if
> I remember my days at IBM correctly (no, I'm not speaking for them
> in any way). Simply put, the system just isn't going to tell you
> on that model what amount of memory each memory card has. That is
> a lot different from saying that it has 0Mb.
>
> Plus, now at 4.1.* the system will at least tell you if you have
> L2cache or not, something that was a bit more difficult at 3.2.*.
>
> --
> Kevin R. Gee
> ge...@caldera.com ge...@byu.edu
> I do not, repeat DO NOT, speak for AIX Support Family.
--
Kevin Kehne
RiscSystem 6000 Product Engineering
(512)-838-7847
Inet : kke...@austin.ibm.com
Curt Finch 4138005
> mem0 00-00 Memory
> % lsdev -Ccmemory
> mem0 Available 00-00 Memory
> Can anyone explain this? Machine has AIX 4 installed.
for whatever reason on that box you don't get as useful an answer
from lsdev. so now i use this, which works everywhere:
lsattr -El sys0 -a realmem
--
Curt Finch - The Kernel Group Inc. - cu...@tkg.com - (512)413-8005
- Find memory bugs even in stripped AIX binaries with a 7 day -
- FREE Evaluation of ZeroFault at ... http://www.tkg.com/ -
Peter Kinev
Well Curt,
there are few compelling reasons for this misbehavior.
They are as following,
1. missing entry for the "setno" 1 "msgno" 55 in the device.cat for
the new type "totmem". (Real "bug").
2. old ambiguity with definition of parent-child device relations,
see definition for two descriptors, "connwhere" and "location"
in Customized Devices Object Class. If we will try to be consistent
through all types of machine, then it should look like that,
"mem0 Available 00-0M XXXXXXXXXXXXXXXXX"
"L2cache0 Available 00-0L XXXXXXXXXXXXXXXXX"
with definition for these devices in CuDv as following,
"CuDv:
name = "mem0"
status = 1
chgstatus = 2
ddins = ""
location = "00-00"
parent = "sysplanar0"
connwhere = "M"
PdDvLn = "memory/sys/totmem"
CuDv:
name = "L2cache0"
status = 1
chgstatus = 2
ddins = ""
location = "00-00"
parent = "sysplanar0"
connwhere = "L"
PdDvLn = "memory/sys/L2cache_rspc"".
The similar entry in different type of machine with different type
of memory indeed displays a location code different from "00-00".
It includes a memory on the board, as well as on the card.
3. The missing info on VPD for whatever reason. It's true not only
for the memory, now it includes many other resources, check it
with "lscfg -v".
You may consult a source code. I suspect "bug" there too.
Regardless, missed VPD information will represent some
serious inconvenience in new hardware/EC/microcode maintenance.
And last thing, use "lsattr -l mem0 (or L2cache0) -E" to display
attribute info for the specific data object.
Regards,
Peter.
Ron Bremer
>Ali Albayrak wrote:
>> mem0 00-00 Memory
>> % lsdev -Ccmemory
>> mem0 Available 00-00 Memory
>>
>> Can anyone explain this? Machine has AIX 4 installed.
>
>for whatever reason on that box you don't get as useful an answer
>from lsdev. so now i use this, which works everywhere:
>
> lsattr -El sys0 -a realmem
On the newer RS/6000s with the PCI/ISA bus, AIX cannot determine the size
of the memory SIMMs during the configuration process on startup, since
they are on the system board like a PC. The "lsdev" command only reports
that there is memory present, not the particular memory SIMM (by way of
it's size).
The "classic" RS/6000s, which have a Normal/Secure/Service key, do not
display this characteristic since the actual memory card(s) installed in
the machine are detected by AIX during the configuration phase of the
bootup process.
--
==========================================================================
Ron Bremer Email Address:
Carlisle, Ontario, Canada a750...@mcmail.mcmaster.ca
==========================================================================