nV News Forums

 
 

nV News Forums (http://www.nvnews.net/vbulletin/index.php)
-   NVIDIA Linux (http://www.nvnews.net/vbulletin/forumdisplay.php?f=14)
-   -   VDPAU error "NNNN 60 5", "NNNN 58 5", and "NNNN 43 5" (http://www.nvnews.net/vbulletin/showthread.php?t=130690)

Stephen Warren 03-26-09 04:48 PM

VDPAU error "NNNN 60 5", "NNNN 58 5", and "NNNN 43 5"
 
This thread is for discussion of the following VDPAU error messages:

VDPAU nvidia: Error detected NNNN 60 5
VDPAU nvidia: Error detected NNNN 58 5
VDPAU nvidia: Error detected NNNN 43 5

Where NNNN is some number, and may vary between drivers versions.

We have reproduced "NNNN 43 5", but don't have any further information to announce yet.

We have not managed to reproduce "NNNN 58 5", but believe that it's the same basic issue as "NNNN 43 5". However, we would like to confirm this on actual silicon; if you are experiencing this issue, and are willing to ship us your HW (just the graphics board for desktop PCs), please contact me.

We have not managed to reproduce "NNNN 60 5", and have not yet determined any possible cause. Again, we would like to investigate this on actual silicon; if you are experiencing this issue, and are willing to ship us your HW (just the graphics board for desktop PCs), please contact me.

---------------------------------

I'm adding the following addendum to the message above to save users from having to search for these instructions in the middle of this long thread:

The problems covered by this thread manifest as the following error codes printed by the driver when "export VDPAU_NVIDIA_DEBUG=3" is set:

In drivers up to 185.18.14: VdpDecoderCreate will return VDP_STATUS_ERROR (25), and print error message "NNNN 43 5", or "NNNN 58 5", or "NNNN 60 5"

In drivers after 185.18.14: vdp_device_create_x11 will return VDP_STATUS_NO_IMPLEMENTATION (1), and print error message "0 NNNN".

In all cases, "NNNN" is a number that may vary based on driver version.

NOTE: Not all error codes of the form above indicate one of the specific problems covered by this thread.

To confirm you're seeing one of the exact issues covered by this thread, you will need to test *both* with driver version less than or equal to 185.18.14, and a driver version *after* 185.18.14. Please post the error messages produced by both driver versions, the exact driver versions tested, and an "nvidia bug report". An NVIDIA engineer will interpret those error messages to confirm whether you are affected by one of those problems.

DeiF 03-27-09 06:13 AM

Re: VDPAU error "NNNN 60 5" and "NNNN 43 5"
 
1) I remember that this problem occurred with 185.13. Not sure about 180.41.

2) and 3) There's no BIOS upgrade for my comp.

4) I'm sure it happens between cold reboots. Not sure after hibernate/resume.
It happens with every video AFAIK, with no other apps using XV or VDPAU.

5) I tried logging with Xfce and LXDE, and running vdpau from a Xterm.
I also tried disabling the composite extension (Composite "off"), and removing some NVidia options that I added manually, just to be sure.
I have yet to try your suggestion with SSH, but I don't have my laptop at hand at the moment (the graphic card was damaged after <1 year of use, so I'm returning it to the reseller for a replacement).

6) I had nothing externally plugged in the laptop, except the AC adaptor.

7) No overcloking from my part (maybe the manufacturer overclocked the card, I dunno). I had a plasmoid showing the GPU's temperature all the time. Temp at idle was about 75șC, in use 85șC (I never saw it reaching 90șC). I don't know if that is normal or not.

8) The laptop was a Clevo M665SRU. VDPAU worked in the first drivers that supported it, with no additional config, running KDE 4.2 with effects on.

9) I don't remember seeing any of that in dmesg, but I cannot be sure since I don't have the laptop at hand.


When I'll get my laptop repaired I'll look after these things more carefully. Thank you for your support.

Stephen Warren 03-27-09 10:38 AM

Re: VDPAU error "NNNN 60 5" and "NNNN 43 5"
 
DeiF,

A yes, I think I recall you saying that it used to work.

All,

It'd be very useful to know exactly which driver release broke it. I know it's a lot of work, but could you try each release in turn, starting from the oldest, to find out? 180.06 180.08, 180.11, 180.16, 180.18 (DeiF reported the problem against this release, so I assume this is broken for everyone there. If not, please keep going through all releases on download.nvidia.com)

Thanks very much!

bluebenno 03-29-09 05:40 PM

