While loading attached image file, gnome desktop flickers.

sangu · 07-16-11, 11:34 PM

While loading attached image file, gnome desktop flickers.

this image file : http://uploading.com/files/2dd47bme/...rrror.jpg.bz2/

$ dmesg
[...]
[ 9220.396827] NVRM: Xid (0000:02:00): 6, PE0001
[ 9220.409249] NVRM: Xid (0000:02:00): 6, PE0001
[ 9220.422568] NVRM: Xid (0000:02:00): 6, PE0001
[ 9220.435734] NVRM: Xid (0000:02:00): 6, PE0001
[ 9220.446313] NVRM: Xid (0000:02:00): 6, PE0001
[ 9220.456615] NVRM: Xid (0000:02:00): 6, PE0001
[ 9220.466926] NVRM: Xid (0000:02:00): 6, PE0001
[ 9220.477350] NVRM: Xid (0000:02:00): 12, COCOD 00000001 e0019700 00005097 00001880 00321d48

$ cat /var/log/Xorg.0.log
[ 9220.664] (WW) NVIDIA(0): The NVIDIA X driver has encountered too many errors. Falling
[ 9220.666] (WW) NVIDIA(0): back to write-back cached memory.

sandipt · 07-18-11, 04:46 AM

Due to security reason we are unable to download image file. Please provide file as attachment OR upload file somewhere else. Also do some more experiments and let us know reproduction steps for this issue.

artem · 07-18-11, 06:39 AM

Quote:

While loading attached image file, gnome desktop flickers.

Loading where, how, what exactly flickers?

I'm 99% sure it's not his particular image related.

artem · 07-21-11, 05:05 PM

Wow, wow, wow!

All Linux applications here cannot load this image. Instead of the image I see some garbage.

Irfan View under Wine has no problems loading it.

And I also see this error:

Code:

(WW) NVIDIA(0): The NVIDIA X driver has encountered too many errors.  Falling
(WW) NVIDIA(0):     back to write-back cached memory.

Most likely it's not GPU related - it's a problem with drivers.

sandipt, you can download this image here.

mocharhw · 07-22-11, 02:25 AM

Is this some kind of joke that I'm just not getting? I can open this image just fine with any photo viewer application. I use Gnome 2.32 and Nvidia 270.41.06 with a 9500GT card. I opened this image in gthumb, gimagereader, eog, xnviewmp, gimp, you name it..

DeiF · 07-22-11, 05:27 AM

The problem, at least for me, is just Firefox.

With Firefox I get garbage (like artem's screenshot), but with other apps (Gwenview, Gimp, ShowFoto, Okular, etc) I can open the image just fine (like mocharhw).

Edit: I noticed 8 error messages in dmesg like this: "NVRM: Xid (0000:05:00): 6, PE0001" but I don't know if they happened while loading this image or while playing a video with the newest flash.
What is more worrying is that I managed to crash X by opening this image various times (Xorg restarted). Here's the log:

Code:

[  4951.753] (WW) NVIDIA(0): The NVIDIA X driver has encountered too many errors.  Falling
[  4951.753] (WW) NVIDIA(0):     back to write-back cached memory.
[  5488.803]
Backtrace:
[  5488.844] 0: /usr/bin/Xorg (xorg_backtrace+0x28) [0x483068]
[  5488.844] 1: /usr/bin/Xorg (0x400000+0x5e6d9) [0x45e6d9]
[  5488.844] 2: /lib64/libc.so.6 (0x7f0de38e8000+0x32b30) [0x7f0de391ab30]
[  5488.844] 3: /usr/lib64/xorg/modules/drivers/nvidia_drv.so (0x7f0ddf0a0000+0xe2115) [0x7f0ddf182115]
[  5488.844] 4: /usr/lib64/xorg/modules/drivers/nvidia_drv.so (0x7f0ddf0a0000+0xe49c2) [0x7f0ddf1849c2]
[  5488.844] 5: /usr/lib64/xorg/modules/drivers/nvidia_drv.so (0x7f0ddf0a0000+0xbac96) [0x7f0ddf15ac96]
[  5488.844] 6: /usr/lib64/xorg/modules/drivers/nvidia_drv.so (0x7f0ddf0a0000+0xbb332) [0x7f0ddf15b332]
[  5488.844] 7: /usr/lib64/xorg/modules/drivers/nvidia_drv.so (0x7f0ddf0a0000+0x7ed9e) [0x7f0ddf11ed9e]
[  5488.844] 8: /usr/lib64/xorg/modules/drivers/nvidia_drv.so (0x7f0ddf0a0000+0xe3eaf) [0x7f0ddf183eaf]
[  5488.844] 9: /usr/lib64/xorg/modules/drivers/nvidia_drv.so (0x7f0ddf0a0000+0x418d00) [0x7f0ddf4b8d00]
[  5488.844] 10: /usr/lib64/xorg/modules/drivers/nvidia_drv.so (0x7f0ddf0a0000+0x417375) [0x7f0ddf4b7375]
[  5488.844] 11: /usr/lib64/xorg/modules/drivers/nvidia_drv.so (0x7f0ddf0a0000+0x418f3d) [0x7f0ddf4b8f3d]
[  5488.844] 12: /usr/bin/Xorg (0x400000+0xc0de0) [0x4c0de0]
[  5488.844] 13: /usr/bin/Xorg (0x400000+0x4f023) [0x44f023]
[  5488.844] 14: /usr/bin/Xorg (0x400000+0x52561) [0x452561]
[  5488.844] 15: /usr/bin/Xorg (0x400000+0x25ace) [0x425ace]
[  5488.844] 16: /lib64/libc.so.6 (__libc_start_main+0xfd) [0x7f0de3906bfd]
[  5488.845] 17: /usr/bin/Xorg (0x400000+0x25679) [0x425679]
[  5488.845] Segmentation fault at address (nil)
[  5488.845]
Fatal server error:
[  5488.845] Caught signal 11 (Segmentation fault). Server aborting
[  5488.845]
[  5488.845]
Please consult the The X.Org Foundation support
         at http://wiki.x.org
 for help.
[  5488.845] Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[  5488.845]
[  5488.863] (II) Power Button: Close
[  5488.863] (II) UnloadModule: "evdev"
[  5488.865] (II) Power Button: Close
[  5488.865] (II) UnloadModule: "evdev"
[  5488.867] (II) AVerMedia A815: Close
[  5488.867] (II) UnloadModule: "evdev"
[  5488.869] (II) IR-receiver inside an USB DVB receiver: Close
[  5488.869] (II) UnloadModule: "evdev"
[  5488.871] (II) UVC Camera (046d:0825): Close
[  5488.871] (II) UnloadModule: "evdev"
[  5488.873] (II) AT Translated Set 2 keyboard: Close
[  5488.873] (II) UnloadModule: "evdev"
[  5488.877] (II) ImExPS/2 Logitech Explorer Mouse: Close
[  5488.877] (II) UnloadModule: "evdev"

Using the 280.04 driver in a GT240 card.

leigh123linux · 07-22-11, 07:12 AM

No issues here with firefox

http://www.fedoraforum.org/leigh123l...screenshot.jpg

Code:

[leigh@main_pc ~]$ rpm -qa kmod-nvidia\*  kernel\* |sort
kernel-2.6.39.1-1.el6.x86_64
kernel-3.0-0.rc6.git6.1.el6.x86_64
kernel-3.0-1.el6.x86_64
kernel-devel-2.6.39.1-1.el6.x86_64
kernel-devel-3.0-0.rc6.git6.1.el6.x86_64
kernel-devel-3.0-1.el6.x86_64
kernel-headers-3.0-1.el6.x86_64
kmod-nvidia-3.0-0.rc6.git6.1.el6.x86_64-270.41.19-2.el6.x86_64
kmod-nvidia-3.0-1.el6.x86_64-270.41.19-2.el6.x86_64
[leigh@main_pc ~]$ uname -r
3.0-1.el6.x86_64
[leigh@main_pc ~]$

yumkam · 07-22-11, 08:17 AM

Maybe effect depends on libjpeg version (and kind - there are ABI-compatible SIMD-optimized replacement from libjpeg-turbo and [older jpeg-simd])?
Maybe running running image viewer and djpeg -dct float <image.jpeg >/dev/null (same with -dct int and -dct fast) in valgrind (and valgrind --tool=exp-ptrcheck) will give more insight (you'll need debug info for libjpeg for that).
Maybe it's not particular image, but just specific image resolution?

07-18-11, 04:46 AM	#2
sandipt NVIDIA Corporation Join Date: Dec 2010 Posts: 259	Re: While loading attached image file, gnome desktop flickers. Due to security reason we are unable to download image file. Please provide file as attachment OR upload file somewhere else. Also do some more experiments and let us know reproduction steps for this issue.

07-21-11, 05:05 PM	#4
artem Registered User Join Date: Jun 2006 Posts: 681	Re: While loading attached image file, gnome desktop flickers. Wow, wow, wow! All Linux applications here cannot load this image. Instead of the image I see some garbage. Irfan View under Wine has no problems loading it. And I also see this error: Code: (WW) NVIDIA(0): The NVIDIA X driver has encountered too many errors. Falling (WW) NVIDIA(0): back to write-back cached memory. Most likely it's not GPU related - it's a problem with drivers. sandipt, you can download this image here. Attached Thumbnails

07-22-11, 02:25 AM	#5
mocharhw Registered User Join Date: May 2008 Posts: 113	Re: While loading attached image file, gnome desktop flickers. Is this some kind of joke that I'm just not getting? I can open this image just fine with any photo viewer application. I use Gnome 2.32 and Nvidia 270.41.06 with a 9500GT card. I opened this image in gthumb, gimagereader, eog, xnviewmp, gimp, you name it.. Attached Thumbnails

07-22-11, 08:17 AM	#8
yumkam Registered User Join Date: Jul 2007 Posts: 5	Re: While loading attached image file, gnome desktop flickers. Maybe effect depends on libjpeg version (and kind - there are ABI-compatible SIMD-optimized replacement from libjpeg-turbo and [older jpeg-simd])? Maybe running running image viewer and djpeg -dct float <image.jpeg >/dev/null (same with -dct int and -dct fast) in valgrind (and valgrind --tool=exp-ptrcheck) will give more insight (you'll need debug info for libjpeg for that). Maybe it's not particular image, but just specific image resolution?