Linux Tegra architecture development
 help / color / mirror / Atom feed
From: Guenter Roeck <linux-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>
To: Jon Hunter <jonathanh-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>,
	Greg Kroah-Hartman
	<gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org>
Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org,
	akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org,
	shuah-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
	patches-ssFOTAMYnuFg9hUCZPvPmw@public.gmane.org,
	ben.hutchings-4yDnlxn2s6sWdaTGBSpHTA@public.gmane.org,
	lkft-triage-cunTk1MwBs8s++Sfvej+rw@public.gmane.org,
	stable-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-tegra <linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH 4.19 000/639] 4.19.99-stable review
Date: Sat, 25 Jan 2020 07:46:47 -0800	[thread overview]
Message-ID: <eadee1dd-fb6d-855d-935a-4bf93a9ad505@roeck-us.net> (raw)
In-Reply-To: <87fcb1f0-b1b8-a6e2-b8f6-b95a07f67919-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>

On 1/25/20 3:32 AM, Jon Hunter wrote:
> 
> On 24/01/2020 18:07, Jon Hunter wrote:
>>
>> On 24/01/2020 17:36, Greg Kroah-Hartman wrote:
>>> On Fri, Jan 24, 2020 at 02:50:05PM +0000, Jon Hunter wrote:
>>>> Hi Greg,
>>>>
>>>> On 24/01/2020 09:22, Greg Kroah-Hartman wrote:
>>>>> This is the start of the stable review cycle for the 4.19.99 release.
>>>>> There are 639 patches in this series, all will be posted as a response
>>>>> to this one.  If anyone has any issues with these being applied, please
>>>>> let me know.
>>>>>
>>>>> Responses should be made by Sun, 26 Jan 2020 09:26:29 +0000.
>>>>> Anything received after that time might be too late.
>>>>>
>>>>> The whole patch series can be found in one patch at:
>>>>> 	https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.19.99-rc1.gz
>>>>> or in the git tree and branch at:
>>>>> 	git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-4.19.y
>>>>> and the diffstat can be found below.
>>>>>
>>>>> thanks,
>>>>>
>>>>> greg k-h
>>>>>
>>>>> -------------
>>>>> Pseudo-Shortlog of commits:
>>>>
>>>> ...
>>>>
>>>>> Rafael J. Wysocki <rafael.j.wysocki-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
>>>>>      PCI: PM: Skip devices in D0 for suspend-to-idle
>>>>
>>>> The above commit is causing a suspend regression on Tegra124 Jetson-TK1.
>>>> Reverting this on top of v4.19.99-rc1 fixes the issue.
>>>
>>> This is also in the 4.14 queue, so should I drop it there too?
>>
>> I did not see any failures with the same board on that branch, so I
>> would say no, but odd that it only fails here. It was failing for me
>> 100% so I would have expected to see if there too if it was a problem.
> 
> Hmmm, rc2 still not working for me ...
> 
> Test results for stable-v4.19:
>      11 builds:	11 pass, 0 fail
>      22 boots:	22 pass, 0 fail
>      32 tests:	30 pass, 2 fail
> 
> Linux version:	4.19.99-rc2-g24832ad2c623
> Boards tested:	tegra124-jetson-tk1, tegra186-p2771-0000,
>                  tegra194-p2972-0000, tegra20-ventana,
>                  tegra210-p2371-2180, tegra30-cardhu-a04
> 
> I still see the following commit in rc2 ...
> 
> commit bb52152abe85f971278a7a4f033b29483f64bfdb
> Author: Rafael J. Wysocki <rafael.j.wysocki-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
> Date:   Thu Jun 13 23:59:45 2019 +0200
> 
>      PCI: PM: Skip devices in D0 for suspend-to-idle
> 
> BTW, I checked the 4.14. queue and I do not see the above change in
> there, however, there is similar change ...
> 
> Rafael J. Wysocki <rafael.j.wysocki-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
>      PCI: PM: Avoid possible suspend-to-idle issue
> 
bb52152abe85 fixes this one, which in turn fixes 33e4f80ee69b.
The above in 4.14 but not its fixes is spelling a bit of trouble.

Maybe commit 471a739a47aa7 ("PCI: PM: Avoid skipping bus-level
PM on platforms without ACPI") was added to -rc2, since it is
supposed to fix bb52152abe85.

Guenter

  parent reply	other threads:[~2020-01-25 15:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20200124093047.008739095@linuxfoundation.org>
2020-01-24 14:50 ` [PATCH 4.19 000/639] 4.19.99-stable review Jon Hunter
2020-01-24 17:36   ` Greg Kroah-Hartman
2020-01-24 18:07     ` Jon Hunter
     [not found]       ` <8a782263-aca3-3846-12a0-4eb21f015894-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2020-01-25 11:32         ` Jon Hunter
     [not found]           ` <87fcb1f0-b1b8-a6e2-b8f6-b95a07f67919-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2020-01-25 15:46             ` Guenter Roeck [this message]
2020-01-26  9:13               ` Greg Kroah-Hartman
2020-01-27  9:38                 ` Jon Hunter
2020-01-27  9:41                   ` Greg Kroah-Hartman

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=eadee1dd-fb6d-855d-935a-4bf93a9ad505@roeck-us.net \
    --to=linux-0h96xk9xttrk1umjsbkqmq@public.gmane.org \
    --cc=akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org \
    --cc=ben.hutchings-4yDnlxn2s6sWdaTGBSpHTA@public.gmane.org \
    --cc=gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org \
    --cc=jonathanh-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=lkft-triage-cunTk1MwBs8s++Sfvej+rw@public.gmane.org \
    --cc=patches-ssFOTAMYnuFg9hUCZPvPmw@public.gmane.org \
    --cc=shuah-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
    --cc=stable-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.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