Re: VDPAU error "NNNN 60 5" and "NNNN 43 5"
 
Thanks for the help very much appreciated. I look into this, this week and report back in detail.

- The BIOS on the motherboard is very old, so just the excuse I need to flash it. There are recent updates and they use the word "nvidia". I didn't look in detail so plz don't jump to any conclusions! For sure I try this as soon as I can.

- Occurs 100% of the time. I have a an AOpen i975Xa-YDG motherboard with an 9400GT ( G86 core ) running with the mother of all heatsinks that I get cheapas on ebay from China. Rig runs Fedora10 and every driver I tried thus far ( haven't tried 180.41 ). It also occurred under Ubuntu before I reinstall with F10. Even with just X, running from SSH the vdpinfo program [always] fails.


Thanks again, Cheers Benno - will update as soon as I can...

saly 03-31-09 03:45 PM

Re: VDPAU error "NNNN 60 5" and "NNNN 43 5"
 
Hi! After updating my BIOS and suspending, my computer is broken and heading to the service center as soon as possible, so I cannot answer everything, but as much as I can respond:

1) Not working in 185.13
2) 3) Updated, VDPAU did not work and after suspend :-P
4) Yes. Suspend/Hibernation never worked on my PC in Linux(the only thing, but really useful)
5) I tried every combination. I cannot test SSH so far, I will do it as soon as my laptop will be repaired.
6) No.
7) No.
8) No.
9) No.

Some logs provided here: http://www.nvnews.net/vbulletin/showthread.php?t=130035
By the way, it should be good idea to lock the thread above and the threads, that complain about this bug and left just this, where are you asking about circumstances?

bluebenno 04-03-09 05:06 AM

Re: VDPAU error "NNNN 60 5" and "NNNN 43 5"
 
Hi, Here are my findings. I have quite an adventure as guess what I was doing when the big blackout happened in Sydney - upgrading my BIOS! I'm very lucky I just lose my settings.


1) Does this problem reproduce on the latest drivers; please try both 180.41 and 185.13
Yes (both)

2) Please try upgrading your system BIOS (see motherboard/PC manufacturer)
Upgraded to latest - no change.

3) Please try upgrading your video BIOS (see motherboard/PC manufacturer for integrated GPUs, see video card manufacturer for plugin cards)
I haven't seen an upgrade for my card - it's a noname ebay special. 9400GT G86 core.

4) Does the problem happen 100% of the time. Does it only happen after hibernate/resume, or after cold power cycles and reboots too?
100% of the time

5) Are you running any OpenGL applications (or compositing managers) or any other applications that use video (Xv) or VDPAU? Can you try starting a bare X server (e.g. choose a cut-down X session from the X display manager, or quit X, log in via SSH, start X by running "sudo X", then run your VDPAU application from SSH too)

No. All testing done from vanilla session from ssh ( using vdpinfo ). Blackbox and TWM used as window managers.



6) Do you have any unusual PCI cards plugged in. Does the issue occur if you remove them?
Have TV card that has USB hub in it - I removed all cards still occurs.


7) Have you overclocked any of your CPU, RAM, or video card? Does the issue occur if you don't?
n/a don't overclock.


8) Anything else different/unusual about your setup?
It's a full size Aopen motherboard that tapes laptop cpu's, it has a T2700 in it.


9) Do you see any messages in your system log of the form "NVRM: Xid: ..."
No.


I do see this in syslog:

Apr 4 07:01:28 localhost kernel: NVRM: loading NVIDIA UNIX x86 Kernel Module 185.13 Thu Mar 12 17:57:13 PST 2009
Apr 4 07:03:54 localhost kernel: nvidia: module license 'NVIDIA' taints kernel.
Apr 4 07:03:54 localhost kernel: nvidia 0000:02:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
Apr 4 07:03:54 localhost kernel: NVRM: loading NVIDIA UNIX x86 Kernel Module 185.13 Thu Mar 12 17:57:13 PST 2009
Apr 4 07:06:15 localhost kernel: IRQ 16/nvidia: IRQF_DISABLED is not guaranteed on shared IRQs

- there is some stuff about the shared IRQ on google.



Let me know if you want me to try anything - for sure I'm up for it :-)




Much thanks cheers Ben



edit................................

I've now tried the following drivers - none of them work!

180.06
180.08
180.11.02
180.11
180.16
180.18
180.25
180.27
180.29
180.44
185.13

Recall the error I'm getting is from 'vdpinfo' is:

Code:

./vdpinfo
display: :0.0  screen: 0
Error creating VDPAU device: 25


export VDPAU_TRACE=1
export VDPAU_NVIDIA_DEBUG=3

./vdpinfo
display: :0.0  screen: 0
VDPAU capture: Enabled
vdp_imp_device_create_x11(0x9d95008, 0, -, -)
VDPAU nvidia: Error detected 1029 60  5
VDPAU nvidia: Backtrace:
01: /usr/lib/libvdpau_nvidia.so [0x34b33e]
02: /usr/lib/libvdpau_nvidia.so [0x34c1d9]
03: /usr/lib/libvdpau_nvidia.so [0x3b341b]
04: /usr/lib/libvdpau_nvidia.so [0x3959e8]
05: /usr/lib/libvdpau_nvidia.so [0x361f3b]
06: /usr/lib/libvdpau_nvidia.so(vdp_imp_device_create_x11+0x3d9) [0x34c8f9]
07: /usr/lib/libvdpau_trace.so(vdp_trace_device_create_x11+0x14c) [0x25ffec]
08: /usr/lib/libvdpau.so.1(vdp_device_create_x11+0xf3) [0x345773]
09: ./vdpinfo [0x804c448]
10: /lib/libc.so.6(__libc_start_main+0xe5) [0xd176e5]
11: ./vdpinfo [0x8048771]
VDPAU nvidia: Error detected 0 5425
VDPAU nvidia: Backtrace:
01: /usr/lib/libvdpau_nvidia.so [0x34b33e]
02: /usr/lib/libvdpau_nvidia.so [0x34b409]
03: /usr/lib/libvdpau_nvidia.so(vdp_imp_device_create_x11+0x437) [0x34c957]
04: /usr/lib/libvdpau_trace.so(vdp_trace_device_create_x11+0x14c) [0x25ffec]
05: /usr/lib/libvdpau.so.1(vdp_device_create_x11+0xf3) [0x345773]
06: ./vdpinfo [0x804c448]
07: /lib/libc.so.6(__libc_start_main+0xe5) [0xd176e5]
08: ./vdpinfo [0x8048771]
    -> 25
Error creating VDPAU device: 25


Digging around that corresponds to "VDP_STATUS_RESOURCES The system does not have enough resources to complete the requested operation at this time. " stracing the program shows that it's hits th /proc/interupts and later on gets a bunch of Resource temporarily unavailable.

Code:


{ this is with driver 180.06 and kernel 2.6.29.1  }



