Post

Replies

Boosts

Views

Activity

Reply to Big Sur panic when connect/disconnect usb-c dock
I'm also seeing constant kernel panics when connecting/disconnecting my monitors. I have a 2021 16" MacBook Pro (2019 model, 2.3 GHz 8-Core Intel Core i9, 32 GB 2667 MHz DDR4, Intel UHD Graphics 630 1536 MB) and am running Big Sur 11.3.1. The machine is only a couple of weeks old and I can easily reproduce the problem by simply connecting and disconnecting the monitor cable 2 or 3 times. I initially thought the problem was my CalDigit TS3 Plus but I started to remove all peripherals to see what was causing the problem and eventually got to a single monitor (Dell U2415) and a single USB-C to DisplayPort cable - no dock or hub involved. I disconnected keyboard, trackpad, headphones, yubi key, etc etc. I even booted in safe mode but issue persists. My crash report is the same as reported by most folks in this thread: panic(cpu 0 caller 0xffffff801d69f6b6): [kext.kalloc.2048]: element modified after free (off:1672, val:0xfffffffe00000000, sz:2048, ptr:0xffffff93926d4000, prot:zero) The interesting bit I found was that everything works fine if I connect my monitors via HDMI rather than DisplayPort. So at the moment I have 2 external monitor connected via USB-C to HDMI cables (1 using the TS3 dock, and 1 using a cheap USB hub).
Topic: App & System Services SubTopic: Core OS Tags:
Jun ’21
Reply to Big Sur panic when connect/disconnect usb-c dock
Just realised one of my Dell monitors has an option to use DisplayPort 1.1 (instead of the default 1.2) and in this mode it doesn't seem to crash my laptop. I'll leave this running for another while to see if it gets around the problem. Of course this option might not be available in more recent monitors and also DP 1.1 is very limiting in terms of resolution/refresh rate (it can't run 4K at 60fps) but for anyone with lower res monitors suffering daily crashes this might be a better compromise until Apple get their act together.
Topic: App & System Services SubTopic: Core OS Tags:
Jul ’21
Reply to Is macOS now so broken that it's no longer worth fixing bugs?
You're not alone... I spent weeks troubleshooting a kernel panic on my brand new top-of-the-line 16" MacBook Pro and eventually figured it was caused by connecting an external monitor via DisplayPort. The crash report looks similar to one of your issues: element modified after free. Apple support is truly infuriating. After a million useless steps they won't accept the blame and just point fingers at "third-party" devices... I mean, hello??? It's just a bloody monitor! As it turned out, I found two workarounds that may help you: 1) use HDMI instead of DisplayPort, or 2) disable DisplayPort 1.2 support on your monitor if possible. Both aren't great options of course as your max resolution may be limited, but it may be better than multiple crashes a day. See this other thread: https://developer.apple.com/forums/thread/678644
Topic: App & System Services SubTopic: Core OS Tags:
Jul ’21