From owner-freebsd-sparc64@FreeBSD.ORG Fri Aug 21 19:37:42 2009 Return-Path: Delivered-To: freebsd-sparc64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 95CAD106568C for ; Fri, 21 Aug 2009 19:37:42 +0000 (UTC) (envelope-from marius@alchemy.franken.de) Received: from alchemy.franken.de (alchemy.franken.de [194.94.249.214]) by mx1.freebsd.org (Postfix) with ESMTP id 2261F8FC0A for ; Fri, 21 Aug 2009 19:37:41 +0000 (UTC) Received: from alchemy.franken.de (localhost [127.0.0.1]) by alchemy.franken.de (8.14.3/8.14.3/ALCHEMY.FRANKEN.DE) with ESMTP id n7LJbfYt066861; Fri, 21 Aug 2009 21:37:41 +0200 (CEST) (envelope-from marius@alchemy.franken.de) Received: (from marius@localhost) by alchemy.franken.de (8.14.3/8.14.3/Submit) id n7LJbeuf066860; Fri, 21 Aug 2009 21:37:40 +0200 (CEST) (envelope-from marius) Date: Fri, 21 Aug 2009 21:37:40 +0200 From: Marius Strobl To: Christian Ramseyer , ardelean@ww.uni-erlangen.de Message-ID: <20090821193740.GA66639@alchemy.franken.de> References: <4A7C6B50.3070503@networkz.ch> <20090817205340.GA75477@alchemy.franken.de> <20090817215612.GB75477@alchemy.franken.de> <20090818192748.GA6585@alchemy.franken.de> <20090819161410.GA19351@alchemy.franken.de> <4A8DC0DF.4040701@networkz.ch> <4A8EDE72.6040703@networkz.ch> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4A8EDE72.6040703@networkz.ch> User-Agent: Mutt/1.4.2.3i Cc: freebsd-sparc64@freebsd.org Subject: Re: Audio on Sunblade 100 X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Aug 2009 19:37:42 -0000 On Fri, Aug 21, 2009 at 07:50:42PM +0200, Christian Ramseyer wrote: > Gheorghe Ardelean wrote: > > > > On Thu, 20 Aug 2009, Christian Ramseyer wrote: > > > > [...] > >> As it worked for Gheorghe, chances are that I'm doing something > >> wrong/different: > > > > Now I have tested also mpg321 and it has a not that good sound quality. > > A lot of noise is coming out but the sound is there all the time. The > > noise is coming always on the bass (maybe drums?) parts. > > > > Christian, could please also test mpg123 and let us know if you get > > different results? > > > > I've got maybe 10 seconds of sound, then silence and these messages: > > [audio.c:596] error: Error in writing audio (Invalid argument?)! > [mpg123.c:577] error: Deep trouble! Cannot flush to my output anymore! > > There was the "usual" message: > pcm0:virtual:dsp0.vp0: play interrupt timeout, channel dead > > Also, I have the impressions that the rare events where I get some > seconds of sound only occur when the box was powered down for some time > before, subsequent attempts (also after reboot without power cycle) > never seem to produce sound. This symptom is similar to when using non-working DMA tag parameters, except that I get no sound at all then but possibly a non-correctable DMA error panic. This also might occur due to other kinds of bugs in the driver, but without deeper insight in the sound subsystem and no programming manual for the M5451 this is kind of unfun... Given that the driver works for Gheorghe with the same hardware model I suspect an initialization issue based on different firmware revsions. Could both of you please run `pciconf -lv` and report the two lines starting with isab0 and pcm0 (just these two lines, not the whole output from that command). Then get a complete dump of the PCI configuration header by running `pciconf -rb 0:255` on the selectors contained in the isab0 and pcm0 strings, for example: `pciconf -rb isab0@pci0:1:7:0 0:255` Please also report the pcm0 parts of a verbose boot (stop the boot count-down by pressing space and issue a `set boot_verbose`, followed by `boot`, then get the pcm0 lines from for example the dmesg-output). Yongari, given that you've worked on sound drivers and snd_t4dwave(4) in particular before, can you spot something obviously wrong with the DMA programming this driver does, for example in the CSO and ESO parts? > > > So this is some kind of strange to me. I have tested also xmms with > > the result of only noise comming out. > > I tried xmms with similar results: one short burst of noise/static, then > silence. Plus some complaining about ioctls: > > ** WARNING **: SNDCTL_DSP_SETFMT ioctl failed: Invalid argument > ** WARNING **: SNDCTL_DSP_SPEED ioctl failed: Invalid argument > >From the symptoms Gheorghe reported for mpg321 I suspect it has some LP64 and/or endian bugs, while mpg123 hasn't. IIRC Yongari once also had a fix for such a bug in XMMS, which isn't necessarily the cause for the above problem though. Marius