From: Martin Steigerwald <martin@lichtvoll.de>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Thorsten Leemhuis <regressions@leemhuis.info>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Tejun Heo <tj@kernel.org>
Subject: Re: [Possible REGRESSION, 4.16-rc4] Error updating SMART data during runtime and could not connect to lvmetad at some boot attempts
Date: Mon, 19 Mar 2018 13:35:59 +0100 [thread overview]
Message-ID: <1592165.6qU88H7nrm@merkaba> (raw)
In-Reply-To: <f6f20cd6-0d52-4501-f8ea-c4da9ec128cf@redhat.com>
Hi Thorsten.
Hans de Goede - 19.03.18, 10:50:
> On 19-03-18 10:42, Thorsten Leemhuis wrote:
> > Hi! On 11.03.2018 09:20, Martin Steigerwald wrote:
> >> Since 4.16-rc4 (upgraded from 4.15.2 which worked) I have an issue
> >
> >> with SMART checks occassionally failing like this:
> > Martin (or someone else): Could you gibe a status update? I have this
> > issue on my list or regressions, but it's hard to follow as two
> > different issues seem to be discussed. Or is it just one issue? Did the
There are at least two issues.
> > patch/discussion that Bart pointed to help? Is the issue still showing
> > up in rc6?
>
> Your right there are 2 issues here:
>
> 1) The Crucial M500 SSD (at least the 480GB MU03 firmware version) does
> not like enabling SATA link power-management at a level of min_power
> or at the new(ish) med_power_with_dipm level. This problem exists in
> older kernels too, so this is not really a regression.
>
> New in 4.16 is a Kconfig option to enable SATA LPM by default, which
> makes this existing problem much more noticeable. Not sure if you want
> to count this as a regression. Either way I'm preparing and sending
> out a patch fixing this (by blacklisting LPM for this model SSD) right
> now.
Yes, and this is fixed by the nolpm quirk patch of Hans.
> 2) There seem to be some latency issues in the MU03 version of the
> firmware, triggered by polling SMART data, which causes lvmetad to
> timeout in some cases. Note I'm not involved in that part of this
> thread, but I believe that issue is currently unresolved.
Additionally I get a failure on boot / resume from hibernation in
blk_mq_terminate_expire occassionally. But I tend to believe that this is the
same issue.
This is still unresolved as of 4.16-rc6 + nolpm quick patch from Hans and the
"Change synchronize_rcu() in scsi_device_quiesce() into synchronize_sched()"
patch by Bart. Cause I had this occassional boot failure with it already.
The patch by Bart seems to be related to another issue of the blk-mq quiescing
stuff.
Thanks,
--
Martin
next prev parent reply other threads:[~2018-03-19 12:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-11 8:20 Martin Steigerwald
2018-03-11 14:37 ` Hans de Goede
2018-03-11 16:28 ` Martin Steigerwald
2018-03-11 16:41 ` Hans de Goede
2018-03-13 13:08 ` Martin Steigerwald
2018-03-13 14:32 ` Ming Lei
2018-03-13 14:56 ` Bart Van Assche
2018-03-14 11:01 ` Martin Steigerwald
2018-03-14 11:05 ` Hans de Goede
2018-03-14 12:48 ` Martin Steigerwald
2018-03-18 21:34 ` Hans de Goede
2018-03-18 22:06 ` Martin Steigerwald
2018-03-19 9:32 ` Hans de Goede
2018-03-15 10:48 ` Martin Steigerwald
2018-03-19 9:42 ` Thorsten Leemhuis
2018-03-19 9:50 ` Hans de Goede
2018-03-19 12:35 ` Martin Steigerwald [this message]
2018-04-10 17:30 ` Martin Steigerwald
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=1592165.6qU88H7nrm@merkaba \
--to=martin@lichtvoll.de \
--cc=hdegoede@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=regressions@leemhuis.info \
--cc=tj@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®