DisplayLink Forum
Page 5 of 6 « First 34 5 6
Show 40 post(s) from this thread on one page

DisplayLink Forum (https://displaylink.org/forum/index.php)
-   Mac Software (https://displaylink.org/forum/forumdisplay.php?f=30)
-   -   Endless log spam _CGXGLDisplayContextForDisplayDevice: No matching context for device (https://displaylink.org/forum/showthread.php?t=62987)

silence 06-09-2017 04:11 PM
Quote:
Originally Posted by Carlo (Post 83459)
Can you please copy and paste the log message? It may be a new one.

Kind regards,
Carlo
Can confirm this is an issue on Sierra 12.12.5. My log looks exactly like dude123's, and the existing fix no longer works.

steve_s 06-12-2017 12:29 AM
Quote:
Originally Posted by dude123 (Post 83460)
Yes sure!

Code:
No matching context for device (0x7fe957c26f90) - disabling OpenGL
Sender:
/System/Library/PrivateFrameworks/SkyLight.framework/Resources/WindowServer
(/System/Library/PrivateFrameworks/SkyLight.framework/Versions/A/SkyLight)

Subsystem:
com.apple.SkyLight
I am getting the same behavior, running Sierra, with a different 0x... number:

Code:
No matching context for device (0x7ff8ca335340) - disabling OpenGL

wa2flq 06-13-2017 12:28 PM
Can not reproduce the "ignore" fix.
 
Quote:
Originally Posted by mcousins (Post 75956)
I seem to have stopped the log spam by adding this to my asl.conf in /etc at the top of the file

? [= Sender WindowServer] ignore

And then performing the sudo kill -HUP [PID of process]
I've tired this asl.conf. I can't seem to make it work in Sierra.
I have SIP (temporarily) turned off. Also tried this in /etc/asl/com.apple.windowserver and com.displaylink.windowserver. I can see that aslmanager is restarting after the HUP to syslog.

I still see tons of messages in the Console. Any thoughts as to what I am doing wrong?

duncanm 06-22-2017 01:16 PM
Stopping log spam in sierra
 
As a temporary fix you can enter the following in your terminal:

Code:
sudo log config --process=[PID] --mode "level:off"
where [PID] is the ID of the process you see in the console.

You have to re-do it every time you re-start your mac which is a pain, but at least it saves all those writes to your disk

wa2flq 06-23-2017 02:49 AM
That works, thanks.

dude123 07-27-2017 08:52 PM
Quote:
Originally Posted by duncanm (Post 83688)
As a temporary fix you can enter the following in your terminal:

Code:
sudo log config --process=[PID] --mode "level:off"
where [PID] is the ID of the process you see in the console.

You have to re-do it every time you re-start your mac which is a pain, but at least it saves all those writes to your disk
Yes, can confirm, this is the first "solution" that works on Sierra.
MacOS 10.12.6 - DisplayLink 3.1

benwen 09-07-2017 05:43 AM
Quote:
Originally Posted by duncanm (Post 83688)
As a temporary fix you can enter the following in your terminal:

Code:
sudo log config --process=[PID] --mode "level:off"
where [PID] is the ID of the process you see in the console.

You have to re-do it every time you re-start your mac which is a pain, but at least it saves all those writes to your disk
Thank you duncamn!

Here's a quick and dirty shell script to automate the finding of the PID
Code:
#!/bin/sh
pid=`ps -ax | awk '/SkyLight.framework/ && !/awk/ {print $1}'`
echo "Skylight.framework with OpenGL logorrhea PID found. Suppressing log for PID $pid"
sudo log config --process=$pid --mode "level:off"
Put that in a file 'quite-dlink' in your $PATH, chmod 0755 it and execute it in Terminal at startup.

paultzirides 09-11-2017 12:47 PM
Still necessary?
 
After installing the 4.0 beta, I'm no longer noticing any log spam. I ran the terminal command anyway, but observed no change in the amount or type of logs being generated by the system. Is anyone else seeing the same?

dude123 09-30-2017 02:33 AM
Problem solved!!!

Update to 4.0 didn't make it better on macOS 10.12 - BUT after the system update to 10.13 combined with 4.0 - now finally the log spam is solved and on top of that also the hardware support for video etc is very much improved.

Well done!! Thank you a lot DisplayLink-Team!!!!

jormsby 10-24-2017 05:43 PM
My new MacBook Pro running 10.12.6 and with DisplayLink 4.0.0 is filling up my Console with this error message.

I see where 10.13 might fix it but that is not an option on this work computer.

Any suggestions on how to get this to stop?


All times are GMT. The time now is 12:13 PM.
Page 5 of 6 « First 34 5 6
Show 40 post(s) from this thread on one page

Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2024, vBulletin Solutions, Inc.