[gst-devel] Problems when using osssink in ARM

[Sjoerd Simons]

On Fri, Sep 21, 2007 at 11:35:06AM +0200, Ali Sabil wrote:
> Hi,
> 
> If you take a closer look at this output, you will see some alignment
> traps being triggered, I am not sure where the problem comes from, but
> it is probably a bug in either the oss userspace libraries or gst oss
> element.

Note that on an ARM, hitting the alignment trap can either means that the kernel
fixes it for you or that it does something ARM specific.

To check what it does see the ``User Faults'' field in /proc/cpu/alignment, if
this contains ``fixup'' the traps are harmless (apart from causing a performance
hit), otherwise the result is probably not what ossink expected.

> > Feb 6 09:21:33 freescale user.warn kernel: Alignment trap:
> > gst-launch-0.10 (877) disable codec..
> > PC=0x402f7588 Instr=0xe584c008 Address=0x15a104a7 FSR 0x801
> > Feb 6 09:21:33 freescale user.warn kernel: disable codec..
> > Setting pipeline to PAUSED ...
> > 0:00:11.602708000 880 0x150c0 DEBUG audiosi
> > MXC Enable Codec(write)
> > nk gstaudiosink.c:562:gst_audio_sink_create_ringbuffer: creating
> > ringbuffer
> > 0:00:11.605841000 880 0x150c0 DEBUG audiosink
> > gstaudiosink.c:564:gst_audio_sink_create_ringbuffer: created
> > ringbuffer @0x841f8
> > Feb 6 09:21:45 freescale user.warn kernel: 
> > Feb 6 09:21:45 freescale user.warn kernel: MXC Enable Codec(write) 

  Sjoerd
-- 
In order to dial out, it is necessary to broaden one's dimension.