Bug 90398 - RHEL 2.1 hangs when vncserver running on dual Xeons
Summary: RHEL 2.1 hangs when vncserver running on dual Xeons
Alias: None
Product: Red Hat Enterprise Linux 2.1
Classification: Red Hat
Component: kernel
Version: 2.1
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: Larry Woodman
QA Contact: Brian Brock
Depends On:
TreeView+ depends on / blocked
Reported: 2003-05-07 17:16 UTC by Brian Faustyn
Modified: 2007-11-30 22:06 UTC (History)
2 users (show)

Clone Of:
Last Closed: 2007-10-19 19:25:01 UTC

Attachments (Terms of Use)

Description Brian Faustyn 2003-05-07 17:16:15 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030225

Description of problem:
reported by Lou Lohman <LLohman@WeberMarking.com>

My problem arises out of the fact that we have a serious bug in a program that
comes as part of the AS 2.1 distribution � vncserver. We have discovered that
using VNC in a two-way Dell 2650 (dual Xeon) locks up the system in a very short
period of time.  The system has run for weeks now without the VNC in use, and
that�s the only change we�ve made, so we are certain the VNC is the issue.  It
does NOT happen to single processor systems � we have several Dell 1650�s in
which we have run this software in the past, and VNC ran with impunity in them.
 But, now that we have re-architected the project, and we are running the
Database Server in the two-way and the Apps server in a single processor system,
we have encountered this problem with VNC.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.see above

Additional info:

related to BZ#88248?

Comment 1 Tim Waugh 2003-05-08 08:46:20 UTC
Please expand on 'locks up the system': does it respond to pings, for instance?

This sounds like a kernel problem.

Comment 2 RHEL Product and Program Management 2007-10-19 19:25:01 UTC
This bug is filed against RHEL2.1, 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.

Note You need to log in before you can comment on or make changes to this bug.