From owner-freebsd-current@FreeBSD.ORG Tue Feb 12 07:50:09 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 823DA495; Tue, 12 Feb 2013 07:50:09 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe08.c2i.net [212.247.154.226]) by mx1.freebsd.org (Postfix) with ESMTP id B3423A62; Tue, 12 Feb 2013 07:50:08 +0000 (UTC) X-T2-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED Received: from [176.74.213.204] (account mc467741@c2i.net HELO laptop015.hselasky.homeunix.org) by mailfe08.swip.net (CommuniGate Pro SMTP 5.4.4) with ESMTPA id 378120205; Tue, 12 Feb 2013 08:50:06 +0100 From: Hans Petter Selasky To: freebsd-current@freebsd.org, Alexander Motin Subject: Re: HEAD memsticks broken? [USB/CAM Problems?] Date: Tue, 12 Feb 2013 08:51:18 +0100 User-Agent: KMail/1.13.7 (FreeBSD/9.1-STABLE; KDE/4.8.4; amd64; ; ) References: <20130209073241.GN21730@jd.benders.se> <20130209230939.GQ21730@jd.benders.se> <20130211222105.GC838@jd.benders.se> In-Reply-To: <20130211222105.GC838@jd.benders.se> X-Face: ?p&W)c(+80hU; '{.$5K+zq{oC6y| /D'an*6mw>j'f:eBsex\Gi, Cc: Joel Dahl X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 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: Tue, 12 Feb 2013 07:50:09 -0000 On Monday 11 February 2013 23:21:05 Joel Dahl wrote: > On 10-02-2013 0:09, Joel Dahl wrote: > > On 09-02-2013 20:28, Alexander Motin wrote: > > > How long ago that HEAD was built? Could you get full dmesg? I don't > > > think that "PREVENT ALLOW MEDIUM REMOVAL" should cause device drop. "No > > > sense data present" also doesn't look right. > > > > As I mentioned earlier, I've tried several HEAD snapshots. > > Just a quick update on this: I've built quite a few releases now and > managed to track down the problem to somewhere between r235789 and > r237855. It'll probably take me another day or two before I know which > commit actually broke it. Hi, I don't see any relevant USB+UMASS patches for your issue in this interval, but many patches in the SCSI/CAM area. --HPS