linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Jens Axboe <axboe@kernel.dk>
Cc: kernel list <linux-kernel@vger.kernel.org>,
	rjw@rjwysocki.net, linux-pm@vger.kernel.org,
	sfr@canb.auug.org.au, linux-next@vger.kernel.org,
	hdegoede@redhat.com, linux-ide@vger.kernel.org
Subject: Re: next-20190408..0418: Suspend/resume problems on Thinkpad X60
Date: Wed, 24 Apr 2019 11:54:31 +0200	[thread overview]
Message-ID: <20190424095431.GA32457@amd> (raw)
In-Reply-To: <41d56ba6-d0cb-5d5e-f5f4-9bca045440dd@kernel.dk>

[-- Attachment #1: Type: text/plain, Size: 1147 bytes --]

On Tue 2019-04-23 07:55:05, Jens Axboe wrote:
> On 4/23/19 4:22 AM, Pavel Machek wrote:
> > Hi!
> > 
> >>> It boots ok (unlike mainline -- I'm debugging that), and I can suspend
> >>> and resume... but then cursor in X is moving and I can talk to
> >>> applications cached in memory, but any access to disk hangs.
> >>
> >> Mainline problem was identified.
> >>
> >> But resume is still broken. I took advantage of fact that I can still
> >> do cached commands, and got complete dmesg. I'm attaching it.
> > 
> > Still broken in 0418. Ideas would be welcome at this point.
> 
> Bisect it?

commit fdbbda7b3a0622fcfe630238d0bf6c57c4ba3663
Merge: 3c442d5 6c88d73
Author: Jens Axboe <axboe@kernel.dk>
Date:   Mon Apr 22 13:57:36 2019 -0600

Works ok. So... block is not responsible.

Let me check

commit 91b112cf3b599f06f1e810cfedf37023f25d5588
Merge: fb2c4a8 e32d939
Author: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Date:   Mon Apr 22 01:52:48 2019 +0200

									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  parent reply	other threads:[~2019-04-24  9:54 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-08 17:39 next-20190408: Suspend/resume problems on Thinkpad X60 Pavel Machek
2019-04-12 10:28 ` Pavel Machek
2019-04-23 10:22   ` next-20190408..0418: " Pavel Machek
2019-04-23 13:55     ` Jens Axboe
2019-04-24  8:26       ` Pavel Machek
2019-04-24  9:54       ` Pavel Machek [this message]
2019-04-24 10:48         ` Pavel Machek
2019-04-24 20:21           ` Pavel Machek
2019-04-24 20:48             ` regression -next -- scsi: sd: Rely on the driver core for asynchronous probing was " Pavel Machek
2019-04-24 20:51               ` Pavel Machek
2019-04-24 20:56                 ` Bart Van Assche
2019-04-25  7:33                   ` Pavel Machek
2019-04-25 13:35                     ` Bart Van Assche
2019-04-26 10:32                       ` Pavel Machek
2019-04-26 14:58                         ` Bart Van Assche
2019-04-26 17:59                           ` Pavel Machek
2019-04-23 14:09     ` Bart Van Assche
2019-04-24 10:17       ` Pavel Machek
2019-04-24 22:34         ` 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=20190424095431.GA32457@amd \
    --to=pavel@ucw.cz \
    --cc=axboe@kernel.dk \
    --cc=hdegoede@redhat.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=sfr@canb.auug.org.au \
    /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;
as well as URLs for NNTP newsgroup(s).