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

Newegg Daily Deals

Reply
 
Thread Tools
Old 05-11-06, 03:20 PM   #1
Wille_W
Registered User
 
Join Date: May 2006
Posts: 8
Default Crash when switching between tv-out and another X

I run the tv-out on a different X server than my kde/gnome desktop and i have a problem with crashes when switching between different X servers (one is the tv-out) and the Console with the crtl + alt + F? combinations. Sometimes it crashes the computer totaly, and sometimes just the X server and other times everything works as it should. I'am running fedora core 5 with kernel 2.6.16.9-smp and the newest nvidia drivers. I have tried to use combinations of noapic acpi=off kernel params but with no legible difference in stability. I have attached the dmesg error log below from last crash that only killed my X. It's impossible to fix a crash even it it's just the X server, the same image will stay on the tv all the way until the computer has restarted.


DMESG:
audit(1147380717.288:3): avc: denied { execmod } for pid=1860 comm="Xorg" name="libnvidia-tls.so.1.0.8756" dev=hde1 ino=2453023 scontext=system_u:system_r:xdm_t:s0-s0:c0.c255 tcontext=root:object_r:lib_t:s0 tclass=file
audit(1147380733.489:4): avc: denied { execmod } for pid=1898 comm="X" name="libnvidia-tls.so.1.0.8756" dev=hde1 ino=2453023 scontext=root:system_r:xdm_xserver_t:s0-s0:c0.c255 tcontext=root:object_r:lib_t:s0 tclass=file
Unable to handle kernel paging request at virtual address 00147400
printing eip:
00147400
*pde = 33a55067
*pte = 00000000
Oops: 0000 [#1]
SMP
Modules linked in: ppdev autofs4 nfs lockd nfs_acl sunrpc floppy nvram uhci_hcd nvidia agpgart via686a hwmon parport_pc parport i2c_isa i2c_viapro i2c_core
CPU: 0
EIP: 0060:[<00147400>] Tainted: P VLI
EFLAGS: 00213287 (2.6.16.9 #5)
EIP is at 0x147400
eax: 00147400 ebx: f2e54800 ecx: f3fa0000 edx: f000e7e7
esi: 00000000 edi: ea335af4 ebp: ea33594c esp: ea335930
ds: 007b es: 007b ss: 0068
Process X (pid: 1898, threadinfo=ea334000 task=e6115030)
Stack: <0>f8e92a98 f3fa0000 00000000 00203286 ea335a10 f8e878bb f48af000 ea335a10
f8e878d0 f3fa0000 00000000 00000007 00000000 f8edb7c8 00000000 ea335af4
00000000 f8edba08 f3ddebc0 00000008 00000000 000000ff f48af000 ecf23b60
Call Trace:
[<f8e92a98>] _nv008066rm+0x1c/0x20 [nvidia]
[<f8e878bb>] _nv008217rm+0x3f/0x70c [nvidia]
[<f8e878d0>] _nv008217rm+0x54/0x70c [nvidia]
[<f8edb7c8>] _nv003307rm+0x4ec/0x73c [nvidia]
[<f8edba08>] _nv003307rm+0x72c/0x73c [nvidia]
[<f8e2cb26>] _nv002532rm+0x1a/0x6c [nvidia]
[<f8e1bf2a>] _nv002668rm+0x26/0x2c [nvidia]
[<f8e87872>] _nv008218rm+0x3a/0x44 [nvidia]
[<f8e87859>] _nv008218rm+0x21/0x44 [nvidia]
[<f8e1bf2a>] _nv002668rm+0x26/0x2c [nvidia]
[<f8edf25d>] _nv003088rm+0x87d/0x934 [nvidia]
[<f8e951d2>] _nv008085rm+0x5a/0xa0 [nvidia]
[<f8e8ea51>] _nv008012rm+0x14d/0x188 [nvidia]
[<f8e93155>] _nv008055rm+0x45/0x50 [nvidia]
[<f8e2aed3>] _nv002500rm+0x1b/0x20 [nvidia]
[<f8edf57c>] _nv003094rm+0x268/0x10ac [nvidia]
[<f8f91d71>] _nv005434rm+0x15/0x1c [nvidia]
[<f8f91d71>] _nv005434rm+0x15/0x1c [nvidia]
[<f90733c5>] _nv000338rm+0x49/0x54 [nvidia]
[<f8e02ca2>] _nv009133rm+0x16/0x30 [nvidia]
[<f9070555>] _nv000362rm+0x85/0x22c [nvidia]
[<f90705de>] _nv000362rm+0x10e/0x22c [nvidia]
[<f8e02b6a>] _nv009134rm+0x1a/0x54 [nvidia]
[<f8f6e7aa>] _nv006071rm+0x9a/0xfc [nvidia]
[<f8f91d71>] _nv005434rm+0x15/0x1c [nvidia]
[<f8f6e8cd>] _nv006069rm+0x51/0x5c [nvidia]
[<f8f6e8c3>] _nv006069rm+0x47/0x5c [nvidia]
[<f8f6e9cc>] _nv006072rm+0x74/0x94 [nvidia]
[<f8f6e9e1>] _nv006072rm+0x89/0x94 [nvidia]
[<f8f91d57>] _nv005436rm+0x23/0x28 [nvidia]
[<f8e4671a>] _nv009209rm+0x4a/0x58 [nvidia]
[<f8f90dcc>] _nv005473rm+0x64/0x47c [nvidia]
[<f8e12380>] _nv001840rm+0x8c/0xcc [nvidia]
[<f8e1239f>] _nv001840rm+0xab/0xcc [nvidia]
[<f8e11662>] _nv001857rm+0x1d2/0x1dc [nvidia]
[<f9084428>] os_acquire_sema+0x5a/0x6f [nvidia]
[<f8e2b406>] _nv002584rm+0x12/0x18 [nvidia]
[<f8e0e027>] _nv003363rm+0x33/0x9c [nvidia]
[<f8e0e05d>] _nv003363rm+0x69/0x9c [nvidia]
[<f8e34edd>] _nv001809rm+0x3d/0x5d0 [nvidia]
[<f8e35043>] _nv001809rm+0x1a3/0x5d0 [nvidia]
[<c0104629>] simd_math_error+0x42/0xdd
[<c01b7ddb>] inode_has_perm+0x38/0x57
[<f8e3387c>] rm_ioctl+0x1c/0x24 [nvidia]
[<c0104629>] simd_math_error+0x42/0xdd
[<f90815f6>] nv_kern_ioctl+0x33c/0x397 [nvidia]
[<c01b7e86>] file_has_perm+0x8c/0x91
[<c0104629>] simd_math_error+0x42/0xdd
[<f908167a>] nv_kern_unlocked_ioctl+0x29/0x2d [nvidia]
[<c0104629>] simd_math_error+0x42/0xdd
[<c0164169>] do_ioctl+0x55/0x68
[<c0104629>] simd_math_error+0x42/0xdd
[<c01642c6>] vfs_ioctl+0x59/0x191
[<c0104629>] simd_math_error+0x42/0xdd
[<c0104629>] simd_math_error+0x42/0xdd
[<c016445b>] sys_ioctl+0x5d/0x66
[<c0104629>] simd_math_error+0x42/0xdd
[<c0102827>] sysenter_past_esp+0x54/0x75
[<c0104629>] simd_math_error+0x42/0xdd
Code: Bad EIP value.
Wille_W is offline   Reply With Quote
Old 05-11-06, 04:23 PM   #2
Wille_W
Registered User
 
Join Date: May 2006
Posts: 8
Default Re: Crash when switching between tv-out and another X

I tried to remove my old SB-Live card out of the computer but that did not help anything. Last error log from dmesg attached. Please tell me if you need some more information about my hardware/software configuration.
Attached Files
File Type: log dmesg.log (3.9 KB, 151 views)
Wille_W is offline   Reply With Quote
Old 05-11-06, 06:22 PM   #3
paulcheck
Registered User
 
Join Date: Feb 2005
Posts: 16
Default Re: Crash when switching between tv-out and another X

Willie: You say you run two Xservers...do you mean two screens? Please see my post "8756, Dual Screen...". Let me know if this is the same/similar problem. --Paul
paulcheck is offline   Reply With Quote
Old 05-11-06, 10:44 PM   #4
netllama
NVIDIA Corporation
 
Join Date: Dec 2004
Posts: 8,763
Default Re: Crash when switching between tv-out and another X

Wille_W, please generate and post an nvidia-bug-report.log. Also, does this reproduce with an official FC5 kernel?

Thanks,
Lonni
netllama is offline   Reply With Quote
Old 05-12-06, 07:30 AM   #5
Wille_W
Registered User
 
Join Date: May 2006
Posts: 8
Default Re: Crash when switching between tv-out and another X

Quote:
Originally Posted by netllama
Wille_W, please generate and post an nvidia-bug-report.log. Also, does this reproduce with an official FC5 kernel?
It's the same with last official FC5 kernel to but it seems like it hard locks everytime with the official kernel and most often just the X with my own built kernel. It's only a problem when i use the tv-out, switching between two kde sessions is no problem but directly when i use the tv-out and try to switch back from the blank monitor to my kde session it crashes, same when switching to gdm login session.

Quote:
Originally Posted by paulcheck
Willie: You say you run two Xservers...do you mean two screens? Please see my post "8756, Dual Screen...". Let me know if this is the same/similar problem. --Paul
Paul: It looks similar to your problem but as i just sad, no problem if the tv-out is not activated. I'am not sure about what you mean by to screens/X-servers but this is my config files so i guess you can figure it out. i run this command to start freevo on my tv and i use gdm to log in to kde.

To start freevo:
xinit /usr/bin/xterm -e freevo -- :1 -layout TV &
sleep 5
/usr/bin/xset s off -display :1
Attached Files
File Type: zip nvidia-bug-report.log.zip (23.4 KB, 145 views)
File Type: zip xorg.conf.zip (1.9 KB, 150 views)
Wille_W is offline   Reply With Quote
Old 05-12-06, 04:43 PM   #6
Wille_W
Registered User
 
Join Date: May 2006
Posts: 8
Default Re: Crash when switching between tv-out and another X

I'am just want to add that i'am using the latest bios for my motherboard. Going back to "dos" instead of switching directly between tv-out mode and kde/gnome reduce the risk of a crash a lot, but you are still in a big risk!
//Wille
Wille_W is offline   Reply With Quote
Old 05-12-06, 07:24 PM   #7
paulcheck
Registered User
 
Join Date: Feb 2005
Posts: 16
Default Re: Crash when switching between tv-out and another X

Ok, it looks like you really are running two X servers (eg one starts with :0 and another with :1) as opposed to two screens, where one starts with :0.0 and another with :0.1. The latter configuration is mine. So, our setups are different, but, the symptoms/problem are/is identical.
paulcheck is offline   Reply With Quote
Old 05-15-06, 10:43 AM   #8
Wille_W
Registered User
 
Join Date: May 2006
Posts: 8
Default Re: Crash when switching between tv-out and another X

Quote:
Originally Posted by paulcheck
Ok, it looks like you really are running two X servers (eg one starts with :0 and another with :1) as opposed to two screens, where one starts with :0.0 and another with :0.1. The latter configuration is mine. So, our setups are different, but, the symptoms/problem are/is identical.
Yes.. I have now downgraded to 8178 and everything works perfect again so if i don't hear any more from the developers at nvidia i'll run with that driver untill they release an update. I have nothing against testing a little bit more though, if they come up with an idea about what's wrong.
Wille_W 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 06:31 PM.


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