KDE locking the whole box on SuSE 9.1

Thu Aug 26 22:49:31 BST 2004

I too have had the same trouble, usually when switching displays.  I have 
encountered this phenomenon on SuSE 8.0 and Mandrake 9.2. It is true that the 
X server spins and locks up the CPU. I suspected the nVidia driver as the 
cause. 

When this occurs, I start konsole or a text terminal on another computer on my 
home network. I then log in to the locked up computer via ssh *in text mode* 
giving me console access to the locked up computer.  I then su to root on the 
locked up computer. It is then possible to kill any process. I tried to kill 
X, but this did not produce any useful results.  So I used this facility to 
do a proper shutdown / reboot.

Recently I had a case of lockup, and I found that killing all instances of 
"kdeinit" unlocked the original console, dropping it back into a standard 
text console.  The X server and xdm could be restarted, and thence KDE.  

I have not been able to verify this procedure for the (happy) reason that I 
have not experienced another lockup since.

One extra point - when you log out from KDE 3.1 or 3.2, an orphan "kdeinit" 
process is always left.  If you leave the computer running continuously and 
log in and out with one or more users, these orphan "kdeinit" processes 
accumulate.  I clean them out regularly.  This may not be relevant to this 
problem, but I think it worth a mention.  

The program I use to list processes is "top -bn1"

Hope this helps

Basil Fowler

On Thursday 26 Aug 2004 18:41, Daniel Eshuis wrote:
> liste at hgfelger.de wrote:
> 
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > Salut Denis & Rikard,
> >
> > On Thu, 26 Aug 2004, Denis Vlasenko wrote:
> >
> >> On Thursday 26 August 2004 13:17, Rikard Johnels wrote:
> >>
> >>> KDE locks up randomly after a few minutes.
> >>
> > I don't think it is KDE to blame for... (see  below).
> >
> >>> No keyboard, no network no nothing but the button-on-the-front can 
> >>> unluck
> >>
> > What is this button on the front???
> >
> I guess his on/off switch :)
> 
> >>> it. I cant seem to find the answer to why or what causes the lockup.
> >>> Thought it to be YAS, but even if i dont run it it locks.
> >>> Thought it was a number of other things, none applied.
> >>> It just wont run.
> >>> It looses keyboard, CAPS and NUM toggles, but you cant shift to another
> >>> terminal to kill X, and you cant even bail out with 
> >>> ctrl-alt-backspace. YOu
> >>> cant access the box via keyboard at all.
> >>> It also kills network connections, i cant ping let alone ssh to the 
> >>> box as
> >>> it hangs.
> >>
> > If the keyboard and ping did not work, you may be pretty sure, the 
> > machine is realy out of business at this time... ping works almoust 
> > all the time, also if the kernel is 90% crashed...
> >
> >> You can try Magic SysRq keys. SysRq-B reboots. If it does that, then
> >> machine still services interrupts. May be useful:
> >> tErm (SysRq-E): TERM all tasks
> >> kIll: KILL all tasks
> >> showPc: get current stacktrace
> >> showTasks: get all processes' stacktraces
> >
> > I do not know, if it will show something while X is runnung and shown.
> > On the other hand with my laptop the Magic SysRq do not work, as the 
> > keyboard is broken by design. So maybe you want to check the 
> > Magic-SysRq procedure first from an virtual console, while the machine 
> > is not crashed.
> >
> > As you have all drivers loaded, when you start KDE (ie. sound, 
> > graphics (maybe even GL, ie. 3D-acceleration) etc.) it may show you 
> > some incompatibility then, that need not to be related to KDE itself.
> >
> > Cheers
> >   hartwig felger
> >
> > Hartwig Felger informatics
> >
> I had the same problem a while back with my SuSE 9.0 installation. At 
> first I also thought the problem was KDE related.  But after upgrading 
> 3.2 to 3.3 the problem still 'hung' around. I realised I still had the 
> network running, which enabled me to notice that  X was locked up / 
> using 98% of my CPU. Sending a SIGKILL helped X restart but f*cked up my 
> console display, only a reboot would fix that. The X version info showed 
> that it was the 4.3.0.1 Pre-Release version.  Upgrading X solved the 
> issue for me.
> 
> On another box I had arts making a mess, I had xmms with OSS plugin 
> running instead of the arts plugins, this somehow froze the box 
> everytime the arts deamon tried to throw a 'system sound' @ the 
> soundcard. Getting xmms to work with the arts-plugin solved that issue.
> 
> Maybe the info helps...
> Daniel Eshuis
> 
> > - -- 1024D/339FD693 Hartwig Felger <hgfelger at hgfelger.de>
> > Key fingerprint = FB2F 3EE9 345A D55B 6FF2  0EC1 F5B0 684F 339F D693
> > For the pulic keys, please visit my page.
> > -----BEGIN PGP SIGNATURE-----
> > Version: GnuPG v1.2.2 (GNU/Linux)
> >
> > iD8DBQFBLegI9bBoTzOf1pMRAkJLAJ9NFxCEsHQLfZ+7YavdWSxYnQZubgCeIbV4
> > nm3kxI5SWDEkIIuQKir+IZI=
> > =eFkh
> > -----END PGP SIGNATURE-----
> > ___________________________________________________
> > This message is from the kde mailing list.
> > Account management:  https://mail.kde.org/mailman/listinfo/kde.
> > Archives: http://lists.kde.org/.
> > More info: http://www.kde.org/faq.html.
> >
> 
> ___________________________________________________
> This message is from the kde mailing list.
> Account management:  https://mail.kde.org/mailman/listinfo/kde.
> Archives: http://lists.kde.org/.
> More info: http://www.kde.org/faq.html.
> 

___________________________________________________
This message is from the kde mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.