Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: kuninori.morimoto.gx@renesas.com
Cc: Linux-ALSA <alsa-devel@alsa-project.org>,
	Mark Brown <broonie@opensource.wolfsonmicro.com>,
	Kuninori Morimoto <morimoto.kuninori@gmail.com>,
	Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: ALSA become "Segmentation fault" on current linus tree
Date: Tue, 05 Jul 2011 07:41:10 +0200	[thread overview]
Message-ID: <s5hvcvhffnt.wl%tiwai@suse.de> (raw)
In-Reply-To: <87k4bxfjue.wl%kuninori.morimoto.gx@renesas.com>

At Tue, 05 Jul 2011 13:10:49 +0900,
kuninori.morimoto.gx@renesas.com wrote:
> 
> 
> Dear Liam, Mark
> 
> Currect linus tree become "Segmentation fault" when I use aplay.
> 
> # aplay xxx.wav                                          
> Segmentation fault
> 
> I used "git bisect" and 1st bad commit was below.
> I'm using sh7372 mackerel board.
> 
> commit 22de71ba03311cdc1063757c50a1488cb90a1fca
> Author: Liam Girdwood <lrg@ti.com>
> Date:   Thu May 12 16:14:04 2011 +0100
> 
> ASoC: core - allow ASoC more flexible machine name
> 
> Allow ASoC machine drivers to register a driver name
> and a longname. This allows user space to determine
> the flavour of machine driver.
> 
> Signed-off-by: Liam Girdwood <lrg@ti.com>
> Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>

Hm, this should have been fixed by the later commit:
  commit 2b39535b9e54888649923beaab443af212b6c0fd
  Author: Jarkko Nikula <jhnikula@gmail.com>
  Date:   Fri May 20 15:47:40 2011 +0300

    ASoC: core: Don't set "(null)" as a driver name

Could you check whether the segfault occurs at this point?
It's possible that another bug was introduced after it, of course.


thanks,

Takashi

  reply	other threads:[~2011-07-05  5:41 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-05  4:10 ALSA become "Segmentation fault" on current linus tree kuninori.morimoto.gx
2011-07-05  5:41 ` Takashi Iwai [this message]
2011-07-05  5:57   ` kuninori.morimoto.gx
2011-07-05  6:06     ` Takashi Iwai
2011-07-05  6:08       ` kuninori.morimoto.gx
2011-07-05  6:07     ` kuninori.morimoto.gx
2011-07-05  6:19       ` Takashi Iwai
2011-07-05  6:29         ` kuninori.morimoto.gx
2011-07-05  6:33           ` Takashi Iwai
2011-07-05  6:52             ` kuninori.morimoto.gx
2011-07-05  7:12               ` kuninori.morimoto.gx
2011-07-05  7:15                 ` [PATCH 1/3] ASoC: sh: fsi-ak4642: fixup snd_soc_card name Kuninori Morimoto
2011-07-09 10:06                   ` Mark Brown
2011-07-05  7:16                 ` [PATCH 2/3] ASoC: sh: fsi-da7210: " Kuninori Morimoto
2011-07-05  7:16                 ` [PATCH 3/3] ASoC: sh: fsi-hdmi: " Kuninori Morimoto
2011-07-05  7:33                 ` ALSA become "Segmentation fault" on current linus tree Takashi Iwai
2011-07-05  8:11                   ` kuninori.morimoto.gx
2011-07-05 10:22                   ` Liam Girdwood
2011-07-05 12:41                     ` Takashi Iwai
2011-07-05 17:14                       ` Mark Brown

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=s5hvcvhffnt.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=kuninori.morimoto.gx@renesas.com \
    --cc=lrg@slimlogic.co.uk \
    --cc=morimoto.kuninori@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