- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- HPE 9000 and HPE e3000 Servers
- >
- L2000 Memory
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-27-2005 06:35 PM
тАО11-27-2005 06:35 PM
L2000 Memory
I think I followed all the rules. Everything was done in pairs, the HP memory stayed in the low slots (in case I had to pull the Kingston memory), all are 512MB so no size issues. Upon reboot the system went into a panic and the GSP reported many errors, mostly along the lines of:
SOURCE: 7 = memory
SOURCE DETAIL: 6 = physical memory SOURCE ID: 0
PROBLEM DETAIL: B = missing
SOURCE: 7 = memory
SOURCE DETAIL: 6 = physical memory SOURCE ID: FF
PROBLEM DETAIL: A = ECC error
SOURCE: 7 = memory
SOURCE DETAIL: 4 = SIMM or DIMM SOURCE ID: 0
PROBLEM DETAIL: D = control address parity error
PROBLEM DETAIL: 2 = single bit error
(full versions attached)
So I thought I maybe had a bad chip. I tried two Kingston in 4a/4b and had the same issue, tried a different two Kingston in 4a/4b, and so on. I was going to pull the HP memory and try all Kingston but my downtime window is just about up. I could see one, maybe two bad chips, but I find it hard to believe all 8 were DOA.
Am I missing anything? From forum reading I see that people have gotten it to work.
Jim
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-27-2005 08:37 PM
тАО11-27-2005 08:37 PM
Re: L2000 Memory
I think you have a physical memory problem.
Are all the modules wel installed in the slots.
The combination of HP and Kingston memory is possible.
You only receive the following error during boot
One or more on HP DIMS were detected.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-27-2005 10:04 PM
тАО11-27-2005 10:04 PM
Re: L2000 Memory
You have a memory model problem which one it is i can't see you have too look in your log file.
If you have a remote console start the logging. and dump the gsp log. In the gsp/mcp log you can see wich module is going wrong on which slot.
grtz. Mark
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-28-2005 05:43 AM
тАО11-28-2005 05:43 AM
Re: L2000 Memory
What's the PN on the SDRAMs you are using?
What's the PDC and GSP firmware versions?
Are these error are coming for a specific slot ?
What you see in
GSP> CL
GSP> SL > E
BCH> IN > IO
BCH> ME
after installing the new memory?
There is no attachment of the complete GSP log.
I would try with a pair in a slot at a time This is just to verify if the slots are OK. It may be a case where you are trying pairs of new memory in slots 4A/4B and one of them is not OK.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-28-2005 07:16 AM
тАО11-28-2005 07:16 AM
Re: L2000 Memory
The attachement is here this time, although it isn't the whole log as I have no clean way of dumping it. At the end of the log is also a cstm output of my working configuration (without Kingston memory).
I've never had the honor of messing with the BCH, so I don't have any information from it. I will do some reading on that before my next downtime window.
GSP Info: Hardware Revision 8 Firmware Revision A.01.10 May 24 2001,11:05:55 (I'll be upgrading to A.01.12 which I think is the best I can do for this)
System firmware = 44.28 (which I think is the latest)
It appears TG Manikandan had the same problem (same error messages) in: http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=141530 but there was no resolution posted.
The info on the memory is:
Kingston KTH-LSVR/1024 (2x512MB)
PN: 9962326-001B00
So I already had 8x512MB HP chips in 0a/0b thru 3a/3b, and wanted to add 8 Kinston chips to 4a/4b thru 7a/7b.
Jim
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-28-2005 08:20 AM
тАО11-28-2005 08:20 AM
Re: L2000 Memory
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-28-2005 06:41 PM
тАО11-28-2005 06:41 PM
Re: L2000 Memory
For the logging. If you use putty or something like that you can tur on logging.
After that logon the gsp and read the log files. When you read the logfiles al the output is stored in the putty.log file and then you can publish that.
Other question your system is now running without the kingston memory?
grtz. Mark
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-29-2005 05:48 AM
тАО11-29-2005 05:48 AM
Re: L2000 Memory
If you can get past the alert messages and get to BCH (Boot Control Handler, or "Press any key within 10 seconds to interrupt the boot process"), type in the following command without the quotes, "in me" which is INformation MEmory. This will display your memory and show the locations of any problem DIMMS. Hope it helps!
Tim
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-29-2005 03:56 PM
тАО11-29-2005 03:56 PM
Re: L2000 Memory
As per the GSP log, it could be make out as follows
Memory module 6b ( module which was installed at that time ) has "control address parity error".
Memory modules 0a,0b has "ECC error".
Now the log seems to be conflicting because 0a,0b modules (old) are working OK without new memory right? Did you see such "ECC error" earlier for those modules?
If not, I would take out that 6b module and
see what happens. I maybe wrong , but the memory interleaving causing this??
Moreover,I would go through the complete GSP log (from the fist entry to most recent entry)to have more assessment.
As I said before, it is better to try with a pair of modules and a slot pair at a time.
Then looking for GSP logs for errors if any.