From owner-freebsd-usb@freebsd.org Tue Nov 1 13:24:21 2016 Return-Path: Delivered-To: freebsd-usb@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B0459C27657 for ; Tue, 1 Nov 2016 13:24:21 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9F9A31153 for ; Tue, 1 Nov 2016 13:24:21 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id uA1DOLqK006111 for ; Tue, 1 Nov 2016 13:24:21 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-usb@FreeBSD.org Subject: [Bug 213877] xhci reset causes panic on SuperMicro A1SRi-2758F board Date: Tue, 01 Nov 2016 13:24:21 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: usb X-Bugzilla-Version: 11.0-RELEASE X-Bugzilla-Keywords: crash, needs-qa X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: voltagex@voltagex.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-usb@FreeBSD.org X-Bugzilla-Flags: mfc-stable9? mfc-stable10? mfc-stable11? X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Nov 2016 13:24:21 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213877 --- Comment #6 from Adam Baxter --- (In reply to Hans Petter Selasky from comment #5) Hi Hans, I'm trying to reproduce it, however this is difficult as it takes 2-16 hours for the bug to occur. Strangely, turning off soft journaling on the root filesystem allows the system to run for a lot longer before crashing. I've switched to another RNDIS device so that I can test for longer periods= of time. I also may try to get the serial console going over the weekend so I don't have to use a screen recorder to get the trace. To be honest, it's unlikely I'll be able to get to a root cause for this is= sue - the setup I have is only while my main internet connection is down, await= ing repairs. --=20 You are receiving this mail because: You are the assignee for the bug.=