<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - Radeon uvd makes VDPAU clients to crash at vlVdpDecoderCreate with 1080p videos" href="https://bugs.freedesktop.org/show_bug.cgi?id=78297#c11">Comment # 11</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - Radeon uvd makes VDPAU clients to crash at vlVdpDecoderCreate with 1080p videos" href="https://bugs.freedesktop.org/show_bug.cgi?id=78297">bug 78297</a> from <a class="email" href="mailto:deathsimple@vodafone.de" title="Christian König <deathsimple@vodafone.de>"> Christian König</a> <pre>(In reply to <a href="show_bug.cgi?id=78297#c10">comment #10</a>) > (In reply to <a href="show_bug.cgi?id=78297#c9">comment #9</a>) > > That's the problem: > > > > [ 1.714537] [drm] Detected VRAM RAM=1024M, BAR=128M > > > > Your PCI BAR is smaller than usually, for a REDWOOD 256M are normal. Going > > to hack up a patch for this. > > Nice to hear! > But in these cases where there's not enough memory, shouldn't the vdpau > driver to fail returning an error (making the client to fallback to software > rendering), instead of crashing? It's not the VDPAU driver that's failing here, it's the kernel. When the kernel can't place a buffer into visible VRAM the buffer should be moved into GART instead for CPU access. But instead we just return a SIGBUS to the application effectively crashing it.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>