Hi,
Any update to this issue?
I have the same system (SYS-2028U-TN24R4T+) with 11 x intel P3600 2.0TB, NVMe
PCIe 3.0, HET MLC 20nm 3DWPD (SSDPE2ME020T4). I install it successfully with
20170116T154141Z platform and it works for a few days then the headnode lost
connection with it. I can not
Hi Robert,
Thanks for looking into this issue.
I tried MSI interrupt type on my own but it didn't work, but I will try
your patch again and then report back.
I've studied the nvme driver in Solaris 11.3, it seems they do the same
thing as Linux - MSI-X first, then MSI, finally FIXED, see
On 8/4/16 11:25 , Youzhong Yang wrote:
> Thanks for the input Robert.
>
> I believe the issue is now resolved by using MSI-X (instead of FIXED)
> interrupt type inside nvme_init() for the admin queue.
>
> Here is the issue report I just filed:
>
> https://www.illumos.org/issues/7273
>
> I
On 8/4/16 11:25 , Youzhong Yang wrote:
> Thanks for the input Robert.
>
> I believe the issue is now resolved by using MSI-X (instead of FIXED)
> interrupt type inside nvme_init() for the admin queue.
>
> Here is the issue report I just filed:
>
> https://www.illumos.org/issues/7273
>
> I
On 8/1/16 10:41 , Youzhong Yang wrote:
> Hello again,
>
> Thanks Robert for the advises. I've spent some time struggling with why
> NVMe SSDs were retired but there's no error reported by NVMe driver, it
> turns out to be a victim of fmd_asru_hash_replay_asru(), i.e. if we don't
> tell fmd a
Thanks Hans. I built a new kernel and tested it, now it works better, but
can still report errors - less frequently. Out of 5 reboots, it failed
once, so something is still there to be found.
On Mon, Aug 1, 2016 at 3:42 PM, Hans Rosenfeld
wrote:
> On Mon, Aug 01,
This does not make sense to me, not sure if it's relevant to the issue I am
seeing:
http://www.nvmexpress.org/wp-content/uploads/NVM-Express-1_1b.pdf
page 42 defines 'CSTS -Controller Status',
but our code defines it as
typedef union {
struct {
uint32_t csts_rdy:1; /* Ready */
uint32_t
Hello again,
Thanks Robert for the advises. I've spent some time struggling with why
NVMe SSDs were retired but there's no error reported by NVMe driver, it
turns out to be a victim of fmd_asru_hash_replay_asru(), i.e. if we don't
tell fmd a fault is repaired, next time when the host is rebooted,
On 6/24/16 11:05 , Youzhong Yang wrote:
> I panicked the host when e_ddi_retire_device() is called, here is what I
> found:
>
> it is /usr/lib/fm/fmd/fmd who calls modctl -> modctl_retire
> -> e_ddi_retire_device to retire /pci@0,0/pci8086,6f08@3.
Okay, this makes some amount of sense, we're
> On Jun 22, 2016, at 9:20 AM, 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
Here's a dtrace
10 matches
Mail list logo