Bug 52427 - Slowpoke kernel
Summary: Slowpoke kernel
Keywords:
Status: CLOSED DUPLICATE of bug 52374
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kernel
Version: 7.3
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Arjan van de Ven
QA Contact: Brock Organ
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-08-23 17:41 UTC by Stephen John Smoogen
Modified: 2007-04-18 16:36 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2001-08-24 17:09:00 UTC
Embargoed:


Attachments (Terms of Use)

Description Stephen John Smoogen 2001-08-23 17:41:43 UTC
I am using kernel-2.4.7-2.5 and usually leave myself
logged in over night. The last 2 days, I have turned on the monitor at 7
am and started typing along..  and found the machine to be very
un-responsive.. it seems the programs are all in swap and they all need
to be swapped back in.  Looking at the GNOME memory/swap/cpu counter,   
there is a flurry of activity as the memory bar moves to the top, and   
then seems to empty down to a minimal 32 megs or so (top reported the 
same thing). It then fills itself back up and many apps become useful 
again.

The funny thing is that certain apps like Mozilla, Xchat, Pan, and
Galeon do not get better.. you type on them, and it takes a while (up to
30 seconds) for the keyboard and screen to sink up with each other.
Looking at top, it reports that the process is out of swap.. but I dont
know how useful that is. I played around with x-chat this morning, and
it stayed in this ulta-nice'd state for about 10 minutes.. I finally
gave up and killed the apps and then start new ones. These new ones
function like normal.

Comment 1 Glen Foster 2001-08-24 17:08:55 UTC
This defect is considered SHOULD-FIX for Fairfax.

Comment 2 Arjan van de Ven 2001-08-24 17:15:29 UTC
Sounds like a dupe of 52374 (eg nightly updatedb run ruins your cache)

*** This bug has been marked as a duplicate of 52374 ***


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