OSX10.9.2 + DL2.2 Beta + Belkin B2B044 == KABOOM
Ever since receiving this Belkin dock, my system began hanging or crashing after the my MBP goes to sleep for the night.
When I try waking it, the system hangs with only the mouse cursor moving or doesn't do anything. I tried isolating it to a specific application when I noticed that unplugging the dock prior to letting the system sleep overnight prevents the system from hanging/crashing. Pretty annoying and defeats the purpose of the dock, but it's a workaround. My setup: MBP mDP -> 27" monitor DP MBP usb 3 -> Belkin Dock Belkin Dock -> USB Keyboard, LAN, DVI-D -> HDMI 24" monitor I also noticed that I get the following logs appears in Console.app 1-5 times a second: 2014-03-23 12:42:33.764 AM WindowServer[224]: _CGXGLDisplayContextForDisplayDevice: No matching context for device (0x7fc2c051b9b0) - disabling OpenGLDoes this have to do with the hangs/crashes? Thanks, RPD |
_CGXGLDisplayContextForDisplayDevice logs should not be related to the issue you reported. These are WindowServer warnings in disabling OpenGL since it's not supported.
With crashing, do you mean kernel panics? In case, could you please upload the panic logs. You should see Kernel_xx.panic logs in/Library/Logs/DiagnosticReports/. Any other crash log in that folder generated right before or after the machine crash/hang. Could you also please use the debug tool ( http://www.displaylink.com/support/ticket.php?id=269) and collect the DisplayLink logs?. Have you ever used the 2.1 driver with 10.9.2 and experienced a similar problem? In case you've never used it, could you please use it and check if it show the same problem. Many thanks |
2 Attachment(s)
Quote:
From the period of Mar 20 to today I have about 110 DisplayLinkUserAgent_*.crash logs. I've attached a couple of these crash logs (CrashLogs.zip) and the logs from running the debug tool (DisplayLinkLogs.zip). I've downgraded the driver from 2.2 to 2.1. I'll post back what happens. Let me know if you need me to try anything else. Thanks for your help! RPD |
:confused:
Hi Christian, any update on this issue? |
Quote:
|
1 Attachment(s)
Quote:
I'm still experiencing the crashes. I've ran the log tool and I've included the logs for your review. In addition, my dock is now having the monitor go in and out of power save mode and never fully turning off. RPD |
Quote:
I see some kernel panic logs reported in your system profile. Are you experiencing kernel panics or simply DisplayLinkUserAgent crashes? In case you just see DisplayLinkUserAgent crashes, could you please upload a couple of new DisplayLinkUserAgent crash logs? These are not included in logs collected by the debug tool, but you can find them under yourhomedirectory/Library/Logs/DiagnosticReports/ Thanks |
Quote:
I don't have any logs being generated in that folder. Is there anything you'd like me to try out in the meantime? RPD |
Ok, so it seems that DisplayLinkUserAgent is not crashing anymore.
Just to be sure, what kind of crash do you experience? Are you experiencing kernel panics? I mean, do you see gray screen and the machine need to be restarted? Thanks |
During the course of the day while I'm actively using the system, the system does not have a kernal panic. When I'm away for an extended period of time I often see the displays going grey and restarting the system. Once I log back in I get a 'system had restarted due to an error' message and it is something that involves the DisplayLink.
If the log utility doesn't provide you with that log i can copy it so you can examine the stack trace. RPD |
1 Attachment(s)
Hi Christian,
It does appear to be a kernal panic. I've attached the report that's generated by the system. Thanks, RPD |
Hi RPD,
Useful kernel panic, something between our process and the USB framework. Or inside the framework itself. But no reproduction for us so far. We have seen in our lab a system freeze that was as mysterious, simply having any event on the USB bus while in sleep caused it but only on one specific machine. In that case it helped to resetting the NVRAM to default. I would try to reset the the NVRAM, the instructions are in http://support.apple.com/kb/ht1379 Carlo |
Quote:
Thanks for the update. I'll reset the NVRAM and report back. Cheers! RPD |
1 Attachment(s)
Hi Carlo,
Resetting the NVRAM has not corrected the issue. I had my system hang on me and required a hard reboot to reset it. The Apple report generated is attached. It seems like it's from the DisplayLinkManag; not sure if it's the same issue before. Thanks, RPD |
All times are GMT. The time now is 08:57 PM. |
Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2024, vBulletin Solutions, Inc.