Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
Status
Not open for further replies.

Macschrauber

macrumors 68030
Dec 27, 2015
2,981
1,487
Germany
So I got brave and restarted thru the garbage collection just with -no_compat_check and it also survived without any OpenCore version.

wait, why does it runs for hours and fails for hours.

cold boot, smc reset...

so did smc reset (cut mains for a few seconds) and I got a freeze !
5A2DA7FB-E151-4A6D-AA09-C6DFA35F603D.jpeg





next step

booting into a known working system, in this case my mavericks tool disk, warm boot into OpenCore, selecting 11.3 and it boots again.


so theres an issue with cold booting?

thats maybe the reason why nvram reset helps, as the restarts during the reset changes the situation from cold boot to warm boot?
 
Last edited:

cdf

macrumors 68020
Jul 27, 2012
2,256
2,583
@Macschrauber, these are interesting test results. If I've understood correctly: with OCLP you observed a rather good success rate (20 successful boots in a row). OCLP enables several kexts more than prescribed in the OC thread here. I wonder if these extra kexts are not slowing down the boot process just enough to help with the underlying race condition...
 

Macschrauber

macrumors 68030
Dec 27, 2015
2,981
1,487
Germany
@Macschrauber, these are interesting test results. If I've understood correctly: with OCLP you observed a rather good success rate (20 successful boots in a row). OCLP enables several kexts more than prescribed in the OC thread here. I wonder if these extra kexts are not slowing down the boot process just enough to help with the underlying race condition...


I also tested about 10 times rebooting without any OpenCore flavor.

With the same boot-args oclp set plus no compat check

(keepsyms=1 debug=0x100 -v -no_compat_check)

then thought what about adding my AHCI test blade.

Stopped thinking, but than I do a smc reset. So did a smc reset allone without adding hardware.

And got into this cold boot after smc reset situation and 11.3 stopped booting.

Cold booted into another OS, restarted and selected oclp again and got back into a booting 11.3


what we can try is simply reboot once or twice via open core when cold booting the machine.
 

JohnD

macrumors regular
Jun 2, 2005
150
97
Los Angeles, California
so theres an issue with cold booting?

thats maybe the reason why nvram reset helps, as the restarts during the reset changes the situation from cold boot to warm boot?
Nope - I always perform the 20x reboots test and have both successes and fails from both cold boots and warm boots (from my SATA SSD on PCIe card - the SATA HDD in sled bay does fail, just nowhere near as often). My last test was for a claim of an older version of OpenCore working for someone yesterday, so I only performed 10x reboots, and here's that result (which is consistent with the ~50% success/fail I've always experienced from the PCIe SSD, regardless of test - none have had any apparent influence).

warm - success
warm - fail
cold - success
warm - success
warm - success
warm - success
warm - success
warm - fail
cold - fail
cold - fail
 

Macschrauber

macrumors 68030
Dec 27, 2015
2,981
1,487
Germany
Nope - I always perform the 20x reboots test and have both successes and fails from both cold boots and warm boots (from my SATA SSD on PCIe card - the SATA HDD in sled bay does fail, just nowhere near as often). My last test was for a claim of an older version of OpenCore working for someone yesterday, so I only performed 10x reboots, and here's that result (which is consistent with the ~50% success/fail I've always experienced from the PCIe SSD, regardless of test - none have had any apparent influence).

warm - success
warm - fail
cold - success
warm - success
warm - success
warm - success
warm - success
warm - fail
cold - fail
cold - fail

My test rig was just with a Sata SSD connected to the backplane bays. One 3,46 Quad CPU.
 

startergo

macrumors 603
Sep 20, 2018
5,022
2,283
this time I took care to set Startup Disk from the prefpane to the Big Sur 11.3 Disk
Code:
An error occurred while setting “BigSurSSD” as the startup disk: The operation couldn’t be completed. (SDErrorDomain error 104.)
 

freqrider

macrumors regular
Feb 10, 2019
213
74
I can't even pretend I have the knowledge most of the people in this forum have; I just like to tinker. Still, this is, to my understanding, a valid point: if there is an incompatibility with PCIe in cMPs, it will definitely have an impact on GPUs. So, what if the problem is in the way 11.3 and 11.4 handle storage and kexts such as IOStorageFamily?

