public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Jarkko Nikula <jarkko.nikula@nokia.com>
To: ext Arun KS <getarunks@gmail.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: NULL pointer dereference when using ALSA SOC
Date: Tue, 23 Sep 2008 11:50:53 +0300	[thread overview]
Message-ID: <20080923115053.e404f43e.jarkko.nikula@nokia.com> (raw)
In-Reply-To: <dfeb90390809222326s44162f94sf42f96fdfc0a0690@mail.gmail.com>

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'm using up-to-date l-o with following patches:

Author: Jarkko Nikula <jarkko.nikula@nokia.com>
Date:   Fri Sep 19 16:36:38 2008 +0300

    ARM: OMAP: Fixes to omap_mcbsp_request function

Author: Jarkko Nikula <jarkko.nikula@nokia.com>
Date:   Tue Sep 16 15:56:53 2008 +0300

    ARM: OMAP: Add RX/TX interrupts for 2430 and 34xx McBSP ports 3-5

Author: ext Felipe Contreras <felipe.contreras@gmail.com>
Date:   Tue Sep 16 23:51:35 2008 +0300

    alsa: add Beagleboard SoC configuration.


I don't know is this configuration difference necessarily related to sound since I tried to modify N810 sound configuration similar to Overo defconfig but wasn't able to reproduce. Have to continue hunting.


Jarkko

  reply	other threads:[~2008-09-23  8:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-23  6:26 NULL pointer dereference when using ALSA SOC Arun KS
2008-09-23  8:50 ` Jarkko Nikula [this message]
2008-09-25 11:05   ` Jarkko Nikula
2008-09-25 13:27     ` Philip Balister
2008-09-25 13:32       ` Koen Kooi
2008-09-25 13:38         ` Arun KS
2008-09-25 17:22           ` David Brownell
2008-09-25 17:34             ` Steve Sakoman
2008-09-25 21:46               ` Koen Kooi
2008-09-25 19:20 ` Siarhei Siamashka
2008-09-26  7:40   ` Tony Lindgren
2008-09-26  7:56   ` Jarkko Nikula

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080923115053.e404f43e.jarkko.nikula@nokia.com \
    --to=jarkko.nikula@nokia.com \
    --cc=getarunks@gmail.com \
    --cc=linux-omap@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox