From: Patrick Steinhardt <ps@pks.im>
To: Tomas Janousek <tomi@nomi.cz>
Cc: Ming Lei <tom.leiming@gmail.com>, Jens Axboe <axboe@kernel.dk>,
linux-block <linux-block@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] block: fix NPE when resuming SCSI devices using blk-mq
Date: Mon, 30 Jul 2018 09:59:49 +0200 [thread overview]
Message-ID: <20180730075949.GA1755@xps.pks.im> (raw)
In-Reply-To: <20180729094131.4kwuukzgfgtisgya@notes.lisk.in>
[-- Attachment #1: Type: text/plain, Size: 1232 bytes --]
On Sun, Jul 29, 2018 at 11:41:31AM +0200, Tomas Janousek wrote:
> Hi,
>
> On Fri, Jul 13, 2018 at 09:41:41PM +0800, Ming Lei wrote:
> > Now runtime PM is disabled for blk-mq/scsi_mq, not sure how this issue is
> > triggered on your machine.
>
> While Patrick did miss the following patch:
>
> * 765e40b675a9 ("block: disable runtime-pm for blk-mq"; July 2017).
>
> there is at least one other way to trigger it -- enable laptop-mode-tools
> or tlp which enable runtime-pm for all devices.
>
> The "disable runtime-pm for blk-mq" only disables it _by_default_, but doesn't
> prevent it from being enabled again from user-space, which it is unless one
> manually blacklists sd devices from runtime-pm enablement. It's bitten a few
> people already: https://github.com/rickysarraf/laptop-mode-tools/issues/123
>
> (I found this thread because I'm also getting the NULL pointer dereference at
> 00000000000001a8 on resume from suspend.)
Huh, I did send out some more details on how I reproduce the
issue, but it seems like my mail didn't get through. While I
don't use laptop-mode-tools, I do have some custom hotplugging
scripts which do in fact enable runtime-PM for most devices.
Regards
Patrick
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-07-30 7:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-13 13:29 Patrick Steinhardt
2018-07-13 13:41 ` Ming Lei
2018-07-16 15:11 ` Patrick Steinhardt
2018-07-29 9:41 ` Tomas Janousek
2018-07-30 7:59 ` Patrick Steinhardt [this message]
2018-07-30 11:50 ` Ming Lei
2018-07-30 15:00 ` Tomas Janousek
2018-07-25 18:13 ` Bart Van Assche
2018-07-26 8:38 ` Patrick Steinhardt
2018-07-26 13:51 ` Bart Van Assche
2018-07-27 12:35 ` Patrick Steinhardt
2018-07-27 15:03 ` Bart Van Assche
2018-07-28 18:50 ` Patrick Steinhardt
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=20180730075949.GA1755@xps.pks.im \
--to=ps@pks.im \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tom.leiming@gmail.com \
--cc=tomi@nomi.cz \
/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®