From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-eopbgr80090.outbound.protection.outlook.com ([40.107.8.90]:58002 "EHLO EUR04-VI1-obe.outbound.protection.outlook.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1728312AbeH2Ovh (ORCPT ); Wed, 29 Aug 2018 10:51:37 -0400 Subject: Re: reboot on wandboard fails with v4.14.67 (bisected to 2059e527a6) From: Rasmus Villemoes To: stable@vger.kernel.org, Fabio Estevam Cc: LKML , =?UTF-8?Q?Sean_Nyekj=c3=a6r?= , Andrey Smirnov , Greg Kroah-Hartman , Shawn Guo References: Message-ID: Date: Wed, 29 Aug 2018 12:55:03 +0200 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: stable-owner@vger.kernel.org List-ID: 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