From owner-freebsd-usb@freebsd.org  Sat Sep 30 17:26:52 2017
Return-Path: <owner-freebsd-usb@freebsd.org>
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 1B151E2B72F
 for <freebsd-usb@mailman.ysv.freebsd.org>;
 Sat, 30 Sep 2017 17:26:52 +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 08ADD75A1C
 for <freebsd-usb@FreeBSD.org>; Sat, 30 Sep 2017 17:26:52 +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 v8UHQpiR063961
 for <freebsd-usb@FreeBSD.org>; Sat, 30 Sep 2017 17:26:51 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-usb@FreeBSD.org
Subject: [Bug 222624] [usb] [panic] thread's sleep queue 0 is not empty at
 usb_process.c:193
Date: Sat, 30 Sep 2017 17:26:51 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 11.1-RELEASE
X-Bugzilla-Keywords: crash
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: decke@FreeBSD.org
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-usb@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-222624-17-AT1Py9Y1fJ@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-222624-17@https.bugs.freebsd.org/bugzilla/>
References: <bug-222624-17@https.bugs.freebsd.org/bugzilla/>
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 <freebsd-usb.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-usb>,
 <mailto:freebsd-usb-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-usb/>
List-Post: <mailto:freebsd-usb@freebsd.org>
List-Help: <mailto:freebsd-usb-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-usb>,
 <mailto:freebsd-usb-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 30 Sep 2017 17:26:52 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D222624

--- Comment #4 from Bernhard Froehlich <decke@FreeBSD.org> ---
I also do have this panics with the release kernel but never got any useful
info from it when it happened because it just stopped and did not even show=
 a
panic. What makes me confident that it's not a faulty hardware is that 10.3=
 was
running very solid on it for around a year and that I have two of those
machines with the exact same symptoms.

--=20
You are receiving this mail because:
You are the assignee for the bug.=