Just a thought.
I too suspect IOStorageFamily as the problem persists not just with nvme drives but any pci storage.
 

startergo

macrumors 603
Sep 20, 2018
5,022
2,283
I have added to my NVMe SSDT's Chipset name: SSD Controller:
1619970014506.png

This can be added through device properties as well. Also I have added through device properties
pci-aspm-default 02000000
1619970316042.png

Not sure which one helped, but with Lycom-120 and OWC Aura Nvme installed I can boot every other time. First time I get the usual NVMe panic and the second boot is successful.
 

w1z

macrumors 6502a
Aug 20, 2013
692
481
I have added to my NVMe SSDT's Chipset name: SSD Controller:
View attachment 1768680
This can be added through device properties as well. Also I have added through device properties
pci-aspm-default 02000000
View attachment 1768681
Not sure which one helped, but with Lycom-120 and OWC Aura Nvme installed I can boot every other time. First time I get the usual NVMe panic and the second boot is successful.

Is this with or without the nvmefix.kext as the latest commits added aspm support?
 

startergo

macrumors 603
Sep 20, 2018
5,022
2,283
Upgraded my MBP15,1's thunderbolt OWC NVMe drive to BS 11.4b1 and booting without any issues.
 

JohnD

macrumors regular
Jun 2, 2005
150
97
Los Angeles, California
Installed 11.3 in a Parallels VM (host running 11.2.3). Attempting to boot the 11.3 VM, my screens went black, and the whole system rebooted! Um, that shouldn't happen... I'll run some more tests tomorrow night - need the system stable for work tomorrow - just thought there might be a clue in that behavior.
 

PeterHolbrook

macrumors 68000
Sep 23, 2009
1,625
441
Installed 11.3 in a Parallels VM (host running 11.2.3). Attempting to boot the 11.3 VM, my screens went black, and the whole system rebooted! Um, that shouldn't happen... I'll run some more tests tomorrow night - need the system stable for work tomorrow - just thought there might be a clue in that behavior.
I reported my experience with Parallels and 11.3 about one week ago. It didn't cause my Mac to reboot, but I was unable to update 11.2.3 to 11.3 on the virtual machine (this happened twice). However, I succeeded in creating an 11.3 virtual machine from scratch.
 

JohnD

macrumors regular
Jun 2, 2005
150
97
Los Angeles, California
I reported my experience with Parallels and 11.3 about one week ago. It didn't cause my Mac to reboot, but I was unable to update 11.2.3 to 11.3 on the virtual machine (this happened twice). However, I succeeded in creating an 11.3 virtual machine from scratch.
Yes, I recall. My clean install of 11.2.3 finally gave me the option to upgrade to 11.3, so I 'successfully' upgraded it to 11.3, but upon booting, out go the lights. One thing to note actually, is that due to the Parallels networking issue, where you cannot use bridged networking in a VM, I enabled KEXT mode in the Parallels config.

/Library/Preferences/Parallels/network.desktop.xml - change <UseKextless> from 1 to 0.
1620049659097.png
 
Last edited:

Enricote

macrumors regular
Oct 7, 2018
129
100
Madrid, Spain
I reported my experience with Parallels and 11.3 about one week ago. It didn't cause my Mac to reboot, but I was unable to update 11.2.3 to 11.3 on the virtual machine (this happened twice). However, I succeeded in creating an 11.3 virtual machine from scratch.
Apple has just released BigSur 11.3.1 (20E241) with 11.49 GB. Any difference?
Screenshot 2021-05-03 at 19.32.30.png
 
Last edited:

MacToby

macrumors member
May 13, 2020
66
19
Europe
Apple has just released BigSur 11.3.1 (20E241) with 11.49 GB. Any difference? View attachment 1769190
Huh? What is this? I downloaded macOS Big Sur 11.3.1 as an update and then when I clicked restart to install the update my Mac just did a normal restart and then I got this. It looks like my Mac is now re-downloading the update. I come from macOS Big Sur 11.2.3
 

Attachments

  • 505746E4-A630-4912-B399-1CCA913B263B.png
    505746E4-A630-4912-B399-1CCA913B263B.png
    158.4 KB · Views: 87
Status
Not open for further replies.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.