[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190706151645.GA9856@amd>
Date: Sat, 6 Jul 2019 17:16:45 +0200
From: Pavel Machek <pavel@....cz>
To: "Rafael J. Wysocki" <rafael@...nel.org>
Cc: "Rafael J. Wysocki" <rjw@...ysocki.net>,
Linux-pm mailing list <linux-pm@...r.kernel.org>,
kernel list <linux-kernel@...r.kernel.org>,
Stephen Rothwell <sfr@...b.auug.org.au>
Subject: Re: suspend broken in next-20190704 on Thinkpad X60
Hi!
> > > > Suspend is broken in next-20190704 on Thinkpad X60.
> > >
> > > Broken in what way? Any details?
> > >
> > > > It very very probably worked ok in 20190701.
> > >
> > > Well, please try the linux-next branch from linux-pm.git
> > > (git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git)
> > > alone and see if that fails.
> >
> > So... let me try this one?
> >
> > commit 1e2a4c9019eb53f62790fadf86c14a54f4cf4888 (patch)
> > tree cb5339fcaae2166832f91f4ce9f40575cc6cb6e5
> > parent 3836c60c063581294c3a82f8cbccf3f702951358 (diff)
> > parent 0a811974f3f79eea299af79c29595d8e1cb80a15 (diff)
> > download
> > linux-pm-1e2a4c9019eb53f62790fadf86c14a54f4cf4888.tar.gz
> > Merge branch 'pm-cpufreq-new' into
> > linux-nexttestinglinux-nextbleeding-edge
> > * pm-cpufreq-new:
> >
> > That one is broken, too.
> >
> > pavel@amd:~$ sudo pm-suspend
> >
> > Machine suspends, resumes, but I don't get my prompt back.
>
> I'm not sure what you mean here. I'm guessing that you don't get back
> to the console from which you ran the pm-suspend command, but is X
> restored, for example? Is there any way to get into the system in
> that state?
X is restored, and the rest of system works, but "pm-suspend" command
never completes, so I don't get shell prompt back in that window.
> Anyway, if 5.2-rc7 is OK, something in this branch causes the problem
> to happen for you.
>
> I would try
>
> https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/commit/?h=linux-next&id=f012a132824fc870b90980540f727c76fc72e244
>
> to narrow down the scope somewhat.
next-20190701 is ok, next-20190704 is broken. Can we use that to
narrow it down?
Best regards,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
Download attachment "signature.asc" of type "application/pgp-signature" (182 bytes)
Powered by blists - more mailing lists