From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: "Илья Кузнецов" <zloy.technic@gmail.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: [BUG] ALSA FireWire: poll timeout causes JACK to stop (6.10 – 6.17-rc2)
Date: Wed, 3 Sep 2025 08:45:40 +0900 [thread overview]
Message-ID: <20250902234540.GA65685@workstation.local> (raw)
In-Reply-To: <CAAnsHS64Pt9N2Ct3D6X=f6JytCiii9ntQ=MYqvweC=QaFpXPNw@mail.gmail.com>
Hi,
I'm sorry for your inconvenience.
If you have ever used your device with Pipewire, I would like to see
your experiences how it works, since both servers uses the different
ways to handle ALSA PCM device in respect to no-period-wakeup mode..
On Tue, Sep 02, 2025 at 03:11:52PM +0500, Илья Кузнецов wrote:
> ________________________________
>
> Hello ALSA developers,
>
> I would like to report a reproducible issue with snd-fireface on Linux
> kernels 6.10 through 6.17-rc2.
>
> ________________________________
>
> System Information
>
> Kernel versions tested: 6.10 → 6.17-rc2
>
> Audio interface: RME Fireface 800
>
> Driver in use: snd-fireface
>
> Audio server: JACK (tested with jackd and QJackCtl)
>
> Distribution: Debian 12
>
> Kernel config: ALSA FireWire drivers enabled, no FFADO in use
>
> Chip 1394: Texas Instrumets
>
> ________________________________
>
> Steps to Reproduce
>
> Boot kernel 6.10 … 6.17-rc2 with snd-fireface loaded.
>
> Start JACK with ALSA backend, for example:
>
> jackd -d alsa -d hw:Fireface -p 64 -n 3
>
> Use the system normally — during playback, recording, or even when
> idle. The issue may occur at any time without apparent external cause.
>
> Actual Behavior
>
> After some idle time, ALSA stops responding and JACK prints:
>
> ERROR: ALSA: poll time out, polled for ... usecs
> ERROR: JackAudioDriver::ProcessAsync: read error, stopping...
>
> JACK immediately terminates. The Fireface 800 does not recover until
> JACK is restarted.
>
> ________________________________
>
> Expected Behavior
>
> The ALSA FireWire driver should maintain the stream and allow JACK to
> continue running without manual restart, even when idle.
>
> ________________________________
>
> Notes
>
> With FFADO backend (jackd -d firewire), the same hardware works
> reliably and does not exhibit this issue.
>
> This suggests that the problem lies in the ALSA FireWire streaming
> engine rather than the hardware itself.
>
> The problem has been reproducible across all tested kernels (vanila,
> rt, liquorix) from 6.10 through 6.17-rc2.
>
> ________________________________
>
> Request
>
> Could you please confirm if this issue is known?
> Is there any ongoing work on the ALSA FireWire streaming engine
> (snd-fireface) to address these poll timeout conditions?
>
> I can provide additional logs (dmesg, journalctl) or test patches if needed.
>
> Thank you,
>
> Ilya Kuznetsov.
Regards
Takashi Sakamoto
next prev parent reply other threads:[~2025-09-02 23:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-02 10:11 [BUG] ALSA FireWire: poll timeout causes JACK to stop (6.10 – 6.17-rc2) Илья Кузнецов
2025-09-02 23:45 ` Takashi Sakamoto [this message]
2025-09-03 6:14 ` Илья Кузнецов
-- strict thread matches above, loose matches on Subject: below --
2025-08-30 7:01 Илья Кузнецов
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=20250902234540.GA65685@workstation.local \
--to=o-takashi@sakamocchi.jp \
--cc=alsa-devel@alsa-project.org \
--cc=zloy.technic@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 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.