rx8620 hp-ux boot problem after applaing patch PHKL_36143

[Denis Zhuravlev]

HPUX> boot vmunix
> System Memory = 18383 MB
loading section 0
................................................ (complete)
loading section 1
............ (complete)
loading symbol table
loading System Directory (boot.sys) to MFS
....
loading MFSFILES directory (bootfs) to MFS
.x..
Launching /stand/vmunix
SIZE: Text:24510K + Data:5892K + BSS:9348K = Total:39751K

Console is on a Serial Device
Booting kernel...

Sequencer: No wakeup handler is registered!
Sequencer: No wakeup handler is registered!
����& ��& �
0x6d00) Reserved

����& ��& �
��e�s�erved�& �
&
* * %�



e�r�v�ed�&

�*�*&* % f�a
ult ***

St atic Gener al
Regi sters

�e�d��&Reser
----------------------------------------------

HPUX> boot backup
Boot path is now: backup/vmunix
> System Memory = 18383 MB
loading section 0
................................................ (complete)
loading section 1
............ (complete)
loading symbol table
loading System Directory (boot.sys) to MFS
....
loading MFSFILES directory (backup/bootfs) to MFS
....
Launching /stand/backup/vmunix
SIZE: Text:24510K + Data:5892K + BSS:9348K = Total:39751K

Console is on a Serial Device
Booting kernel...

Sequencer: No wakeup handler is registered!
Sequencer: No wakeup handler is registered!
@ p0 �

� @� p 0��> ��@a ., �L t , �X

(� �@>_ ��@ a� �., P5� L�� 0B t� ,
� @� p 0 (� @XH�

[Steven E. Protter]

Shalom,

I would suggest booting of /stand/vmunix.prev

That file was created when the kernel was rebuilt by the patch.

You can also boot off the install media.

cd /stand

cp vmunix.prev vmunix

I'd also report the bug to HP Response center.

SEP

[Denis Zhuravlev]

Do you read second part of my first post?

----------------------------------------------
HPUX> boot backup
....

[Dennis Handly]

>Do you read second part of my first post?

It helps if you have some narrative to go along with the commands you used.

[Anshumali]

If you really want to say that previous kernel is not allowing to boot as well and giving you the same error. I will not call it caused by the kernel patch. How you compiled it?

[Denis Zhuravlev]

>If you really want to say that previous kernel is not allowing to boot as well and giving you the same error.
Yes, with previous kernel same error.

>I will not call it caused by the kernel patch. How you compiled it?
I execute swinstall -s /pathtopatch -x autoreboot=true \*

May be problem with disk? But command ls from bootloader show /stand contains and others dirs.