HPE 9000 and HPE e3000 Servers
cancel
Showing results for 
Search instead for 
Did you mean: 

L2000 loops in early boot

 
Florian Anwander_1
Occasional Visitor

L2000 loops in early boot

Hello,

I have here a L2000-44, 4 CPU, ~5GB RAM (bought used; I do not know, whether it ever worked). The machine loops in the early boot. The GSP log is like follows (I ask for patience for 145 lines :-) ):

********** VIRTUAL FRONT PANEL **********
System Boot detected
*****************************************
LEDs: RUN ATTENTION FAULT REMOTE POWER
OFF FLASH ON OFF ON
LED State: Boot Failed. Non-critical error detected.
Check Chassis and Console Logs for error messages.



platform config 626F
processor slave rendezvous 1C17
processor slave rendezvous 1C17
processor slave rendezvous 1C17
[...]
processor slave rendezvous 1C10
processor test 1142
PDH test 3158
PDH test 3157
PDH test 316E
PDH test 316E
PDH test 316E
PDH test 316E

***** EARLY BOOT VFP : SYSTEM ALERT *****
SYSTEM NAME: uninitialized
DATE: 09/15/2004 TIME: 21:05:16
ALERT LEVEL: 6 = Boot possible, pending failure - action required

REASON FOR ALERT
SOURCE: 3 = PDH
SOURCE DETAIL: 0 = unknown, no source stated SOURCE ID: 0
PROBLEM DETAIL: 0 = no problem detail

LEDs: RUN ATTENTION FAULT REMOTE POWER
FLASH FLASH ON OFF ON
LED State: Boot Failed. Running non-OS code. Non-critical error detected.
Check Chassis and Console Logs for error messages.

0x0000006030001760 000000FF FF02FF85 - type 0 = Data Field Unused
0x5800086030001760 00006808 0F150510 - type 11 = Timestamp 09/15/2004 21:05:16
A/a: ack read of this entry - Q/q: quit Virtual Front Panel Display
Anything else redisplay the log entry
->Choice:a
*****************************************
PDH test 316E
PDH test 316E

***** EARLY BOOT VFP : SYSTEM ALERT *****
SYSTEM NAME: uninitialized
DATE: 09/15/2004 TIME: 21:05:20
ALERT LEVEL: 6 = Boot possible, pending failure - action required

REASON FOR ALERT
SOURCE: 3 = PDH
SOURCE DETAIL: 0 = unknown, no source stated SOURCE ID: 0
PROBLEM DETAIL: 0 = no problem detail

LEDs: RUN ATTENTION FAULT REMOTE POWER
OFF FLASH ON OFF ON
LED State: Boot Failed. Non-critical error detected.
Check Chassis and Console Logs for error messages.

0x0000006030001760 00FFFFFF FFFFFF67 - type 0 = Data Field Unused
0x5800086030001760 00006808 0F150514 - type 11 = Timestamp 09/15/2004 21:05:20
A/a: ack read of this entry - Q/q: quit Virtual Front Panel Display
Anything else redisplay the log entry
->Choice:a
[...]
PDH test 316E
memory config 7210
memory INIT 7702
memory INIT 771D
memory test 7150
memory config 7213
memory config 7213
...
memory config 7214
memory config 7213
memory config 7213
***** EARLY BOOT VFP : SYSTEM ALERT *****
SYSTEM NAME: uninitialized
DATE: 09/15/2004 TIME: 21:05:49
ALERT LEVEL: 8 = Boot Possible, performance impaired

REASON FOR ALERT
SOURCE: 7 = memory
SOURCE DETAIL: 2 = carrier SOURCE ID: FF
PROBLEM DETAIL: 0 = no problem detail

LEDs: RUN ATTENTION FAULT REMOTE POWER
OFF FLASH ON OFF ON
LED State: Boot Failed. Non-critical error detected.
Check Chassis and Console Logs for error messages.

0x2000008072FF2204 0000FF00 01FFFF72 - type 4 = Physical Location
0x5800088072FF2204 00006808 0F150531 - type 11 = Timestamp 09/15/2004 21:05:49
A/a: ack read of this entry - Q/q: quit Virtual Front Panel Display
Anything else redisplay the log entry
->Choice:a
*****************************************

***** EARLY BOOT VFP : SYSTEM ALERT *****
SYSTEM NAME: uninitialized
DATE: 09/15/2004 TIME: 21:05:49
ALERT LEVEL: 7 = reserved

REASON FOR ALERT
SOURCE: 7 = memory
SOURCE DETAIL: 0 = unknown, no source stated SOURCE ID: FF
PROBLEM DETAIL: 0 = no problem detail

LEDs: RUN ATTENTION FAULT REMOTE POWER
OFF FLASH ON OFF ON
LED State: Boot Failed. Non-critical error detected.
Check Chassis and Console Logs for error messages.

0x7000007070FFAC34 C3818000 00000000 - type 14 = Problem Detail
0x5800087070FFAC34 00006808 0F150531 - type 11 = Timestamp 09/15/2004 21:05:49
A/a: ack read of this entry - Q/q: quit Virtual Front Panel Display
Anything else redisplay the log entry
->Choice:a
*****************************************
memory error handler 7AC4
memory machine check 7612
memory machine check 7612
memory error handler 7AB6
platform unspecified 6000
processor unspecified 1000

[...]
At this point the GSP-output hangs several minutes, and then the output starts from the top.

I appreciate any comment.

kind regards, Florian Anwander
6 REPLIES 6
Jeff Schussele
Honored Contributor

Re: L2000 loops in early boot

Hi Florian,

For no other reason than this, I'd say you have a bad memory DIMM:

REASON FOR ALERT
SOURCE: 7 = memory
SOURCE DETAIL: 2 = carrier SOURCE ID: FF

I'd log a HW call to the RC....

HTH.
Jeff
PERSEVERANCE -- Remember, whatever does not kill you only makes you stronger!
Florian Anwander_1
Occasional Visitor

Re: L2000 loops in early boot

Hi Jeff,

thankyou for the response!

This was my suspicion too. In fact I could boot the machine after removing all RAM but 512 MB.
Do see in the GSP logs any hints which one of the DIMMs this might be?

kind regards, Florian
KCS_1
Respected Contributor

Re: L2000 loops in early boot

Hi,

from above message the following
-------------------------------------


***** EARLY BOOT VFP : SYSTEM ALERT *****
SYSTEM NAME: uninitialized
DATE: 09/15/2004 TIME: 21:05:49
ALERT LEVEL: 8 = Boot Possible, performance impaired

REASON FOR ALERT
SOURCE: 7 = memory
SOURCE DETAIL: 2 = carrier SOURCE ID: FF
PROBLEM DETAIL: 0 = no problem detail

LEDs: RUN ATTENTION FAULT REMOTE POWER
OFF FLASH ON OFF ON
LED State: Boot Failed. Non-critical error detected.
Check Chassis and Console Logs for error messages.

0x2000008072FF2204 0000FF00 01FFFF72 - type 4 = Physical Location
0x5800088072FF2204 00006808 0F150531 - type 11 = Timestamp 09/15/2004 21:05:49
A/a: ack read of this entry - Q/q: quit Virtual Front Panel Display
Anything else redisplay the log entry
->Choice:a


--------------------------------------------

another suspections that memory loading rule falut or mismatched product( N and L class memory isn't compatible) was installed. check two parts of them.


Easy going at all.
malvin drakley
Esteemed Contributor

Re: L2000 loops in early boot

Hi Florian, don't forget that there needs to be 2 memory dimms in as a minimum. 0a/0b slots need to be filled first and there is a plan on the cover where those slots are
cheers
malvin
Not me Chief, I'm Radar
Florian Anwander_1
Occasional Visitor

Re: L2000 loops in early boot

Hello Patrick, hello Melvin,

Thanks for the responses.

At first a state:
The machine contains 2x512MB (slots 0A and 0B) and additionally 4x1GB (slots 1A,1B,2A,2B).
I removed all the 1GB DIMMS and booted -> machine booted fine.
Then I added 2 GB, booted(->ok), added the other 2GB, booted (-> also ok).


to Patrick:
Of course we use proper DIMMs for L-Class.
The "impaired" message makes me think, that there was either a bad seating of one DIMM or more some dirt in a connector.

to Melvin:
I personally know about the necessity of the right order and distribution to the slots. But your hint is good for other people, who are looking for a solution of my problem.

Again: Thank you to everyone who helped.