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>,
	sakoman@gmail.com
Subject: Re: NULL pointer dereference when using ALSA SOC
Date: Thu, 25 Sep 2008 14:05:31 +0300	[thread overview]
Message-ID: <20080925140531.64fd14c9.jarkko.nikula@nokia.com> (raw)
In-Reply-To: <20080923115053.e404f43e.jarkko.nikula@nokia.com>

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.


Jarkko

  reply	other threads:[~2008-09-25 11:06 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
2008-09-25 11:05   ` Jarkko Nikula [this message]
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=20080925140531.64fd14c9.jarkko.nikula@nokia.com \
    --to=jarkko.nikula@nokia.com \
    --cc=getarunks@gmail.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=sakoman@gmail.com \
    /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