Jan 22 17:43:50 jankpro2.local WindowServer: Display 0x003f003d: GL mask 0x2 bounds (0, 0), 1 modes available Off-line, enabled, Vendor ffffffff, Model ffffffff, S/N ffffffff, Unit 2, Rotation 0 Jan 22 17:43:50 jankpro2.local WindowServer: Display 0x003f003e: GL mask 0x4 bounds (0, 0), 1 modes available Off-line, enabled, Vendor ffffffff, Model ffffffff, S/N ffffffff, Unit 3, Rotation 0 Jan 22 17:43:50 jankpro2.local WindowServer: Display 0x003f003f: GL mask 0x8 bounds (0, 0), 1 modes available Off-line, enabled, Vendor ffffffff, Model ffffffff, S/N ffffffff, Unit 4, Rotation 0 Jan 22 17:43:50 jankpro2.local WindowServer: Display 0x003f0040: GL mask 0x10 bounds (0, 0), 2 modes available Main, Active, on-line, enabled, built-in, boot, Vendor 610, Model a022, S/N 0, Unit 0, Rotation 0 Jan 22 17:43:50 jankpro2.local WindowServer: Display 0x04280880: GL mask 0x21 bounds (0, 0), 62 modes available Jan 22 17:43:50 jankpro2.local WindowServer: WSMachineUsesNewStyleMirroring: true The domain/default pair of (/Library/Preferences/, IgnoreStartupCompatabilit圜heck) does not exist Jan 22 17:43:50 - last message repeated 2 times. Jan 22 17:43:50 jankpro2.local WindowServer: mux_initialize: Mode is dynamic Jan 22 17:43:50 - last message repeated 3 times.
Jan 22 17:43:50 jankpro2.local WindowServer: Found 1 modes for display 0x00000000 Jan 22 17:43:50 jankpro2.local WindowServer: Found 62 modes for display 0x00000000 As you can see below, some of the values reported by the WindowServer log end up being junk values (e.g., Model ffffffff), and there are some warnings about some singular transformation matrices later (IS SOMEBODY DIVIDING BY ZERO?) In a couple of instances I've had the freeze occur whilst *only* Preview was open, and I was just reading pdfs (admittedly about 200 of them). However, I have also noticed that the freeze can occur when I'm not running *my* GPU code. I do a lot of GPU computing, so I'm getting pretty good at getting my display to freeze, but it doesn't happen every time. It's only a display freeze I can still ssh in from a remote machine and perform computations that don't involve the GPU. Below I've attached some output from /var/log/system.log that preceded a freeze. I have noticed the display freeze is correlated with use of the NVIDIA GPU and/or GL. While I don't have a solution yet, I do have some data that may help the powers that be track down the cause:
Macbook pro late 2013 screen resolution lightning update#
I am having a display freeze problem as well on my 15" late 2013 Retina MBP (EFI 1.3 update installed).
0 kommentar(er)
