Contribute
Register

IONVMeController.cpp compatibility with EVO 960

Status
Not open for further replies.
Joined
Apr 29, 2013
Messages
9
Mac
  1. MacBook Pro
Hi,

First - I am actually running on a 2015 Macbook Pro Model 11,3 where I have removed the original Apple SSD and inserted a Samsung EVO 960 SSD using an NGFF adapter from Sintech.

I am writing this thread in order to hear if there could be some kind of solution / fix to make the above combination more stable in regards to rebooting...

What I see is that if I do a reboot of the machine it will take very long time for it to show the logon screen - plus 45 secs.

Sometimes during reboot it will do a Kernel Panic and try again.

Eventually it will show the login screen and I can login.

Then sometimes the computer is now stable for several weeks because I just close the lid and make the computer sleep. No problems.

But sometimes after logging in the computer gived KP again.

So the NVME driver seems to not be completely happy about the Samsung NVME - are there any patches available??

This is the KP log message that I see:

*** Panic Report ***

panic(cpu 0 caller 0xffffff7f9dedaa3c): nvme: "Fatal error occurred. CSTS=0x3

. FW Revision=3B7QCXE7\n"@/BuildRoot/Library/Caches/com.apple.xbs/Sources/IONVMeFamily/IONVMeFamily-356.30.6/IONVMeController.cpp:5275

Backtrace (CPU 0), Frame : Return Address

0xffffff920d623a10 : 0xffffff801a44f606

0xffffff920d623a60 : 0xffffff801a57c654

0xffffff920d623aa0 : 0xffffff801a56e149

0xffffff920d623b20 : 0xffffff801a401120

0xffffff920d623b40 : 0xffffff801a44f03c

0xffffff920d623c70 : 0xffffff801a44edbc

0xffffff920d623cd0 : 0xffffff7f9dedaa3c

0xffffff920d623e30 : 0xffffff801aa95ecc

0xffffff920d623ea0 : 0xffffff801aa95df6

0xffffff920d623ed0 : 0xffffff801a488ec4

0xffffff920d623f40 : 0xffffff801a4889b5

0xffffff920d623fa0 : 0xffffff801a4004f7

Kernel Extensions in backtrace:

com.apple.iokit.IONVMeFamily(2.1)[8C2350A2-A812-3B8C-8DE1-3A6911793417]@0xffffff7f9dec8000->0xffffff7f9df04fff

dependency: com.apple.driver.AppleMobileFileIntegrity(1.0.5)[498548AE-30A0-36C6-92F7-1714D01C0A98]@0xffffff7f9b425000

dependency: com.apple.iokit.IOPCIFamily(2.9)[8E6C654E-4A8F-3C6B-BBFE-BA8A68C9C146]@0xffffff7f9ac94000

dependency: com.apple.driver.AppleEFINVRAM(2.1)[79C21A42-B04F-314F-BA88-F221F3D54094]@0xffffff7f9b2a3000

dependency: com.apple.iokit.IOStorageFamily(2.1)[B0FCE898-1542-34C0-B845-46FAE81DD9E6]@0xffffff7f9ae46000

dependency: com.apple.iokit.IOReportFamily(31)[D2F2FBDF-4EE4-38BA-99F5-B699F886F413]@0xffffff7f9b550000



BSD process name corresponding to current thread: kernel_task
 
Hi, I experience the same problem with the same drive.. (but the pro version) on same mac year..
I have the same kp who happens often...

Code:
*** Panic Report ***
panic(cpu 0 caller 0xffffff7f849374c6): nvme: "Fatal error occurred. CSTS=0xffffffff US[1]=0x0 US[0]=0x157 VID/DID=0xa804144d
. FW Revision=2B6QCXP7\n"@/BuildRoot/Library/Caches/com.apple.xbs/Sources/IONVMeFamily/IONVMeFamily-387.220.5/IONVMeController.cpp:5327

I think that it doesn't work right with samsung drives.. heard about intel drives working better. I think i'm gonna test that in the future. Or if anyone have the same mac as us with an other SSD with no kp would be great sharing it
 
Status
Not open for further replies.
Back
Top