NVMe for Mac Pro 5,1

[ammulder]

The actual page fault you are encountering is not in the driver, it is in fact 6 calls deep into the completion routine. There are two possibilities here, one that the driver somehow corrupted memory that the callback routine depends on, or that the call back routine has a logic/timing error.

If this is code that you have developed, perhaps you can instrument it to help determine if the driver is corrupting memory or, (assuming that this runs on other storage devices) whether it is a timing issue.

So one of the crashes was during a routine shutdown. I couldn't tell any difference from a normal shutdown, but on startup, I got one of those "your machine shut down because of a problem" messages and the stack trace was in the report it offered to send to Apple. I assume that completion routine is in OS X code somewhere.

The other two crashes were during shutdown of the iOS Simulator, part of XCode, again suggesting the completion routine is in Apple code, or the JavaScript VM, or something like that. The only code I wrote in that case is JavaScript that runs in the browser within iOS, and has no direct access to make I/O calls.

At some point I will see if I can make a small test case of the simulator crash, but it's not going to be REAL small as you'll need to install XCode and various JavaScript libraries to run it.

I don't have a lot of urgency though because I can run the iOS Simulator on a different machine, and otherwise it's been quite stable. I've done a lot of video transcoding and transferring, which is about as many bytes as I ever shuffle to and from storage, and I managed to bork the network driver but the NVMe disk is still running strong.

The only other comment I have is that it's quite slow (by which I mean a few seconds) to delete files on the order of a few GB. I take this to be cleaning up performed by whatever the NVMe TRIM-equivalent is. But I wish it would run asynchronously instead of blocking the delete call until that's done. Not sure whether that's really wise and/or within your power or not.

 

[onemanstartup]

So one of the crashes was during a routine shutdown. I couldn't tell any difference from a normal shutdown, but on startup, I got one of those "your machine shut down because of a problem" messages and the stack trace was in the report it offered to send to Apple. I assume that completion routine is in OS X code somewhere.

The other two crashes were during shutdown of the iOS Simulator, part of XCode, again suggesting the completion routine is in Apple code, or the JavaScript VM, or something like that. The only code I wrote in that case is JavaScript that runs in the browser within iOS, and has no direct access to make I/O calls.

I've got the same troubles. I don't panic at shutdown, but iOS simulator is what I need to be stable

 

[Chopper-K]

Lauwie and jimj740 are great!!

Did anyone succeed in RAID in NVMe on MP5.1?

 

[Brabbelbla]

First of all, many thanks to jimj740 for releasing the NVMe driver, which unlocks the great potential of NVMe for OS X users.

Secondly, @jimj740, I was wondering, is any development going on right now? In this thread, and at other places, too, I saw some reports from people having KP's at shutdown/restart (slow sleep/wake?), and you did respond here, but it did not seem like a definite answer. So is there any chance for those issues getting resolved, or is this more or less the final state of the driver?

 

[magnifico]

I also have problem with El Capitan, I give me a kernel panic at shutdown pc, while Yosemite everything works perfectly

Anonymous UUID: EE5B15CC-F8C2-40CF-8EE5-29AAB8E82A42

SatMar1210:03:482016

***PanicReport***
panic(cpu 0caller0xffffff8013effb5c):"waitq deadlock - waitq=0xffffff81fc3f2e00, cpu=0\n"@/Library/Caches/com.apple.xbs/Sources/xnu/xnu-3248.30.4/osfmk/kern/waitq.c:2742
Backtrace(CPU 0),Frame:ReturnAddress
0xffffff9208f4bd60:0xffffff8013edf792
0xffffff9208f4bde0:0xffffff8013effb5c
0xffffff9208f4be20:0xffffff8013effe5e
0xffffff9208f4be40:0xffffff7f96c34abc
0xffffff9208f4be70:0xffffff7f96c35f5b
0xffffff9208f4beb0:0xffffff7f96c35d90
0xffffff9208f4bef0:0xffffff80144b6ef6
0xffffff9208f4bf40:0xffffff80144b4d61
0xffffff9208f4bf80:0xffffff80144b4e56
0xffffff9208f4bfb0:0xffffff8013fccf77
KernelExtensionsin backtrace:
com.MinnowStor.NVMeGeneric(1.0)[27312503-CF2F-3E2B-8D8D-6E79177410C9]@0xffffff7f96c30000->0xffffff7f96c3cfff
dependency: com.apple.iokit.IOPCIFamily(2.9)[F398CE94-0FBD-3E8E-A7AB-55F7F05A81ED]@0xffffff7f9472c000
dependency: com.apple.iokit.IOStorageFamily(2.1)[DC1AAB7C-F417-3238-BB3F-2A5B84D67B90]@0xffffff7f9464c000

 

