Hi, everyone,
I've been following the Bridge OS thread as I had a single kernel panic and restart on my 13" MacBook Pro. Since then, though, I've had another issue a couple of times and I wonder if it's happened to anyone else.
My 2018 13" MacBook Pro is connected to an LG 4K monitor via USB-C to DisplayPort. It's been working fine but recently I tried to wake the MacBook and the monitor lit up but no picture showed. Moving my cursor, I could see that the screen was there as my cursor could move to it but nothing showed up. I tried different Thunderbolt ports on the MacBook, resetting the settings on the monitor, cycling the power on the monitor, etc. No luck. The only thing that fixed it last time was a restart on the MacBook (which I guess I'll have to do again in a minute). As this just happened again, here's what I'm seeing in the Console app (screenshot attached):
Process: WindowServer
Message: [ERROR] - Fallback GPU Display Pipe transaction submission failed
Any ideas? Luckily, Apple have already sent a replacement after talking to them about the Bridge OS thing but I'm still curious what's going on here. Also, this MacBook Pro was rock solid until day 16 – no crashes or anything like that – but since then I've had this issue 3/4 times.
Update:
I tried with a USB-C to HDMI and that didn't work either. Actually, it made my 4K monitor bright green and there was a big, blurry cursor. Weird. I tried both cables with my girlfriends 2016 MacBook and it works so it's not the cable or the monitor. Anyway, after all that trying I found more errors in Console (also attached as a screenshot):
Process: WindowServer
Message: [ERROR] - Driver bug - rowBytes too small. Display 0x1b56a19d, ioModeID 0x80007021, ioModeDepth 0x1, bytePerRow = 32, width = 1, bitsPerPixel = 32, minRowBytes = 13440 stored width = 3360. Forcing minRowBytes (possibly still wrong).
Note: I'd had no problems all day until the MacBook was asleep with the charger plugged in as well as the USB-C to DisplayPort cable. I'm almost certain that for the first half of the day I had no power and it'd been asleep on and off, without issue, as I was in and out. Hmm.
Lovely.
I've been following the Bridge OS thread as I had a single kernel panic and restart on my 13" MacBook Pro. Since then, though, I've had another issue a couple of times and I wonder if it's happened to anyone else.
My 2018 13" MacBook Pro is connected to an LG 4K monitor via USB-C to DisplayPort. It's been working fine but recently I tried to wake the MacBook and the monitor lit up but no picture showed. Moving my cursor, I could see that the screen was there as my cursor could move to it but nothing showed up. I tried different Thunderbolt ports on the MacBook, resetting the settings on the monitor, cycling the power on the monitor, etc. No luck. The only thing that fixed it last time was a restart on the MacBook (which I guess I'll have to do again in a minute). As this just happened again, here's what I'm seeing in the Console app (screenshot attached):
Process: WindowServer
Message: [ERROR] - Fallback GPU Display Pipe transaction submission failed
Any ideas? Luckily, Apple have already sent a replacement after talking to them about the Bridge OS thing but I'm still curious what's going on here. Also, this MacBook Pro was rock solid until day 16 – no crashes or anything like that – but since then I've had this issue 3/4 times.
Update:
I tried with a USB-C to HDMI and that didn't work either. Actually, it made my 4K monitor bright green and there was a big, blurry cursor. Weird. I tried both cables with my girlfriends 2016 MacBook and it works so it's not the cable or the monitor. Anyway, after all that trying I found more errors in Console (also attached as a screenshot):
Process: WindowServer
Message: [ERROR] - Driver bug - rowBytes too small. Display 0x1b56a19d, ioModeID 0x80007021, ioModeDepth 0x1, bytePerRow = 32, width = 1, bitsPerPixel = 32, minRowBytes = 13440 stored width = 3360. Forcing minRowBytes (possibly still wrong).
Note: I'd had no problems all day until the MacBook was asleep with the charger plugged in as well as the USB-C to DisplayPort cable. I'm almost certain that for the first half of the day I had no power and it'd been asleep on and off, without issue, as I was in and out. Hmm.
Lovely.
Attachments
Last edited: