nV News Forums

 
 

nV News Forums (http://www.nvnews.net/vbulletin/index.php)
-   NVIDIA Linux (http://www.nvnews.net/vbulletin/forumdisplay.php?f=14)
-   -   Spawning new session leads to crash (http://www.nvnews.net/vbulletin/showthread.php?t=115535)

kriko 06-28-08 01:11 PM

Spawning new session leads to crash
 
Hello!
There was a problem introduced after the 100.x.x driver series I think - Xorg crashes when using multiple X sessions.

It's a nasty bug - I wonder if somene else got into it. I certainly can reproduce it alwas.

gbil 06-28-08 01:15 PM

Re: Spawning new session leads to crash
 
Quote:

Originally Posted by kriko (Post 1696924)
Hello!
There was a problem introduced after the 100.x.x driver series I think - Xorg crashes when using multiple X sessions.

It's a nasty bug - I wonder if somene else got into it. I certainly can reproduce it alwas.

I think as stated by NVidia this is not a supported configuration but somehow used to work in earlier drivers!

kriko 06-28-08 01:17 PM

Re: Spawning new session leads to crash
 
What it is not supported configuration? Can't have multiple graphical sessions?

AaronP 06-28-08 04:16 PM

Re: Spawning new session leads to crash
 
I should clarify: Running a single X server with multiple screens on different GPUs and running separate X servers on different VTs are both supported configurations. The configuration that's not supported is using -novtswitch and -sharevts to run two X servers on the same VT at the same time.

kriko 06-28-08 04:27 PM

Re: Spawning new session leads to crash
 
@AaronP: I'm trying to start a new session under different credentials - same monitor (switching is done with ctrl+F7, F8...). Is this supported?

RossBoylan 06-28-08 08:36 PM

Re: Spawning new session leads to crash
 
Quote:

Originally Posted by kriko (Post 1696924)
Hello!
There was a problem introduced after the 100.x.x driver series I think - Xorg crashes when using multiple X sessions.

It's a nasty bug - I wonder if somene else got into it. I certainly can reproduce it alwas.

Same problem here, I think. I have a GeForce 6600 LE with the Debianized 169.12 driver. I use kdm with 1 "static" server and 3 "reserve" (on-demand) servers. I think this fits the description of scenarios that should work, though I'm not sure whether this is one server with multiple vt's or one server per vt. I switch via the KDE menu (KDE3). Or I used to. It didn't always crash my original session immediately, but it usually crashed it soon.

It's certainly a significant problem for me, since I want different family members to use different sessions.

AaronP 06-28-08 10:24 PM

Re: Spawning new session leads to crash
 
Yes, that configuration is supposed to work. I don't see any evidence of a crash in your bug report. Could you please reproduce the crash, generate a new nvidia-bug-report.log, and attach it along with copy of /var/log/Xorg.1.log?

RossBoylan 06-29-08 12:04 AM

Re: Spawning new session leads to crash
 
1 Attachment(s)
Quote:

Originally Posted by AaronP (Post 1697239)
Yes, that configuration is supposed to work. I don't see any evidence of a crash in your bug report. Could you please reproduce the crash, generate a new nvidia-bug-report.log, and attach it along with copy of /var/log/Xorg.1.log?

Here they are. The sequence was
1) login as userA (vt7)
2) switch session to userB
This left me in vt7, logged in as B. The session for A disappeared.
The KDE session menu showed vt8 as unused (but present)

My more usual experience is that after 2) I am logged in to vt8 as user B. After awhile (usually just a few seconds) the display flips back to vt7, which is now empty.

I'm not sure the X logs show much. However, kdm.log includes this:

(==) Log file: "/var/log/Xorg.1.log", Time: Sat Jun 28 21:43:47 2008
(==) Using config file: "/etc/X11/xorg.conf"
(II) Module "ddc" already built-in
(EE) Failed to load module "type1" (module does not exist, 0)
(II) Module "ramdac" already built-in

