[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOMZO5Bvj=kB8m7DcX2vSLr3e0_uW-CnURtwM71YJ=NWT+DCgQ@mail.gmail.com>
Date: Wed, 29 Aug 2018 10:57:37 -0300
From: Fabio Estevam <festevam@...il.com>
To: Rasmus Villemoes <rasmus.villemoes@...vas.dk>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: stable <stable@...r.kernel.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
Andrey Smirnov <andrew.smirnov@...il.com>,
Shawn Guo <shawnguo@...nel.org>,
Sean Nyekjaer <sean.nyekjaer@...vas.dk>
Subject: Re: reboot on wandboard fails with v4.14.67 (bisected to 2059e527a6)
Hi Rasmus,
> On 2018-08-29 11:55, Rasmus Villemoes wrote:
>> We're using imx_v6_v7_defconfig on our Wandboards. After upgrading to
>> v4.14.67, reboot no longer works (or, well, takes a very long time when
>> the watchdog is configured).
>>
>> v4.14.66 works fine, the breakage bisects to
>> 2059e527a659cf16d6bb709f1c8509f7a7623fc4 (ARM: imx_v6_v7_defconfig:
>> Select ULPI support), and reverting that on top of v4.14.67 again works.
>
> FWIW, v4.18 (the mainline release containing the upstream commit
> 157bcc0609) works fine, while v4.17.19 which also has that commit
> backported (as df06ca1f56) fails. So I'm guessing there must be some
> other commits in v4.18 that happen to make imx_v6_v7_defconfig work.
Thanks for reporting.
Commit 157bcc06094c3 ("ARM: imx_v6_v7_defconfig: Select ULPI support")
was meant to be applied for 4.18 only.
I think we should revert it from earlier stable versions.
Thanks
Powered by blists - more mailing lists