DisplayLink Forum - Endless log spam _CGXGLDisplayContextForDisplayDevice: No matching context for device

DisplayLink Forum (https://www.displaylink.org/forum/index.php)

- Mac Software (https://www.displaylink.org/forum/forumdisplay.php?f=30)

- - Endless log spam _CGXGLDisplayContextForDisplayDevice: No matching context for device (https://www.displaylink.org/forum/showthread.php?t=62987)

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.

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

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?

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

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

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.

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?

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!!!!

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?

Quote:

Originally Posted by dude123 (Post 84273)

My logs are filled with 3 per second. Since my log issue is slightly different than the OP I'll post it as an example. I'm not entirely sure it's DisplayLink, but I'm pretty sure.

MacOS High Sierra 10.13.2 - Display Link version 4.0 (sept. newest) with separate spaces checked (enabled)

I was able to suppress log until reboot using: sudo log config --pid=211 --mode "level:off"

Edit:

But you need to lookup the pid every boot, level:off

More Mac log suppression info

http://www.mackungfu.org/TurnoffrunawayloggingonmacOS

Speaking of log spam in High Sierra, I also get month 13 is out of bounds lol, but not as frequently as this:

default 19:04:19.044518 -0700 WindowServer No matching context for device (0x7f898cc3dcb0) - disabling acceleration.
default 19:04:19.044619 -0700 WindowServer No matching context for device (0x7f898cc3dcb0) - disabling acceleration.
default 19:04:19.044671 -0700 WindowServer No matching context for device (0x7f898cc3dcb0) - disabling acceleration.
default 19:04:19.044733 -0700 WindowServer No matching context for device (0x7f898cc3dcb0) - disabling acceleration.
default 19:04:19.044787 -0700 WindowServer No matching context for device (0x7f898cc3dcb0) - disabling acceleration.
default 19:04:19.060220 -0700 WindowServer No matching context for device (0x7f898cc3dcb0) - disabling acceleration.
default 19:04:19.060305 -0700 WindowServer No matching context for device (0x7f898cc3dcb0) - disabling acceleration.
default 19:04:19.060346 -0700 WindowServer No matching context for device (0x7f898cc3dcb0) - disabling acceleration.
default 19:04:19.060396 -0700 WindowServer No matching context for device (0x7f898cc3dcb0) - disabling acceleration.
default 19:04:19.060439 -0700 WindowServer No matching context for device (0x7f898cc3dcb0) - disabling acceleration.
default 19:04:19.153381 -0700 WindowServer No matching context for device (0x7f898cc3dcb0) - disabling acceleration.
default 19:04:19.153478 -0700 WindowServer No matching context for device (0x7f898cc3dcb0) - disabling acceleration.
default 19:04:19.153520 -0700 WindowServer No matching context for device (0x7f898cc3dcb0) - disabling acceleration.
default 19:04:19.153570 -0700 WindowServer No matching context for device (0x7f898cc3dcb0) - disabling acceleration.
default 19:04:19.153614 -0700 WindowServer No matching context for device (0x7f898cc3dcb0) - disabling acceleration.
default 19:04:19.163336 -0700 WindowServer No matching context for device (0x7f898cc3dcb0) - disabling acceleration.
default 19:04:19.163424 -0700 WindowServer No matching context for device (0x7f898cc3dcb0) - disabling acceleration.
default 19:04:19.169631 -0700 WindowServer No matching context for device (0x7f898cc3dcb0) - disabling acceleration.
default 19:04:19.169675 -0700 WindowServer No matching context for device (0x7f898cc3dcb0) - disabling acceleration.
default 19:04:19.169843 -0700 WindowServer No matching context for device (0x7f898cc3dcb0) - disabling acceleration.
default 19:04:19.224995 -0700 WindowServer No matching context for device (0x7f898cc3dcb0) - disabling acceleration.
default 19:04:19.225121 -0700 WindowServer No matching context for device (0x7f898cc3dcb0) - disabling acceleration.
default 19:04:19.225161 -0700 WindowServer No matching context for device (0x7f898cc3dcb0) - disabling acceleration.
default 19:04:19.225210 -0700 WindowServer No matching context for device (0x7f898cc3dcb0) - disabling acceleration.
default 19:04:19.225253 -0700 WindowServer No matching context for device (0x7f898cc3dcb0) - disabling acceleration.
default 19:04:19.421640 -0700 WindowServer No matching context for device (0x7f898cc3dcb0) - disabling acceleration.

Quote:

Originally Posted by dude123 (Post 84273)

Errr... I think you meant: Thank you Apple ! :-)

Some people have expressed concerned about wearing out disks. I don't know about that, however there's another massive difference that the super useful "log config level off" workaround just made: *responsiveness*. The short but still very painful lag between the moment I hit the keyboard and characters appears on the screen is finally gone.

For months and months until I found this message in the logs by chance (while looking for something else) I've been telling all my colleagues that DisplayLink was a technology really not for everyone because of a severe trade-off to make between screen real estate and responsiveness. Now I understand it was actually just that logging issue.

Has Apple any plan to backport the fix to Sierra?

Has DisplayLink updated their test plans to include responsiveness? (and also logging why not)

Quote:

Originally Posted by dude123 (Post 83449)

My syslogs get hit by 60.000 messages per second.

Indeed:

Code:

# log show --last 6h --predicate 'messageType == error and processImagePath endswith "DisplayLinkManager"'



Timestamp                       Thread     Type        Activity             PID    

2018-02-08 09:34:12.277266  0xf609a    Error       0x0                  115    DisplayLinkManager: (CoreFoundation) Detected potentially harmful notification post rate of 60.0026 notifications per second

This message shows up even with the "level: off" workaround (but infrequently).

The fact that my monitors run at 60Hz is likely not a coincidence.