[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b2505963-0fdc-81d2-6b8a-315a31eb922e@prevas.dk>
Date: Wed, 29 Aug 2018 12:55:03 +0200
From: Rasmus Villemoes <rasmus.villemoes@...vas.dk>
To: stable@...r.kernel.org, Fabio Estevam <fabio.estevam@....com>
Cc: LKML <linux-kernel@...r.kernel.org>,
Sean Nyekjær <Sean.Nyekjaer@...vas.dk>,
Andrey Smirnov <andrew.smirnov@...il.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Shawn Guo <shawnguo@...nel.org>
Subject: Re: reboot on wandboard fails with v4.14.67 (bisected to 2059e527a6)
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.
Rasmus
Powered by blists - more mailing lists