DisplayLink Forum

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)

BMT 10-20-2014 03:12 PM

Quote:

Originally Posted by Carlo (Post 75465)
In 2.2 we started using a new API for an important part of the driver. The previous API has been deprecated and its reliability was rapidly decaying with every new OS version.
The new API has benefits but has some issues as well, one of which is the log spamming in some situations. We have raised all issues with Apple.

I cannot share any more information on this I'm sorry

Cheers
Carlo

I see, that makes sense - thanks for the explanation.

tmendo 10-23-2014 08:20 PM

Have should I write in the report for Apple? I want to file a bug report also but not sure what I should write to make it more accurate and less prone to be rejected.

jb8748 11-08-2014 10:04 PM

I've made a configuration file for ASL to claim all these messages and then ignore them. Seems to be a reasonable solution until such time as a bug fix is available.

http://blog.jamesball.co.uk/2014/11/...nk-driver.html

Seemone 11-10-2014 11:24 AM

A finer workaround would be to add

? [= Sender WindowServer] ignore

in the first line of asl.conf (in the etc directory) and then restart syslog by issuing

kill -hup <PID>

where PID is the syslog process pid

This will filter out only WindowServer messages instead of cutting all the syslog output

BMT 11-12-2014 02:48 PM

Disregard.

mcousins 11-12-2014 07:36 PM

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]

Not sure if that's OK, I tried the other way of creating a file under the asl folder and that did nothing for me.

Hope this helps, even if its just towards finding a better answer!

ehendrix 11-13-2014 06:18 PM

I changed it a little bit to:

# WindowServer messages about display context (caused by DisplayLink driver)
? [= Sender WindowServer] [= Level Warning] [A= Message _CGXGLDisplayContextForDisplayDevice] claim only

Seems to be working and ensures that any other messages from WindowServer are still going in.

ehendrix 11-20-2014 10:42 PM

No more messages since I've put this in. Interesting that with all the complaining about this within the forums that DisplayLink was never able to provide this as a solution.
Is it perfect? No.
Is it something Apple should fix? yes
Does the work-around work? Heck yes.
Could DisplayLink provide the work-around? Don't see why not.

Carlo 11-21-2014 09:12 AM

Hi ehendrix,

Sorry for going quiet on this one. Yes we think this is a good workaround, we could apply it at install time.

We'd use
? [= Sender WindowServer] [=S Message_CGXGLDisplayContextForDisplayDevice] ignore

Unless anyone can spot any issue with the approach?

Cheers,
Carlo

jb8748 11-26-2014 04:43 PM

Quote:

Originally Posted by ehendrix (Post 75965)
I changed it a little bit to:

# WindowServer messages about display context (caused by DisplayLink driver)
? [= Sender WindowServer] [= Level Warning] [A= Message _CGXGLDisplayContextForDisplayDevice] claim only

Seems to be working and ensures that any other messages from WindowServer are still going in.

Thank you ehendrix. That does look like a better command - I'm no expert on the logging so I was finding things that worked. I've updated my blog post.

James


All times are GMT. The time now is 06:06 AM.

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