From owner-freebsd-usb@FreeBSD.ORG Sat May 9 19:25:32 2009 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DCD48106566C for ; Sat, 9 May 2009 19:25:32 +0000 (UTC) (envelope-from tinguely@casselton.net) Received: from casselton.net (casselton.net [63.165.140.2]) by mx1.freebsd.org (Postfix) with ESMTP id 8BE778FC17 for ; Sat, 9 May 2009 19:25:32 +0000 (UTC) (envelope-from tinguely@casselton.net) Received: from casselton.net (localhost [127.0.0.1]) by casselton.net (8.14.3/8.14.3) with ESMTP id n49J6avV025538; Sat, 9 May 2009 14:06:36 -0500 (CDT) (envelope-from tinguely@casselton.net) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=casselton.net; s=ccnMail; t=1241895996; bh=yn8LnG7ae/8rZHiFmxKQwoSKgm6h0bWaehYK1PLSvTk=; h=Date:From:Message-Id:To:Subject:Cc:In-Reply-To; b=AnowDOyc8jMDhH0+kPxOYRPjA1lAoztaUVhaltneSySW4nnnncNLaK4xURjMby4B1 SXcw/FsV4IPyhJXzzutuwOZwf7AShMYNduIiEC2ICPJuaaTYp8M5Fx6GAzLDe/nx/7 S45qYhrOvIqIlJYWmTWbesB1ZNER0lYsK8KJ444w= Received: (from tinguely@localhost) by casselton.net (8.14.3/8.14.2/Submit) id n49J6ahs025537; Sat, 9 May 2009 14:06:36 -0500 (CDT) (envelope-from tinguely) Date: Sat, 9 May 2009 14:06:36 -0500 (CDT) From: Mark Tinguely Message-Id: <200905091906.n49J6ahs025537@casselton.net> To: hselasky@c2i.net, yohanes@gmail.com In-Reply-To: <260bb65e0905091102y272de752r750a3a79940486f@mail.gmail.com> X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.1.10 (casselton.net [127.0.0.1]); Sat, 09 May 2009 14:06:36 -0500 (CDT) Cc: freebsd-arm@freebsd.org, freebsd-usb@freebsd.org Subject: Re: EHCI Problem on FreeBSD arm port X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 May 2009 19:25:33 -0000 > > On Sat, May 9, 2009 at 3:09 PM, Hans Petter Selasky wrote: > > > Hi, > > > > If the strings are corrupt I would guess at a busdma issue. > > thank you, adding a "flush all" instruction makes the USB controller > works properly. > > Now i should check the implementation of the FA526 invalidate/flush > instruction, because I shouldn't need the extra flush instruction if > bus_dmamap_sync works properly, right?. > > > Are you running stock 8-current ? > > yes Sounds like the multiple kernel mapping problem in ARM. It was mentioned when the new USB stack was comitted. Muliple kernel mappings can also occur in other situations. There is a patch that has been around for a month and is about to be committed. I just put three counters in the patch to determine if PG_UNMANAGED pages could also be shared. --Mark Tinguely