The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: LKML <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: 5.14-rc failure to resume
Date: Sat, 24 Jul 2021 11:08:08 -0600	[thread overview]
Message-ID: <7df62a0a-d739-57ef-be47-2d9734a1cf7e@kernel.dk> (raw)
In-Reply-To: <eeab973d-f634-a182-6d76-f3912f8cf887@kernel.dk>

On 7/24/21 9:57 AM, Jens Axboe wrote:
> Hi,
> 
> I ran into this when doing the last bit of testing on pending changes
> for this release on the laptop. Outside of running testing on these
> changes, I always build and boot current -git and my changes on my
> laptop as well.
> 
> 5.14-rc1 + changes works fine, current -git and changes fail to resume
> every single time. I just get a black screen. Tip of tree before merging
> fixes is:

Typo, 5.14-rc2 + changes. Hence the problematic change is sometime between
-rc2 and current -git.

Running a bisect now but expecting it to take all day, will report
what it uncovers.

-- 
Jens Axboe


  reply	other threads:[~2021-07-24 17:08 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-24 15:57 5.14-rc failure to resume Jens Axboe
2021-07-24 17:08 ` Jens Axboe [this message]
2021-07-24 17:56 ` Jens Axboe
2021-07-24 19:43   ` Jens Axboe
2021-07-24 20:05     ` Andy Shevchenko
2021-07-24 20:26       ` Jens Axboe
2021-07-24 21:15         ` Andy Shevchenko
2021-07-24 21:21           ` Daniel Scally
2021-07-24 21:35           ` Jens Axboe
2021-07-24 21:39             ` Jens Axboe
2021-07-24 22:37               ` Linus Torvalds
2021-07-24 20:48     ` Linus Torvalds
2021-07-24 21:02       ` Andy Shevchenko
2021-07-24 19:49   ` Andy Shevchenko
2021-07-24 20:24     ` Daniel Scally
2021-07-24 20:28     ` Jens Axboe
2021-07-24 20:34       ` 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=7df62a0a-d739-57ef-be47-2d9734a1cf7e@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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