Go Back   DisplayLink Forum > Alpha, Beta Software Testing Programs > Closed Alpha and Beta Programs > CLOSED: Mac OSX 1.7 Release
Register FAQ Calendar Today's Posts Search

 
 
Thread Tools Search this Thread Display Modes
Old 06-06-2011, 03:15 PM   #1
jbarrow
Member
 
Join Date: Feb 2011
Location: Northeast Oklahoma, USA
Posts: 31
Default Blue screen

After reboot, the window server crashes on startup, displaying the blue screen. The only fix seems to be booting into single user mode and removing the drivers. I would not recommend installing these at this point.

This crash happens on my MBP, late 2010, with or without graphics switching enabled, with or without the adapter plugged in.
jbarrow is offline  
Old 06-06-2011, 03:37 PM   #2
Carlo
Mac Team
 
Join Date: Feb 2009
Posts: 606
Default

jbarrow do you have any information from the kernel panic?
Carlo is offline  
Old 06-06-2011, 03:43 PM   #3
jbarrow
Member
 
Join Date: Feb 2011
Location: Northeast Oklahoma, USA
Posts: 31
Default

Back on my mac now.


This appears to be the valid part of system.log -

Jun 6 10:12:53 Josh-Barrows-MacBook-Pro loginwindow[48]: Login Window Started Security Agent
Jun 6 10:12:53 Josh-Barrows-MacBook-Pro SecurityAgent[286]: Echo enabled
Jun 6 10:12:54 Josh-Barrows-MacBook-Pro SecurityAgent[286]: Error: Mode change called with mode and hint not changed
Jun 6 10:12:54 Josh-Barrows-MacBook-Pro SecurityAgent[286]: SetFocusOn: Password field result = 1
Jun 6 10:12:56 Josh-Barrows-MacBook-Pro ReportCrash[295]: DebugSymbols was unable to start a spotlight query: spotlight is not responding or disabled.
Jun 6 10:12:56 Josh-Barrows-MacBook-Pro SecurityAgent[286]: kCGErrorFailure: _CGSLockWindow: Cannot synchronize window backing store
Jun 6 10:12:56 Josh-Barrows-MacBook-Pro SecurityAgent[286]: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
Jun 6 10:12:56 Josh-Barrows-MacBook-Pro SecurityAgent[286]: kCGErrorFailure: _CGSLockWindow: Cannot synchronize window backing store
Jun 6 10:12:56: --- last message repeated 1 time ---
Jun 6 10:12:56 Josh-Barrows-MacBook-Pro SecurityAgent[286]: HIToolbox: received notification of WindowServer event port death.
Jun 6 10:12:56 Josh-Barrows-MacBook-Pro SecurityAgent[286]: port matched the WindowServer port created in BindCGSToRunLoop
Jun 6 10:12:56 Josh-Barrows-MacBook-Pro SecurityAgent[286]: kCGErrorFailure: _CGSLockWindow: Cannot synchronize window backing store
Jun 6 10:12:56 Josh-Barrows-MacBook-Pro ManagedClient[284]: HIToolbox: received notification of WindowServer event port death.
Jun 6 10:12:56 Josh-Barrows-MacBook-Pro SecurityAgent[286]: kCGErrorFailure: _CGSLockWindow: Cannot synchronize window backing store
Jun 6 10:12:56 Josh-Barrows-MacBook-Pro ManagedClient[284]: port matched the WindowServer port created in BindCGSToRunLoop
Jun 6 10:12:56 Josh-Barrows-MacBook-Pro com.apple.SecurityAgent.00000000-0000-0000-0000-0000000186A4[286]: CAView: failed to lock device (error 1000)
Jun 6 10:12:56: --- last message repeated 2 times ---
Jun 6 10:12:56 Josh-Barrows-MacBook-Pro SecurityAgent[286]: (ipc/send) invalid destination port: CGSGetWorkspaceWindowCountWithOptionsAndTags
Jun 6 10:12:56 Josh-Barrows-MacBook-Pro com.apple.loginwindow[48]: 2011-06-06 10:12:56.875 ManagedClient[284:207] HIToolbox: received notification of WindowServer event port death.
Jun 6 10:12:56 Josh-Barrows-MacBook-Pro com.apple.launchd[1] (com.apple.WindowServer[255]): Job appears to have crashed: Segmentation fault: 11
Jun 6 10:12:56 Josh-Barrows-MacBook-Pro loginwindow[298]: Login Window Application Started
Jun 6 10:12:57 Josh-Barrows-MacBook-Pro ReportCrash[295]: Saved crash report for WindowServer[255] version ??? (???) to /Library/Logs/DiagnosticReports/WindowServer_2011-06-06-101257_localhost.crash
Jun 6 10:12:57 Josh-Barrows-MacBook-Pro ReportCrash[295]: Removing excessive log: /Library/Logs/DiagnosticReports/WindowServer_2011-06-06-092351_localhost.crash
Jun 6 10:12:57 Josh-Barrows-MacBook-Pro loginwindow[298]: **DMPROXY** Found `/System/Library/CoreServices/DMProxy'.
Jun 6 10:12:57 Josh-Barrows-MacBook-Pro com.apple.launchctl.LoginWindow[301]: com.apple.findmymacmessenger: Already loaded
Jun 6 10:12:57 Josh-Barrows-MacBook-Pro loginwindow[298]: Login Window Started Security Agent
Jun 6 10:12:57 Josh-Barrows-MacBook-Pro DisplayLinkUserAgent[307]: SCNetworkReachabilityCreateWithAddress[Pair] called with invalid address family 1
Jun 6 10:12:57 Josh-Barrows-MacBook-Pro SecurityAgent[308]: Echo enabled
Jun 6 10:12:57 Josh-Barrows-MacBook-Pro SecurityAgent[308]: Error: Mode change called with mode and hint not changed
Jun 6 10:12:57 Josh-Barrows-MacBook-Pro SecurityAgent[308]: SetFocusOn: Password field result = 1
Jun 6 10:13:00 Josh-Barrows-MacBook-Pro SecurityAgent[308]: kCGErrorFailure: _CGSLockWindow: Cannot synchronize window backing store
Jun 6 10:13:00 Josh-Barrows-MacBook-Pro SecurityAgent[308]: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
Jun 6 10:13:00 Josh-Barrows-MacBook-Pro SecurityAgent[308]: kCGErrorFailure: _CGSLockWindow: Cannot synchronize window backing store
Jun 6 10:13:00 Josh-Barrows-MacBook-Pro SecurityAgent[308]: HIToolbox: received notification of WindowServer event port death.
Jun 6 10:13:00 Josh-Barrows-MacBook-Pro SecurityAgent[308]: port matched the WindowServer port created in BindCGSToRunLoop
Jun 6 10:13:00 Josh-Barrows-MacBook-Pro SecurityAgent[308]: kCGErrorFailure: _CGSLockWindow: Cannot synchronize window backing store
Jun 6 10:13:00: --- last message repeated 1 time ---
Jun 6 10:13:00 Josh-Barrows-MacBook-Pro ManagedClient[302]: HIToolbox: received notification of WindowServer event port death.
Jun 6 10:13:00 Josh-Barrows-MacBook-Pro SecurityAgent[308]: kCGErrorFailure: _CGSLockWindow: Cannot synchronize window backing store


I would absolutely love to provide the WindowServer crash log, but the forum is prohibiting me from posting that much text, or upload a text file that large (it's 33k).
jbarrow is offline  
Old 06-06-2011, 04:02 PM   #4
Carlo
Mac Team
 
Join Date: Feb 2009
Posts: 606
Default

Quote:
Originally Posted by jbarrow View Post
I would absolutely love to provide the WindowServer crash log, but the forum is prohibiting me from posting that much text, or upload a text file that large (it's 33k).
Thank you very much for your help. It really looks like a "blue" screen as opposed to a kernel panic. The Window Server can't start. Could you please post the crash using http://www.displaylink.com/support/ask_question.php
If at all possible would be great to have also the full output from http://www.displaylink.com/support/ticket.php?id=269

A workaround could be to delete the DisplayLinkGA.plugin folder from /System/Library/Extensions after the installation and before rebooting.

Thank you again for helping with this big cat.
Carlo
Carlo is offline  
Old 06-06-2011, 05:01 PM   #5
jbarrow
Member
 
Join Date: Feb 2011
Location: Northeast Oklahoma, USA
Posts: 31
Default Crash Info Using Display Link tool

Here is the DisplayLink Information.zip file that the tool generated.
Attached Files
File Type: zip DisplayLink Information.zip (313.9 KB, 696 views)
jbarrow is offline  
Old 06-06-2011, 05:26 PM   #6
jbarrow
Member
 
Join Date: Feb 2011
Location: Northeast Oklahoma, USA
Posts: 31
Default

The proposed work-around didn't work, but thanks for the effort. I'll continue waiting patiently for the next beta version, I suppose, unless you have any other suggestions.
jbarrow is offline  
Old 06-06-2011, 07:25 PM   #7
Carlo
Mac Team
 
Join Date: Feb 2009
Posts: 606
Default

Thank you very much for all the information, we have some leads to try in a lab in WWDC today.
Carlo is offline  
Old 06-06-2011, 07:33 PM   #8
jbarrow
Member
 
Join Date: Feb 2011
Location: Northeast Oklahoma, USA
Posts: 31
Default

Excellent. Do post here as soon as you find out something, please.
jbarrow is offline  
Old 06-07-2011, 07:09 PM   #9
Carlo
Mac Team
 
Join Date: Feb 2009
Posts: 606
Default

I don't have particularly good news: tried on a clean Mac Pro and a MBP at WWDC and all working. Also working fine on my test MacBook. Next step is to try to reproduce the issue on more machines but we already tested on one very, very similar to yours.
The only thing I can think of is some machine specific problem with the 64bit kernel, maybe in conjunction with a specific display set up. We do try 64bit but test more the default configuration.

Will keep you updated.
Carlo is offline  
Old 06-07-2011, 07:22 PM   #10
jbarrow
Member
 
Join Date: Feb 2011
Location: Northeast Oklahoma, USA
Posts: 31
Default

That *is* bad news. Over the weekend, I may try a clean install if something else doesn't come up before hand. Thanks for the updates, Carlo.
jbarrow is offline  
 


Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT. The time now is 05:30 AM.


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