On 6/22/16 6:20 , Youzhong Yang wrote:
> Thanks Robert. Yes the driver failed to attach:
>
> # rem_drv nvme
> # add_drv nvme
> devfsadm: driver failed to attach: nvme
> Warning: Driver (nvme) successfully added to system but failed to attach
>
> # modinfo | grep nvme
> 237 f8081000
Thanks Robert. Yes the driver failed to attach:
# rem_drv nvme
# add_drv nvme
devfsadm: driver failed to attach: nvme
Warning: Driver (nvme) successfully added to system but failed to attach
# modinfo | grep nvme
237 f8081000 6088 294 1 nvme (NVMe v1.0e)
On Tue, Jun 21, 2016 at
On 6/21/16 6:12 , Youzhong wrote:
> Any thoughts?
From my perspective, the thing that I would look at is why are we seeing
these PCI express errors. Is this happening when we access the NVMe
device from the driver somehow?
If it's reproducible as part of attaching, it might be interesting to
see
On 22/06/16 1:12 AM, Youzhong wrote:
Any thoughts?
Have you had a look at prtpicl? I have a PCIe SSD that's actually a
PCIe-PCIe bridge then two sticks mounted individually on the child PCIe
bus. SmartOS doesn't see the stuff on the child bus - I imagine this is
what's going on.
I really
Any thoughts?
> On Jun 17, 2016, at 1:17 PM, Youzhong Yang wrote:
>
> Hi Hans,
>
> The drivers won't show up in command output of 'diskinfo' or 'format'.
>
> Please refer to the attachment:
>
> - ls /dev/dsk and /dev/rdsk reported broken sym links
> - once I ran devfsadm