Red Hat Bugzilla – Bug 168981
RHEL3-U6-re0921.0 VNC installation produces library error "/usr/lib/libpango-1.0.so.0: cannot read file data: Invalid argument"
Last modified: 2013-09-02 02:07:03 EDT
# TREE RHEL3-U6-re0921.0
# ARCH ppc
# CASE iSeries VNC installation
Prior to connecting my vncviewer to the the installer vncserver, I see the
following error message. When I connect to the vncserver, I see nothing but a
black screen (see attachment).
Running anaconda, the Red Hat Enterprise Linux system installer - please wait...
Probing for video card: Unable to probe
Probing for monitor type: Unknown monitor
Probing for mouse type: No - mouse
No video hardware found, assuming headless
WARNING!!! VNC server running with NO PASSWORD!
You can use the vncpassword=<password> boot option
if you would like to secure the server.
The VNC server now running.
Please connect to isqa4.test.redhat.com:1 to begin the install...
//usr/bin/mini-wm: error while loading shared libraries:
/usr/lib/libpango-1.0.so.0: cannot read file data: Invalid argument
Created attachment 119097 [details]
Additional data points
- Does not happen on RHEL-3/U5
- Does happen on RHEL3-U6-re0916.0 (RC0)
- Does not happen on power5 hardware (only iSeries)
Bet if you change your iseries config a little to have more or less cpu, it'll
This is a transient error that has popped up from time to time that we've yet to
actually get a handle on because it's really not anything anaconda has any
control over. The dynamic loader is getting -EINVAL from the kernel when we
load a shared library, which then causes things to break.
this error has occurred throughout the RHEL3 U6 cycle for s390/s390x, (including test trees RHEL3-
U6-re0921.0 & RHEL3-U6-re0916.0), but is never deterministic ...
this error can happen for up to ~30% of vnc gui installs for s390/s390x ...
Looks like we already have several similar issues in bugzilla:
katzj ... I think you are on to something
I originally hit this problem 4 out of 4 attempts on the QA4 lpar. Here's what
I've found since then after changing some tunables for the lpar configuration:
- does *not* reproduce on QA2 (lpar on same system but w/ .1 more cpu)
- does *not* reproduce on QA4 (if I in increase num_cpu or cpu_units)
After making the following changes on QA4:
1) increasing the cpu units from .5 to .6
2) increasing number of virtual cpus from 1 to 2
I am not able to hit this bug.
I don't see how this isn't a kernel problem.
This bug is filed against RHEL 3, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products. Since
this bug does not meet that criteria, it is now being closed.
For more information of the RHEL errata support policy, please visit:
If you feel this bug is indeed mission critical, please contact your
support representative. You may be asked to provide detailed
information on how this bug is affecting you.