[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-linux
Subject:    [kde-linux] Fwd: Re: [expert] Mandrake 10.1 Lock-up and runaway CPU
From:       Harry Wert <hwert () earthlink ! net>
Date:       2005-01-17 20:59:01
Message-ID: 200501171601.13710.hwert () earthlink ! net
[Download RAW message or body]

I was asked by Anne Wilson ( Anne Wilson <cannewilson@tiscali.co.uk>) to 
re-post this message from the expert@linux-mandrake.com for general 
information.

Harry Wert
Physicist

----------  Forwarded Message  ----------

Subject: Re: [expert] Mandrake 10.1 Lock-up and runaway CPU status
Date: Monday 17 January 2005 07:00 am
From: Harry Wert <hwert@earthlink.net>
To: expert@linux-mandrake.com

On Sunday 16 January 2005 10:50 pm, Harry Wert wrote:
> This is an update of extensive testing with Mandrake 10.1 Official and
> select Thacs rpm's I have reported on earlier.
>
> The testing was conducted on a computer with a AOPEN mother board MK77M-8XN
> 400 Mhz front side bus
> VIA chipset	VIA KM400 and VIA 8232
> 8X AGP video
> Realtek lan and sound
> Processor is an AMD ATHLON 2500 XP
> 1 Gb of DDR memory
>
> Prior to my last three days of extensive testing, I did not experience hard
> lockups as has been reported by others, but I had many, many CPU runaways
> which required the use of kill -9 xxxx to take control back. The runaway
> culprit is still kded. Killing kded also kills other related processes such
> as printing, rendering it useless until a hard reboot is accomplished.
> Previous testing also revealed a very high propensity to trigger runaway
> CPU problems by plugging in/out various USB deveices such as mice,
> printers, external hard drives (USB), and scanners (USB).  Now the good
> news:
>
> I have tested seven (7) different 2.6.8-x vintage kernels with absolutely
> no effect on my runaway problems.  I have however, developed a stable
> platform which consists of the Mandrake 10.1 Official release with many of
> Thacs RPM's to take me to kde3.3.2.  Gnome is now used as the window
> manager but with the kde login window - I forget what that is called, but
> it's NOT gdm.  With this combination I have beat the system to death for
> two 24 hour days, with ZERO problems no matter what order tests are done to
> test USB operation, as well as extensive use of the kde3.3.2 applications -
> especially the PIM suite (Kontact) et al.  So, since I need to get back to
> my paying job, I plan to use this combination until kde is patched as far
> as the window manager is concerned. Should I run into any further
> difficulty or garner any useful insight, I will report back to this list.
>
> Again, I hope this is useful information.
>
> Harry Wert
> Physicist

Forgot something important: I also ran these same tests with other window
managers such as window manager, mkultra, blackbox, icewm, xandros (window
manger part only), and several others I forgot to write down.  All of these
worked correctly leading me to conclude the culprit must be the kde window
manger or one of it's constituents.

Harry Wert
Physicist

-------------------------------------------------------
___________________________________________________
This message is from the kde-linux mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde-linux.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.
[prev in list] [next in list] [prev in thread] [next in thread]