Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932969AbcKNJtC (ORCPT ); Mon, 14 Nov 2016 04:49:02 -0500 Received: from asix.com.tw ([210.243.224.51]:14936 "EHLO freebsd2.asix.com.tw" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1752435AbcKNJrh (ORCPT ); Mon, 14 Nov 2016 04:47:37 -0500 Reply-To: From: "ASIX_Allan [Office]" To: "'Jon Hunter'" , , , , , , , , , , , , , , , , , , References: <77fa76d6-ef63-47db-a316-93b3a0c0705b@nvidia.com> <00e501d23e54$337d4b70$9a77e250$@asix.com.tw> In-Reply-To: Subject: RE: [PATCH v3 3/5] net: asix: Fix AX88772x resume failures Date: Mon, 14 Nov 2016 17:45:28 +0800 Organization: ASIX Message-ID: <010d01d23e5b$d8993130$89cb9390$@asix.com.tw> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQFzuyiSv/+6T+y6rtkmjO8CY/XxAQNI3qSgAu+f8U8Bl3s9PQG6NthqoUju0XA= Content-Language: zh-tw Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1323 Lines: 40 Hi Jon, Please help to double check if the USB host controller of your Terga platform had been powered OFF while running the ax88772_suspend() routine or not? --- Best regards, Allan Chou -----Original Message----- From: Jon Hunter [mailto:jonathanh@nvidia.com] Sent: Monday, November 14, 2016 5:34 PM To: allan@asix.com.tw; robert.foss@collabora.com; freddy@asix.com.tw; Dean_Jenkins@mentor.com; Mark_Craske@mentor.com; davem@davemloft.net; ivecera@redhat.com; john.stultz@linaro.org; vpalatin@chromium.org; stephen@networkplumber.org; grundler@chromium.org; changchias@gmail.com; andrew@lunn.ch; tremyfr@gmail.com; colin.king@canonical.com; linux-usb@vger.kernel.org; netdev@vger.kernel.org; linux-kernel@vger.kernel.org; vpalatin@google.com Subject: Re: [PATCH v3 3/5] net: asix: Fix AX88772x resume failures Hi Allan, On 14/11/16 08:50, ASIX_Allan [Home] wrote: > It seems the AX88772x dongle had been unexpectedly removed while > running the > ax88772_suspend() routine. If yes, you might see these error messages > because the hardware had been absent. In my case the hardware was never removed. The boards are in a test fixture that are not touched. This is seen on more than one board. By reverting this change I no longer see the error messages and appears to be 100% reproducible. Jon -- nvpublic