From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 94708] Open source radeon drivers not working properly with Radeon HD 8550M
Date: Sun, 03 Apr 2016 18:29:40 +0000 [thread overview]
Message-ID: <bug-94708-502-n60UZ2HYBv@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-94708-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 10162 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=94708
--- Comment #1 from Marko Tikvic <markotikvic@gmail.com> ---
Here are some messages that system spits out after running google chrome with
discrete GPU.
GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer,
GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer,
OpenGL renderer string: Gallium 0.4 on AMD HAINAN
[23858:23858:0402/002423:ERROR:browser_main_loop.cc(245)] GTK theme error:
Unable to locate theme engine in module_path: "murrine",
[23858:23858:0402/002423:ERROR:browser_main_loop.cc(245)] GTK theme error:
Unable to locate theme engine in module_path: "murrine",
[23858:23858:0402/002423:ERROR:browser_main_loop.cc(245)] GTK theme error:
Unable to locate theme engine in module_path: "murrine",
[23858:23858:0402/002423:ERROR:browser_main_loop.cc(245)] GTK theme error:
Unable to locate theme engine in module_path: "murrine",
[23858:23858:0402/002423:ERROR:browser_main_loop.cc(245)] GTK theme error:
Unable to locate theme engine in module_path: "murrine",
[23858:23858:0402/002423:ERROR:browser_main_loop.cc(245)] GTK theme error:
Unable to locate theme engine in module_path: "murrine",
[23858:23858:0402/002423:ERROR:browser_main_loop.cc(245)] GTK theme error:
Unable to locate theme engine in module_path: "murrine",
[23858:23858:0402/002423:ERROR:browser_main_loop.cc(245)] GTK theme error:
Unable to locate theme engine in module_path: "murrine",
[23858:23858:0402/002423:ERROR:browser_main_loop.cc(245)] GTK theme error:
Unable to locate theme engine in module_path: "murrine",
[23858:23858:0402/002423:ERROR:browser_main_loop.cc(245)] GTK theme error:
Unable to locate theme engine in module_path: "murrine",
[23858:23858:0402/002423:ERROR:browser_main_loop.cc(245)] GTK theme error:
Unable to locate theme engine in module_path: "murrine",
[23858:23858:0402/002423:ERROR:browser_main_loop.cc(245)] GTK theme error:
Unable to locate theme engine in module_path: "murrine",
[23858:23858:0402/002423:ERROR:browser_main_loop.cc(245)] GTK theme error:
Unable to locate theme engine in module_path: "murrine",
[23858:23858:0402/002423:ERROR:browser_main_loop.cc(245)] GTK theme error:
Unable to locate theme engine in module_path: "murrine",
[23858:23858:0402/002423:ERROR:browser_main_loop.cc(245)] GTK theme error:
Unable to locate theme engine in module_path: "murrine",
[23858:23858:0402/002423:ERROR:browser_main_loop.cc(245)] GTK theme error:
Unable to locate theme engine in module_path: "murrine",
[23858:23858:0402/002423:ERROR:browser_main_loop.cc(245)] GTK theme error:
Unable to locate theme engine in module_path: "murrine",
[23858:23858:0402/002423:ERROR:browser_main_loop.cc(245)] GTK theme error:
Unable to locate theme engine in module_path: "murrine",
[23858:23858:0402/002423:ERROR:browser_main_loop.cc(245)] GTK theme error:
Unable to locate theme engine in module_path: "murrine",
[23858:23858:0402/002423:ERROR:browser_main_loop.cc(245)] GTK theme error:
Unable to locate theme engine in module_path: "murrine",
[23858:23858:0402/002423:ERROR:browser_main_loop.cc(245)] GTK theme error:
Unable to locate theme engine in module_path: "murrine",
[23858:23858:0402/002423:ERROR:browser_main_loop.cc(245)] GTK theme error:
Unable to locate theme engine in module_path: "murrine",
[23858:23858:0402/002423:ERROR:browser_main_loop.cc(245)] GTK theme error:
Unable to locate theme engine in module_path: "murrine",
[23858:23858:0402/002423:ERROR:browser_main_loop.cc(245)] GTK theme error:
Unable to locate theme engine in module_path: "murrine",
[23858:23858:0402/002423:ERROR:browser_main_loop.cc(245)] GTK theme error:
Unable to locate theme engine in module_path: "murrine",
[23858:23858:0402/002423:ERROR:browser_main_loop.cc(245)] GTK theme error:
Unable to locate theme engine in module_path: "murrine",
[23858:23858:0402/002423:ERROR:browser_main_loop.cc(245)] GTK theme error:
Unable to locate theme engine in module_path: "murrine",
Gtk-Message: Failed to load module "canberra-gtk-module"
[23858:23889:0402/002423:ERROR:nss_util.cc(839)] After loading Root Certs,
loaded==false: NSS error code: -8018
[23916:23916:0402/002423:ERROR:sandbox_linux.cc(334)] InitializeSandbox()
called with multiple threads in process gpu-process
[WARNING:flash/platform/pepper/pep_module.cpp(63)] SANDBOXED
Vector smash protection is enabled.
[23858:23889:0402/100448:ERROR:connection_factory_impl.cc(367)] Failed to
connect to MCS endpoint with error -106
[23858:23889:0402/100455:ERROR:connection_factory_impl.cc(367)] Failed to
connect to MCS endpoint with error -137
[WARNING:flash/platform/pepper/pep_module.cpp(63)] SANDBOXED
Vector smash protection is enabled.
couldn't lock 16384 bytes of memory (secret_session): Cannot allocate memory
[WARNING:flash/platform/pepper/pep_module.cpp(63)] SANDBOXED
Vector smash protection is enabled.
[2046:2066:0402/121635:ERROR:webrtcsession.cc(1446)] ConnectDataChannel called
when data_channel_ is NULL.
[2046:2066:0402/121635:ERROR:webrtcsession.cc(1446)] ConnectDataChannel called
when data_channel_ is NULL.
[2046:2066:0402/121635:ERROR:webrtcsession.cc(1446)] ConnectDataChannel called
when data_channel_ is NULL.
[2046:2067:0402/121637:ERROR:sctpdataengine.cc(987)]
SctpDataMediaChannel->OnPacketFromSctpToNetwork(...): SCTP seems to have made a
packet that is bigger than its official MTU: 1280 vs max of 1200 even after
adding 76 extra SCTP overhead
[2046:2067:0402/121643:ERROR:sctpdataengine.cc(987)]
SctpDataMediaChannel->OnPacketFromSctpToNetwork(...): SCTP seems to have made a
packet that is bigger than its official MTU: 1280 vs max of 1200 even after
adding 76 extra SCTP overhead
[2046:2067:0402/121643:ERROR:sctpdataengine.cc(987)]
SctpDataMediaChannel->OnPacketFromSctpToNetwork(...): SCTP seems to have made a
packet that is bigger than its official MTU: 1280 vs max of 1200 even after
adding 76 extra SCTP overhead
[2046:2067:0402/121645:ERROR:sctpdataengine.cc(987)]
SctpDataMediaChannel->OnPacketFromSctpToNetwork(...): SCTP seems to have made a
packet that is bigger than its official MTU: 1280 vs max of 1200 even after
adding 76 extra SCTP overhead
[2046:2067:0402/121646:ERROR:sctpdataengine.cc(987)]
SctpDataMediaChannel->OnPacketFromSctpToNetwork(...): SCTP seems to have made a
packet that is bigger than its official MTU: 1280 vs max of 1200 even after
adding 76 extra SCTP overhead
[2046:2067:0402/121646:ERROR:sctpdataengine.cc(987)]
SctpDataMediaChannel->OnPacketFromSctpToNetwork(...): SCTP seems to have made a
packet that is bigger than its official MTU: 1280 vs max of 1200 even after
adding 76 extra SCTP overhead
[2046:2067:0402/121650:ERROR:sctpdataengine.cc(987)]
SctpDataMediaChannel->OnPacketFromSctpToNetwork(...): SCTP seems to have made a
packet that is bigger than its official MTU: 1280 vs max of 1200 even after
adding 76 extra SCTP overhead
[2046:2067:0402/121651:ERROR:sctpdataengine.cc(987)]
SctpDataMediaChannel->OnPacketFromSctpToNetwork(...): SCTP seems to have made a
packet that is bigger than its official MTU: 1280 vs max of 1200 even after
adding 76 extra SCTP overhead
[2046:2067:0402/121656:ERROR:sctpdataengine.cc(987)]
SctpDataMediaChannel->OnPacketFromSctpToNetwork(...): SCTP seems to have made a
packet that is bigger than its official MTU: 1280 vs max of 1200 even after
adding 76 extra SCTP overhead
[2046:2066:0402/121657:ERROR:webrtcsession.cc(1446)] ConnectDataChannel called
when data_channel_ is NULL.
[2046:2066:0402/121657:ERROR:webrtcsession.cc(1446)] ConnectDataChannel called
when data_channel_ is NULL.
[2046:2067:0402/121702:ERROR:sctpdataengine.cc(987)]
SctpDataMediaChannel->OnPacketFromSctpToNetwork(...): SCTP seems to have made a
packet that is bigger than its official MTU: 1280 vs max of 1200 even after
adding 76 extra SCTP overhead
[2046:2067:0402/121702:ERROR:sctpdataengine.cc(987)]
SctpDataMediaChannel->OnPacketFromSctpToNetwork(...): SCTP seems to have made a
packet that is bigger than its official MTU: 1280 vs max of 1200 even after
adding 76 extra SCTP overhead
[2046:2066:0402/121703:ERROR:webrtcsession.cc(1446)] ConnectDataChannel called
when data_channel_ is NULL.
[2046:2066:0402/121718:ERROR:webrtcsession.cc(1446)] ConnectDataChannel called
when data_channel_ is NULL.
[2046:2066:0402/121738:ERROR:webrtcsession.cc(1446)] ConnectDataChannel called
when data_channel_ is NULL.
[2046:2066:0402/121747:ERROR:webrtcsession.cc(1446)] ConnectDataChannel called
when data_channel_ is NULL.
[2046:2066:0402/121753:ERROR:webrtcsession.cc(1446)] ConnectDataChannel called
when data_channel_ is NULL.
[2046:2066:0402/122017:ERROR:webrtcsession.cc(1446)] ConnectDataChannel called
when data_channel_ is NULL.
[WARNING:flash/platform/pepper/pep_module.cpp(63)] SANDBOXED
Vector smash protection is enabled.
[23858:23889:0402/135348:ERROR:connection_factory_impl.cc(367)] Failed to
connect to MCS endpoint with error -106
[23858:23889:0402/212205:ERROR:connection_factory_impl.cc(367)] Failed to
connect to MCS endpoint with error -137
[WARNING:flash/platform/pepper/pep_module.cpp(63)] SANDBOXED
Vector smash protection is enabled.
[WARNING:flash/platform/pepper/pep_module.cpp(63)] SANDBOXED
Vector smash protection is enabled.
[23858:23889:0403/013115:ERROR:connection_factory_impl.cc(367)] Failed to
connect to MCS endpoint with error -106
[23858:23988:0403/013512:ERROR:get_updates_processor.cc(250)]
PostClientToServerMessage() failed during GetUpdates
[23858:23988:0403/013515:ERROR:get_updates_processor.cc(250)]
PostClientToServerMessage() failed during GetUpdates
[23858:23889:0403/013517:ERROR:connection_factory_impl.cc(367)] Failed to
connect to MCS endpoint with error -137
[23858:23988:0403/013518:ERROR:get_updates_processor.cc(250)]
PostClientToServerMessage() failed during GetUpdates
[23916:23916:0403/030913:ERROR:sync_control_vsync_provider.cc(63)]
glXGetSyncValuesOML should not return TRUE with a media stream counter of 0.
[23858:23889:0403/030913:ERROR:connection_factory_impl.cc(367)] Failed to
connect to MCS endpoint with error -106
[WARNING:flash/platform/pepper/pep_module.cpp(63)] SANDBOXED
Vector smash protection is enabled.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 11280 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-04-03 18:29 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-25 20:35 [Bug 94708] Open source radeon drivers not working properly with Radeon HD 8550M bugzilla-daemon
2016-03-29 21:40 ` bugzilla-daemon
2016-04-03 18:29 ` bugzilla-daemon [this message]
2016-04-04 13:54 ` bugzilla-daemon
2016-04-04 13:56 ` bugzilla-daemon
2016-04-04 13:57 ` bugzilla-daemon
2016-04-04 13:59 ` bugzilla-daemon
2016-04-04 14:00 ` bugzilla-daemon
2016-04-04 14:04 ` bugzilla-daemon
2016-04-04 14:11 ` bugzilla-daemon
2016-04-04 14:12 ` bugzilla-daemon
2016-04-04 14:19 ` bugzilla-daemon
2016-04-25 19:29 ` bugzilla-daemon
2016-05-03 16:39 ` bugzilla-daemon
2016-05-03 16:55 ` bugzilla-daemon
2016-05-03 17:02 ` bugzilla-daemon
2016-05-03 17:05 ` bugzilla-daemon
2016-05-05 16:25 ` bugzilla-daemon
2016-05-05 16:26 ` bugzilla-daemon
2016-05-05 16:26 ` bugzilla-daemon
2016-05-05 16:27 ` bugzilla-daemon
2016-05-05 16:28 ` bugzilla-daemon
2016-05-05 16:28 ` bugzilla-daemon
2016-05-05 16:29 ` bugzilla-daemon
2016-05-05 16:29 ` bugzilla-daemon
2016-05-05 16:30 ` bugzilla-daemon
2016-05-05 17:07 ` bugzilla-daemon
2016-05-05 17:14 ` bugzilla-daemon
2016-05-05 17:51 ` bugzilla-daemon
2016-05-06 15:25 ` bugzilla-daemon
2019-11-19 9:14 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-94708-502-n60UZ2HYBv@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox