All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hector Martin <marcan@marcan.st>
To: Takashi Iwai <tiwai@suse.de>
Cc: Linux-ALSA <alsa-devel@alsa-project.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: [tiwai/for-next] hard lockups with pipewire and snd-usb-audio
Date: Fri, 2 Jul 2021 19:34:06 +0900	[thread overview]
Message-ID: <4e71531f-4535-fd46-040e-506a3c256bbd@marcan.st> (raw)

Hi Takashi,

I've been testing builds from your for-next branch to get the recent 
firewire fixes. All that works fine, but instead I've been getting hard 
lockups with pipewire and snd-usb-audio. I'm currently on 9a7b7ec3c6.

Backtrace:

  do_raw_spin_lock+0x8e/0x90
  _raw_spin_lock_irqsave+0x3e/0x50
  ? snd_pcm_period_elapsed+0x10/0x30 [snd_pcm]
  snd_pcm_period_elapsed+0x10/0x30 [snd_pcm]
  snd_usb_endpoint_start+0xd8/0x270 [snd_usb_audio]
  start_endpoints+0x50/0x70 [snd_usb_audio]
  snd_usb_substream_playback_trigger+0x58/0x100 [snd_usb_audio]
  snd_pcm_action+0x74/0xb0 [snd_pcm]
  snd_pcm_action_lock_irq+0x36/0x80 [snd_pcm]
  snd_pcm_ioctl+0x1e/0x30 [snd_pcm]
  __x64_sys_ioctl+0x7d/0xb0
  do_syscall_64+0x45/0x80
  entry_SYSCALL_64_after_hwframe+0x44/0xae

To me it looks like it's recursively trying to lock the stream spinlock.

I'm not sure what version this is a regression from; I've only triggered 
it with pipewire so far, which I wasn't previously using. It's easy to 
reproduce. Usually, pulling up pavucontrol on pipewire with the USB 
audio device on an active profile will do it.

Just thought you might want to know. Let me know if you need any more info.

-- 
Hector Martin (marcan@marcan.st)
Public Key: https://mrcn.st/pub

                 reply	other threads:[~2021-07-02 10:34 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4e71531f-4535-fd46-040e-506a3c256bbd@marcan.st \
    --to=marcan@marcan.st \
    --cc=alsa-devel@alsa-project.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tiwai@suse.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.