write(1, "Create an device \n"..., 18Create an device
)  = 18
open("/etc/ld.so.cache", O_RDONLY)      = 4
fstat64(4, {st_mode=S_IFREG|0644, st_size=63879, ...}) = 0
mmap2(NULL, 63879, PROT_READ, MAP_PRIVATE, 4, 0) = 0xb8020000
close(4)                                = 0
open("/usr/lib/libvdpau_nvidia.so", O_RDONLY) = 4
read(4, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0 8\0\0004\0\0\0\354"..., 512) = 512
fstat64(4, {st_mode=S_IFREG|0755, st_size=926436, ...}) = 0
mmap2(NULL, 929280, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 4, 0) = 0xb7f3d000
mmap2(0xb7f99000, 552960, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 4, 0x5b) = 0xb7f99000
close(4)                                = 0
open("/usr/lib/libXext.so.6", O_RDONLY) = 4
read(4, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0@f\361J4\0\0\0\254"..., 512) = 512
fstat64(4, {st_mode=S_IFREG|0755, st_size=62812, ...}) = 0
mmap2(0x4af14000, 64188, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 4, 0) = 0x4af14000
mmap2(0x4af23000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 4, 0xe) = 0x4af23000
close(4)                                = 0
open("/lib/libpthread.so.0", O_RDONLY)  = 4
read(4, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0P\370\275J4\0\0\0004"..., 512) = 512
fstat64(4, {st_mode=S_IFREG|0755, st_size=135836, ...}) = 0
mmap2(0x4abdb000, 102880, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 4, 0) = 0x4abdb000
mmap2(0x4abf1000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 4, 0x15) = 0x4abf1000
mmap2(0x4abf3000, 4576, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x4abf3000
close(4)                                = 0
mprotect(0x4abf1000, 4096, PROT_READ)  = 0
mprotect(0xb7f3d000, 376832, PROT_READ|PROT_WRITE) = 0
mprotect(0xb7f3d000, 376832, PROT_READ|PROT_EXEC) = 0
set_tid_address(0xb8030718)            = 6282
set_robust_list(0xb8030720, 0xc)        = 0
futex(0xbf845240, FUTEX_WAKE_PRIVATE, 1) = 0
rt_sigaction(SIGRTMIN, {0x4abdf300, [], SA_SIGINFO}, NULL, 8) = 0
rt_sigaction(SIGRT_1, {0x4abdf740, [], SA_RESTART|SA_SIGINFO}, NULL, 8) = 0
rt_sigprocmask(SIG_UNBLOCK, [RTMIN RT_1], NULL, 8) = 0
getrlimit(RLIMIT_STACK, {rlim_cur=8192*1024, rlim_max=RLIM_INFINITY}) = 0
uname({sys="Linux", node="e", ...})    = 0
munmap(0xb8020000, 63879)              = 0
futex(0xb801f9e0, FUTEX_WAKE_PRIVATE, 2147483647) = 0
select(4, [3], [3], NULL, NULL)        = 1 (out [3])
writev(3, [{"b\0\4\0\6\0\0\0NV-GLX\0\0"..., 16}], 1) = 16
select(4, [3], [], NULL, NULL)          = 1 (in [3])
read(3, "\1\0\7\0\0\0\0\0\1\220\0\0\0\0\0\0\20\0\0\0\10\0\0\0\320\v\302\10\0\0\0\0"..., 4096) = 32
read(3, 0x80d789c, 4096)                = -1 EAGAIN (Resource temporarily unavailable)
select(4, [3], [3], NULL, NULL)        = 1 (out [3])
writev(3, [{"\220\1\1\0"..., 4}], 1)    = 4
select(4, [3], [], NULL, NULL)          = 1 (in [3])
read(3, "\1\263\10\0\0\0\0\0\0\0\0\0&\367C\0034\331\216\277\231\251\367\266\20\201\20\267\200\364\301\10"..., 4096) = 32
read(3, 0x80d789c, 4096)                = -1 EAGAIN (Resource temporarily unavailable)
shmat(0, 0, 0)                          = 0xb7f1c000
select(4, [3], [3], NULL, NULL)        = 1 (out [3])
writev(3, [{"\220\16\2\0\0\0\0\0"..., 8}], 1) = 8
select(4, [3], [], NULL, NULL)          = 1 (in [3])
read(3, "\1.\t\0\344g\0\0\220\237\1\0\0\0\0\0j#\25\10\204\263!\0104\331\216\277\231\251\367\266\340"..., 4096) = 4096
brk(0x811a000)                          = 0x811a000
read(3, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 102320) = 102320
read(3, 0x80d789c, 4096)                = -1 EAGAIN (Resource temporarily unavailable)
brk(0x8100000)                          = 0x8100000
select(4, [3], [3], NULL, NULL)        = 1 (out [3])
writev(3, [{"b\16\5\0\t\0\0\0Composite\0\0\0"..., 20}], 1) = 20
select(4, [3], [], NULL, NULL)          = 1 (in [3])
read(3, "\1\0\n\0\0\0\0\0\1\233\0\0\0\0\0\0\24\0\0\0\10\0\0\0\320\v\302\10\0\0\0\0"..., 4096) = 32
read(3, 0x80d789c, 4096)                = -1 EAGAIN (Resource temporarily unavailable)
select(4, [3], [3], NULL, NULL)        = 1 (out [3])
writev(3, [{"\220\2\2\0\0\0\0\0"..., 8}], 1) = 8
select(4, [3], [], NULL, NULL)          = 1 (in [3])
read(3, "\1\331\v\0\0\0\0\0\2\0\0\0\0\0!\10\0\0\0\0j#\25\10\204\263!\0104\331\216\277"..., 4096) = 32
read(3, 0x80d789c, 4096)                = -1 EAGAIN (Resource temporarily unavailable)
geteuid32()                            = 502
geteuid32()                            = 502
open("/dev/nvidiactl", O_RDWR|O_LARGEFILE) = 4
ioctl(4, 0xc04846d2, 0xbf82b260)        = 0
ioctl(4, 0xc0e046c8, 0xb801fc00)        = 0
ioctl(4, 0xc00c4622, 0xbf82b3e0)        = 0
ioctl(4, 0xc020462a, 0xbf82b3d0)        = 0
geteuid32()                            = 502
open("/dev/nvidia0", O_RDWR|O_LARGEFILE) = 5
ioctl(4, 0xc048464d, 0xbf82b0d0)        = 0
open("/proc/interrupts", O_RDONLY|O_LARGEFILE) = 6
fstat64(6, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb8044000
read(6, "          CPU0      CPU1      "..., 1024) = 1024
read(6, "us interrupts\nERR:          0\nMIS"..., 1024) = 46
read(6, ""..., 1024)                    = 0
read(6, ""..., 1024)                    = 0
close(6)                                = 0


interrupts maybe? { or complete red-herring }


Code:

# cat /proc/interupts
16:        177    122740  IO-APIC-fasteoi  uhci_hcd:usb2, HDA Intel, nvidia
[ snip ]

# dmesg | grep -i irq | grep 16
pci 0000:00:01.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
pci 0000:00:03.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
pci 0000:00:1c.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
uhci_hcd 0000:06:04.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
uhci_hcd 0000:06:04.0: irq 16, io base 0x00003800
nvidia 0000:02:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
HDA Intel 0000:00:1b.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
IRQ 16/nvidia: IRQF_DISABLED is not guaranteed on shared IRQs

Poor little 16 :ORDER:


BTW kernel config is:
CONFIG_HZ_300=y
CONFIG_HZ=300


- so I think my problem is slightly different as no version of the driver works for me.

Cheers Ben



================================================== ==============================================
update:

Bought a 'new' card from ebay. A 256mb Nvidia-Sparkle - Geforce 8400GS-256MB - dropped it in and VDPAU works off the bat. I'm happy to blame my old card, which was an eBay China special ( 9400GT with G86 core ).

Just want to say thanks again (to everyone!) for the software and support.

Stephen Warren 04-03-09 10:39 AM

Re: VDPAU error "NNNN 60 5" and "NNNN 43 5"
 
bluebenno, Thanks very much for responding and doing all the work. Glad to hear that your BIOS upgrade didn't fail!

Can you try *all* the old drivers too (180.06 180.08, 180.11, 180.16, 180.18, ...) DeiF reported that VDPAU used to work in the very first driver, but then was broken later. It would be *extremely* useful if we could find out if that's true for everybody, and exactly which driver release broken - it'd narrow down the changes we have to look at immensely.

Thanks!

Stephen Warren 04-08-09 05:12 PM

Re: VDPAU error "NNNN 60 5" and "NNNN 43 5"
 
Question: How many of you have DDR2 v.s. DDR3 RAM on your graphics cards? No, off the top of my head, I don't know how to tell if you don't!

cocos 04-15-09 06:38 PM

Re: VDPAU error "NNNN 60 5" and "NNNN 43 5"
 
Don't really know the RAM type. I have a 8400M G card.

Was wondering if there is any update on the old error 25 issue. I'm still getting:

Error creating VDPAU device: 25

in vdpinfo with driver version 180.44.

Stephen Warren 04-15-09 06:53 PM

Re: VDPAU error "NNNN 60 5" and "NNNN 43 5"
 
cocos, No update yet; we are still trying to reproduce this issue. To confirm you're seeing this issue, and don't have some unrelated reason for error code 25, please follow the instruction in the debug sticky to provide a bug report file, and debug MPlayer/VDPAU log. Thanks.

moliones 04-15-09 07:19 PM

Re: VDPAU error "NNNN 60 5" and "NNNN 43 5"
 
1 Attachment(s)
I have a thread already, thought I would add my info here.

http://www.nvnews.net/vbulletin/show....php?p=1983988
(more details, logs provided here)

My card is a 9500GT with 1GB memory.

My card I know has DDR2 onboard.

Also, the VDPAU error numbers are different to those given, I have

VDPAU nvidia: Error detected 1026 58 5

and

VDPAU nvidia: Error detected 0 2589

For the record, have attached vdpinfo output. It doesn't mean much to me.

1) Both 180.44 and 185.19 fail

2) Motherboard BIOS up to date

3) Doesn't appear to be downloadable BIOS for video card

4) Have been unable to get VDPAU playback working with this card under any circumstances. However, playback on this system works (jittery though) with onboard gpu.

5) Composite extension disabled.

6) No PCI cards.

7) No overclocking

8) Not that I can think of.

9) Yes, as given in linked thread.

Teme 04-16-09 09:10 AM

Re: VDPAU error "NNNN 60 5" and "NNNN 43 5"
 
Quote:

Originally Posted by moliones (Post 1984009)
VDPAU nvidia: Error detected 1026 58 5

Me and opiz have exactly same error code and both also have 9500GT with DDR2 memory.


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

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