From: Mark Brown <broonie@kernel.org>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: ALSA Development Mailing List <alsa-devel@alsa-project.org>,
Alex Natalsson <harmoniesworlds@gmail.com>,
Kai Vehmanen <kai.vehmanen@linux.intel.com>,
Takashi Iwai <tiwai@suse.de>,
Ranjani Sridharan <ranjani.sridharan@linux.intel.com>,
linux-sound@vger.kernel.org,
Bard Liao <yung-chuan.liao@linux.intel.com>
Subject: Re: Sound not working after commit bbf7d3b1c4f40eb02dd1dffb500ba00b0bff0303 on Amlogic A311D device
Date: Mon, 27 Jun 2022 17:52:13 +0100 [thread overview]
Message-ID: <YrngPdWIqxlRm4mf@sirena.org.uk> (raw)
In-Reply-To: <15259e38-eccf-d294-a330-a48b5bbbdedf@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 514 bytes --]
On Mon, Jun 27, 2022 at 10:12:37AM -0500, Pierre-Louis Bossart wrote:
> On 6/26/22 04:29, Alex Natalsson wrote:
> > Hello friends.
> > The log after alsamixer launch:
> > [ 103.786358] Internal error: Oops: 96000004 [#1] SMP
> > [ 103.786509] Modules linked in: snd_seq_dummy snd_hrtimer snd_seq
> Any chance you could try with an updated kernel? It's not clear to me if
> this is a real issue or just a warning that's been fixed since by commit.
That's an oops, and the userspace applications are hanging...
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-06-27 16:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CADs9LoPZH_D+eJ9qjTxSLE5jGyhKsjMN7g2NighZ16biVxsyKw@mail.gmail.com>
2022-06-27 15:12 ` Sound not working after commit bbf7d3b1c4f40eb02dd1dffb500ba00b0bff0303 on Amlogic A311D device Pierre-Louis Bossart
2022-06-27 16:52 ` Mark Brown [this message]
[not found] ` <CADs9LoN-L0X1Dr1sP2K7xrcWm7dpHW6MhF47c2eBB0moLNnPRQ@mail.gmail.com>
2022-06-28 22:47 ` Pierre-Louis Bossart
[not found] ` <CADs9LoOZjK=cUuNSEELtgxYoA+yHVFKM_Y9YLcY74smqx8XsjQ@mail.gmail.com>
[not found] ` <c554b69c-0c73-158d-85d8-95a0375babeb@linux.intel.com>
2022-07-01 15:47 ` Alex Natalsson
2022-07-01 16:42 ` Pierre-Louis Bossart
2022-07-01 22:17 ` Alex Natalsson
2022-07-09 11:19 ` Alex Natalsson
2022-07-11 14:33 ` Pierre-Louis Bossart
2022-07-12 8:00 ` Péter Ujfalusi
2022-07-12 9:29 ` Takashi Iwai
2022-07-12 13:05 ` Alex Natalsson
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=YrngPdWIqxlRm4mf@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=harmoniesworlds@gmail.com \
--cc=kai.vehmanen@linux.intel.com \
--cc=linux-sound@vger.kernel.org \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=ranjani.sridharan@linux.intel.com \
--cc=tiwai@suse.de \
--cc=yung-chuan.liao@linux.intel.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