I have a very strange problem with my new install of slack. When I start an X session as root then "end session" my whole computer locks up. Literally you cant even get the CAPS LOCK key to light up. The problem as I see it is I dont know where the problem lies. Is it:

1. KDE config
2. Slackware config
3. Kernel problem
4. Hardware
5. Something else?

The real problem is that there is nothing of any significance in /var/log/messages or /var/log/debug and as the computer completely dies I have nothing to work with at all.

My first thoughts were that it was a KDE problem but I had KDE running fine before slacks under a different distro. Maybe it could be to do with the kernel which I was thinking of upgrading anyway. Anyway, here is what I do know, but I would really be quite surprised if anyone can help me here!

root@linux:/etc# uname -a
Linux linux 2.4.32 #6 Sun Mar 12 18:08:35 CST 2006 i686 pentium4 i386 GNU/Linux
root@linux:/etc# lspci
00:00.0 Host bridge: Intel Corporation 82850 850 (Tehama) Chipset Host Bridge (M
CH) (rev 04)
00:01.0 PCI bridge: Intel Corporation 82850 850 (Tehama) Chipset AGP Bridge (rev
04)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 04)
00:1f.0 ISA bridge: Intel Corporation 82801BA ISA Bridge (LPC) (rev 04)
00:1f.1 IDE interface: Intel Corporation 82801BA IDE U100 (rev 04)
00:1f.2 USB Controller: Intel Corporation 82801BA/BAM USB (Hub #1) (rev 04)
00:1f.3 SMBus: Intel Corporation 82801BA/BAM SMBus (rev 04)
00:1f.4 USB Controller: Intel Corporation 82801BA/BAM USB (Hub #2) (rev 04)
01:00.0 VGA compatible controller: nVidia Corporation NV11 [GeForce2 MX/MX 400]
(rev b2)
02:07.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 0a)
02:07.1 Input device controller: Creative Labs SB Live! MIDI/Game Port (rev 0a)
02:08.0 Communication controller: Agere Systems LT WinModem (rev 02)
02:09.0 Ethernet controller: Winbond Electronics Corp W89C940
02:0a.0 USB Controller: NEC Corporation USB (rev 43)
02:0a.1 USB Controller: NEC Corporation USB (rev 43)
02:0a.2 USB Controller: NEC Corporation USB 2.0 (rev 04)
root@linux:/etc# lspci
00:00.0 Host bridge: Intel Corporation 82850 850 (Tehama) Chipset Host Bridge (MCH) (rev 04)
00:01.0 PCI bridge: Intel Corporation 82850 850 (Tehama) Chipset AGP Bridge (rev 04)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 04)
00:1f.0 ISA bridge: Intel Corporation 82801BA ISA Bridge (LPC) (rev 04)
00:1f.1 IDE interface: Intel Corporation 82801BA IDE U100 (rev 04)
00:1f.2 USB Controller: Intel Corporation 82801BA/BAM USB (Hub #1) (rev 04)
00:1f.3 SMBus: Intel Corporation 82801BA/BAM SMBus (rev 04)
00:1f.4 USB Controller: Intel Corporation 82801BA/BAM USB (Hub #2) (rev 04)
01:00.0 VGA compatible controller: nVidia Corporation NV11 [GeForce2 MX/MX 400] (rev b2)
02:07.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 0a)
02:07.1 Input device controller: Creative Labs SB Live! MIDI/Game Port (rev 0a)
02:08.0 Communication controller: Agere Systems LT WinModem (rev 02)
02:09.0 Ethernet controller: Winbond Electronics Corp W89C940
02:0a.0 USB Controller: NEC Corporation USB (rev 43)
02:0a.1 USB Controller: NEC Corporation USB (rev 43)
02:0a.2 USB Controller: NEC Corporation USB 2.0 (rev 04)

Here is a copy of my /var/log/messages file:
hopkins81.com/messages.txt

cheers!

do you think it could be an apci problem? i guess if it only happens with root and not other user's that is weird.

i would try the stock 2.6.13 kernel (which is on the disk), to see if that helps.

Although I can't offer an immediate explanation, we can certainly try to rule out some of the listed possibilities!

1. KDE config

Try switching window manager (Xfce, Fluxbox) and seeing if the same thing happens.

2. Slackware config

I find problems that revolve around X are usually contained in X. Try defaulting your /etc/X11/xorg.conf file and seeing what happens. Also, try cleaning up the files in /tmp and also take a look at your hidden files (.kde/ for example) in $HOME (/root for root, /home/<user> for anyone else), see if something has gotten stale.

3. Kernel problem

These usually manifest themselves much more strongly, but, if in doubt I'd follow satinet's advice and try some of the stock kernels.

4. Hardware

Although we *could* start swapping out each piece individually, I doubt you have the resources to do that, so, I would guess you have an nVidia card (*checks on the list above* Ooh yeah, I'm good! - back to work! Ed). Try using the official nVidia drivers, and also, try using the vesa driver. It's an old card, so may be not as well supported as some of the newer (GF4 & up) cards - if you can swap this piece of hardware out, that would be great (I can recommend the MX4000s for cheap drop-in replacements - I think mine was about £25).

5. Something else?

Something you might want to try is the method of dropping out of X. You say you're using "end session". Try ctrl + alt + backspace and see if it does the same thing. Try running KDE as a user (it's not usually recommended to run as root all the time). Finally, I had a driver/hardware problem (my poor GF4 got static!) which kept hard locking X - the funny thing was, that I could still SSH into the box and run top to check what was running. X was sitting there at 99% cpu usage, but for all intents and purposes, I couldn't do anything about my system.

Let us know how you get on!

- Piete.

PS: Including your country & distros in your profile will stop us making stupid suggestions and giving out poor advice with regards to hardware purchasing!

Thanks guys, there is actually a lot of stuff I can try (cheers piete). I'll let you know how it goes!