Problems after waking from sleep - log included

[adk1889]

My Macbook (Alum 13") running 10.6.3 has problems when waking from sleep, when my displaylink device is attached. Here are some log messages I get when this problem occurs. Any ideas?

6/12/10 4:00:32 PM DisplayLinkUserAgent[149] (00112b30.382)-[DLDistributedNotificationCenter stream:handleEvent:] Server did die - reconnecting
6/12/10 4:00:32 PM DisplayLinkUserAgent[149] (00112b30.389)-[DLDistributedNotificationCenter stream:handleEvent:] reconnected.
6/12/10 4:00:32 PM DisplayLinkUserAgent[149] (00112b30.374)-[DLDistributedNotificationCenter stream:handleEvent:] stream error: Error Domain=NSPOSIXErrorDomain Code=57 UserInfo=0x403aa0 "The operation couldn’t be completed. Socket is not connected"
6/12/10 4:00:32 PM DisplayLinkUserAgent[149] (00112b30.382)-[DLDistributedNotificationCenter stream:handleEvent:] Server did die - reconnecting
6/12/10 4:00:32 PM DisplayLinkUserAgent[149] (00112b30.389)-[DLDistributedNotificationCenter stream:handleEvent:] reconnected.
6/12/10 4:00:32 PM DisplayLinkUserAgent[149] (00112b30.374)-[DLDistributedNotificationCenter stream:handleEvent:] stream error: Error Domain=NSPOSIXErrorDomain Code=57 UserInfo=0x403aa0 "The operation couldn’t be completed. Socket is not connected"
6/12/10 4:00:32 PM DisplayLinkUserAgent[149] (00112b30.382)-[DLDistributedNotificationCenter stream:handleEvent:] Server did die - reconnecting
6/12/10 4:00:32 PM DisplayLinkUserAgent[149] (00112b30.389)-[DLDistributedNotificationCenter stream:handleEvent:] reconnected.
6/12/10 4:00:32 PM DisplayLinkUserAgent[149] (00112b30.374)-[DLDistributedNotificationCenter stream:handleEvent:] stream error: Error Domain=NSPOSIXErrorDomain Code=57 UserInfo=0x403aa0 "The operation couldn’t be completed. Socket is not connected"
6/12/10 4:00:32 PM DisplayLinkUserAgent[149] (00112b30.382)-[DLDistributedNotificationCenter stream:handleEvent:] Server did die - reconnecting
6/12/10 4:00:32 PM DisplayLinkUserAgent[149] (00112b30.389)-[DLDistributedNotificationCenter stream:handleEvent:] reconnected.
6/12/10 4:00:32 PM DisplayLinkUserAgent[149] *** Assertion failure in -[DLDistributedNotificationCenter writeDatanStreamNumber:], /cruisecontrol/projects/Nivo_Mac1.6_01-devel_Mac_CLEAN/nivo/app/MacOSX/DisplayLinkUserAgent/../app/DLNotificationCenter/DLDistributedNotificationCenter.m:604
6/12/10 4:00:32 PM DisplayLinkUserAgent[149] An uncaught exception was raised
6/12/10 4:00:32 PM DisplayLinkUserAgent[149] Streams differ even though we are a client
6/12/10 4:00:32 PM DisplayLinkUserAgent[149] *** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'Streams differ even though we are a client'
*** Call stack at first throw:
(
0 CoreFoundation 0x982f9bda __raiseError + 410
1 libobjc.A.dylib 0x961d9509 objc_exception_throw + 56
2 CoreFoundation 0x982f9908 +[NSException raise:format:arguments:] + 136
3 Foundation 0x95e4fdc3 -[NSAssertionHandler handleFailureInMethodbject:file:lineNumber:descr iption:] + 116
4 DisplayLinkUserAgent 0x000052c6 -[DLDistributedNotificationCenter writeDatanStreamNumber:] + 705
5 DisplayLinkUserAgent 0x000045f3 -[DLDistributedNotificationCenter stream:handleEvent:] + 290
6 Foundation 0x95ee3223 _outputStreamCallbackFunc + 82
7 CoreFoundation 0x982eedd3 _signalEventSync + 99
8 CoreFoundation 0x982ef7be _cfstream_solo_signalEventSync + 126
9 CoreFoundation 0x982eea88 _CFStreamSignalEvent + 792
10 CoreFoundation 0x982ef737 CFWriteStreamSignalEvent + 39
11 CFNetwork 0x91455d11 _ZN12SocketStream40dispatchSignalFromSocketCallbac kUnlockedEP24SocketStreamSignalHolder + 101
12 CFNetwork 0x91402819 _ZN12SocketStream14socketCallbackEP10__CFSocketmPK 8__CFDataPKv + 217
13 CFNetwork 0x91402721 _ZN12SocketStream22_SocketCallBack_streamEP10__CFS ocketmPK8__CFDataPKvPv + 117
14 CoreFoundation 0x982ab035 __CFSocketDoCallback + 325
15 CoreFoundation 0x982aac97 __CFSocketPerformV0 + 311
16 CoreFoundation 0x98264ff1 __CFRunLoopDoSources0 + 1201
17 CoreFoundation 0x98262c1f __CFRunLoopRun + 1071
18 CoreFoundation 0x982620f4 CFRunLoopRunSpecific + 452
19 CoreFoundation 0x98261f21 CFRunLoopRunInMode + 97
20 Foundation 0x95dc0380 -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 279
21 Foundation 0x95dc025d -[NSRunLoop(NSRunLoop) run] + 76
22 DisplayLinkUserAgent 0x00002852 main + 602
23 DisplayLinkUserAgent 0x000025be _start + 216
24 DisplayLinkUserAgent 0x000024e5 start + 41
)

[mastahype]

I've got the same stack trace in multiple crash logs so this is definitely a bug.
What I've noticed is that if you wait a few minutes, the macbook will recover. It's as if it's caught in some state that takes time to come out of.

[Carlo]

adk/mastahype we tried to reproduce this issue on a number of machines but could not see it. Can you please gather the system and DL info using the tool at http://www.displaylink.com/support/ticket.php?id=269
You can send the file through http://www.displaylink.com/support/ask_question.php

[mastahype]

Originally Posted by Carlo

adk/mastahype we tried to reproduce this issue on a number of machines but could not see it. Can you please gather the system and DL info using the tool at http://www.displaylink.com/support/ticket.php?id=269
You can send the file through http://www.displaylink.com/support/ask_question.php

I've already done this and sent my info before with the tool. The server definitely crashes. I've just sent what I had at that time again. And if you can't reproduce the sleep issue, use any recent Macbook Pro with 10.6.4 with the following:

Primary display on displayport.
Secondary display on DisplayLink device.
Lid closed (I always have my lid closed).

Putting the machine back to sleep using a keyboard shortcut, then re-waking seems to work to reset it most of the time (along with restarting the USB driver), but some times it hard locks up the machine.

The only USB devices I have connected are iPhones and a USB hub at any given time.

[Carlo]

Thank you for the logs, these have been helpful to reproduce the issue.

I can see a similar issue with a simpler setup on a MacBookPro 5,5 (you have a 5,1). Reproduction steps:
- Connect a DisplayLink screen
- Set both the display and the system to sleep after 1 minute.
- Wait for the system to sleep (pulsing LED)
- Wake
- Main screen comes up, DisplayLink screen does not come up. GUI frozen.
- Wait for 1 minute for the display to dim (full display sleep not needed) then move the mouse/touch the trackpad
- All screens work, GUI works

I want to make sure we're working on the right issue. Can you please check if you can reproduce the problem with these steps as well?

[mastahype]

I can confirm that is the behavior. Although my macbook usually needs longer for the initial sleep condition (the 1 minute cycle doesn't seem to cut it). So, after 1 minute the laptop goes to sleep, I leave it for a while and wake it to the cyclops mode (DisplayLink LCD won't wake). Then, after the next idle timeout and the screens go blank, the following wake enables the DisplayLink LCD.

[Carlo]

Thank you mastahype, I think I traced where the problem is, prototyping a solution now and hope to have a build to try soon.

[mastahype]

This would be the single biggest issue I have with the product. I've spent countless hours (including today) trying to create workarounds for this.
I held back recommending it to a friend because of this, but he did proceed to get his Macbook after my recommendation.

Hope you get something that works soon.

[Pawel]

We are happy to inform that there is a new 1.6 Beta 3 driver available for download from here.

This release has fixed a GUI freeze issue when resuming from sleep on some systems.

Regards

[Pawel]

This issue has been discussed here.