XFree86 crash on HP-UX 11i v3 Update 4

[Andrey Chipalyuk]

I had tried to install the HP-UX 11i v3 Update 4.

a) In interactively prompt for keyboard mapping I choose 26 keymap:

# cat /etc/kbdlang
USB_PS2_DIN_US_English

b) The Server XFree86 had crashed when I was trying to open XDMCP session. Xf86.0.log contains strins:

...
(II) Loaded keymap USB_PS2_DIN_US_English from file /etc/X11/XHPKeymaps
(**) Option "Device" "/dev/hid/kbd_000"
(II) Using keyboard device file "/dev/hid/kbd_000"
(WW) Unable to open keyboard device "/dev/hid/kbd_000"
(WW) Reason: No such file or directory
(WW) Continuing without a keyboard
No core pointer
...

c) I was changing /etc/kbdlang much as it was in HP-UX 11.23 version:

# cat /etc/kbdlang
Not_Applicable

Then i shutdown and reboot server. HP-UX was requiring to select keymap by start HP-UX:

1) USB_PS2_DIN_Belgian
...
26) USB_PS2_DIN_US_English
27) USB_PS2_DIN_US_English_Euro

I choose 26 keymap:

# cat /etc/kbdlang
USB_PS2_DIN_US_English

The problem remains.

[Matti_Kurkela]

The error message at step b) would seem to indicate that the server had no USB keyboard connected to it at the moment. Did someone unplug it between steps a) and b)?

If you are opening a XDMCP session, that implies your X server is located in your *local* X terminal or workstation. XDMCP does not require an X server at the *remote* side - just the X Display Manager (xdm/dtlogin/whatever).

So, for clarification:

Does the HP-UX 11iv3 server have a keyboard, mouse and display installed or not? (If not, the X server won't start and is not needed.)

When you say you were "trying to open XDMCP session", what exactly were you doing? Did you use ReflectionX, Xming or some other Windows-based X server software on some other host?

When you are choosing the keymap, what type of connection are you using? Local keyboard+display? Serial-attached terminal? Networked iLO remote console? If this is an Itanium machine, what is your console configuration in the EFI?

MK

[Andrey Chipalyuk]

1) Yes, the server have no keyboard, mouse and display connected to it at the moment.
The keyboard, mouse and display was connected at the moment of server start, i.e. from power on to start HP-UX.
Then it was disconected and HP-UX was shudown and reboot. Power was stayed on.
2) Yes, I was opening a XDMCP session, that implies my X server is located in my workstation.
3) Yes, I use Xming (i was trying other Windows-based X server software as well).
3.1) I was trying to open session.
3.2) At the CDE Window "Please enter your user name" I was typing a user name and pressing "Ok".
3.3) Then I was typing a password. When I was typing letter the session is Ok, but the session is crush when I was typing numeral symbols.
3.4) I was trying to change password only letter symbols. The session was established and I opened X desktop.
3.5) I.e. the session was crash when I typing numeral symbols in the password window. I was trying to type numeral symbols in the user name window and session is Ok!
4) Yes, it is itanium machine. I was choosing keymaps at the hpterm console by installation. Then i was trying to change keymaps at the putty console (xterm).

[Andrey Chipalyuk]

Probably the head of message is not correct. There is cause of crash may be CDE and there isn't XFree86. Have any idea?

[Andrey Chipalyuk]

After crash session core file contains strings "Dtlogin..." (i.e. CDE login service). For example:

...
Dtlogin*altDtKey4: /usr/dt/bin/Xsession
Dtlogin*altDtName: %DisplayName%Home
Dtlogin*altDtName1: Current
Dtlogin*altDtName2: Home
Dtlogin*altDtName3: %DisplayName%Current
Dtlogin*altDtName4: %DisplayName%Home
Dtlogin*altDtStart: /usr/dt/bin/Xsession -session display-home
...

I have found patch PHSS_39409:

Patch Description: 11.31 CDE Applications Creation Date: 09/04/06

I have installed this patch. The messages "No core pointer" disappeared, but problem remains.

[Andrey Chipalyuk]

I have tried to enables dtlogin debug auto-start feature with a debug level of 10:

/usr/dt/bin/dtconfig -debug

I have run:

/sbin/init.d/dtlogin.rc start

When I was typing numeral symbols in password window of CDE the session was crash.
The dtlogin.11330.log file contains strings:

...
...
[Mon Jun 29 11:29:38 2009] [11330](main) select() returns -1. Rescan: 0 ChildReady: 1
[Mon Jun 29 11:29:38 2009] [11330](main) select() error - 4
[Mon Jun 29 11:29:38 2009] [11330](main) Processing child death, pid = 11954, status 1024
[Mon Jun 29 11:29:38 2009] [11330](main) Account: id=35:0, user=NULL, line=NULL, pid=11954, type=DEAD_PROCESS
[Mon Jun 29 11:29:38 2009] [11330](main) PamAccounting: prog_name=dtlogin
...
...
[Mon Jun 29 11:29:38 2009] [11330](main) PamAccounting: display_location=1024
[Mon Jun 29 11:29:38 2009] [11330](main) PamAccounting: exitcode=1599099471
[Mon Jun 29 11:29:38 2009] [11330](main) PamInit: pam_start success
[Mon Jun 29 11:29:38 2009] [11330](main) Display exited with OPENFAILED_DISPLAY
[Mon Jun 29 11:29:38 2009] [11330](main) Display start failed, sending Failed
[Mon Jun 29 11:29:38 2009] [11330](main) Send FAILED to session ID 1, msg = Session 1 failed for display 172.16.248.35:0: Cannot open display
[Mon Jun 29 11:29:38 2009] [11330](main) XdmcpFlush - send_failed - addr.sin6_port = 4955 addr.sin6_addr
[Mon Jun 29 11:29:38 2009] [11330](main) StopDisplay(): 172.16.248.35:0, server pid = -1, manager pid = -1, dtlogin_shutdown = 0
[Mon Jun 29 11:29:38 2009] [11330](main) Account: id=35:0, user=NULL, line=NULL, pid=0, type=DEAD_PROCESS
...
...

[Dennis Handly]

>core file contains strings "Dtlogin..."

This is why you don't use strings(1) on a core file. It can only confuse you.
Instead you should use gdb on your core file and get a stack trace:
$ gdb executable core
(gdb) bt
(gdb) q

[Steven E. Protter]

Shalom,

At this point to have things clean, I would swremove CDE, uninstall xfree86, whatever its source, boot the system and reinstall both.

SEP

[Andrey Chipalyuk]

Thank!
The output of gdb is next:

# gdb -core=core
...
warning: Unknown symbols for 'core'; use the 'symbol-file' command.
Core was generated by `dtgreet'.
Program terminated with signal 10, Bus error.
BUS_ADRALN - Invalid address alignment. Please refer to the following link that helps in handling unaligned data: http://docs.hp.com/en/7730/newhelp0610/pragmas.htm#pragma-pack-ex3
No object file symbols.
#0 0x60000000cbc992d0 in ()
(gdb) bt
#0 0x60000000cbc992d0 in ()
warning: Attempting to unwind past bad PC 0x60000000cbc992d0
#1 0x60000000cbc99270 in ()

[Dennis Handly]

># gdb -core=core
>Core was generated by `dtgreet'.

You need to specify the executable and core file. It told you that it was dtgreet and you now need to find the absolute path.