public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
From: Oleksandr Natalenko <oleksandr@natalenko.name>
To: Jens Axboe <axboe@kernel.dk>
Cc: Greg KH <gregkh@linuxfoundation.org>,
	Mike Galbraith <efault@gmx.de>, Christoph Hellwig <hch@lst.de>,
	linux-block@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: blk-mq breaks suspend even with runtime PM patch
Date: Tue, 08 Aug 2017 18:36:01 +0200	[thread overview]
Message-ID: <2416479.dXsOYsr7UT@natalenko.name> (raw)
In-Reply-To: <843d7ee7-63b9-d34c-6d91-dea0b940d330@kernel.dk>

Could you queue "block: disable runtime-pm for blk-mq" too please? It is al=
so=20
related to suspend-resume freezes that were observed by multiple users.

Thanks.

On =C3=BAter=C3=BD 8. srpna 2017 18:33:29 CEST Jens Axboe wrote:
> On 08/08/2017 10:22 AM, Greg KH wrote:
> > On Sun, Jul 30, 2017 at 03:50:15PM +0200, Oleksandr Natalenko wrote:
> >> Hello Mike et al.
> >>=20
> >> On ned=C4=9Ble 30. =C4=8Dervence 2017 7:12:31 CEST Mike Galbraith wrot=
e:
> >>> FWIW, first thing I'd do is update that 4.12.0 to 4.12.4, and see if
> >>> stable fixed it.
> >>=20
> >> My build already includes v4.12.4.
> >>=20
> >>> If not, I'd find these two commits irresistible.
> >>>=20
> >>> 5f042e7cbd9eb blk-mq: Include all present CPUs in the default queue
> >>> mapping
> >>> 4b855ad37194f blk-mq: Create hctx for each present CPU
> >>=20
> >> I've applied these 2 commits, and cannot reproduce the issue anymore.
> >> Looks
> >> like a perfect hit, thanks!
> >>=20
> >>> 'course applying random upstream bits does come with some risk, trying
> >>> a kernel already containing them has less "entertainment" potential.
> >>=20
> >> Should you consider applying them to v4.12.x stable series? CC'ing Greg
> >> just in case.
> >=20
> > I can queue these up if I get an ack from the developers/maintainers
> > that it is ok to do so...
>=20
> You can add those two commits to stable.

  reply	other threads:[~2017-08-08 16:36 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-29 15:27 blk-mq breaks suspend even with runtime PM patch Oleksandr Natalenko
2017-07-29 21:17 ` Oleksandr Natalenko
2017-07-30  5:12 ` Mike Galbraith
2017-07-30 13:50   ` Oleksandr Natalenko
2017-08-08 16:22     ` Greg KH
2017-08-08 16:33       ` Jens Axboe
2017-08-08 16:36         ` Oleksandr Natalenko [this message]
2017-08-08 16:43           ` Greg KH
2017-08-08 16:46             ` Oleksandr Natalenko
2017-08-08 16:34       ` Mike Galbraith
2017-08-08 16:44         ` Greg KH
2017-08-08 16:50           ` Mike Galbraith
2017-08-08 18:33             ` Mike Galbraith
2017-08-08 18:35               ` Jens Axboe

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=2416479.dXsOYsr7UT@natalenko.name \
    --to=oleksandr@natalenko.name \
    --cc=axboe@kernel.dk \
    --cc=efault@gmx.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=hch@lst.de \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.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