Ubuntu
linux-restricted-modules-2.6.20 package

[nvidia-glx-new] Graphical Freeze when using 3d apps with nvidia-glx

Bug #112473 reported by Joseph Maillardet
8
Affects Status Importance Assigned to Milestone
linux-restricted-modules-2.6.20 (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

When asking "big job" to my graphical card like running compiz+blender, OpenArena, FlightGear, etc ... the display seem to freeze - sometime with operational mouse -

-> To solve the problem I just have to wait 10~30 seconds.

***

Found in syslog :

May 4 21:55:14 casa kernel: [ 2591.009827] nvidia: module license 'NVIDIA' taints kernel.
May 4 21:55:14 casa kernel: [ 2591.260997] ACPI: PCI Interrupt 0000:04:00.0[A] -> GSI 16 (level, low) -> IRQ 16
May 4 21:55:14 casa kernel: [ 2591.261392] PCI: Setting latency timer of device 0000:04:00.0 to 64
May 4 21:55:14 casa kernel: [ 2591.262512] NVRM: loading NVIDIA Linux x86 Kernel Module 1.0-9631 Thu Nov 9 17
:38:10 PST 2006
May 4 21:55:15 casa kernel: [ 2591.645016] **WARNING** I2C adapter driver [NVIDIA i2c adapter 0 at 4:00.0] forgo
t to specify physical device; fix it!
May 4 21:55:15 casa kernel: [ 2591.646790] **WARNING** I2C adapter driver [NVIDIA i2c adapter 1 at 4:00.0] forgo
t to specify physical device; fix it!
May 4 21:55:15 casa kernel: [ 2591.648238] **WARNING** I2C adapter driver [NVIDIA i2c adapter 2 at 4:00.0] forgo
t to specify physical device; fix it!

(...) -> running OpenArena ~ 22:48

May 4 22:50:12 casa kernel: [ 5880.341198] NVRM: os_map_kernel_space: can't map 0xe0008000, invalid context!
May 4 22:50:12 casa kernel: [ 5880.341208] NVRM: os_map_kernel_space: can't map 0xe0008000, invalid context!
May 4 22:50:12 casa kernel: [ 5880.341215] NVRM: os_map_kernel_space: can't map 0xe0008000, invalid context!
May 4 22:50:12 casa kernel: [ 5880.341220] NVRM: os_map_kernel_space: can't map 0xe0008000, invalid context!
May 4 22:50:12 casa kernel: [ 5880.341226] NVRM: os_map_kernel_space: can't map 0xe0008000, invalid context!
May 4 22:50:12 casa kernel: [ 5880.341233] NVRM: os_map_kernel_space: can't map 0xe0008000, invalid context!
May 4 22:50:12 casa kernel: [ 5880.341240] NVRM: os_map_kernel_space: can't map 0xe0008000, invalid context!
May 4 22:50:12 casa kernel: [ 5880.341247] NVRM: os_map_kernel_space: can't map 0xe0008000, invalid context!
May 4 22:50:12 casa kernel: [ 5880.341255] NVRM: os_map_kernel_space: can't map 0xe0008000, invalid context!
May 4 22:50:12 casa kernel: [ 5880.341262] NVRM: os_map_kernel_space: can't map 0xe0008000, invalid context!
May 4 22:50:12 casa kernel: [ 5880.341269] NVRM: os_map_kernel_space: can't map 0xe0008000, invalid context!
May 4 22:50:12 casa kernel: [ 5880.341276] NVRM: os_map_kernel_space: can't map 0xe0008000, invalid context!
May 4 22:50:12 casa kernel: [ 5880.341283] NVRM: os_map_kernel_space: can't map 0xe0008000, invalid context!
May 4 22:50:12 casa kernel: [ 5880.341299] NVRM: Xid (0004:00): 8, Channel 00000020
May 4 22:50:12 casa kernel: [ 5880.341970] NVRM: Xid (0004:00): 29, L1 -> L0
May 4 22:50:16 casa kernel: [ 5884.332221] NVRM: os_map_kernel_space: can't map 0xe0008000, invalid context!
May 4 22:50:16 casa kernel: [ 5884.332229] NVRM: os_map_kernel_space: can't map 0xe0008000, invalid context!
May 4 22:50:16 casa kernel: [ 5884.332235] NVRM: os_map_kernel_space: can't map 0xe0008000, invalid context!
May 4 22:50:16 casa kernel: [ 5884.332240] NVRM: os_map_kernel_space: can't map 0xe0008000, invalid context!
May 4 22:50:16 casa kernel: [ 5884.332244] NVRM: os_map_kernel_space: can't map 0xe0008000, invalid context!
May 4 22:50:16 casa kernel: [ 5884.332249] NVRM: os_map_kernel_space: can't map 0xe0008000, invalid context!
May 4 22:50:16 casa kernel: [ 5884.332254] NVRM: os_map_kernel_space: can't map 0xe0008000, invalid context!
May 4 22:50:16 casa kernel: [ 5884.332259] NVRM: os_map_kernel_space: can't map 0xe0008000, invalid context!
May 4 22:50:16 casa kernel: [ 5884.332264] NVRM: os_map_kernel_space: can't map 0xe0008000, invalid context!
May 4 22:50:16 casa kernel: [ 5884.332271] NVRM: os_map_kernel_space: can't map 0xe0008000, invalid context!
May 4 22:50:16 casa kernel: [ 5884.332303] NVRM: os_map_kernel_space: can't map 0xe0008000, invalid context!
May 4 22:50:16 casa kernel: [ 5884.332308] NVRM: os_map_kernel_space: can't map 0xe0008000, invalid context!
May 4 22:50:16 casa kernel: [ 5884.332313] NVRM: os_map_kernel_space: can't map 0xe0008000, invalid context!
May 4 22:50:16 casa kernel: [ 5884.332328] NVRM: Xid (0004:00): 4, Ch 00000002 SC 00000001 M 00001818 Data 3e105
7bb
May 4 22:50:16 casa kernel: [ 5884.333025] NVRM: Xid (0004:00): 29, L0 -> L0

***

Fresh install of Feisty (i386) with nvidia-glx -- all up-to-date

***

M.B. Asus socket 775 fanless, chipset Intel
Proc. Pentium 4 HT
RAM DDR2 1G
G.C. Gigabyte 7600GT fanless

***

xorg.conf tweak :
Section "Screen"
...
    Option "RenderAccel" "True"
    Option "AllowGLXWithComposite" "True"
    Option "AddARGBGLXVisuals" "True"
...
EndSection
Section "Extensions"
    Option "Composite" "Enable"
EndSection

Thanks for help.

Revision history for this message
Joseph Maillardet (jokx) wrote :

Juste trying nvidia-glx-new

Same problem.

***

Found in syslog :

-> Running OpenArena ~ 23:42:12 ! :-/

May 4 23:42:16 casa kernel: [ 93.753881] NVRM: os_map_kernel_space: can't map 0xe0008000, invalid context!
May 4 23:42:16 casa kernel: [ 93.753890] NVRM: os_map_kernel_space: can't map 0xe0008000, invalid context!
May 4 23:42:16 casa kernel: [ 93.753896] NVRM: os_map_kernel_space: can't map 0xe0008000, invalid context!
May 4 23:42:16 casa kernel: [ 93.753900] NVRM: os_map_kernel_space: can't map 0xe0008000, invalid context!
May 4 23:42:16 casa kernel: [ 93.753904] NVRM: os_map_kernel_space: can't map 0xe0008000, invalid context!
May 4 23:42:16 casa kernel: [ 93.753908] NVRM: os_map_kernel_space: can't map 0xe0008000, invalid context!
May 4 23:42:16 casa kernel: [ 93.753914] NVRM: os_map_kernel_space: can't map 0xe0008000, invalid context!
May 4 23:42:16 casa kernel: [ 93.753921] NVRM: os_map_kernel_space: can't map 0xe0008000, invalid context!
May 4 23:42:16 casa kernel: [ 93.753927] NVRM: os_map_kernel_space: can't map 0xe0008000, invalid context!
May 4 23:42:16 casa kernel: [ 93.753933] NVRM: os_map_kernel_space: can't map 0xe0008000, invalid context!
May 4 23:42:16 casa kernel: [ 93.753939] NVRM: os_map_kernel_space: can't map 0xe0008000, invalid context!
May 4 23:42:16 casa kernel: [ 93.753946] NVRM: os_map_kernel_space: can't map 0xe0008000, invalid context!
May 4 23:42:16 casa kernel: [ 93.753952] NVRM: os_map_kernel_space: can't map 0xe0008000, invalid context!
May 4 23:42:16 casa kernel: [ 93.753965] NVRM: Xid (0004:00): 8, Channel 00000002
May 4 23:42:16 casa kernel: [ 93.754612] NVRM: Xid (0004:00): 30, L1 -> L0

need help :'-(

Revision history for this message
Joseph Maillardet (jokx) wrote :

Get a try to the 64bit edition of ubuntu, same result with nvidia-glx & nvidia-glx-new

Revision history for this message
Sitsofe Wheeler (sitsofe) wrote :

Joseph:
Since you are seeing an NVRM Xid your best is to contact NVIDIA as mentioned in the troubleshooting section of https://help.ubuntu.com/community/BinaryDriverHowto/Nvidia#troubleshooting .

Revision history for this message
sirianni (eric-sirianni) wrote :

I have similar problems but I don't see any "Xid" errors. This caused my system to lock up and then reboot itself:

Jan 3 17:34:37 localhost kernel: [97047.912612] NVRM: os_map_kernel_space: can't map 0xe0008000, invalid context!
Jan 3 17:34:37 localhost kernel: [97047.912622] NVRM: os_map_kernel_space: can't map 0xe0008000, invalid context!
Jan 3 17:34:37 localhost kernel: [97047.912629] NVRM: os_map_kernel_space: can't map 0xe0008000, invalid context!
Jan 3 17:34:37 localhost kernel: [97047.912633] NVRM: os_map_kernel_space: can't map 0xe0008000, invalid context!
Jan 3 17:34:37 localhost kernel: [97047.912637] NVRM: os_map_kernel_space: can't map 0xe0008000, invalid context!
Jan 3 17:34:37 localhost kernel: [97047.912641] NVRM: os_map_kernel_space: can't map 0xe0008000, invalid context!
Jan 3 17:34:37 localhost kernel: [97047.912645] NVRM: os_map_kernel_space: can't map 0xe0008000, invalid context!
Jan 3 17:34:37 localhost kernel: [97047.912650] NVRM: os_map_kernel_space: can't map 0xe0008000, invalid context!
Jan 3 17:34:37 localhost kernel: [97047.912656] NVRM: os_map_kernel_space: can't map 0xe0008000, invalid context!
Jan 3 17:34:37 localhost kernel: [97047.912662] NVRM: os_map_kernel_space: can't map 0xe0008000, invalid context!
Jan 3 17:34:37 localhost kernel: [97047.912669] NVRM: os_map_kernel_space: can't map 0xe0008000, invalid context!
Jan 3 17:34:37 localhost kernel: [97047.912675] NVRM: os_map_kernel_space: can't map 0xe0008000, invalid context!
Jan 3 17:34:37 localhost kernel: [97047.912681] NVRM: os_map_kernel_space: can't map 0xe0008000, invalid context!
Jan 3 17:35:33 localhost syslogd 1.4.1#21ubuntu3: restart.

Revision history for this message
Motin (motin) wrote :

@sirlanni: Since you're symptoms are different you should report a separate bug report. First, you should however follow the guidelines on the Nvidia forums as mentioned above. This way your problem will more likely be addressed.

@Joseph: Are you still experiencing this with updated drivers?
Please feel free to close this bug report if the issue has been fixed upstream.
Thanks!

Revision history for this message
Bryce Harrington (bryce) wrote : linux-restricted-modules-2.6.20 is obsolete

This package has become obsolete so we're closing out the bug report as WONTFIX.
Thanks for reporting it though!

Changed in linux-restricted-modules-2.6.20:
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.