[bacosca]

Me too, with the m2 950pro

*** Panic Report ***
Panic(CPU 0): Unresponsive processor (this CPU did not acknowledge interrupts) TLB state:0x0
RAX: 0xffffff802c717240, RBX: 0xffffff91f487ae08, RCX: 0xffffff8028e41db0, RDX: 0x0000005200000000
RSP: 0xffffff81f3183dc0, RBP: 0xffffff81f3183de0, RSI: 0x000000533d896dc0, RDI: 0xffffff91f487ae08
R8: 0xffffff802838d000, R9: 0x0000000000000388, R10: 0x0000000000000000, R11: 0x0000000000000001
R12: 0x0000000000000000, R13: 0x0000000000000001, R14: 0xffffff91f487ae00, R15: 0xffffff91f487ae00
RFL: 0x0000000000000006, RIP: 0xffffff80049c4d90, CS: 0x0000000000000008, SS: 0x0000000000000010
Backtrace (CPU 0), Frame : Return Address
0xffffff81c8ae0f80 : 0xffffff80049d18cf
0xffffff81c8ae0fd0 : 0xffffff80049f03f9
0xffffff81f3183de0 : 0xffffff80048ffb5c
0xffffff81f3183e20 : 0xffffff80048ffe5e
0xffffff81f3183e40 : 0xffffff7f8635aabc
0xffffff81f3183e70 : 0xffffff7f8635bf5b
0xffffff81f3183eb0 : 0xffffff7f8635bd90
0xffffff81f3183ef0 : 0xffffff8004eb6ef6
0xffffff81f3183f40 : 0xffffff8004eb4d61
0xffffff81f3183f80 : 0xffffff8004eb4e56
0xffffff81f3183fb0 : 0xffffff80049ccf77
Kernel Extensions in backtrace:
com.MinnowStor.NVMeGeneric(1.0)[27312503-CF2F-3E2B-8D8D-6E79177410C9]@0xffffff7f86356000->0xffffff7f86362fff
dependency: com.apple.iokit.IOPCIFamily(2.9)[F398CE94-0FBD-3E8E-A7AB-55F7F05A81ED]@0xffffff7f8512c000
dependency: com.apple.iokit.IOStorageFamily(2.1)[DC1AAB7C-F417-3238-BB3F-2A5B84D67B90]@0xffffff7f8504c000

 

[magnifico]

Me too, with the m2 950pro

*** Panic Report ***
Panic(CPU 0): Unresponsive processor (this CPU did not acknowledge interrupts) TLB state:0x0
RAX: 0xffffff802c717240, RBX: 0xffffff91f487ae08, RCX: 0xffffff8028e41db0, RDX: 0x0000005200000000
RSP: 0xffffff81f3183dc0, RBP: 0xffffff81f3183de0, RSI: 0x000000533d896dc0, RDI: 0xffffff91f487ae08
R8: 0xffffff802838d000, R9: 0x0000000000000388, R10: 0x0000000000000000, R11: 0x0000000000000001
R12: 0x0000000000000000, R13: 0x0000000000000001, R14: 0xffffff91f487ae00, R15: 0xffffff91f487ae00
RFL: 0x0000000000000006, RIP: 0xffffff80049c4d90, CS: 0x0000000000000008, SS: 0x0000000000000010
Backtrace (CPU 0), Frame : Return Address
0xffffff81c8ae0f80 : 0xffffff80049d18cf
0xffffff81c8ae0fd0 : 0xffffff80049f03f9
0xffffff81f3183de0 : 0xffffff80048ffb5c
0xffffff81f3183e20 : 0xffffff80048ffe5e
0xffffff81f3183e40 : 0xffffff7f8635aabc
0xffffff81f3183e70 : 0xffffff7f8635bf5b
0xffffff81f3183eb0 : 0xffffff7f8635bd90
0xffffff81f3183ef0 : 0xffffff8004eb6ef6
0xffffff81f3183f40 : 0xffffff8004eb4d61
0xffffff81f3183f80 : 0xffffff8004eb4e56
0xffffff81f3183fb0 : 0xffffff80049ccf77
Kernel Extensions in backtrace:
com.MinnowStor.NVMeGeneric(1.0)[27312503-CF2F-3E2B-8D8D-6E79177410C9]@0xffffff7f86356000->0xffffff7f86362fff
dependency: com.apple.iokit.IOPCIFamily(2.9)[F398CE94-0FBD-3E8E-A7AB-55F7F05A81ED]@0xffffff7f8512c000
dependency: com.apple.iokit.IOStorageFamily(2.1)[DC1AAB7C-F417-3238-BB3F-2A5B84D67B90]@0xffffff7f8504c000

On El capitain or Yose?

 

[bacosca]

yes on el capitan, also its seen as external drive

 

[magnifico]

yes on el capitan, also its seen as external drive

Mhmm very strange on yose work perfect whyle on yose no..mmm
@ Dev can you resolve this strange problem?
Thz

 

[NeroTheWolf]

This driver isn't working for me and many other users on 10.11.4. I PM'd you a copy of the kernel panic I'm getting. Is there any way you could take a look at it?

Thanks!

 

[magnifico]

This driver isn't working for me and many other users on 10.11.4. I PM'd you a copy of the kernel panic I'm getting. Is there any way you could take a look at it?

Thanks!

Perhaps the developer is working on this annoying problem...very strange on yosemite 10.10.5 work perfect

 

[Brabbelbla]

Out of my own curiosity; which motherboards do you guys have?

 

[magnifico]

@ Devoleper have you a news about problem on EL capitain?

 

[Brabbelbla]

@magnifico: no mobo?

@jimj740 has been offline for almost two weeks now, has ignored my own PM's and post in this thread for one-and-a-half month now and to my knowledge hasn't posted anything regarding his NVMe driver for months. There was a post on tonymacx86 from someone else announcing a debugging session, with the dev, but no news after that. Of course the fact there IS a driver (which within certain boundaries does its job fine) at all is thanks to him , so kudos for that. But I have given up hope for a resolution anytime soon.

 

[magnifico]

does the job in half, on el capitan does not work, a job half does not make sense for the community, end of story.

My mobo is asrock z97 extreme 6

 

[Hackaro]

does the job in half, on el capitan does not work, a job half does not make sense for the community, end of story.

My mobo is asrock z97 extreme 6

Purtroppo!

Same here ... this driver is not reliable at all! Keep causing problems in shutdown (restart instead of shutdown) and in wake up after sleep.

I strongly suggest not to use it if it will not be updated

does anybody know if there are other 3rd party drivers that can be used instead of it?
[doublepost=1461150866][/doublepost]

Out of my own curiosity; which motherboards do you guys have?

Gigabyte Z170X Gaming 5

 

[joevt]

I've been using the NVMe driver on a Gigabyte Z170X Gaming 7. I have Mac OS X 10.11.4 booting from an NVMe drive. I'm using two 512GB Samsung 950 Pros. I haven't noticed any real problems, except at shutdown. I've disabled sleep for now and depend on the CPU 800 MHz idle to save power so I haven't encountered any sleep panics.

I have the built in serial port (COM port) of the Gaming 7 motherboard connected to another Mac and have "debug=0x108 serial=3 serialbaud=115200" added to boot args in Clover config to output kprintf and IOLog messages out the serial port.

