Repository navigation
10.15 beta 4 AppleIntelMCEReporter #424
Description
Is there away we can get a new patch added to Lilu to patch AppleIntelMCEReporter.kext. Apple has introduced a new controller inside the driver called AppleIntelMCEInteruptController which has included the iMacPro1,1, MacPro6,1 and assume the new MacPro7,1 board-ids. This is causing kernel panic for Ivy Bridge-EP CPUs.
10.15 beta 3 AppleIntelMCEReporter.kext Info.plist
https://imgur.com/S9De4FP
10.15 beta 4 AppleIntelMCEReporter.kext Ino.plist
https://imgur.com/ACDbmQf
Activity
PMheart commentedon Jul 17, 2019
Hello,
I have several ideas to test:
PMheart commentedon Jul 17, 2019
Sorry for the close. Reopening.
vit9696 commentedon Jul 17, 2019
It makes sense to me to block kext with OC, Lilu has nothing to do with it. Closing as not an issue really.
Pavo-IM commentedon Jul 17, 2019
Use OC Kernel > Block did not work. This is from OC logs:
00:000 00:000 OC: Prelink blocker com.apple.driver.AppleIntelMCEReporter init failure - Not FoundI am assuming Kernel > Block section can only block kexts that is in the Prelink and not during booting phase. The KP is happening on update phase and fresh install phase.
vit9696 commentedon Jul 17, 2019
Well, ok, do provide a panic log now then with keepsyms=1 in boot arguments and the kext file attached.
Pavo-IM commentedon Jul 17, 2019
https://imgur.com/QRawrsH
vit9696 commentedon Jul 17, 2019
Please reread what I said, make good sense of it, and provide the necessary data. Thank you.
Pavo-IM commentedon Jul 17, 2019
Oh my bad here is the kext, didn't read that part lol.
AppleIntelMCEReporter.kext.zip
vit9696 commentedon Jul 17, 2019
It's keepsyns=1 instead of keepsyms=1 too, and thus no symbols are visible ^^
Pavo-IM commentedon Jul 17, 2019
26 remaining items
naveenkrdy commentedon Sep 26, 2019
Here is a small codeless kext to disable it.
AppleMCEReporterDisabler.kext.zip
And also any idea why the kext blocking mechanism of OC is not working for this kext ?
and i have also observed that blocking AppleIntelCPUpowermanagement.kext is also not working and due to that i had to use nullcpu kext .
vit9696 commentedon Sep 26, 2019
I think the issue is in kextd reloading the kext after blocking. It will be nice if you could create a separate bugreport for failing kext blocking with examples of working and not working kext blocks. I think we could try increasing kext version in addition to kmod patching or maybe nulling the constructors…
naveenkrdy commentedon Sep 27, 2019
@vit9696 sure! will create a seperate bugreport for it.
zhang-wenchao commentedon Oct 24, 2019
@naveenkrdy Me too. I must needs AppleMCEReporterDisabler.kext and NullCPUPowerManagement.kext. Thank you for your work.
@vit9696 CPUFriend not work
Pavo-IM commentedon Oct 24, 2019
Well looks like the Disablerkext isn't working for 10.15.1 b3. Guess I'll have to use a different SMBIOS until CPUFriend or something else has figured out how to disable this from getting loaded.
zhang-wenchao commentedon Oct 26, 2019
My CPU is Intel Xeon Gold 5117，must fackcpuid 0x0306E0 to boot。
mrmiller commentedon Oct 26, 2019
Are you running OpenCore? I submitted patches a month or so ago that allow Xeon Golds (and others) to boot without a fake CPU ID. That is unrelated to this issue and workaround though.
zhang-wenchao commentedon Oct 26, 2019
This is causing kernel panic for Ivy Bridge-EP CPUs, If my don't use fakecpuid, 10.15 should work.
Pavo-IM commentedon Oct 26, 2019
Here is a pic of the new panic of AppleIntelMCEReporter
startergo commentedon Nov 18, 2019
I can report the same issue in Catalina 10.15.1 with a real MacPro5,1 and iMacPro1.1 board ID. It does not happen in Mojave. Please see here:
https://www.insanelymac.com/forum/topic/338516-opencore-discussion/?do=findComment&comment=2697758
Gengik84 commentedon Dec 2, 2019
HI
I know it's not a good solution but for now it's the only way for use some smbios.
I avoid KP by simply putting the original kext from S/L/E into EFI's folder.
I hope for a better solution and Apple will also fix some bugs about it.
vit9696 commentedon Dec 4, 2019
Yes, we hope too. I removed the patch from CPUFriend as it does not work anyway, thus closing the issue.
startergo commentedon Dec 14, 2019
Please elaborate. To solve the issue you remove the kext from S/L/E and load it from the EFI/Kexts? Or you use some specific kext?
Gengik84 commentedon Dec 14, 2019
No, you only have to put the original kext into EFI/OC/kext folder.
I didn't say to remove any kext from S/L/E.