emilevirus Posted March 24, 2019 Share Posted March 24, 2019 I'm getting kernel panics on my laptop every few hours. It's caused by IONVMeFamily, but my NVMe is an Adata sx6000 which is supposedly compatible with MacOS. Panics are very random. Sometimes it happens 10 minutes after booting up and sometimes 5 hours. I can't figure out why. Specs: HP 17-BY0062ST 8 GB DDR4 2400 MHz i5-8250U Adata sx6000 + 1 TB HDD Anonymous UUID: 65CBDC89-F93F-1600-75A9-8D6C3660ABDC Sat Mar 23 18:53:49 2019 *** Panic Report *** panic(cpu 3 caller 0xffffff7f9f4b2172): nvme: "Fatal error occurred. CSTS=0x1 US[1]=0x0 US[0]=0x6c VID/DID=0x576210ec . FW Revision=V9001b19\n"@/BuildRoot/Library/Caches/com.apple.xbs/Sources/IONVMeFamily/IONVMeFamily-387.230.1/IONVMeController.cpp:5327 Backtrace (CPU 3), Frame : Return Address 0xffffff8130d2ba10 : 0xffffff801c9aeb0d 0xffffff8130d2ba60 : 0xffffff801cae8653 0xffffff8130d2baa0 : 0xffffff801cada07a 0xffffff8130d2bb10 : 0xffffff801c95bca0 0xffffff8130d2bb30 : 0xffffff801c9ae527 0xffffff8130d2bc50 : 0xffffff801c9ae373 0xffffff8130d2bcc0 : 0xffffff7f9f4b2172 0xffffff8130d2be20 : 0xffffff801d05e147 0xffffff8130d2be90 : 0xffffff801d05e069 0xffffff8130d2bec0 : 0xffffff801c9eb085 0xffffff8130d2bf40 : 0xffffff801c9eac35 0xffffff8130d2bfa0 : 0xffffff801c95b0ce Kernel Extensions in backtrace: com.apple.iokit.IONVMeFamily(2.1)[ABA6DFDD-AC72-3008-83FE-EF9722E66FEB]@0xffffff7f9f49d000->0xffffff7f9f4dcfff dependency: com.apple.driver.AppleMobileFileIntegrity(1.0.5)[A2492141-9480-3177-BC7D-455925BB4A2E]@0xffffff7f9db0b000 dependency: com.apple.iokit.IOPCIFamily(2.9)[5C9A453F-559B-3683-9E81-D288D13A33CE]@0xffffff7f9d295000 dependency: com.apple.driver.AppleEFINVRAM(2.1)[328FCBD7-8C2C-3A4A-AF92-9270C1403891]@0xffffff7f9dc44000 dependency: com.apple.iokit.IOStorageFamily(2.1)[9B2E7108-AA17-3998-BF41-4B1297F455E5]@0xffffff7f9d941000 dependency: com.apple.iokit.IOReportFamily(47)[5F165AE5-F4F2-3415-857C-34F2462A730E]@0xffffff7f9d3db000 BSD process name corresponding to current thread: kernel_task Boot args: lilucpu=9 Mac OS version: 18D109 Kernel version: Darwin Kernel Version 18.2.0: Thu Dec 20 20:46:53 PST 2018; root:xnu-4903.241.1~1/RELEASE_X86_64 Kernel UUID: 1970B070-E53F-3178-83F3-1B95FA340695 Kernel slide: 0x000000001c600000 Kernel text base: 0xffffff801c800000 __HIB text base: 0xffffff801c700000 System model name: MacBookPro14,1 (Mac-B4831CEBD52A0C4C) System uptime in nanoseconds: 7213294349950 last loaded kext at 3444781076145: com.apple.driver.AppleXsanScheme 3 (addr 0xffffff7f9fa3e000, size 32768) last unloaded kext at 3708147405925: com.apple.driver.AppleXsanScheme 3 (addr 0xffffff7f9fa3e000, size 32768) loaded kexts: (none) EOF Model: MacBookPro14,1, BootROM 184.0.0.0.0, 4 processors, Intel Core i5, 1.80 GHz, 8 GB, SMC 2.43f6 Graphics: Intel UHD Graphics 620, Intel UHD Graphics 620, Built-In Memory Module: BANK 0/DIMM0, 8 GB, DDR4, 2400 MHz, Ramaxel Technology, RMSA3260NA78HAF-2400 Network Service: Ethernet, Ethernet, en0 Serial ATA Device: HGST HTS541010B7E610, 1 TB Serial ATA Device: hp DVDRW GUE1N USB Device: USB 3.0 Bus USB Device: Bluetooth Radio USB Device: HP TrueVision HD Camera Thunderbolt Bus: [/CODE] Send me emiles-MacBook-Pro (1).zip Link to comment Share on other sites More sharing options...
MaLd0n Posted March 24, 2019 Share Posted March 24, 2019 check if work, replace full clover folder and install last clover version again CLOVER.zip Link to comment Share on other sites More sharing options...
emilevirus Posted March 25, 2019 Author Share Posted March 25, 2019 (edited) It seems ok now. What did you change? Edited March 25, 2019 by emilevirus Link to comment Share on other sites More sharing options...
MaLd0n Posted March 26, 2019 Share Posted March 26, 2019 13 hours ago, emilevirus said: It seems ok now. What did you change? many fixs via DSDT, compare both files enjoy Link to comment Share on other sites More sharing options...
weeze Posted June 7, 2019 Share Posted June 7, 2019 I have pretty much the same KP when booting from the NVMe drive on my ThinkPad E480. I've done a diff between OP's and MaLd0n's patched DSDT, but there's a lot going on there. Any insight into what sort of patches are needed for this drive would be great. Based on reading through the patched DSDT, it seems like a PXSX device needs to be replaced on the RP0* device that corresponds to the NVMe controller (without _PRW?), among many other changes, such as removing device-specific methods for the RP0* device and returning 0 from the _INI method... obviously I'm not sure what I'm talking about yet but I'm learning as I go. Sadly, booting from USB (when boot drive is APFS) rarely works, usually getting stuck at "End RandomSeed" but not outputting any "+" signs. So that I can get proper file dumps / reporting files, I'm working on using ditto to create an HFS Mojave drive to boot from so I have a working install to work off of. I'll post what I can once I have a stable system up and running. Link to comment Share on other sites More sharing options...
weeze Posted June 11, 2019 Share Posted June 11, 2019 If anyone else finds this and is wondering the cause of the issue, I've determined that my kernel panic (which seems to be same as OP but cannot confirm) is due to the PM981 Samsung SSD in the drive. I'm solving through replacing the drives as it seems through my research the patches available are not full proof. Link to comment Share on other sites More sharing options...
Recommended Posts