Go Back   nV News Forums > Linux Support Forums > NVIDIA Linux

Newegg Daily Deals

Reply
 
Thread Tools
Old 02-11-06, 09:53 AM   #13
JaXXoN
Registered User
 
Join Date: Jul 2005
Location: Munich
Posts: 910
Default Re: X lockup with nv-1.0-8178 and 2.6.15-1.1830_FC4smp

Hi!

I was able to to narrow the problem down a little bit further
and found a workaround:

When binding all graphical applications to the first CPU, then
the acid test worked stable for about an hour (then aborted).

I'm using the following "Xaffinity" script to move everyting to
the first CPU (when already being logged in - the script has to
be invoked as root):

Code:
PROCS="X fvwm95 FvwmAuto FvwmPager xclock"
for i in $PROCS; do echo $i; affinity -p `pidof $i` -m 1; done
All subsequently started applications are children of the window
manager and thus inherit its limited SMP affinity CPU mask.
So if you start an xterm (executed by the window manager)
which will in turn execute a bash, then all commands running
in that console will also be bound to the first CPU! You need to
explicitly change the CPU mask for the SMP affinity of the bash in
order to make use of the second CPU, i.e. when compiling a kernel
with "make -j2" (which i did in parallel to the acid test, BTW.).

I guess you already recognized that this is not realy a handy
solution, but those having system freezes with SMP multi-GPU
boxes might give it a try just to check if we are having the same
problem (as discussed earlier, the problem didn't yet showed
up for two CPUs / one GPU and for one CPU / two GPUs
configurations - i didn't yet tested the one CPU / one GPU config.).

The list of processes (PROCS) certainly varies for a KDE or
Gnome desktop.

I will try out more fine grained cpu affinity settings, i.e. it might
be sufficient to just run the X server on CPU 0.

The "affinity" tool can be found here:
http://www.nvnews.net/vbulletin/show...5&postcount=30

regards

Bernhard
JaXXoN is offline   Reply With Quote
Old 02-13-06, 05:13 PM   #14
JaXXoN
Registered User
 
Join Date: Jul 2005
Location: Munich
Posts: 910
Default Re: X lockup with nv-1.0-8178 and 2.6.15-1.1830_FC4smp

Hi!

Just to let you know: applying "acpi=off" seems to help:
I'm running the before-mentioned "acid test" now for over
an hour using 2.6.14-1.1656_FC4smp.

So at least we know the regression happend somewhere in the
ACPI code. BTW.: applying "acpi=noirq" (don't use ACPI
for irq routing or scaning) generates the same IRQ routing
as when applying "acpi=off), but doesn't help (system freezes
and reboots within a few minutes running the acid test).

The only problem when applying this option is that the machine
doesn't powerdown with the "poweroff" command and i need to
switch it off manually
- that's a little bit annoying, but i guess i
could life with that until the problem get's fixed.

regards

Bernhard
JaXXoN is offline   Reply With Quote
Old 06-23-06, 10:11 AM   #15
mmisc
Registered User
 
Join Date: Jun 2006
Posts: 1
Default Re: X lockup with nv-1.0-8178 and 2.6.15-1.1830_FC4smp

Im having the same trouble, will this work with the next nvidia module?
mmisc is offline   Reply With Quote
Old 06-23-06, 10:42 AM   #16
JaXXoN
Registered User
 
Join Date: Jul 2005
Location: Munich
Posts: 910
Default Re: X lockup with nv-1.0-8178 and 2.6.15-1.1830_FC4smp

Quote:
Originally Posted by mmisc
Im having the same trouble, will this work with the next nvidia module?
It turned out that since 2.6.14, the kernel uses a different scheme
for the PCI configuration which seems to affect dual-core dual-GPU
setups. So this is not an nvidia driver issue! Please try "pci=conf1"
as kernel boot option in order tell the kernel to use the old PCI
configuration method. This helped for me and - as far as i'm
aware - for anybody else who was facing this problem.
BTW.: ACPI will then be enabled, again, and the machine will turn
automatically off after shutdown. I have no information if or
when this bug will be fixed in the kernel.

regards

Bernhard
JaXXoN is offline   Reply With Quote
Reply


Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump


All times are GMT -5. The time now is 09:54 PM.


Powered by vBulletin® Version 3.7.1
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Copyright 1998 - 2014, nV News.