From owner-freebsd-current@FreeBSD.ORG  Mon Oct 10 15:28:22 2011
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 CDEF11065672;
	Mon, 10 Oct 2011 15:28:22 +0000 (UTC)
	(envelope-from hselasky@freebsd.org)
Received: from swip.net (mailfe01.c2i.net [212.247.154.2])
	by mx1.freebsd.org (Postfix) with ESMTP id 298D98FC15;
	Mon, 10 Oct 2011 15:28:21 +0000 (UTC)
X-T2-Spam-Status: No, hits=-0.3 required=5.0 tests=ALL_TRUSTED,
	BAYES_40,SPF_SOFTFAIL
Received: from [188.126.198.129] (account mc467741@c2i.net HELO
	laptop002.hselasky.homeunix.org)
	by mailfe01.swip.net (CommuniGate Pro SMTP 5.2.19)
	with ESMTPA id 190942649; Mon, 10 Oct 2011 17:28:19 +0200
Received-SPF: softfail receiver=mailfe01.swip.net; client-ip=188.126.198.129;
	envelope-from=hselasky@freebsd.org
From: Hans Petter Selasky <hselasky@freebsd.org>
To: Adrian Chadd <adrian@freebsd.org>
Date: Mon, 10 Oct 2011 17:25:18 +0200
User-Agent: KMail/1.13.5 (FreeBSD/8.2-STABLE; KDE/4.4.5; amd64; ; )
References: <CAGH67wTtLqVyKRynOHDF4yD7+6J38+k507BUeTjsvrG6HuaAGw@mail.gmail.com>
	<CAJ-Vmom1Mq7sRmGSftiEsvjGFAYHMSNcF7LtchLq33TiWhnRkg@mail.gmail.com>
In-Reply-To: <CAJ-Vmom1Mq7sRmGSftiEsvjGFAYHMSNcF7LtchLq33TiWhnRkg@mail.gmail.com>
X-Face: *nPdTl_}RuAI6^PVpA02T?$%Xa^>@hE0uyUIoiha$pC:9TVgl.Oq,NwSZ4V"
	=?iso-8859-1?q?=7CLR=2E+tj=7Dg5=0A=09=25V?=,x^qOs~mnU3]Gn;
	cQLv&.N>TrxmSFf+p6(30a/{)KUU!s}w\IhQBj}[g}bj0I3^glmC(
	=?iso-8859-1?q?=0A=09=3AAuzV9=3A=2EhESm-x4h240C=609=3Dw?=
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="windows-1252"
Content-Transfer-Encoding: 7bit
Message-Id: <201110101725.18195.hselasky@freebsd.org>
Cc: Garrett Cooper <yanegomi@gmail.com>,
	freebsd-current <freebsd-current@freebsd.org>
Subject: Re: USB storage corruption/panic when doing file IO and unplugging
	(another, non-storage) device
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Oct 2011 15:28:22 -0000

On Friday 07 October 2011 08:32:40 Adrian Chadd wrote:
> On 7 October 2011 13:55, Garrett Cooper <yanegomi@gmail.com> wrote:
> >> Has anyone seen this before?
> >> 
> >> This is _not_ plug/unplug the active storage device, or another
> >> storage device. This is when doing IO on a storage device (whether the
> >> root device or a media device) whilst plug/unplug a non-storage USB
> >> device (wifi chipsets w/ no driver.)
> > 
> >    Yeah. Ran into it earlier on in the 9.x cycle with twa unplugging
> > a USB keyboard when I was rebooting a machine; the panic was fixed in
> > twa, not ukbd. I suppose my question is: does this only happen with
> > USB, or is firewire affected, and why aren't the devices being
> > properly masked against interrupts [in the same queue??] [by
> > newbus???]?
> 
> Let's wait for hps to get back to us. This seems like something he can
> replicate very quickly.

Hi,

Could you send me the backtrace of the panic. USB is a broadcast system and 
connecting and disconnecting devices might cause interference. Make sure your 
driver is self powered. I have not seen this issue before. I'm using a USB 
disk every day.

--HPS