Bug 96952 - Nouveau driver doesn't working well when on Kdenlive
Summary: Nouveau driver doesn't working well when on Kdenlive
Status: RESOLVED MOVED
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/nouveau (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Nouveau Project
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-07-16 00:24 UTC by Rafael Favero
Modified: 2019-12-04 09:15 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Rafael Favero 2016-07-16 00:24:55 UTC
Recently I'm having dificulties with Kdenlive, in the logs os Ubuntu 15.10, there was a issue involving the noveau driver. Log in next.

Log:

Jul 10 19:09:06 Rafael-desktop gnome-session[1605]: QXcbConnection: XCB error: 8 (BadMatch), sequence: 7899, resource id: 60817680, major code: 130 (Unknown), minor code: 3
Jul 10 19:09:06 Rafael-desktop gnome-session[1605]: QXcbConnection: XCB error: 8 (BadMatch), sequence: 7947, resource id: 60817680, major code: 130 (Unknown), minor code: 3
Jul 10 19:09:10 Rafael-desktop gnome-session[1605]: QXcbConnection: XCB error: 8 (BadMatch), sequence: 19520, resource id: 60817680, major code: 130 (Unknown), minor code: 3
Jul 10 19:09:10 Rafael-desktop gnome-session[1605]: QXcbConnection: XCB error: 8 (BadMatch), sequence: 19548, resource id: 60817680, major code: 130 (Unknown), minor code: 3
Jul 10 19:09:10 Rafael-desktop gnome-session[1605]: QXcbConnection: XCB error: 8 (BadMatch), sequence: 19639, resource id: 60817680, major code: 130 (Unknown), minor code: 3
Jul 10 19:09:11 Rafael-desktop gnome-session[1605]: nouveau: kernel rejected pushbuf: Arquivo ou diretório não encontrado
Jul 10 19:09:11 Rafael-desktop gnome-session[1605]: nouveau: ch0: krec 0 pushes 0 bufs 2 relocs 0
Jul 10 19:09:11 Rafael-desktop gnome-session[1605]: nouveau: ch0: buf 00000000 00000002 00000004 00000004 00000000
Jul 10 19:09:11 Rafael-desktop gnome-session[1605]: nouveau: ch0: buf 00000001 00000006 00000004 00000000 00000004
Jul 10 19:09:11 Rafael-desktop kernel: [ 8475.196277] nouveau E[kdenlive[5804]] Unknown handle 0x0000001d
Jul 10 19:09:11 Rafael-desktop kernel: [ 8475.196286] nouveau E[kdenlive[5804]] validate_init
Jul 10 19:09:11 Rafael-desktop kernel: [ 8475.196287] nouveau E[kdenlive[5804]] validate: -2
Jul 10 19:09:12 Rafael-desktop kernel: [ 8476.033404] show_signal_msg: 45 callbacks suppressed
Jul 10 19:09:12 Rafael-desktop kernel: [ 8476.033411] FrameRenderer[5821]: segfault at 8 ip 00007f967805f58c sp 00007f96477fd680 error 4 in libdrm_nouveau.so.2.0.0[7f967805c000+6000]

I have a NVidia 210 GeForce.
It's my first time here and if I made a mistake sorry, wasn't my pretention.
Comment 1 Ilia Mirkin 2016-07-16 00:38:49 UTC
Do you know whether kdenlive does GL and VDPAU calls from parallel threads?

Separately, what version of libdrm(_nouveau) do you have?
Comment 2 Rafael Favero 2016-07-16 13:12:24 UTC
Maybe I made a mistake, I was advised to report the problem here, but I was on another forum and one user tell me that the problema maybe wasn't especific on the driver, but could really be on Kdenlive. I really know few about this things and I think I could not help this, I'll try to contact Kdenlive's support to show the mistake, thanks for the help.
Comment 3 Rafael Favero 2016-07-18 13:43:51 UTC
I upgraded Ubuntu to 16.04 and Kdenlive to lastest version, but the problem continue, I'm a normal user and I don't know how does GL and VDPAU calls from parallel threads, and the version of libdrm(_nouveau)is 2.4.67-1ubuntu0.16.04.1.
Comment 4 Martin Peres 2019-12-04 09:15:20 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/issues/276.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.