[TM1701] System crashes when running memory intense operations. #740
Comments
MrFoxPro
changed the title
MrFoxPro
changed the title
|
Thank you for the detailed description and log. One thing worth trying is to dis-enable |
CPU error could be because I tried to disable SIP. Not sure btw. I also ran memtest for a hour, had two passes, probably ram is fine. I'm wondering if I can get more detailed logs |
|
I deleted some entries from config.plist and crashes became less frequent. My suspicion on RestrictEvents.kext |
|
Could it be because of running out of memory and macos trying to use swap? |
|
Same errors here: https://www.tonymacx86.com/threads/sudden-macos-hang-ups-kernel-traps.297883/page-2 I'm not sure, seems like SMBus is already configured in this repo. So I will run memtest for night and see if I have ram problems. |
|
According to OC instructions, SSDT-MCHC should be changed to PC00.SMBC: |
In the sample, they change the SMBUS' ACPI path because the ACPI path for their SMBus device is I don't think patching SMBus will help with this issue. The |
|
|
|
@MrFoxPro You can try out the lastest 0E07 package in https://github.com/daliansky/XiaoMi-Pro-Hackintosh/blob/main/BIOS/TM1701/XMAKB5R0P0E07.exe |
|
I think it's memory leak. Whenever I start simulator and it fully loads, it takes almost full RAM, I have only ~100M free of 16GB. I'm not sure if it's correct behavior. |
|
As for now:
Nothing helped I installed Sonoma alongside and WiFI driver doesn't work, but! Ethernet via type-c hub suddenly connected. |
|
I don't think it's an EFI related issue, but rather a user space problem. If a specifix kext causes kernel panic, you can see clearly the kext name in the crash report. Maybe related to SSD model. You can try NVMeFix or tune SetApfsTrimTimeout in config.plist. For Sonoma wifi, you need to make sure you install the latest beta. AirportItlwm_Sonoma used in v1.8.0 release only supports beta5+. Ref: OpenIntelWireless/itlwm#883 (comment) |
Yep thank you, I will try. Right now I updated BIOS as you suggested and my MacOS now doesn't boot at all. I think I need to reinstall again. Btw, can you suggest 100% working SSD model? |
|
After updating the BIOS, you need to patch cfg and 64dvmt again, or turn on the AppleXcpmCfgLock and reverse framebuffer-fbmem and framebuffer-stolenmem changes. For compatible SSD model, I recommend referring to dortania/bugtracker#192 |
Not quite understood, does ***A07 BIOS compatable with dvmt64 and cfg unlock patches? |
|
Yes, it does compatible. However, upgrading BIOS will restore every changes you made to BIOS (e.g. cfg, 64dvmt) to factory setting, so you have to patch them again or use the original config. |
|
So, I:
Same errors: kernel trap / memory corruption Anyway, thank you for your work and especially for involvement in my issue! |
MrFoxPro
changed the title
|
Also, does system-boot or nvme slot matter? As I remember they have different number or bus lanes. |
|
One of my guesses turned out to be true:
I was lucky to buy used Samsung 960 EVO and now it's not crashing. Before, when I started apps, Thank you @stevezhengshiqi |
|
I faced this issue again after a while. Seems like it happened because of running fstrim on linux. And seems like it could be fixed by removing/create new empty apfs partitions with some reserved size |
State the model
Xiaomi Mi Notebook Pro i7-8550U, 16Gb, MX150
MacOS 13.5.2(Same on 12, 13, 14)MacOS installed on 512GB SSD with
Silicon Motion SM2263XTcontroller in 0 slot alongside with Windows and other partitions, and second SSD with Linux hasSilicon Powercontroller.State the version of the EFI
Tried 1.7.9 and beta-8c15a8f
Describe the bug
System crashes when running memory intense operations: unpacking Xcode xip, running IOS simulator. I tried OpenCore 1.7.0, OpenCore beta, and Clover from mentioned before beta.
NOTE: I have patched EC604 BIOS (patch for fans temp by Cyb).
I also removed AirportItlwm_* for previous MacOS versions from
Kextsfolder and removed it fromconfig.plist. But before this it was crashing too.System log
timed-out on cpu 4, NMI-ing
Possible memory corruption
Kernel trap at 0xffffff8010ee1d3f, type 14=page
panic(cpu 2 caller 0xffffff8008195d23): Possible memory corruption
panic(cpu 4 caller 0xffffff8011595e03): Possible memory corruption
panic(cpu 6 caller 0xffffff8006797925): Possible memory corruption
Attach your entire EFI folder
efi.zip
Attach system.log
log
My installation process was:
Thank you for you work and will also appreciate your help!
The text was updated successfully, but these errors were encountered: