Date: Mon, 8 Feb 2010 19:24:54 +0100 From: Hans Petter Selasky <hselasky@c2i.net> To: pyunyh@gmail.com Cc: freebsd-sparc64@freebsd.org, linimon@freebsd.org, Marius Strobl <marius@alchemy.franken.de> Subject: Re: sparc64/141918: [ehci] ehci_interrupt: unrecoverable error, controller halted (sparc64) Message-ID: <201002081924.54241.hselasky@c2i.net> In-Reply-To: <20100208180549.GB1358@michelle.cdnetworks.com> References: <201002080910.o189A3fp080625@freefall.freebsd.org> <201002081520.26468.hselasky@c2i.net> <20100208180549.GB1358@michelle.cdnetworks.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Monday 08 February 2010 19:05:49 Pyun YongHyeon wrote: > On Mon, Feb 08, 2010 at 03:20:26PM +0100, Hans Petter Selasky wrote: > > On Monday 08 February 2010 10:10:03 Marius Strobl wrote: > > > The following reply was made to PR sparc64/141918; it has been noted by > > > GNATS. > > > > > > From: Marius Strobl <marius@alchemy.franken.de> > > > To: linimon@freebsd.org, bug-followup@freebsd.org, bel@orel.ru > > > Cc: > > > Subject: Re: sparc64/141918: [ehci] ehci_interrupt: unrecoverable > > > error, controller halted (sparc64) Date: Mon, 8 Feb 2010 10:07:42 +0100 > > > > > > On Mon, Feb 08, 2010 at 07:05:29AM +0000, linimon@freebsd.org wrote: > > > > hps claims that this may be sparc64-specific. > > > > > > As outlined here it's unlikely that this is a problem of the sparc64 > > > bus_dmamap_sync(9): > > > > Hi, > > > > > > > > http://lists.freebsd.org/pipermail/freebsd-sparc64/2009-December/006866 > > >.ht ml There are however known problems with usb(4) in this regard, see > > > for > > > > The issue mentioned above was patched in 9-current some months back. Have > > you tried 9-current? > > > > > http://svn.freebsd.org/viewvc/base?view=revision&revision=203080 > > > > On point about busdma is that you should be able to pass any kernel > > virtual address to be loaded into DMA. If the kernel virtual address is > > not correctly aligned, a bounce page must be used, so that surrounding > > memory is not disturbed. And that is not an USB problem. > > Would you elaborate on this? I don't think sparc64 needs bounce > buffer as it uses DVMA. I have no idea how bounce buffer can > address the alignment mismatches unless bounce buffer is created on > certain alignment boundary. If you put the data in a bounce buffer, you can clear data before and after the actual data without caring too much about it. --HPS
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201002081924.54241.hselasky>