Backtrace:
0: /usr/bin/X(xf86SigHandler+0x7e) [0x80c913e]
1: [0xffffe420]
2: /usr/bin/X(ProcPolyPoint+0x13a) [0x808aeca]
3: /usr/bin/X [0x81547a4]
4: /usr/bin/X(Dispatch+0x314) [0x808dde4]
5: /usr/bin/X(main+0x4b5) [0x8074765]
6: /lib/i686/cmov/libc.so.6(__libc_start_main+0xe0) [0xb7ce5450]
7: /usr/bin/X(FontFileCompleteXLFD+0x219) [0x8073a51]

Fatal server error:
Caught signal 11. Server aborting

The failure to load type1 is typical; the traceback is not. Here are the more typical last entries in kdm.log:
(==) Using config file: "/etc/X11/xorg.conf"
(II) Module "ddc" already built-in
(EE) Failed to load module "type1" (module does not exist, 0)
(II) Module "ramdac" already built-in
Could not init font path element unix/:7100, removing from list!
Could not init font path element /usr/share/fonts/X11/cyrillic, removing from list!
SetClientVersion: 0 9
SetGrabKeysState - disabled
FreeFontPath: FPE "/usr/share/fonts/X11/misc" refcount is 2, should be 1; fixing.
SetGrabKeysState - enabled
SetClientVersion: 0 9

daemon.log has this
Jun 28 21:43:48 corn kdm[6768]: X server for display :0 terminated unexpectedly

kern.log has this
Jun 28 21:42:01 corn kernel: nvidia: module license 'NVIDIA' taints kernel.
Jun 28 21:42:01 corn kernel: ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 16 (level, low) -> IRQ 16
Jun 28 21:42:01 corn kernel: PCI: Setting latency timer of device 0000:01:00.0 to 64
Jun 28 21:42:01 corn kernel: NVRM: loading NVIDIA UNIX x86 Kernel Module 169.12 Thu Feb 14 17:53:07 PST 2008
Jun 28 21:43:48 corn kernel: Xorg[6787]: segfault at 000001a4 eip 08194aaa esp bfc1fdb0 error 4


The attached files were created with tar czf.

RossBoylan 06-29-08 11:44 AM

Re: Spawning new session leads to crash
 
It might be relevant that I have a P4 with hyperthreading. The OS represents this as 2 CPUs, though it's really only got 1.

drbloed 06-29-08 01:47 PM

Re: Spawning new session leads to crash
 
I don't think that this is related to HT, because i got the same
problem on an amd64X2.
It happens since nvidia-drivers >100.14.xx for me and is reproducable.

Howto reproduce:
Run a kde-session, then start another kde-session (owned by another(?) user).
Some minutes later (when using something like flash in a browser or so) session :0 just crashes(back to kdm) while session :1 stays alive.

As my 2 pc are multiuser machines, every ">nvidia-driver-100.14.xx" is totally unuseable.

There are also some threads that seem to be related to this problem
-> http://www.nvnews.net/vbulletin/showthread.php?t=113140
-> http://www.nvnews.net/vbulletin/showthread.php?t=111048

PS: Dear guys @nvidia, could you please create a bugzilla or something like that?
Reporting bugs in this forum is not really helpful, actually nobody
knows if somebody did already file a bug or whatever.
Additionally nobody ever really knows if bugs got fixed.
Thanks for reading ;)

kriko 06-29-08 02:19 PM

Re: Spawning new session leads to crash
 
It is not related to HT, I have an old Athlon64.
Steps to reproduce this are as drbloed described.

nvidia-bugreport seems to include only active log of X, not all.

AaronP 06-29-08 05:34 PM

Re: Spawning new session leads to crash
 
All of the reports of this problem seem to be with xserver 1.4.0.90, so my guess is that some change in that particular server version broke something. Also, I've seen reports of BackingStore causing crashes due to missing GC validation in the server somewhere. For those that have BackingStore enabled, does disabling it fix the problem? Also, please try the nv or vesa drivers to see if they have a similar problem.


All times are GMT -5. The time now is 02:36 AM.

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