From: Jens Axboe <axboe@kernel.dk>
To: Pavel Machek <pavel@ucw.cz>,
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: Tue, 23 Apr 2019 07:55:05 -0600 [thread overview]
Message-ID: <41d56ba6-d0cb-5d5e-f5f4-9bca045440dd@kernel.dk> (raw)
In-Reply-To: <20190423102239.GA15531@amd>
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?
--
Jens Axboe
next prev parent reply other threads:[~2019-04-23 13:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190408173928.GB13260@amd>
2019-04-12 10:28 ` next-20190408: Suspend/resume problems on Thinkpad X60 Pavel Machek
2019-04-23 10:22 ` next-20190408..0418: " Pavel Machek
2019-04-23 13:55 ` Jens Axboe [this message]
2019-04-24 8:26 ` Pavel Machek
2019-04-24 9:54 ` Pavel Machek
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=41d56ba6-d0cb-5d5e-f5f4-9bca045440dd@kernel.dk \
--to=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=pavel@ucw.cz \
--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).