Hi,

I'm running 2.6.7 (or was) except i've had 5 or 6 system lockups, making the system completely irresponsive.

I've double checked the configuration, and recompiled, i've updated subsystems and no avail, it still crashes.

My system is slackware current (pre 10.0 by ... 4 days [oh the irony]) running a tained kernel (NVidia). I'm semi certain it isn't a NVidia problem in a malfunction, but i can't confirm that.

Symptoms: all activity dies, no IO, no hard drive activity, no modem activity (if online), no flashing keyboard lights (which i used to get on kernel panics and the like). Nada, no mouse movement, no screen updates.

What's happening at the time, anything special really, on screen programs are OpenOffice, gkrellm, sometimes gaim and firefox (or mozilla), sometimes jedit, the GUI is KDE. 3.2.2

ALL of the system works on 2.6.6 with matching configuration, so i don't mind waiting for 2.6.8 comming out, HOWEVER what i would like to know is:

1) anyone have similar issues?
2) HOW can i track what is actually happening, something must be logging ... something (like /var/log/messages) what should i look for?
3) what is the spinlock thing in the kernel? (something about processes getting noisy when caught in one, but what is a spinlock ... i'm guessing process / thread handling?)

System Specs
AMD AthlonXP 2800+
2 x Corsair TwinX 512 RAM
Elsa Geforce Fx5900 SE (128MB)
GA-7N400 Pro2 (nForce2 Ultra400 chipset)

I'm using NVidia's GFX driver 5336, with NVidias own NvAGP

I know that there is little to go off, but i'm mainly interested as to how to find out the info to look at these things?

I have had 5 to 6 lock ups with kernel 2.6.7 also (In a two day period). I also am running Slack 10, four days ahead of yours I have recompiled my kernel sereral times. I have ATI's video drivers installed and I do not think that is causing it because I think it crashed prior to the install. I am also having a DMA issue I cant get my HD to use DMA

I posted this in a different post but no response...

Im going to stick it out with 2.6.7 and figure it out but it is tough on a lock up because you cant find logs of what the heck happend at least i cant.

Slack 10 really seems to bog my system down to. Things are really slow maybe my kernel config is all screwy but I like to think I no my hardware well enough to run a custom kernel

Ohh well onwards we go.

interesting that the default config would cause issues, especially since distro's compile very conservative, to cater for any need.

I can't say i have noticed an DMA issues with my HDD, though hdparm is set to start up in my rc.d scripts.

One thing on that subject though, my usb flash drive was hooked on when linux crashed, and the drive cratered, requiring a windows eject because linux wouldn't aknowledge it ... That said i did see an error message saying that the flashdrive was rejecting the scsi assignment of device number ... maybe it has something to do with it ...

As for 4 days behind / ahead ... well ... I'm subscribed to Slackware, so i'll upgrade when i get my pressed disks, ... till then i doubt there is too much difference ... 4 days and KDE3.2.3 .. which reminds me ... kde ... LOL

Chakkerz

Check this post out. Many people are having trouble with the new 2.6.7 kernel and NVIDIA drivers. After looking through nvidias linux forums i come across this. It works for me. I run Slack 10 kernel 2.6.7 no problems at all.

http://www.linuxquestions.org/questi...hreadid=198461

Just read my post in that thread it should help you out.

4 k stack issues hey ...

I was actually looking at that option wondering about it ... I'll check that when i get home ... TA