From owner-freebsd-current@FreeBSD.ORG Sat Jul 19 23:06:18 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D0B1B37B401; Sat, 19 Jul 2003 23:06:18 -0700 (PDT) Received: from sccrmhc12.comcast.net (sccrmhc12.comcast.net [204.127.202.56]) by mx1.FreeBSD.org (Postfix) with ESMTP id 03F3543FBF; Sat, 19 Jul 2003 23:06:18 -0700 (PDT) (envelope-from bleez@comcast.net) Received: from gravy.homeunix.net ([68.81.196.221]) by comcast.net (sccrmhc12) with ESMTP id <200307200606170120059g6be>; Sun, 20 Jul 2003 06:06:17 +0000 Received: from gravy.homeunix.net (gravy.homeunix.net [192.168.1.2]) by gravy.homeunix.net (8.12.9/8.12.9) with ESMTP id h6K66GcK000548; Sun, 20 Jul 2003 02:06:16 -0400 (EDT) (envelope-from bleez@comcast.net) Date: Sun, 20 Jul 2003 02:06:16 -0400 (EDT) From: Bryan Liesner To: Juli Mallett In-Reply-To: <20030719194215.A6668@FreeBSD.org> Message-ID: <20030720015113.A536@gravy.homeunix.net> References: <20030719194215.A6668@FreeBSD.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@freebsd.org Subject: Re: USB crappiness? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 20 Jul 2003 06:06:19 -0000 On Sat, 19 Jul 2003, Juli Mallett wrote: > Hi, > > I tried to upgrade my workstation to current recently, and I have to > use a lot of USB, and while using some USB mass storage device, with > a UFS filesystem on it, and doing a large operation to it (tar c|tar x) > everything deadlocked on ufs, the USB stack blew up, and upon causing > an interrupt to it, it panicked, and panic pagefaulted. > > Anyone else seeing these sorts of cohesive fallovers? > > Thanx, > juli. > Yes, I can confirm that. I do an nightly dump to a file on my USB hard disk (ehci). I woke up to find a screen full of read errors, and at first I thought the disk went belly up. I reverted back and it was working fine. I/O speed has _seriously_ degraded as well. Prior to the bus dma patches, I was getting a little better than 8 MB/s writes to the disk, afterwards, less than 2 MB/s. The "performance hit" discussed prior to the commit is a bit of an understatement. -Bryan