Re: NULL pointer dereference when using ALSA SOC

Philip Balister
2008-09-25T13:27:08Z

[-- Attachment #1: Type: text/plain, Size: 1646 bytes --]

Jarkko Nikula wrote:
> On Tue, 23 Sep 2008 11:50:53 +0300
> "ext Jarkko Nikula" <jarkko.nikula@nokia.com> wrote:
>
>> On Tue, 23 Sep 2008 11:56:00 +0530
>> "ext Arun KS" <getarunks@gmail.com> wrote:
>>
>>> Hi all,
>>>
>>> I am writing an ASOC driver for tlvaic23 on osk5912 platform.
>>> When do an aplay, I m getting a NULL pointer dereference. I added
>>> some debug prints in the soc/core/pcm_native.c, also in codec and
>>> platform drivers. The null pointer is comming in IOCTL
>>> SNDRV_PCM_IOCTL_SYNC_PTR. Log is pasted below.
>>>
>> It's good that you can reproduce this on OSK as well.
>>
>> I think some configuration difference is revealing this bug out. For
>> instance I can trigger this on Beagle with overo_defconfig + manually
>> adding support for Beagle (CONFIG_MACH_OMAP3_BEAGLE=y) and ASoC
>> Beagle (CONFIG_SND_OMAP_SOC_OMAP3_BEAGLE=y).
>>
>> But I cannot reproduce this with Beagle defconfig + manually adding
>> support for Overo (CONFIG_MACH_OVERO=y) and ASoC Beagle
>> (CONFIG_SND_OMAP_SOC_OMAP3_BEAGLE=y).
>>
> I narrowed this into CONFIG_SLUB. When it's set, I can reproduce the
> bug both with N810 and Beagle but not when using CONFIG_SLAB.
>
> Can you try will the problem disappear on your OSK and Overo if you
> select slab allocator instead? You find selection under "General
> setup" menu.

I've also verified this works on a Beagle with Angstrom.

Thanks for tracking this down!

Philip

>
>
> Jarkko
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3303 bytes --]