driver for apple storage controller 106b:2001

driver for apple storage controller 106b:2001

[David Craven]

Hello dear nvme mailing list,

I'm having trouble getting the ssd controller in the new apple macbook
2015 model to work.

This is what I tried:
insmod /usr/lib/modules/4.0.7-2-ARCH/kernel/drivers/block/nvme.ko.gz
echo "106b 2001" > /sys/bus/pci/drivers/nvme/new_id

And this is the error I got:
- @archiso ..ules/4.0.7-2-ARCH/kernel/drivers/block # echo "106b 2001"
> /sys/bus/pci/driuers/nume/new_id

[318.531670] nvme 0000:03:00.0: Minimum device page size (134217728)
too large for host (4096)
[318.537166] nvme 0000:03:00.0: Minimum device page size (134217728)
too large for host (4096)
[318.553789] BUG: unable to handle kernel NULL pointer dereference at
00000000000004ac
[318.555753] IP: [<fiffffff812c21f5>] kobject_put+0x15/0x210
[318.557122] PGD 0
[318.558475] Oops: 0000 [#1] PREEMPT SMP
[318.559838] Modules linked in: nume intel_rapl iosf_mbi
x86_pkg_temp_thermal intel_powerclamp coretemp kum_intel kum
snd_hda_codec_cirrus crc ul snd_hda_controller iTCO_wdt glue helper
snd_hda_codec led_class ablk_helper iTCO_uendor_support bdc_pci
input_polldeu cryptd iZc_i801 snd_hud h_fq_codel nfs lockd grace
sunrpc fscache ip_tables x_tables ext4 crc16 mbcache jbd2 dm_snapshot
dm_bufio dm_mod squashfs loop isofs sd_mod hid l_gtt uideo button
[318.567542] CPU: 1 PID: 553 Comm: nvme0 Not tainted 4.0.7-2-ARCH #1
[318.569110] Hardware name: Apple Inc.
MacBook8,1/Mac-BE0E8AC46FE800CC, BIOS MB81.882.0164.B06.1506051617
06/05/2015
[318.570702] task: fiff88025bcf32410 ti: ffff88025fb7c000 task.ti:
ffff88025fb7c000
[318.572303] RIP: 0010:[<ffffffff812c21f5A l<ffffffff812c21f5A
kobject_put+0x15/0x210
[318.573945] RSP: 0018:ffff88025fb7fe28 EFLAGS: 00010296
[318.575540] RAX: 0000000000000000 RBX: 0000000000000470 RCX: 000000000000000c
[318.577190] RDX: ffffiff181849340 RSI: 0000000000000246 RDI: 0000000000000470
[318.579031] RBP: ffff88025fb7fe48 R08: 0000000000000000 R09: 0000000000000000
[318.580860] R10: 0000000000000000 R11: 0000000000000000 R12: 1f11880251115150
[318.582686] R13: ffff88025f1f5150 R14: ffff88025f1f5160 R15: ffff88025f115000
[318.584513] FS: 0000000000000000(0000) GS:ffff88026ec40000(0000)
kn1GS:0000000000000000
[318.586349] CS: 0010 DS: 0000 ES: 0000 CRO: 0000000080050033
[318.588133] CR2: 00000000000004ac CR3: 000000000180b000 CR4:
[318.589886] DRO: 0000000000000000 DR1: 0000000000000000 DR2:
[318.591506] DR3: 0000000000000000 DR6: 00000000fffeOf10 DR7:
[318.593068] Stack:
[318.594659] ffff88025fb7fe58
[318.596246] ffff88025fb7fe58
[318.597830] fffiffffa064eed0
[318.599413] Call Trace:
[318.601012] [<ffffffff8128fbb5>] blk_put_queue+0x15/0x20
[318.602601] [<ffffiffa064eelb>] nume_free_deu+Oxdb/Ox110 [nvme]
[318.604237] [<ffffffffa064eed>] ? nvme_dev_release+0x40/0x40 [nvme]
[318.605879] [<fffffffa064eed>] ? nvme_dev_release+0x40/0x40 [nvme]
[318.607541] [<ffffiffa064efld>] nvme_remove_dead_ctr1+0x4d/Ox60 [nvme]
[318.609186] [<ffIffff810934b8>] kthread+Oxd8/Oxf0
[318.610837] [<fffiffff810933e0>] kthread_workerfn+Ox170/0x170
[318.612490] [<ffffffff8157a718>] ret_from_fork+0x58/0x90
[318.614162] [<ffffffff810933e0] 7 kthread_worker_fn+Ox170/0x170
[318.615802] Code: 00 eb a0 48 c7 c2 18 ad 73 81 eb c7 66 2e Of if 84
00 00 00 00 00 48 85 ff 74 2b 55 48 89 e5 41 55 41 54 53 48 89 fb 48
83 ec
[318.617595] RIP [<ffffffff812c2115>] kobject_put+0x15/0x210
[318.619232] RSP <ffff88025fb7feZ8>
[318.628882] CR2: 00000000000004ac
[318.622507] ---t end trace ce75ab8b43f65f78

Does this error message make sense to you guys? Is this the correct
driver for the 106b:2001, or does that need a totally different
driver? How can I go about deciphering this error? How do I find other
people with the same issue / am I at the right place here?
I'd really appreciate any pointers, help or suggestions you can give me.

Thank you
David

P.S It may have been screwed up a little by my ocr software, I'll fix
it up some more if it doesn't make sense...

driver for apple storage controller 106b:2001

[Keith Busch]

On Fri, 31 Jul 2015, David Craven wrote:
> I'm having trouble getting the ssd controller in the new apple macbook
> 2015 model to work.
>
> This is what I tried:
> insmod /usr/lib/modules/4.0.7-2-ARCH/kernel/drivers/block/nvme.ko.gz
> echo "106b 2001" > /sys/bus/pci/drivers/nvme/new_id
>
> And this is the error I got:
> - @archiso ..ules/4.0.7-2-ARCH/kernel/drivers/block # echo "106b 2001"
>> /sys/bus/pci/driuers/nume/new_id
>
> [318.531670] nvme 0000:03:00.0: Minimum device page size (134217728) too large for host (4096)
>
> [318.553789] BUG: unable to handle kernel NULL pointer dereference at  00000000000004ac

Hi,

This doesn't appear to be an NVMe device. Its "minimum page size"
supported is so absurd that I can't believe this is came from an NVMe
device register set.

If this were an NVMe device, you should not have needed to manually bind
the VID/DID to the nvme driver since it is a generic driver that binds
to all devices with an NVM-Express class code (10802h).

But since you've done this, you've discovered a bug that was present in
4.0, but fixed in 4.2. I should probably post these fixes to stable...

> Does this error message make sense to you guys? Is this the correct
> driver for the 106b:2001, or does that need a totally different
> driver? How can I go about deciphering this error? How do I find other
> people with the same issue / am I at the right place here?
> I'd really appreciate any pointers, help or suggestions you can give me.

I think this needs a different driver. If this really is an NVMe device,
then the h/w vendor either needs to adjust their implementation or supply
a quirk patch.

driver for apple storage controller 106b:2001

[Stephan Günther]

Hi David,

I have the same problem, but an ass of work at the moment. I will write 
another request asap.

For the time beeing: it seems to me that the Apple controller either 
reports an incorrect PCI-class-id (in that case it isn't an NVMe 
controller) or Apple built something that is reported in press to be an 
NVMe controller but is in reality some kind of PCIe-based SSD 
controller.

I don't have any experience with that kind of stuff, unfortunately.


Best,
Stephan


On 2015/July/31 02:38, David Craven wrote:
> Hello dear nvme mailing list,
> 
> I'm having trouble getting the ssd controller in the new apple macbook
> 2015 model to work.
> 
> This is what I tried:
> insmod /usr/lib/modules/4.0.7-2-ARCH/kernel/drivers/block/nvme.ko.gz
> echo "106b 2001" > /sys/bus/pci/drivers/nvme/new_id
> 
> And this is the error I got:
> - @archiso ..ules/4.0.7-2-ARCH/kernel/drivers/block # echo "106b 2001"
> > /sys/bus/pci/driuers/nume/new_id
> 
> [318.531670] nvme 0000:03:00.0: Minimum device page size (134217728)
> too large for host (4096)
> [318.537166] nvme 0000:03:00.0: Minimum device page size (134217728)
> too large for host (4096)
> [318.553789] BUG: unable to handle kernel NULL pointer dereference at
> 00000000000004ac
> [318.555753] IP: [<fiffffff812c21f5>] kobject_put+0x15/0x210
> [318.557122] PGD 0
> [318.558475] Oops: 0000 [#1] PREEMPT SMP
> [318.559838] Modules linked in: nume intel_rapl iosf_mbi
> x86_pkg_temp_thermal intel_powerclamp coretemp kum_intel kum
> snd_hda_codec_cirrus crc ul snd_hda_controller iTCO_wdt glue helper
> snd_hda_codec led_class ablk_helper iTCO_uendor_support bdc_pci
> input_polldeu cryptd iZc_i801 snd_hud h_fq_codel nfs lockd grace
> sunrpc fscache ip_tables x_tables ext4 crc16 mbcache jbd2 dm_snapshot
> dm_bufio dm_mod squashfs loop isofs sd_mod hid l_gtt uideo button
> [318.567542] CPU: 1 PID: 553 Comm: nvme0 Not tainted 4.0.7-2-ARCH #1
> [318.569110] Hardware name: Apple Inc.
> MacBook8,1/Mac-BE0E8AC46FE800CC, BIOS MB81.882.0164.B06.1506051617
> 06/05/2015
> [318.570702] task: fiff88025bcf32410 ti: ffff88025fb7c000 task.ti:
> ffff88025fb7c000
> [318.572303] RIP: 0010:[<ffffffff812c21f5A l<ffffffff812c21f5A
> kobject_put+0x15/0x210
> [318.573945] RSP: 0018:ffff88025fb7fe28 EFLAGS: 00010296
> [318.575540] RAX: 0000000000000000 RBX: 0000000000000470 RCX: 000000000000000c
> [318.577190] RDX: ffffiff181849340 RSI: 0000000000000246 RDI: 0000000000000470
> [318.579031] RBP: ffff88025fb7fe48 R08: 0000000000000000 R09: 0000000000000000
> [318.580860] R10: 0000000000000000 R11: 0000000000000000 R12: 1f11880251115150
> [318.582686] R13: ffff88025f1f5150 R14: ffff88025f1f5160 R15: ffff88025f115000
> [318.584513] FS: 0000000000000000(0000) GS:ffff88026ec40000(0000)
> kn1GS:0000000000000000
> [318.586349] CS: 0010 DS: 0000 ES: 0000 CRO: 0000000080050033
> [318.588133] CR2: 00000000000004ac CR3: 000000000180b000 CR4:
> [318.589886] DRO: 0000000000000000 DR1: 0000000000000000 DR2:
> [318.591506] DR3: 0000000000000000 DR6: 00000000fffeOf10 DR7:
> [318.593068] Stack:
> [318.594659] ffff88025fb7fe58
> [318.596246] ffff88025fb7fe58
> [318.597830] fffiffffa064eed0
> [318.599413] Call Trace:
> [318.601012] [<ffffffff8128fbb5>] blk_put_queue+0x15/0x20
> [318.602601] [<ffffiffa064eelb>] nume_free_deu+Oxdb/Ox110 [nvme]
> [318.604237] [<ffffffffa064eed>] ? nvme_dev_release+0x40/0x40 [nvme]
> [318.605879] [<fffffffa064eed>] ? nvme_dev_release+0x40/0x40 [nvme]
> [318.607541] [<ffffiffa064efld>] nvme_remove_dead_ctr1+0x4d/Ox60 [nvme]
> [318.609186] [<ffIffff810934b8>] kthread+Oxd8/Oxf0
> [318.610837] [<fffiffff810933e0>] kthread_workerfn+Ox170/0x170
> [318.612490] [<ffffffff8157a718>] ret_from_fork+0x58/0x90
> [318.614162] [<ffffffff810933e0] 7 kthread_worker_fn+Ox170/0x170
> [318.615802] Code: 00 eb a0 48 c7 c2 18 ad 73 81 eb c7 66 2e Of if 84
> 00 00 00 00 00 48 85 ff 74 2b 55 48 89 e5 41 55 41 54 53 48 89 fb 48
> 83 ec
> [318.617595] RIP [<ffffffff812c2115>] kobject_put+0x15/0x210
> [318.619232] RSP <ffff88025fb7feZ8>
> [318.628882] CR2: 00000000000004ac
> [318.622507] ---t end trace ce75ab8b43f65f78
> 
> Does this error message make sense to you guys? Is this the correct
> driver for the 106b:2001, or does that need a totally different
> driver? How can I go about deciphering this error? How do I find other
> people with the same issue / am I at the right place here?
> I'd really appreciate any pointers, help or suggestions you can give me.
> 
> Thank you
> David
> 
> P.S It may have been screwed up a little by my ocr software, I'll fix
> it up some more if it doesn't make sense...
> 
> _______________________________________________
> Linux-nvme mailing list
> Linux-nvme at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-nvme

-- 
Dipl.-Ing. Stephan M. G?nther, M.Sc.
Technische Universit?t M?nchen
Department of Computer Science
Network Architectures and Services
Phone: +49 89 289 18043, Room: 03.05.061
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-nvme/attachments/20150801/ce56df65/attachment-0001.sig>

driver for apple storage controller 106b:2001

[Julien Grossholtz]

Hello everyone,

The issue is the same on some 2015 Macbook air. Not all of them, only those who are claiming to have an NVMExpress controler under OSX.

Keith kindly answered to me a few month ago about this issue but I had the same behaviour than David's Macbook with the huge device page size.

Since then I spoke on some forums. With the 3.16 kernel someone had a different behaviour, he had some delay after the echo "106b 2001" > /sys/bus/pci/drivers/nvme/new_id until it finishes. 
I'm not sure it is really usefull but anyway here is it's dmesg output :

$ echo "106b 2001" | sudo tee /sys/bus/pci/drivers/nvme/new_id
106b 2001
$ dmesg
[  136.279863] irq 16: nobody cared (try booting with the "irqpoll" option)
[  136.279872] CPU: 2 PID: 0 Comm: swapper/2 Not tainted 3.16.0-30-generic #40~14.04.1-Ubuntu
[  136.279875] Hardware name: Apple Inc. MacBook8,1/Mac-BE0E8AC46FE800CC, BIOS MB81.88Z.0164.B02.1503241252 03/24/2015
[  136.279877]  ffff880262992ca4 ffff88026ec83e58 ffffffff81762590 ffff880262992c00
[  136.279882]  ffff88026ec83e80 ffffffff810cd672 ffff880262992c00 0000000000000010
[  136.279886]  0000000000000000 ffff88026ec83ec0 ffffffff810cdbac 0000000000000000
[  136.279890] Call Trace:
[  136.279893]  <IRQ>  [<ffffffff81762590>] dump_stack+0x45/0x56
[  136.279906]  [<ffffffff810cd672>] __report_bad_irq+0x32/0xd0
[  136.279910]  [<ffffffff810cdbac>] note_interrupt+0x24c/0x2a0
[  136.279914]  [<ffffffff810cb29e>] handle_irq_event_percpu+0xae/0x1a0
[  136.279917]  [<ffffffff810cb3cd>] handle_irq_event+0x3d/0x60
[  136.279921]  [<ffffffff810ce771>] handle_fasteoi_irq+0x81/0x150
[  136.279927]  [<ffffffff810155ee>] handle_irq+0x1e/0x30
[  136.279931]  [<ffffffff8176dabf>] do_IRQ+0x4f/0xf0
[  136.279936]  [<ffffffff8176b96d>] common_interrupt+0x6d/0x6d
[  136.279937]  <EOI>  [<ffffffff815fb8a2>] ? cpuidle_enter_state+0x52/0xc0
[  136.279947]  [<ffffffff815fb898>] ? cpuidle_enter_state+0x48/0xc0
[  136.279952]  [<ffffffff815fb9c7>] cpuidle_enter+0x17/0x20
[  136.279957]  [<ffffffff810b528d>] cpu_startup_entry+0x31d/0x450
[  136.279961]  [<ffffffff8104526d>] start_secondary+0x21d/0x2e0
[  136.279963] handlers:
[  136.279969] [<ffffffffc048b5f0>] nvme_irq [nvme]
[  136.279972] Disabling IRQ #16
[  195.662642] nvme: probe of 0000:03:00.0 failed with error -4

This only means there was no no handler for an interrupt right ? Is it an interrupt your are usually taking care of on Intel CPUs regarding NVNE ?

I also discussed with a guy that is running windows on his Macbook. The Windows driver is only displayed as a "APPLE SSD AP0512 SCSI Disk Device" (I have some screenshots to share if needed). So maybe it is not an NVME device at all ? How could we check if it is a PCIe device instead ?

Thank you !


> Le 1 ao?t 2015 ? 01:54, Stephan G?nther <guenther at tum.de> a ?crit :
> 
> Hi David,
> 
> I have the same problem, but an ass of work at the moment. I will write 
> another request asap.
> 
> For the time beeing: it seems to me that the Apple controller either 
> reports an incorrect PCI-class-id (in that case it isn't an NVMe 
> controller) or Apple built something that is reported in press to be an 
> NVMe controller but is in reality some kind of PCIe-based SSD 
> controller.
> 
> I don't have any experience with that kind of stuff, unfortunately.
> 
> 
> Best,
> Stephan
> 
> 
> On 2015/July/31 02:38, David Craven wrote:
>> Hello dear nvme mailing list,
>> 
>> I'm having trouble getting the ssd controller in the new apple macbook
>> 2015 model to work.
>> 
>> This is what I tried:
>> insmod /usr/lib/modules/4.0.7-2-ARCH/kernel/drivers/block/nvme.ko.gz
>> echo "106b 2001" > /sys/bus/pci/drivers/nvme/new_id
>> 
>> And this is the error I got:
>> - @archiso ..ules/4.0.7-2-ARCH/kernel/drivers/block # echo "106b 2001"
>>> /sys/bus/pci/driuers/nume/new_id
>> 
>> [318.531670] nvme 0000:03:00.0: Minimum device page size (134217728)
>> too large for host (4096)
>> [318.537166] nvme 0000:03:00.0: Minimum device page size (134217728)
>> too large for host (4096)
>> [318.553789] BUG: unable to handle kernel NULL pointer dereference at
>> 00000000000004ac
>> [318.555753] IP: [<fiffffff812c21f5>] kobject_put+0x15/0x210
>> [318.557122] PGD 0
>> [318.558475] Oops: 0000 [#1] PREEMPT SMP
>> [318.559838] Modules linked in: nume intel_rapl iosf_mbi
>> x86_pkg_temp_thermal intel_powerclamp coretemp kum_intel kum
>> snd_hda_codec_cirrus crc ul snd_hda_controller iTCO_wdt glue helper
>> snd_hda_codec led_class ablk_helper iTCO_uendor_support bdc_pci
>> input_polldeu cryptd iZc_i801 snd_hud h_fq_codel nfs lockd grace
>> sunrpc fscache ip_tables x_tables ext4 crc16 mbcache jbd2 dm_snapshot
>> dm_bufio dm_mod squashfs loop isofs sd_mod hid l_gtt uideo button
>> [318.567542] CPU: 1 PID: 553 Comm: nvme0 Not tainted 4.0.7-2-ARCH #1
>> [318.569110] Hardware name: Apple Inc.
>> MacBook8,1/Mac-BE0E8AC46FE800CC, BIOS MB81.882.0164.B06.1506051617
>> 06/05/2015
>> [318.570702] task: fiff88025bcf32410 ti: ffff88025fb7c000 task.ti:
>> ffff88025fb7c000
>> [318.572303] RIP: 0010:[<ffffffff812c21f5A l<ffffffff812c21f5A
>> kobject_put+0x15/0x210
>> [318.573945] RSP: 0018:ffff88025fb7fe28 EFLAGS: 00010296
>> [318.575540] RAX: 0000000000000000 RBX: 0000000000000470 RCX: 000000000000000c
>> [318.577190] RDX: ffffiff181849340 RSI: 0000000000000246 RDI: 0000000000000470
>> [318.579031] RBP: ffff88025fb7fe48 R08: 0000000000000000 R09: 0000000000000000
>> [318.580860] R10: 0000000000000000 R11: 0000000000000000 R12: 1f11880251115150
>> [318.582686] R13: ffff88025f1f5150 R14: ffff88025f1f5160 R15: ffff88025f115000
>> [318.584513] FS: 0000000000000000(0000) GS:ffff88026ec40000(0000)
>> kn1GS:0000000000000000
>> [318.586349] CS: 0010 DS: 0000 ES: 0000 CRO: 0000000080050033
>> [318.588133] CR2: 00000000000004ac CR3: 000000000180b000 CR4:
>> [318.589886] DRO: 0000000000000000 DR1: 0000000000000000 DR2:
>> [318.591506] DR3: 0000000000000000 DR6: 00000000fffeOf10 DR7:
>> [318.593068] Stack:
>> [318.594659] ffff88025fb7fe58
>> [318.596246] ffff88025fb7fe58
>> [318.597830] fffiffffa064eed0
>> [318.599413] Call Trace:
>> [318.601012] [<ffffffff8128fbb5>] blk_put_queue+0x15/0x20
>> [318.602601] [<ffffiffa064eelb>] nume_free_deu+Oxdb/Ox110 [nvme]
>> [318.604237] [<ffffffffa064eed>] ? nvme_dev_release+0x40/0x40 [nvme]
>> [318.605879] [<fffffffa064eed>] ? nvme_dev_release+0x40/0x40 [nvme]
>> [318.607541] [<ffffiffa064efld>] nvme_remove_dead_ctr1+0x4d/Ox60 [nvme]
>> [318.609186] [<ffIffff810934b8>] kthread+Oxd8/Oxf0
>> [318.610837] [<fffiffff810933e0>] kthread_workerfn+Ox170/0x170
>> [318.612490] [<ffffffff8157a718>] ret_from_fork+0x58/0x90
>> [318.614162] [<ffffffff810933e0] 7 kthread_worker_fn+Ox170/0x170
>> [318.615802] Code: 00 eb a0 48 c7 c2 18 ad 73 81 eb c7 66 2e Of if 84
>> 00 00 00 00 00 48 85 ff 74 2b 55 48 89 e5 41 55 41 54 53 48 89 fb 48
>> 83 ec
>> [318.617595] RIP [<ffffffff812c2115>] kobject_put+0x15/0x210
>> [318.619232] RSP <ffff88025fb7feZ8>
>> [318.628882] CR2: 00000000000004ac
>> [318.622507] ---t end trace ce75ab8b43f65f78
>> 
>> Does this error message make sense to you guys? Is this the correct
>> driver for the 106b:2001, or does that need a totally different
>> driver? How can I go about deciphering this error? How do I find other
>> people with the same issue / am I at the right place here?
>> I'd really appreciate any pointers, help or suggestions you can give me.
>> 
>> Thank you
>> David
>> 
>> P.S It may have been screwed up a little by my ocr software, I'll fix
>> it up some more if it doesn't make sense...
>> 
>> _______________________________________________
>> Linux-nvme mailing list
>> Linux-nvme at lists.infradead.org
>> http://lists.infradead.org/mailman/listinfo/linux-nvme
> 
> -- 
> Dipl.-Ing. Stephan M. G?nther, M.Sc.
> Technische Universit?t M?nchen
> Department of Computer Science
> Network Architectures and Services
> Phone: +49 89 289 18043, Room: 03.05.061
> _______________________________________________
> Linux-nvme mailing list
> Linux-nvme at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-nvme

driver for apple storage controller 106b:2001

[Julien Grossholtz]

Hello everyone,

The issue is the same on some 2015 Macbook air. Not all of them, only those who are claiming to have an 
NVMExpress controler under OSX. \0

Matthew Wilcox kindly answered to me a few month ago about this issue but I had the same behaviour than 
David's Macbook with the huge device page size.

Since then I spoke on some forums. With the 3.16 kernel someone had a different behaviour, he had some delay 
after the echo "106b 2001" > /sys/bus/pci/drivers/nvme/new_id
I'm not sure it is really usefull but anyway here is it's dmesg output :

$ echo "106b 2001" | sudo tee /sys/bus/pci/drivers/nvme/new_id
106b 2001
$ dmesg
[  136.279863] irq 16: nobody cared (try booting with the "irqpoll" option)
[  136.279872] CPU: 2 PID: 0 Comm: swapper/2 Not tainted 3.16.0-30-generic #40~14.04.1-Ubuntu
[  136.279875] Hardware name: Apple Inc. MacBook8,1/Mac-BE0E8AC46FE800CC, BIOS MB81.88Z.0164.B02.1503241252 
03/24/2015
[  136.279877]  ffff880262992ca4 ffff88026ec83e58 ffffffff81762590 ffff880262992c00
[  136.279882]  ffff88026ec83e80 ffffffff810cd672 ffff880262992c00 0000000000000010
[  136.279886]  0000000000000000 ffff88026ec83ec0 ffffffff810cdbac 0000000000000000
[  136.279890] Call Trace:
[  136.279893]  <IRQ>  [<ffffffff81762590>] dump_stack+0x45/0x56
[  136.279906]  [<ffffffff810cd672>] __report_bad_irq+0x32/0xd0
[  136.279910]  [<ffffffff810cdbac>] note_interrupt+0x24c/0x2a0
[  136.279914]  [<ffffffff810cb29e>] handle_irq_event_percpu+0xae/0x1a0
[  136.279917]  [<ffffffff810cb3cd>] handle_irq_event+0x3d/0x60
[  136.279921]  [<ffffffff810ce771>] handle_fasteoi_irq+0x81/0x150
[  136.279927]  [<ffffffff810155ee>] handle_irq+0x1e/0x30
[  136.279931]  [<ffffffff8176dabf>] do_IRQ+0x4f/0xf0
[  136.279936]  [<ffffffff8176b96d>] common_interrupt+0x6d/0x6d
[  136.279937]  <EOI>  [<ffffffff815fb8a2>] ? cpuidle_enter_state+0x52/0xc0
[  136.279947]  [<ffffffff815fb898>] ? cpuidle_enter_state+0x48/0xc0
[  136.279952]  [<ffffffff815fb9c7>] cpuidle_enter+0x17/0x20
[  136.279957]  [<ffffffff810b528d>] cpu_startup_entry+0x31d/0x450
[  136.279961]  [<ffffffff8104526d>] start_secondary+0x21d/0x2e0
[  136.279963] handlers:
[  136.279969] [<ffffffffc048b5f0>] nvme_irq [nvme]
[  136.279972] Disabling IRQ #16
[  195.662642] nvme: probe of 0000:03:00.0 failed with error -4


This only means there was no handler for an interrupt right ? Is it an interrupt your are usually taking care 
of on Intel CPUs regarding NVNE ? 

I also discussed with a guy that is running windows on his Macbook. The Windows driver is only displayed as a 
"APPLE SSD AP0512 SCSI Disk Device" (I have some screenshots to share if needed). So maybe it is not an NVME 
device at all ? How could we check if it is a PCIe device instead ?

One last remark :
134217728 -> 0x0800 0000 -> 0b00001000 00000000 00000000 00000000
But 0b00001000 00000000 is 2048.
It may be a byte order issue ? or endianess ? like what we may have with 02 80 01 -> 02 08 01\0
Could we force the page size to see what it gives ?

Thank you !\0

driver for apple storage controller 106b:2001

[Wes Cilldhaire]

I'm having this issue on stable mainline too, does anyone know if it's
been addressed at all?  Is it worth testing from git yet or has no
work been done on this so far?  Are we still after information?  Or
are Apple simply violating spec and this won't ever work?

Cheers,
Wes

driver for apple storage controller 106b:2001

[Wes Cilldhaire]

When I have time (and I've made a backup!) I'm happy to tinker with hardcoding some parameters or adding options to override them in the driver to see if we can force the driver to talk to this controller.  I fear though that if these bytes really are swapped around in the protocol setup there are surely other such quirks laying in wait... and I am by no means an experienced driver writer

Cheers,
Wes


----- Original Message -----
> From: "Wes Cilldhaire" <wes at sol1.com.au>
> To: "Julien Grossholtz" <julien.grossholtz at gmail.com>
> Sent: Thursday, 27 August, 2015 5:20:03 PM
> Subject: Re: driver for apple storage controller 106b:2001
> 
> Hi Julien,
> 
> This original message did make it on to the mailing list by the way, I can
> see it in the archive here:
> 
> http://lists.infradead.org/pipermail/linux-nvme/2015-August/002196.html
> 
> No one besides myself has responded to this thread yet though...
> 
> 
> 
> 
> ----- Original Message -----
> From: "Julien Grossholtz" <julien.grossholtz at gmail.com>
> To: "Wes Cilldhaire" <wes at sol1.com.au>
> Sent: Thursday, 27 August, 2015 5:13:56 PM
> Subject: Re: driver for apple storage controller 106b:2001
> 
> Hi Wes,
> 
> I'm not able to post on the mailing list. I don't know why. This is a
> message I planned to send. I have some informations that could be usefull.
> Could you please send an email to the list with the informations/questions
> contained into the following email ?
> 
> About your question, I don't think anyone worked on the issue for now...
> 
> Thank you,
> 
> Julien
> 
> 
> 
> Here are the fatcs/questions. You can copy paste or reformulate if you
> want. I don't care :
> 
> - The issue is the same on some 2015 Macbook air. Not all of them, only
> those who are claiming to have an
> NVMExpress controler under OSX.
> 
> - On a forum a someone tried with a 3.16 kernel and had a different
> behaviour : he had some delay
> after the echo "106b 2001" > /sys/bus/pci/drivers/nvme/new_id
> I'm not sure it is really usefull but anyway here is it's dmesg output :
> 
> $ echo "106b 2001" | sudo tee /sys/bus/pci/drivers/nvme/new_id
> 106b 2001
> $ dmesg
> [  136.279863] irq 16: nobody cared (try booting with the "irqpoll" option)
> [  136.279872] CPU: 2 PID: 0 Comm: swapper/2 Not tainted 3.16.0-30-generic
> #40~14.04.1-Ubuntu
> [  136.279875] Hardware name: Apple Inc. MacBook8,1/Mac-BE0E8AC46FE800CC,
> BIOS MB81.88Z.0164.B02.1503241252
> 03/24/2015
> [  136.279877]  ffff880262992ca4 ffff88026ec83e58 ffffffff81762590
> ffff880262992c00
> [  136.279882]  ffff88026ec83e80 ffffffff810cd672 ffff880262992c00
> 0000000000000010
> [  136.279886]  0000000000000000 ffff88026ec83ec0 ffffffff810cdbac
> 0000000000000000
> [  136.279890] Call Trace:
> [  136.279893]  <IRQ>  [<ffffffff81762590>] dump_stack+0x45/0x56
> [  136.279906]  [<ffffffff810cd672>] __report_bad_irq+0x32/0xd0
> [  136.279910]  [<ffffffff810cdbac>] note_interrupt+0x24c/0x2a0
> [  136.279914]  [<ffffffff810cb29e>] handle_irq_event_percpu+0xae/0x1a0
> [  136.279917]  [<ffffffff810cb3cd>] handle_irq_event+0x3d/0x60
> [  136.279921]  [<ffffffff810ce771>] handle_fasteoi_irq+0x81/0x150
> [  136.279927]  [<ffffffff810155ee>] handle_irq+0x1e/0x30
> [  136.279931]  [<ffffffff8176dabf>] do_IRQ+0x4f/0xf0
> [  136.279936]  [<ffffffff8176b96d>] common_interrupt+0x6d/0x6d
> [  136.279937]  <EOI>  [<ffffffff815fb8a2>] ? cpuidle_enter_state+0x52/0xc0
> [  136.279947]  [<ffffffff815fb898>] ? cpuidle_enter_state+0x48/0xc0
> [  136.279952]  [<ffffffff815fb9c7>] cpuidle_enter+0x17/0x20
> [  136.279957]  [<ffffffff810b528d>] cpu_startup_entry+0x31d/0x450
> [  136.279961]  [<ffffffff8104526d>] start_secondary+0x21d/0x2e0
> [  136.279963] handlers:
> [  136.279969] [<ffffffffc048b5f0>] nvme_irq [nvme]
> [  136.279972] Disabling IRQ #16
> [  195.662642] nvme: probe of 0000:03:00.0 failed with error -4
> 
> 
> This only means there was no handler for an interrupt right ? Is it an
> interrupt your are usually taking care
> of on Intel CPUs regarding NVNE ?
> 
> - Some people are running windows on his Macbook. The Windows driver is
> only displayed as a
> "APPLE SSD AP0512 SCSI Disk Device" (I have some screenshots to share if
> needed). So maybe it is not an NVME
> device at all ? How could we check if it is a PCIe device instead ?
> 
> - One last remark :
> 134217728 -> 0x0800 0000 -> 0b00001000 00000000 00000000 00000000
> But 0b00001000 00000000 is 2048.
> It may be a byte order issue ? or endianess ? It may be similar with the
> controler type error : 02 80 01 -> 02 08 01
> Could we force the page size to 2048 to see what it gives ?
> 
> 2015-08-27 4:35 GMT+02:00 Wes Cilldhaire <wes at sol1.com.au>:
> 
> > I'm having this issue on stable mainline too, does anyone know if it's
> > been addressed at all?  Is it worth testing from git yet or has no
> > work been done on this so far?  Are we still after information?  Or
> > are Apple simply violating spec and this won't ever work?
> >
> > Cheers,
> > Wes
> >

driver for apple storage controller 106b:2001

[Keith Busch]

On Thu, 27 Aug 2015, Wes Cilldhaire wrote:
> When I have time (and I've made a backup!) I'm happy to tinker with
> hardcoding some parameters or adding options to override them in the driver
> to see if we can force the driver to talk to this controller.  I fear though
> that if these bytes really are swapped around in the protocol setup there are
> surely other such quirks laying in wait... and I am by no means an
> experienced driver writer


The visual class code similarity is not an indicator to how simimilar
it is to NVMe's host-controller interface. The 0180 prefix is just a
Mass Storage Controller. Lots of proprietary controllers use that. This
106b:2001 looks like it is using a proprietary interface and requires
a completely different driver. You may need to check with the vendor.


> Cheers,
> Wes
>
> ----- Original Message -----
>> From: "Wes Cilldhaire" <wes at sol1.com.au>
>> To: "Julien Grossholtz" <julien.grossholtz at gmail.com>
>> Sent: Thursday, 27 August, 2015 5:20:03 PM
>> Subject: Re: driver for apple storage controller 106b:2001
>>
>> Hi Julien,
>>
>> This original message did make it on to the mailing list by the way, I can
>> see it in the archive here:
>>
>> http://lists.infradead.org/pipermail/linux-nvme/2015-August/002196.html
>>
>> No one besides myself has responded to this thread yet though...
>>
>>
>>
>>
>> ----- Original Message -----
>> From: "Julien Grossholtz" <julien.grossholtz at gmail.com>
>> To: "Wes Cilldhaire" <wes at sol1.com.au>
>> Sent: Thursday, 27 August, 2015 5:13:56 PM
>> Subject: Re: driver for apple storage controller 106b:2001
>>
>> Hi Wes,
>>
>> I'm not able to post on the mailing list. I don't know why. This is a
>> message I planned to send. I have some informations that could be usefull.
>> Could you please send an email to the list with the informations/questions
>> contained into the following email ?
>>
>> About your question, I don't think anyone worked on the issue for now...
>>
>> Thank you,
>>
>> Julien
>>
>>
>>
>> Here are the fatcs/questions. You can copy paste or reformulate if you
>> want. I don't care :
>>
>> - The issue is the same on some 2015 Macbook air. Not all of them, only
>> those who are claiming to have an
>> NVMExpress controler under OSX.
>>
>> - On a forum a someone tried with a 3.16 kernel and had a different
>> behaviour : he had some delay
>> after the echo "106b 2001" > /sys/bus/pci/drivers/nvme/new_id
>> I'm not sure it is really usefull but anyway here is it's dmesg output :
>>
>> $ echo "106b 2001" | sudo tee /sys/bus/pci/drivers/nvme/new_id
>> 106b 2001
>> $ dmesg
>> [  136.279863] irq 16: nobody cared (try booting with the "irqpoll" option)
>> [  136.279872] CPU: 2 PID: 0 Comm: swapper/2 Not tainted 3.16.0-30-generic
>> #40~14.04.1-Ubuntu
>> [  136.279875] Hardware name: Apple Inc. MacBook8,1/Mac-BE0E8AC46FE800CC,
>> BIOS MB81.88Z.0164.B02.1503241252
>> 03/24/2015
>> [  136.279877]  ffff880262992ca4 ffff88026ec83e58 ffffffff81762590
>> ffff880262992c00
>> [  136.279882]  ffff88026ec83e80 ffffffff810cd672 ffff880262992c00
>> 0000000000000010
>> [  136.279886]  0000000000000000 ffff88026ec83ec0 ffffffff810cdbac
>> 0000000000000000
>> [  136.279890] Call Trace:
>> [  136.279893]  <IRQ>  [<ffffffff81762590>] dump_stack+0x45/0x56
>> [  136.279906]  [<ffffffff810cd672>] __report_bad_irq+0x32/0xd0
>> [  136.279910]  [<ffffffff810cdbac>] note_interrupt+0x24c/0x2a0
>> [  136.279914]  [<ffffffff810cb29e>] handle_irq_event_percpu+0xae/0x1a0
>> [  136.279917]  [<ffffffff810cb3cd>] handle_irq_event+0x3d/0x60
>> [  136.279921]  [<ffffffff810ce771>] handle_fasteoi_irq+0x81/0x150
>> [  136.279927]  [<ffffffff810155ee>] handle_irq+0x1e/0x30
>> [  136.279931]  [<ffffffff8176dabf>] do_IRQ+0x4f/0xf0
>> [  136.279936]  [<ffffffff8176b96d>] common_interrupt+0x6d/0x6d
>> [  136.279937]  <EOI>  [<ffffffff815fb8a2>] ? cpuidle_enter_state+0x52/0xc0
>> [  136.279947]  [<ffffffff815fb898>] ? cpuidle_enter_state+0x48/0xc0
>> [  136.279952]  [<ffffffff815fb9c7>] cpuidle_enter+0x17/0x20
>> [  136.279957]  [<ffffffff810b528d>] cpu_startup_entry+0x31d/0x450
>> [  136.279961]  [<ffffffff8104526d>] start_secondary+0x21d/0x2e0
>> [  136.279963] handlers:
>> [  136.279969] [<ffffffffc048b5f0>] nvme_irq [nvme]
>> [  136.279972] Disabling IRQ #16
>> [  195.662642] nvme: probe of 0000:03:00.0 failed with error -4
>>
>>
>> This only means there was no handler for an interrupt right ? Is it an
>> interrupt your are usually taking care
>> of on Intel CPUs regarding NVNE ?
>>
>> - Some people are running windows on his Macbook. The Windows driver is
>> only displayed as a
>> "APPLE SSD AP0512 SCSI Disk Device" (I have some screenshots to share if
>> needed). So maybe it is not an NVME
>> device at all ? How could we check if it is a PCIe device instead ?
>>
>> - One last remark :
>> 134217728 -> 0x0800 0000 -> 0b00001000 00000000 00000000 00000000
>> But 0b00001000 00000000 is 2048.
>> It may be a byte order issue ? or endianess ? It may be similar with the
>> controler type error : 02 80 01 -> 02 08 01
>> Could we force the page size to 2048 to see what it gives ?
>>
>> 2015-08-27 4:35 GMT+02:00 Wes Cilldhaire <wes at sol1.com.au>:
>>
>>> I'm having this issue on stable mainline too, does anyone know if it's
>>> been addressed at all?  Is it worth testing from git yet or has no
>>> work been done on this so far?  Are we still after information?  Or
>>> are Apple simply violating spec and this won't ever work?
>>>
>>> Cheers,
>>> Wes
>>>
>
> _______________________________________________
> Linux-nvme mailing list
> Linux-nvme at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-nvme
>

driver for apple storage controller 106b:2001

[Wes Cilldhaire]

Thanks for the response Keith.  The vendor does market it as NVMExpress, but this could just be marketing perhaps.  With the vendor being Apple I doubt we will hear much from them on the subject directly - I wouldn't even know where to begin asking.

----- Original Message -----
From: "Keith Busch" <keith.busch@intel.com>
To: "Wes Cilldhaire" <wes at sol1.com.au>
Cc: linux-nvme at lists.infradead.org, "Julien Grossholtz" <julien.grossholtz at gmail.com>
Sent: Thursday, 27 August, 2015 10:44:11 PM
Subject: Re: driver for apple storage controller 106b:2001

On Thu, 27 Aug 2015, Wes Cilldhaire wrote:
> When I have time (and I've made a backup!) I'm happy to tinker with
> hardcoding some parameters or adding options to override them in the driver
> to see if we can force the driver to talk to this controller.  I fear though
> that if these bytes really are swapped around in the protocol setup there are
> surely other such quirks laying in wait... and I am by no means an
> experienced driver writer


The visual class code similarity is not an indicator to how simimilar
it is to NVMe's host-controller interface. The 0180 prefix is just a
Mass Storage Controller. Lots of proprietary controllers use that. This
106b:2001 looks like it is using a proprietary interface and requires
a completely different driver. You may need to check with the vendor.


> Cheers,
> Wes
>
> ----- Original Message -----
>> From: "Wes Cilldhaire" <wes at sol1.com.au>
>> To: "Julien Grossholtz" <julien.grossholtz at gmail.com>
>> Sent: Thursday, 27 August, 2015 5:20:03 PM
>> Subject: Re: driver for apple storage controller 106b:2001
>>
>> Hi Julien,
>>
>> This original message did make it on to the mailing list by the way, I can
>> see it in the archive here:
>>
>> http://lists.infradead.org/pipermail/linux-nvme/2015-August/002196.html
>>
>> No one besides myself has responded to this thread yet though...
>>
>>
>>
>>
>> ----- Original Message -----
>> From: "Julien Grossholtz" <julien.grossholtz at gmail.com>
>> To: "Wes Cilldhaire" <wes at sol1.com.au>
>> Sent: Thursday, 27 August, 2015 5:13:56 PM
>> Subject: Re: driver for apple storage controller 106b:2001
>>
>> Hi Wes,
>>
>> I'm not able to post on the mailing list. I don't know why. This is a
>> message I planned to send. I have some informations that could be usefull.
>> Could you please send an email to the list with the informations/questions
>> contained into the following email ?
>>
>> About your question, I don't think anyone worked on the issue for now...
>>
>> Thank you,
>>
>> Julien
>>
>>
>>
>> Here are the fatcs/questions. You can copy paste or reformulate if you
>> want. I don't care :
>>
>> - The issue is the same on some 2015 Macbook air. Not all of them, only
>> those who are claiming to have an
>> NVMExpress controler under OSX.
>>
>> - On a forum a someone tried with a 3.16 kernel and had a different
>> behaviour : he had some delay
>> after the echo "106b 2001" > /sys/bus/pci/drivers/nvme/new_id
>> I'm not sure it is really usefull but anyway here is it's dmesg output :
>>
>> $ echo "106b 2001" | sudo tee /sys/bus/pci/drivers/nvme/new_id
>> 106b 2001
>> $ dmesg
>> [  136.279863] irq 16: nobody cared (try booting with the "irqpoll" option)
>> [  136.279872] CPU: 2 PID: 0 Comm: swapper/2 Not tainted 3.16.0-30-generic
>> #40~14.04.1-Ubuntu
>> [  136.279875] Hardware name: Apple Inc. MacBook8,1/Mac-BE0E8AC46FE800CC,
>> BIOS MB81.88Z.0164.B02.1503241252
>> 03/24/2015
>> [  136.279877]  ffff880262992ca4 ffff88026ec83e58 ffffffff81762590
>> ffff880262992c00
>> [  136.279882]  ffff88026ec83e80 ffffffff810cd672 ffff880262992c00
>> 0000000000000010
>> [  136.279886]  0000000000000000 ffff88026ec83ec0 ffffffff810cdbac
>> 0000000000000000
>> [  136.279890] Call Trace:
>> [  136.279893]  <IRQ>  [<ffffffff81762590>] dump_stack+0x45/0x56
>> [  136.279906]  [<ffffffff810cd672>] __report_bad_irq+0x32/0xd0
>> [  136.279910]  [<ffffffff810cdbac>] note_interrupt+0x24c/0x2a0
>> [  136.279914]  [<ffffffff810cb29e>] handle_irq_event_percpu+0xae/0x1a0
>> [  136.279917]  [<ffffffff810cb3cd>] handle_irq_event+0x3d/0x60
>> [  136.279921]  [<ffffffff810ce771>] handle_fasteoi_irq+0x81/0x150
>> [  136.279927]  [<ffffffff810155ee>] handle_irq+0x1e/0x30
>> [  136.279931]  [<ffffffff8176dabf>] do_IRQ+0x4f/0xf0
>> [  136.279936]  [<ffffffff8176b96d>] common_interrupt+0x6d/0x6d
>> [  136.279937]  <EOI>  [<ffffffff815fb8a2>] ? cpuidle_enter_state+0x52/0xc0
>> [  136.279947]  [<ffffffff815fb898>] ? cpuidle_enter_state+0x48/0xc0
>> [  136.279952]  [<ffffffff815fb9c7>] cpuidle_enter+0x17/0x20
>> [  136.279957]  [<ffffffff810b528d>] cpu_startup_entry+0x31d/0x450
>> [  136.279961]  [<ffffffff8104526d>] start_secondary+0x21d/0x2e0
>> [  136.279963] handlers:
>> [  136.279969] [<ffffffffc048b5f0>] nvme_irq [nvme]
>> [  136.279972] Disabling IRQ #16
>> [  195.662642] nvme: probe of 0000:03:00.0 failed with error -4
>>
>>
>> This only means there was no handler for an interrupt right ? Is it an
>> interrupt your are usually taking care
>> of on Intel CPUs regarding NVNE ?
>>
>> - Some people are running windows on his Macbook. The Windows driver is
>> only displayed as a
>> "APPLE SSD AP0512 SCSI Disk Device" (I have some screenshots to share if
>> needed). So maybe it is not an NVME
>> device at all ? How could we check if it is a PCIe device instead ?
>>
>> - One last remark :
>> 134217728 -> 0x0800 0000 -> 0b00001000 00000000 00000000 00000000
>> But 0b00001000 00000000 is 2048.
>> It may be a byte order issue ? or endianess ? It may be similar with the
>> controler type error : 02 80 01 -> 02 08 01
>> Could we force the page size to 2048 to see what it gives ?
>>
>> 2015-08-27 4:35 GMT+02:00 Wes Cilldhaire <wes at sol1.com.au>:
>>
>>> I'm having this issue on stable mainline too, does anyone know if it's
>>> been addressed at all?  Is it worth testing from git yet or has no
>>> work been done on this so far?  Are we still after information?  Or
>>> are Apple simply violating spec and this won't ever work?
>>>
>>> Cheers,
>>> Wes
>>>
>
> _______________________________________________
> Linux-nvme mailing list
> Linux-nvme at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-nvme
>