From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <stable-owner@vger.kernel.org>
Received: from mail-eopbgr10109.outbound.protection.outlook.com ([40.107.1.109]:53824
        "EHLO EUR02-HE1-obe.outbound.protection.outlook.com"
        rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP
        id S1727172AbeH2NwM (ORCPT <rfc822;stable@vger.kernel.org>);
        Wed, 29 Aug 2018 09:52:12 -0400
To: stable@vger.kernel.org, Fabio Estevam <fabio.estevam@nxp.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
        =?UTF-8?Q?Sean_Nyekj=c3=a6r?= <Sean.Nyekjaer@prevas.dk>,
        Andrey Smirnov <andrew.smirnov@gmail.com>,
        Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
        Shawn Guo <shawnguo@kernel.org>
From: Rasmus Villemoes <rasmus.villemoes@prevas.dk>
Subject: reboot on wandboard fails with v4.14.67 (bisected to 2059e527a6)
Message-ID: <b2ea002f-4fe8-0738-b346-69ed138cecd0@prevas.dk>
Date: Wed, 29 Aug 2018 11:55:16 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Sender: stable-owner@vger.kernel.org
List-ID: <stable.vger.kernel.org>

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.

Rasmus