It panics only half the time at shutdown. A shutdown without panic looks like this from the serial port (you might notice some output is missing - the serial port output is not perfect, flow control is disabled, maybe multiple kernel threads will write messages to the serial port at the same time? Using serialbaud=57600 doesn't help much and just makes it slower):

backing_store_stop_compaction = TRUE
Kext loading now disabled.
Kext unloading now disabled.
Kext autounloading now disabled.
Kernel requests now disabled.
Process launchd [1] disabling system-wide I/O Throttling
WProcess launchd [1] disabling system-wide CPU Throttling
eProcess mds_stores [194] disabling system-wide I/O Throttling
Process mds_stores [194] disabling system-wide CPU Throttling
d May  4 00:08:38 2016 Joes-Giga-Mac.local com.apple.xpc.launchd[1] (com.apple.xpc.launchd.domain.system) <Notice>: System shutdown initiated by: shutdown.1720<-sessionlogoutd.1719<-launchd.1

in6_unlink_ifa: IPv6 address 0x6c581c394be9cd99 has no prefix
hfs: unmount initiated on Empty2 on device disk1s5
hfs: unmount initiated on Empty1 on device disk1s2
Wed May  4 00:08:41 2016 Joes-Giga-Mac.local com.apple.xpc.launchd[1] (com.apple.xpc.launchd.domain.system) <Notice>: Userspace teardown took: 3040 ms

PMRD: PagingOff all drivers took 25 ms
syncing disks... Killing all processes

continuing
hfs: unmount initiated on ElCappy on device disk3s2
Unmount of /home failed (45)
Unmount of /net failed (45)
hfs: unmount initiated on ElCapitan on device unknown device
done
MACH Reboot
[AppleBroadcomBluetoothHostController][SetHIDEmulation] ### ERROR: opCode = 0xFC3B (Broadcom VSC -- Enable HID Emulation) -- send request failed -- err = 0x0001 (kBluetoothHCIErrorUnknownHCICommand)
REQUIRE_NO_ERR failure: 0x1 - file: /BuildRoot/Library/Caches/com.apple.xbs/Sources/IOBluetoothFamily_kexts/IOBluetoothFamily-4404.4.4/Core/Family/HCI/HostControllers/IOBluetoothHostController.cpp:22169
REQUIRE_NO_ERR failure: 0x1 - file: /BuildRoot/Library/Caches/com.apple.xbs/Sources/IOBluetoothFamily_kexts/IOBluetoothFamily-4404.4.4/Core/Family/HCI/Transports/USB/BroadcomBluetoothHostControllerUSBTransport/BroadcomBluetoothHostC
**** [IOBluetoothHostControllerUSBTransport][InterruptReadHandler] -- Received kIOReturnAborted error - retrying: 1 -- 0x2800
**** [IOBluetoothHostControllerUSBTransport][InterruptReadHandler] -- failed to post another Read on the interrupt pipe -- error (0xE00002D8 (kIOReturnNotReady)) queueing next read.
**** [IOBluetoothHostControllerUSBTransport][DoDeviceReset] -- thread_call_enter1 (mReEnumerateOrResetThread) -- reEnumerateOrReset = 1 (ReEnumerate Module) --  returned FALSE -- 0x2800 ****
**** [IOBluetoothHostControllerUSBTransport][ReEnumerateOrResetThreadEntry] -- entering -- param0 = 0x2800, param1 = 0x0001 -- 0x2800
**** [IOBluetoothHostControllerUSBTransport][ReEnumerateOrResetThreadEntry] -- exiting -- 0x2800

028309.614991 AppleUSBHostResources@: AppleUSBHostResources::allocateDownstreamBusCurrentGated: assuming successful wakeUnits 150 sleepUnits 0
028309.627403 AppleUSBHostResources@: AppleUSBHostResources::allocateDownstreamBusCurrentGated: assuming successful wakeUnits 150 sleepUnits 0
028309.641477 AppleUSBHostResources@: AppleUSBHostResources::allocateDownstreamBusCurrentGated: assuming successful wakeUnits 150 sleepUnits 0
028309.653835 AppleUSBHostResources@: AppleUSBHostResources::allocateDownstreamBusCurrentGated: assuming successful wakeUnits 150 sleepUnits 0
028309.666313 AppleUSBHostResources@: AppleUSBHostResources::allocateDownstreamBusCurrentGated: assuming successful wakeUnits 150 sleepUnits 0
PMRD: Restart still waiting on IntelMausi
Restart still waiting on IntelMausi
Ethernet [IntelMausi]: Link down on en0
PMRD: Restart driver IntelMausi (0x1000002ad) took 5189 ms
X86PlatformPlugin::systemWillShutdown!
X86PlatformPlugin::systemWillShutdown!
PMRD: Restart all drivers took 5393 ms

One of the panics looks like this:

backing_store_stop_compaction = TRUE
Kext loading now disabled.
Kext unloading now disabled.
Kext autounloading now disabled.
Kernel requests now disabled.
Process launchd [1] disabling system-wide I/O Throttling
Process launchd [1] disabling system-wide CPU Throttling
WProcess mds_stores [194] disabling system-wide I/O Throttling
eProcess mds_stores [194] disabling system-wide CPU Throttling
d May  4 00:10:33 2016 Joes-Giga-Mac.local com.apple.xpc.launchd[1] (com.apple.xpc.launchd.domain.system) <Notice>: System shutdown initiated by: shutdown.475<-sessionlogoutd.474<-launchd.1

Panic(CPU 4): Unresponsive processor (this CPU did not acknowledge interrupts) TLB state:0x0
RAX: 0xffffff806eeae490, RBX: 0xffffff93d8342e08, RCX: 0xffffff806c594db0, RDX: 0x00006de700000000
RSP: 0xffffff93d84abdc0, RBP: 0xffffff93d84abde0, RSI: 0x00006de7ba53e735, RDI: 0xffffff93d8342e08
R8:  0xffffff806b829800, R9:  0x000000000000028e, R10: 0x0000000000000000, R11: 0x0000000000000001
R12: 0x0000000000000000, R13: 0x0000000000000001, R14: 0xffffff93d8342e00, R15: 0xffffff93d8342e00
RFL: 0x0000000000000006, RIP: 0xffffff801f9c0c40, CS:  0x0000000000000008, SS:  0x0000000000000010
Backtrace (CPU 4), Frame : Return Address
0xffffff83cbbe0f80 : 0xffffff801f9cd77f
0xffffff83cbbe0fd0 : 0xffffff801f9ec439
0xffffff93d84abde0 : 0xffffff801f8fb11c
0xffffff93d84abe20 : 0xffffff801f8fb41e
0xffffff93d84abe40 : 0xffffff7fa1ea5abc
0xffffff93d84abe70 : 0xffffff7fa1ea6f5b
0xffffff93d84abeb0 : 0xffffff7fa1ea6d90
0xffffff93d84abef0 : 0xffffff801feb4956
0xffffff93d84abf40 : 0xffffff801feb27c1
0xffffff93d84abf80 : 0xffffff801feb28b6
0xffffff93d84abfb0 : 0xffffff801f9c8e27
      Kernel Extensions in backtrace:
         com.MinnowStor.NVMeGeneric(1.0)[27312503-CF2F-3E2B-8D8D-6E79177410C9]@0xffffff7fa1ea1000->0xffffff7fa1eadfff
            dependency: com.apple.iokit.IOPCIFamily(2.9)[4FE41F9B-2849-322A-BBF8-A94816C003D6]@0xffffff7fa010a000
            dependency: com.apple.iokit.IOStorageFamily(2.1)[DC1AAB7C-F417-3238-BB3F-2A5B84D67B90]@0xffffff7fa0168000

BSD process name corresponding to current thread: kernel_task
Boot args: -v dart=0 nvda_drv=1 nv_spanmodepolicy=1 uia_exclude=HS11;HS12;HS13;HS14;USR1;USR2;SS07;SS08;SS09;SS10;HS02 debug=0x108 serial=3 serialbaud=115200

Mac OS version:
15E65

Kernel version:
Darwin Kernel Version 15.4.0: Fri Feb 26 22:08:05 PST 2016; root:xnu-3248.40.184~3/RELEASE_X86_64
Kernel UUID: 4E7B4496-0B81-34E9-97AF-F316103B0839
Kernel slide:     0x000000001f600000
Kernel text base: 0xffffff801f800000
__HIB  text base: 0xffffff801f700000
System model name: iMac17,1 (Mac-65CE76090165799A)

System uptime in nanoseconds: 84821635310
Panic initiated, string: "TLB invalidation IPI timeout: " "CPU(s) failed to respond to interrupts, unresponsive CPU bitmap: 0x%llx, NMIPI acks: orig: 0x%lx, now: 0x%lx"@/Library/Caches/com.apple.xbs/Sources/xnu/xnu-3248.40.184/osfmk/x86_64/pmap.c:2596
panic(cpu 7 caller 0xffffff801f9ad0aa): "TLB invalidation IPI timeout: " "CPU(s) failed to respond to interrupts, unresponsive CPU bitmap: 0x10, NMIPI acks: orig: 0x0, now: 0x1"@/Library/Caches/com.apple.xbs/Sources/xnu/xnu-3248.40.
Debugger called: <panic>
Debugger called: <panic>
Backtrace (CPU 7), Frame : Return Address
0xffffff83d6aab950 : 0xffffff801f8dab12
0xffffff83d6aab9d0 : 0xffffff801f9ad0aa
0xffffff83d6aaba70 : 0xffffff801f9b3f0b
0xffffff83d6aabb60 : 0xffffff801f9b4c36
0xffffff83d6aabbd0 : 0xffffff801f960cc5
0xffffff83d6aabce0 : 0xffffff801f95626c
0xffffff83d6aabd10 : 0xffffff801f951733
0xffffff83d6aabd40 : 0xffffff801f8e451d
0xffffff83d6aabd60 : 0xffffff801f8cd84a
0xffffff83d6aabdb0 : 0xffffff801f8fea0a
0xffffff83d6aabdf0 : 0xffffff801fd9a998
0xffffff83d6aabe60 : 0xffffff801fdb31ae
0xffffff83d6aabee0 : 0xffffff801fdb36c7
0xffffff83d6aabf20 : 0xffffff801f8d548d
0xffffff83d6aabf60 : 0xffffff801f9cec4e
0xffffff83d6aabf80 : 0xffffff801f9ec23f

BSD process name corresponding to current thread: SpotlightNetHelp
Attempting to commit panic log to NVRAM
EFI: couldn't save panic info (err = 80000010)

Debugger not configured. Hanging.

Here's another panic:

backing_store_stop_compaction = TRUE
Kext loading now disabled.
Kext unloading now disabled.
Kext autounloading now disabled.
Kernel requests now disabled.
Process launchd [1] disabling system-wide I/O Throttling
WProcess launchd [1] disabling system-wide CPU Throttling
ed May  4 00:54:19 2016 Process mds_stores [193] disabling system-wide I/O Throttling
in6_unlink_ifa: IPv6 address 0xa41389f76cb9fafd has no prefix
JProcess mds_stores [193] disabling system-wide CPU Throttling
oes-Giga-Mac.local com.apple.xpc.launchd[1] (com.apple.xpc.launchd.domain.system) <Notice>: System shutdown initiated by: shutdown.508<-sessionlogoutd.507<-launchd.1

Panic initiated, string: "waitq deadlock - waitq=%p, cpu=%d\n"@/Library/Caches/com.apple.xbs/Sources/xnu/xnu-3248.40.184/osfmk/kern/waitq.c:2742
panic(cpu 1 caller 0xffffff80026fb11c): "waitq deadlock - waitq=0xffffff83b965ae00, cpu=1\n"@/Library/Caches/com.apple.xbs/Sources/xnu/xnu-3248.40.184/osfmk/kern/waitq.c:2742
Debugger called: <panic>
Debugger called: <panic>
Backtrace (CPU 1), Frame : Return Address
0xffffff93bb683d60 : 0xffffff80026dab12 
0xffffff93bb683de0 : 0xffffff80026fb11c 
0xffffff93bb683e20 : 0xffffff80026fb41e 
0xffffff93bb683e40 : 0xffffff7f84ca5abc 
0xffffff93bb683e70 : 0xffffff7f84ca6f5b 
0xffffff93bb683eb0 : 0xffffff7f84ca6d90 
0xffffff93bb683ef0 : 0xffffff8002cb4956 
0xffffff93bb683f40 : 0xffffff8002cb27c1 
0xffffff93bb683f80 : 0xffffff8002cb28b6 
0xffffff93bb683fb0 : 0xffffff80027c8e27 
      Kernel Extensions in backtrace:
         com.MinnowStor.NVMeGeneric(1.0)[27312503-CF2F-3E2B-8D8D-6E79177410C9]@0xffffff7f84ca1000->0xffffff7f84cadfff
            dependency: com.apple.iokit.IOPCIFamily(2.9)[4FE41F9B-2849-322A-BBF8-A94816C003D6]@0xffffff7f82f0a000
            dependency: com.apple.iokit.IOStorageFamily(2.1)[DC1AAB7C-F417-3238-BB3F-2A5B84D67B90]@0xffffff7f82f68000

BSD process name corresponding to current thread: kernel_task
Boot args: -v dart=0 nvda_drv=1 nv_spanmodepolicy=1 uia_exclude=HS11;HS12;HS13;HS14;USR1;USR2;SS07;SS08;SS09;SS10;HS02 debug=0x108 serial=3 serialbaud=115200 debug=0x108 serial=3 serialbaud=57600 io=0x00200000 

Mac OS version:
15E65

Kernel version:
Darwin Kernel Version 15.4.0: Fri Feb 26 22:08:05 PST 2016; root:xnu-3248.40.184~3/RELEASE_X86_64
Kernel UUID: 4E7B4496-0B81-34E9-97AF-F316103B0839
Kernel slide:     0x0000000002400000
Kernel text base: 0xffffff8002600000
__HIB  text base: 0xffffff8002500000
System model name: iMac17,1 (Mac-65CE76090165799A)

System uptime in nanoseconds: 437654525979
Attempting to commit panic log to NVRAM
EFI: couldn't save panic info (err = 80000010)

Debugger not configured. Hanging.

 

[machinesworking]

Hi, unluckily enough I didn't know this was an issue (NVMe VS UHCI in OSX etc.), until I bought a 512GB SM951 for dirt cheap off of Amazon.

Luckily enough I did get the driver working, after dealing with getting the ownership assigned etc.
No kernel panics or other issues anyway.

Here's the deal though, on my system (Mac Pro 2009) it's reading as an internal drive, and with a read speed of 775mbs, roughly half of what a single SM951 can read in the X16 slot in the Pro. System report states it's got a link speed of 2.5 and link width of 4X... anyway to fix this? and anyone else have this issue?

 

[flowrider]

^^^^Yes move it to a X4 slot. There is a problem with the card in a X16 slot.

https://forums.macrumors.com/threads/samsung-sm951-ssd-help.1973512/#post-22921615

Lou

 

[Baunkjaer]

No matter the gain, I would appreciate a 950 Pro as it´s cheaper than the SM951.

 

[Gabeloooooo]

So, my understanding is that there is still no way to get xCode simulator to be stable on the NVMe drive (I'm getting the panics)?

I have to move my OSX install to a non nvme drive to get xcode simulator working reliably?

 

[Daniel_dbb]

Hi, I did some tests with 950 and 951 running in the same mp5.1, I used 2 mp5.1 2010 12core,
Angelbird Wings PX1 M.2 Adapter and Lycom DT-120 M.2 to PCIe adapter.
951 works with both adapters on both mp's anytime while 950 only at one mp
Everytime when I removed 950 from the mp, restart w/out and put them back in the same or other slot mp didn't boot at all (white screen).
PRAM reset made it possible to use 950 again. Concerning speed in x4 slot (1,2) both ssd R/W with 1500 mb/sec while in x16 (3rd slot) both made 775mb/sec. Of course mp booted from sata ssd not from nvme.
I tried to get them working in Raid0 with appleRAID and SoftRAID 5.5 - no.go ... (Error-50), could not write or create Volume. Once long time after start I succeed to get diglloyTools running Sequential Test at Raid0, only once and never again.
I have some other test to run. Let you know when any news.
Did someone tried Boot Camp Windows with nvme disks in mp?

 

[joevt]

I've switched to using a patched NVMeFamily.kext (removed NVMeGeneric.kext). It stopped the kernel panics at shutdown / startup.
https://github.com/RehabMan/patch-nvme

 

[Ulmo]

I agree this should get moved... but will leave it up to the moderators. The danger is really that I do not see the new thread and am not notified of threads I am not following...

To be clear, it would be helpful to know exactly what is not working. There is no need to substitute the symbolic names for the admin user and wheel group; the numeric value of 0:0 is fine.

There can be several possible problems here...

1) The working directory of your terminal process must contain the NVMeGeneric.kext, or alternately you must specify the full path to the kext (such as sudo chown -R 0:0 /Library/ExtensionsNVMeGeneric.kext since you already put it there)

2) Ideally you want ownership set correctly BEFORE moving the kext to /Library/Extensions... but if you copy it there with incorrect ownership and later fix the ownership, you can recover by issuing the command sudo touch /Library/Extensions which will let the system know to scan for new drivers.

If the two steps above don't fix the issue, what does the following command line return? ls -ld /Library/Extensions/NVMeGeneric.kext

-JimJ

Calling Jim J 740! @jimj740 !!! I think you already know what I'm calling you for I'd like to use your wonderful driver under Sierra. I posted a new thread at https://forums.macrumors.com/threads/intel-ssd-750-for-macos-sierra-10-12.2001916/ and I'd like for you to go there and help me out. I'd be willing to plead or pay for your assistance, or that of anybody that can help solve this for me. Thank you. Please go to that thread for that topic.

 

[TheStork]

I, too, am using the NVMeGeneric.kext. Unfortunately, it is not compliant with Sierra. Will there be an update to the NVMeGeneric.kext for Sierra? You have many users who are dependent upon the NVMeGeneric.kext for the capability it brings to our computing systems.