HP-UX
1753561 회원
5684 온라인
108796 솔루션
새 메시지

HP K260 System Hang 질문

 
송우락
비정기 기여자

HP K260 System Hang 질문

안녕하세요.



시스템에 계속적으로 문제가 발생되어 도움을 얻고자 글을 올립니다.

* OS : HP-UX 11.0 CPU 3EA , Memory 512MB (64MB * 8EA)



1. system hang 이 발생

-. LCD 판넬에는 (RUN F13F )로 표기 되어 있는 상태로 멈춰짐.

-. syslog 등 core file도 발생되지 않음



2. 시스템 리부팅 후 정상적으로 동작됨

-. LCD 판넬 (RUN F13F <-> F03F) 반복적으로 나타남.



HP서버가 시스템 hang 걸리는 원인을 알고 싶습니다.

그리고 혹시 Patch를 해줘야 하는지도요..



아참 그리고 메모리쪽 Single Bit Error가 발생하네요..(메모리 교체는 하였습니다.)

답변 부탁드리겠습니다.



Memory Error Log Summary



Error

Board Error Address Error Type Page Count

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

EXT0 1a 0x000000001d9187a0 Single-Bit 0x001d918 1



System start: Mon Apr 1 13:15:58 2002.

Last error check: Wed Aug 11 23:06:08 2004.

Logging interval: 3600 seconds.

1 address(es) with errors logged by memory logging daemon.

2 응답 2
김병수
본과생

HP K260 System Hang 질문

잘은 모르겠으나 우선 RUN code FxyF code에 관하여 말씀을 드리면



x is updates every 5 seconds withthe length of the run queue at that time 를 의미한다고 합니다.



y is indicated the number of processes (1,2,3 or 4 )

를 의미한다고 합니다.



cpu를 check하여 보심이 좋을듯합니다.



그전에 물론 기본적인 patch및 firmware 는 upgrade하여 보시기 바랍니다.
고광태
중학생

HP K260 System Hang 질문

제가 보기에는 firmware 쪽 확률이 높을거란 생각이 드네요..



kx60 용 firmware 41.33 을 첨부합니다.



아래의 내용 참조 하시기 바랍니다.



Installation Instructions:



Please review all instructions and the "Hewlett-Packard

Support Tool License Terms" or your Hewlett-Packard support

terms and conditions for precautions, scope of license,

restrictions, and, limitation of liability and warranties,

before installing this patch.



PLEASE BACK UP YOUR SYSTEM BEFORE YOU INSTALL THE PATCH.





NOTE: It is important that you read and understand these

instructions completely before you begin. This can

determine your success in completing the Firmware update.



Be sure to prepare the system and its users before

beginning a Firmware update. Since the system will not be

in operation during the update, you should notify

appropriate managers and users as to when it will be

shutdown and for how long it will remain inoperative.



The Firmware update should take no longer than 30 minutes

to complete.





* * * * * * * * VERIFYING CURRENT REVISION OF FIRMWARE * * * * * * * *





VERIFYING FIRMWARE REVISION WITH ON-LINE DIAGNOSTICS



The current revision of Firmware can be determined using on-line

diagnostics. If on-line diagnostics are not present on your

system, use the BOOT CONSOLE HANDLER procedure to verify the

current revision.



Procedure for all systems

1. Login as root

2. At the prompt, enter 'mstm'

3. Press f2 (ok)

4. Move the cursor to "CPU"

5. Press f3 (select)

6. Press f4 (menu bar on)

7. Enter "T" to select Tool Menu

8. Enter "I" to select Information Mode

9. Enter "R" to Run

After a few seconds, the Information Tool Log for

the CPU will be displayed. The 'PDC Firmware

Revision' is displayed in the first column.

10. Note the PDC Firmware value

11. Press f8 (done)

12. Press f8 (exit)

13. Press f2 (ok)



If the revision is not 41.33, your system will require

a Firmware update. Skip the next section, and follow the

instructions for CREATING THE FIRMWARE UPDATE TAPE.





VERIFYING FIRMWARE REVISION WITH BOOT CONSOLE HANDLER (BCH)



1. Log on as root, and enter "shutdown -r". This command

will shutdown the Operating System and reboot the system.



2. If AUTOBOOT is on, you will receive the following message:



"Process is starting autoboot process

To discontinue, press any key within 10 seconds."



At this point, press ANY KEY within 10 seconds to

interrupt the booting process.



3. The Main Menu is displayed. A prompt will appear as

".



Enter the command "in".



"



Enter the command "fv"



The system will respond with the current firmware

revision. If the revision is not revision 41.33

your system will require a Firmware update. Follow the

instructions in the next section, CREATING THE FIRMWARE

UPDATE TAPE.





* * * * * * * * * * CREATING THE FIRMWARE UPDATE TAPE * * * * * * * *



After retrieving the patch file from the HP-ESC, use the HP-UX

'sh' command to open the patch package:



prompt: sh PF_CMHK4133



Two additional files will now be available. These files are

CMHK4133.text and CMHK4133.frm. The .text file (this file) provides

specific instructions for that release of firmware. The .frm file

is the actual update image file.



1. Verify the checksum of the file "CMHK4133.frm" using

the "sum" command. Results of the command should be

equal to "4531 7256 CMHK4133.frm".



2. Use the "dd" command to copy the file "CMHK4133.frm"

to tape, as follows:



dd if=CMHK4133.frm of=/dev/rmt/0m bs=2k

^^^^^^^^^^^

(device path dependent)



NOTE: Blocksize (bs) must be 2k





* * * * * * * * * * * FIRMWARE UPDATE PROCEDURE * * * * * * * * * * *



NOTE: ENSURE YOUR SYSTEM IS FULLY BACKED UP BEFORE

PROCEEDING WITH THIS FIRMWARE UPDATE.



1. Log on as root, and enter "shutdown -r". This command

will shutdown the Operating System and reboot the system.



2. If AUTOBOOT is on, you will receive the following

message:



"Process is starting autoboot process

To discontinue, press any key within 10 seconds."



PRESS ANY KEY WITHIN 10 SECONDS TO INTERRUPT

THE BOOTING PROCESS.



3. Boot from the device that contains the firmware update tape

you just created.







Respond with "N".



A series of messages will be displayed. No user

intervention is required. Proceed to step 5.



5. A message will be displayed as follows:



"F/W file Note:"

"A-Class PDC firmware image, Version 41.33"



"Continue (/n)?"



Enter "y".



CAUTION: FROM THIS POINT FORWARD, THIS PROCESS CANNOT

BE INTERRUPTED UNTIL COMPLETION. INTERRUPTING

THIS PROCESS WILL CAUSE YOUR SYSTEM TO BE

INOPERATIVE.



6. The update should take approximately two minutes.

After the tape has been read by the update

program, a message will be displayed as follows:



"Firmware downloaded SUCESSFULLY!"

THIS UTILITY WILL NOW RESET THE SYSTEM....



7. The system will automatically reset, and the boot

process will begin. Boot your system with your

normal process.



If there is a problem with your system after the

update, please contact your service representative.



* * * * * * * * * * * * * * END OF UPDATE * * * * * * * * * * * * * *