All of lore.kernel.org
 help / color / mirror / Atom feed
From: koos vriezen <koos.vriezen@gmail.com>
To: Keith Busch <kbusch@kernel.org>
Cc: linux-nvme@lists.infradead.org
Subject: Re: bisected: 5befc7c26e nvme impl non-mdts gives smartd error log entries
Date: Mon, 2 Aug 2021 18:49:00 +0200	[thread overview]
Message-ID: <CAGCbPWSK+AnEwM79vAfU7GG1eTjPB5xvDju4DofTf_vqWQBNyg@mail.gmail.com> (raw)
In-Reply-To: <20210802155639.GA2293188@dhcp-10-100-145-180.wdc.com>

Hi,

Op ma 2 aug. 2021 om 17:56 schreef Keith Busch <kbusch@kernel.org>:
>
> On Sat, Jul 31, 2021 at 10:32:20AM +0200, koos vriezen wrote:
> > Hi,
> >
> > On my XPS 13 9380 I get local mails with content
> >
> > "
> > The following warning/error was logged by the smartd daemon:
> >
> > Device: /dev/nvme0, number of Error Log entries increased from 28 to 29
> >
> > Device info:
> > PM981 NVMe Samsung 512GB, S/N:S3ZHNF0KB11472, FW:EXA74D1Q, 512 GB
> > "
> >
> > after boot and increasing numbers after resume. Git bisect report:
>
> The controller shouldn't log an error when we request an optional
> identification. We don't have another way to determine if the controller
> supports this other than to request it. I think this should be reported
> to the device vendor for a firmware fix.

Thanks for your answer. I have the latest Dell bios installed (which
applied quite some firmware updates as well during install -- not that
I remembered which one exactly) and officially this device is too old
for support from Dell.

I didn't see any recents hits with google for this error, so maybe
it's just this device. I guess I can add a `return 0;`  just before
the `nvme_ctrl_limited_cns` call in `nvme_init_non_mdts_limits`
locally for now.

Cheers,
Koos Vriezen

_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme

  reply	other threads:[~2021-08-02 16:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-31  8:32 bisected: 5befc7c26e nvme impl non-mdts gives smartd error log entries koos vriezen
2021-08-02 15:56 ` Keith Busch
2021-08-02 16:49   ` koos vriezen [this message]
2021-10-14  2:04 ` Keith Busch
  -- strict thread matches above, loose matches on Subject: below --
2021-07-29  9:18 koos vriezen
2021-07-30  3:27 ` Bart Van Assche

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAGCbPWSK+AnEwM79vAfU7GG1eTjPB5xvDju4DofTf_vqWQBNyg@mail.gmail.com \
    --to=koos.vriezen@gmail.com \
    --cc=kbusch@kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.