From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2999621AbdEANs5 (ORCPT ); Mon, 1 May 2017 09:48:57 -0400 Received: from mail.tomasu.net ([192.241.222.217]:59400 "EHLO mail.tomasu.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2998565AbdEANst (ORCPT ); Mon, 1 May 2017 09:48:49 -0400 X-Greylist: delayed 522 seconds by postgrey-1.27 at vger.kernel.org; Mon, 01 May 2017 09:48:49 EDT From: Thomas Fjellstrom To: linux-usb@vger.kernel.org Cc: LKML Subject: Asmedia USB 1343 crashes Date: Mon, 01 May 2017 07:40:03 -0600 Message-ID: <24094857.9esuq4f4c4@natasha> User-Agent: KMail/5.2.3 (Linux/4.11.0-rc7; KDE/5.28.0; x86_64; ; ) MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org I've got a 970 Pro gaming aura motherboard with an Asmedia 1343 Usb 3.1 controller. It's been consistently throwing errors and eventually crashing and becomming unresponsive. Even just plugging in one device to the rear port will eventually cause the controller to die. Usually only takes a few hours for it to completely die. One of the errors that shows up consistently is: usbfs: process did not claim interface 0 before use Later on, devices start to throw errors and eventually everything goes away. A little while ago, I disabled usb autosuspend and things seem to be behaving. I'm currently running 4.11-rc7 but the issue appeared on several earlier kernels as well. -- Thomas Fjellstrom thomas@fjellstrom.ca