LinuxQuestions.org
Visit the LQ Articles and Editorials section
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - General
User Name
Password
Linux - General This Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.

Notices

Reply
 
Search this Thread
Old 05-09-2005, 11:07 PM   #1
molgrum
LQ Newbie
 
Registered: May 2005
Posts: 2

Rep: Reputation: 0
Nvidia and Xorg freeze when switching tty/X


Hi.
I have a strange problem with system freeze that seems to follow a certain pattern. The problem isn't _inside_ X, that part is working just fine. The problem is when switching to a tty (like CTRL+ALT+F1) and back to X again, and then back to the tty and THEN when i try to switch to X a second time the system freezes! What I can see then is the tty, with the blinking cursor gone, and it just holds there and does nothing. Music goes on playing, servers work fine, but I can't do shit! The logs doesn't seem to report anything either. Worth mentioning is that if I start X, switch to a tty and kill X, restart X and switch to the tty and repeat this, I can go on forever. So if I play a game that halts and I need to go to a tty to kill it, then X grant me ONLY THIS one wish and I can then safely go back to X ONLY THIS one time, and after that I can never ever go back to X after switching to a tty a second time...

I run latest Slackware (10.1), latest nvidia drivers and xorg, my card is a Geforce 4 Ti 4200.

EDIT:

I get this strange message in my syslog when the bug occurs:
Code:
May 10 05:47:05 gravity kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000080
May 10 05:47:05 gravity kernel:  printing eip:
May 10 05:47:05 gravity kernel: e0f4460b
May 10 05:47:05 gravity kernel: *pde = 00000000
May 10 05:47:05 gravity kernel: Oops: 0000 [#1]
May 10 05:47:05 gravity kernel: PREEMPT
May 10 05:47:05 gravity kernel: Modules linked in: w83627hf eeprom i2c_sensor i2c_isa i2c_viapro nvidia
May 10 05:47:05 gravity kernel: CPU:    0
May 10 05:47:05 gravity kernel: EIP:    0060:[<e0f4460b>]    Tainted: P      VLI
May 10 05:47:05 gravity kernel: EFLAGS: 00013287   (2.6.11.8)
May 10 05:47:05 gravity kernel: EIP is at _nv006639rm+0xf/0x20 [nvidia]
May 10 05:47:05 gravity kernel: eax: 00000000   ebx: ffffffff   ecx: d5ae0000   edx: d4edb000
May 10 05:47:05 gravity kernel: esi: 00000000   edi: d5ae0000   ebp: d7e15dac   esp: d7e15d9c
May 10 05:47:05 gravity kernel: ds: 007b   es: 007b   ss: 0068
May 10 05:47:05 gravity kernel: Process Xorg (pid: 3334, threadinfo=d7e15000 task=df6340e0)
May 10 05:47:05 gravity kernel: Stack: d7e15dbc e0f289a3 d457f800 000000eb d7e15e0c e0f142cb d5ae0000 00000000
May 10 05:47:05 gravity kernel:        d5ae0000 d4edb000 d5ae0000 d4edb000 0000003b d7e15e0b d4edb000 00000000
May 10 05:47:05 gravity kernel:        e0a9800c e0ee0eaa df58b400 dfdb73a0 d7e15e0c e0f4773d d5ae0000 00000000
May 10 05:47:05 gravity kernel: Call Trace:
May 10 05:47:05 gravity kernel:  [<e0f289a3>] _nv003296rm+0x3f/0x4c [nvidia]
May 10 05:47:05 gravity kernel:  [<e0f142cb>] _nv006582rm+0x18b/0x304 [nvidia]
May 10 05:47:05 gravity kernel:  [<e0ee0eaa>] _nv001889rm+0x36/0xe0 [nvidia]
May 10 05:47:05 gravity kernel:  [<e0f4773d>] _nv006757rm+0x19/0x20 [nvidia]
May 10 05:47:05 gravity kernel:  [<e0ef30c0>] _nv001180rm+0xc4/0x128 [nvidia]
May 10 05:47:05 gravity kernel:  [<e0ee0eaa>] _nv001889rm+0x36/0xe0 [nvidia]
May 10 05:47:05 gravity kernel:  [<e1100446>] os_release_sema+0x45/0x78 [nvidia]
May 10 05:47:05 gravity kernel:  [<e0ef364e>] _nv001291rm+0xe2/0x278 [nvidia]
May 10 05:47:05 gravity kernel:  [<e0eedef6>] _nv001740rm+0x12/0x18 [nvidia]
May 10 05:47:05 gravity kernel:  [<e0ef4a3e>] rm_change_res_mode+0x32/0x9c [nvidia]
May 10 05:47:05 gravity kernel:  [<e0ef4a82>] rm_change_res_mode+0x76/0x9c [nvidia]
May 10 05:47:05 gravity kernel:  [<e0ef595d>] _nv001201rm+0x3d/0x618 [nvidia]
May 10 05:47:05 gravity kernel:  [<e0ef5c77>] _nv001201rm+0x357/0x618 [nvidia]
May 10 05:47:05 gravity kernel:  [<c0104648>] die_nmi+0x28/0xa0
May 10 05:47:05 gravity kernel:  [<c0352c7d>] pci_read+0x3d/0x50
May 10 05:47:05 gravity kernel:  [<e0ef49f7>] rm_ioctl+0x23/0x38 [nvidia]
May 10 05:47:05 gravity kernel:  [<c0104648>] die_nmi+0x28/0xa0
May 10 05:47:05 gravity kernel:  [<e10fd747>] nv_kern_ioctl+0x38c/0x3df [nvidia]
May 10 05:47:05 gravity kernel:  [<c0104648>] die_nmi+0x28/0xa0
May 10 05:47:05 gravity kernel:  [<c01693ef>] do_ioctl+0x6f/0xa0
May 10 05:47:05 gravity kernel:  [<c0104648>] die_nmi+0x28/0xa0
May 10 05:47:05 gravity kernel:  [<c0169645>] vfs_ioctl+0x65/0x1e0
May 10 05:47:05 gravity kernel:  [<c0104648>] die_nmi+0x28/0xa0
May 10 05:47:05 gravity kernel:  [<c0169805>] sys_ioctl+0x45/0x80
May 10 05:47:05 gravity kernel:  [<c0104648>] die_nmi+0x28/0xa0
May 10 05:47:05 gravity kernel:  [<c010325b>] syscall_call+0x7/0xb
May 10 05:47:05 gravity kernel:  [<c0104648>] die_nmi+0x28/0xa0
May 10 05:47:05 gravity kernel: Code: 31 c0 8d 65 e8 5b 5e 89 ec 5d c3 90 55 89 e5 8b 45 0c 8b 80 b8 0b 00 00 89 ec 5d c3 55
 89 e5 83 ec 08 8b 4d 08 8b 45 0c 83 c4 f8 <8b> 90 80 00 00 00 50 51 8b 42 04 ff d0 89 ec 5d c3 55 89 e5 8b

Last edited by molgrum; 05-10-2005 at 12:47 AM.
 
Old 05-10-2005, 06:38 AM   #2
__J
Senior Member
 
Registered: Dec 2004
Distribution: Slackware, ROCK
Posts: 1,973

Rep: Reputation: 46
the nvidia drivers have always been buggy, and react different to different hardware configurations. I used to get this problem all of the time, either freezing or horribly garbled lines through the screen after re-entering X from a console. I have a different mobo now and don't have the problem anymore ( the old mobo had an nforce chipset, and it worked so-so with a nvidia card and drivers, but a sis chipset works good ???).
 
Old 05-10-2005, 01:52 PM   #3
molgrum
LQ Newbie
 
Registered: May 2005
Posts: 2

Original Poster
Rep: Reputation: 0
My nvidia conf section from xorg.conf:
Code:
Section "Device"
    Identifier  "My Video Card"
    Vendor      "Nvidia Corporation"
    Driver      "nvidia"
    BusID       "PCI:1:0:0"
    Option      "IgnoreDisplayDevices"  "TV"
    Option      "NoFlip"                "false"
    Option      "NoLogo"                "true"
    Option      "NoRenderExtension"     "false"
    Option      "NvAGP"                 "3"
    Option      "RenderAccel"           "false"
    #VideoRam    32768
    # Insert Clocks lines here if appropriate
EndSection
Any other configuration file that affects Geforce hardware?
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

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


Similar Threads
Thread Thread Starter Forum Replies Last Post
New nVidia Driver & Xorg Freeze drowbot Linux - Hardware 19 04-16-2005 09:59 PM
Window managers freeze xorg kaon Slackware 5 02-09-2005 08:45 AM
Switching From Xorg to Xfree86 4.3.0 predator.hawk Slackware 7 09-27-2004 02:48 PM
Gnome 2.6 freeze, slackware-current, Xorg maciek Slackware 6 08-31-2004 09:50 AM
Strange pointer after switching X <-> tty Florio Linux - Software 5 12-16-2002 10:11 AM


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

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration