mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jernej Škrabec" <jernej.skrabec@siol.net>
To: kuninori.morimoto.gx@renesas.com
Cc: broonie@kernel.org, maxime.ripard@free-electrons.com,
	wens@csie.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org
Subject: [BUG] Kernel crash on Allwinner H3 due to sound core changes
Date: Wed, 28 Feb 2018 22:02:09 +0100	[thread overview]
Message-ID: <2424862.oPtAVTfrB9@jernej-laptop> (raw)

Hi all,

with todays linux-next (next-20180228), kernel on Allwinner H3 SoC crashes 
with dmesg like that: https://pastebin.com/raw/0D5JeaJ8

I bisected the kernel and first offending commit is:
be7ee5f32a9a ("ASoC: soc-generic-dmaengine-pcm: replace platform to 
component")

I know that crash message is completely unrelated to sound subsystem, but it 
turns out that if I disable CONFIG_SND_SUN4I_CODEC kernel works ok, but this 
way I lose analog audio output.

Any suggestions what can be the issue?

Best regards,
Jernej

             reply	other threads:[~2018-02-28 21:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-28 21:02 Jernej Škrabec [this message]
2018-03-01  1:49 ` Kuninori Morimoto
2018-03-01 22:23 ` Jernej Škrabec
2018-03-02 12:40   ` Mark Brown
2018-03-05 21:30     ` Jernej Škrabec
2018-03-07 21:11       ` Jernej Škrabec
2018-03-08  1:21         ` Kuninori Morimoto
2018-03-08  6:03           ` [alsa-devel] " Jernej Škrabec
2018-03-08 11:13           ` Mark Brown
2018-03-08 23:49             ` Kuninori Morimoto
2018-03-09  6:33               ` [alsa-devel] " Jernej Škrabec
2018-03-09 11:14               ` Mark Brown
2018-03-19  8:08               ` Applied "soc-core: don't call kfree() for component" to the asoc tree 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=2424862.oPtAVTfrB9@jernej-laptop \
    --to=jernej.skrabec@siol.net \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=kuninori.morimoto.gx@renesas.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maxime.ripard@free-electrons.com \
    --cc=wens@csie.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
all inboxes | Powered by JetHome®