From owner-freebsd-current@FreeBSD.ORG Sun Mar 7 10:24:18 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 59048106566C; Sun, 7 Mar 2010 10:24:18 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: from mail-pw0-f54.google.com (mail-pw0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id 2771F8FC08; Sun, 7 Mar 2010 10:24:17 +0000 (UTC) Received: by pwj1 with SMTP id 1so3623688pwj.13 for ; Sun, 07 Mar 2010 02:24:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=RPyasE1LZGkmN/5FfnHqIvm5jn0wmuyXMLQsw7PNkGs=; b=ix1ktyIXNvupRcU8LT4+KRIyP6ytp0FoLnrz8eJ5qb8pFgAixmD44Tf0Mv39dHZMao pdFT/sB8pvq72qDy6ZmZz9t6wFuaaBIyTCNxXtaxcGP2EZ3yl7b8uFlkZzKpLmI8DEbC qIvNVwf13zAvxtXKVvXtOMhk5KAAw/9uLCGSQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=pE/o3cK1IW/bYl07vOg2b9rbtGs1nRVPzqx47downpGVNFDtfQ5a1auqP/bUVfAVQS fJmxTXnBDoLuwI8OQ3Linl5by52pX8YcxAMmFh5LZRreAH9q4J96z+1kYaF90JYOCBWQ /niWH2VerbY0UKgxzIQHdhwijRfXapKn0f1ss= MIME-Version: 1.0 Received: by 10.142.67.36 with SMTP id p36mr2230261wfa.167.1267957457053; Sun, 07 Mar 2010 02:24:17 -0800 (PST) In-Reply-To: <7d6fde3d1003070207q621e69ado2cb64e431feacd76@mail.gmail.com> References: <7d6fde3d1003070207q621e69ado2cb64e431feacd76@mail.gmail.com> Date: Sun, 7 Mar 2010 02:24:17 -0800 Message-ID: <7d6fde3d1003070224k3626a9b5y98c11a43eef1bed4@mail.gmail.com> From: Garrett Cooper To: Alexander Motin , Hans Petter Selasky Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: FreeBSD Current Subject: Re: Removing USB keyboard after filesystems synced causes panic with destroyed mutex twa(4)? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Mar 2010 10:24:18 -0000 On Sun, Mar 7, 2010 at 2:07 AM, Garrett Cooper wrote: > Hi Alexander and Hans, > =A0 =A0I recently did the following which generated a panic on a > 9-CURRENT kernel compiled on the 26th: > > 1. Executed reboot > 2. Removed keyboard. > 3. Some time after `All buffers synced\nUptime: ...' was displayed, > the keyboard was registered disconnected. > 4. The interrupt was delivered to my twa(4) enabled card and the > kernel panicked, like so: > > ugen2.2: at usbus2 (disconnected) > uhub8: at uhub2, port 1, addr 2 (disconnected) > ugen2.3: at usbus2 (disconnected) > ukbd0: at uhub8, port 3, addr 3 (disconnected) > uhid0: at uhub8, port 3, addr 3 (disconnected) > panic: mtx_lock_spin() of destroyed mutex @ /usr/src/sys/dev/twa/tw_cl_in= tr.c:88 > > cpuid =3D 1 > KDB: enter: panic > [thread pid 12 tid 100025 ] > Stopped at =A0 =A0 =A0 =A0 kdb_enter+0x3d: movq =A0 =A0 $0,0x40289c(%rip) > db> > > =A0 =A0I wish I could provide you with more details, but unfortunately I > the USB bus isn't registering the fact that I'm reattaching the > keyboard right now and the box won't reboot automatically :( (didn't > set the right sysctl beforehand to panic automatically). I'll try and > reproduce the issue again, but I was just wondering whether or not you > guys had seen this problem before. Phew... it's reproducible with that kernel. Here's what I did exactly (because my original directions were incorrect): 1. Hit power button (for S5). 2. Disconnect keyboard RIGHT as `Uptime: ...' is displayed. Kernel panicked on my system again. Now to figure out if it still exists with a kernel compiled today, and also how to debug it if it still does exist :/... Thanks, -Garrett