A blogger that I usually follow finally reveals the problem, here is the link.
Point taken, however my choices seem to be: (1) Make Apple fix it or (2)
You are not being rude at all. This is very frustrating for all of us.
Just off the phone again with Apple and re-opened my case. This time they want me to reinstall MacOS. Nice.
It would seem my (our?) options are:
1) Keep returning the machines. Maybe when we get to 100,000, someone will take notice?
2) Futz with Apple support: reinstall MACOS, reset SMC, reset NVRAM, rinse & repeat
3) Wait for Apple to acknowledge there truly is a problem and hope they will release a patch/fix before we die of old age.
4) Buy a Dell?
A blogger that I usually follow finally reveals the problem, here is the link.
On the very first night, I had it panic with no external displays or accessories connected, just the power chord. Though after properly resetting NVRAM and SMC, haven't had the issue repeat yet for about a week now. It's not limited to sleeping while connected to external displays.
I also tried the USB adapter repro (connect while sleeping and wake it back up) - no luck.
It seems you are running iStat Menu, as I am. How many of us experiencing this problem are running iStat Menu?
A blogger that I usually follow finally reveals the problem, here is the link.
I didn't have iStat Menus installed when I had my kernel panic during sleep.
I just retried all the know repro attempts with iStats 6 running. No kernel panics from sleep.I am. Maybe just correlative though... but it is talking to Bridge OS to get all that data... you may have something... who isn’t who is having this issue is the better question...
This post is reinforcing my assumption regarding the T2 . It seems like it's reporting these issues not necessarily the cause of them. As i look through this thread and look at any stack traces they seem kernel related. My understanding T2 is it's own OS running, so it would be available after the OS crashed thus able to report these type issues. Of course I don't know for sure, but have had a bit of time debugging linux kernel and most of these issues I'm seeing look like they're software/driver related. So Bridge OS errors may be something of a red herring of multiple issues effecting these new machines and unless we have a Apple kernel dev willing to comment I don't think we can just put the blame on Bridge OS just yet.
Nice video.A blogger that I usually follow finally reveals the problem, here is the link.
Not only do I was send the report, but I also send along a nice little note full of colorful language LOL.Hopefully, everyone is doing this, but just in case: Make sure you click the "report" button to send your crash log to Apple. If you don't, they are making decisions on incomplete information.
Hopefully, everyone is doing this, but just in case: Make sure you click the "report" button to send your crash log to Apple. If you don't, they are making decisions on incomplete information.
Well I would think if everyone's macbooks were restarting. There be some.sort of recallUnknown
Also any way to track if it's certain models. Or models with certain configurations?
It seems you are running iStat Menu, as I am. How many of us experiencing this problem are running iStat Menu?
I am pretty sure not all macbook pros are affected. Its been a few weeks for me with my mac completely set up from a fresh install and it has not crashed once for any reason (I am getting that youtube playing bug though). Mine is a 15 inch 2.6/32GB/2TB. I have been using filevault encryption since day 1 too
[doublepost=1534997817][/doublepost]
Just to add, I am running istat menus and am not experiencing the issue
A blogger that I usually follow finally reveals the problem, here is the link.
It's great to see one of the bigger tech journalists releasing a video about this. Let's hope it gets others thinking about releasing one as well if they've been hit with the issue.
Yes please, this is what I've been advocating for from the start. More media attention. Put the pressure on Apple.
It's great to see one of the bigger tech journalists releasing a video about this. Let's hope it gets others thinking about releasing one as well if they've been hit with the issue.