Bug 18898 - Slow response on Dell PowerEdge 8450 in "init 5"
Slow response on Dell PowerEdge 8450 in "init 5"
Status: CLOSED WONTFIX
Product: Red Hat Linux
Classification: Retired
Component: XFree86 (Show other bugs)
7.0
i686 Linux
high Severity high
: ---
: ---
Assigned To: Mike A. Harris
David Lawrence
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2000-10-11 11:45 EDT by Need Real Name
Modified: 2005-10-31 17:00 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2001-04-03 03:23:21 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Need Real Name 2000-10-11 11:45:58 EDT
I installed linux RedHat version 7.0 on a dell poweredge 8450 with 4 cpu 
and 4 Gb of memory.  When I boot the system in "init 5", it takes about 5 
minutes to login, and it is very slow to respond.  I ran top it after a 
couple of minutes the application started and showed all the cpu's are 
about 50 or mor utilized mostly by the system.  The top itself was using 
about 45% of the cpus.  When I run the system in "init 3", every thing 
runs normally.
Comment 1 Alan Cox 2000-10-14 13:57:41 EDT
If you boot to run level 3 then start X11 does it stay fast ?
Comment 2 Need Real Name 2000-10-16 11:13:10 EDT
Yes, even after I start with init 3 and run startx, the system slows down 
drastilcaly.
Comment 3 Bernhard Rosenkraenzer 2000-12-30 13:19:18 EST
Are you using kdm, gdm or xdm?
Comment 4 Mike A. Harris 2001-04-03 03:23:17 EDT
Can you try out the latest rawhide XFree86 packages?  XFree86-4.0.3-5
and Mesa-3.4-13.

Do they change the situation for you at all?
Comment 5 Mike A. Harris 2002-01-25 06:02:15 EST
Please reopen bug if problem persists after upgrading to red Hat Linux 7.2
and applying all updates that have been released.

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