Re: firewire-ohci fails to initialize Texas Instruments XIO2213A/B/XIO2221 based controller on realtime kernels [5.4.91-rt50, 5.10.8-rt24]

From: David Runge <dave@sleepmap.de>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: "Ahmed S. Darwish" <a.darwish@linutronix.de>,
	linux-rt-users@vger.kernel.org,
	linux1394-devel@lists.sourceforge.net,
	Stefan Richter <stefanr@s5r6.in-berlin.de>
Subject: Re: firewire-ohci fails to initialize Texas Instruments XIO2213A/B/XIO2221 based controller on realtime kernels [5.4.91-rt50, 5.10.8-rt24]
Date: Wed, 10 Mar 2021 19:15:20 +0100	[thread overview]
Message-ID: <YEkMvjJt/Vu9Jbgu@hmbx> (raw)
In-Reply-To: <20210308141210.yoa37dsc26p4jsim@linutronix.de>

[-- Attachment #1: Type: text/plain, Size: 2985 bytes --]

On 2021-03-08 15:12:10 (+0100), Sebastian Andrzej Siewior wrote:
> On 2021-02-18 10:27:51 [+0100], To David Runge wrote:
> > On 2021-02-18 09:38:49 [+0100], To David Runge wrote:
> > > On 2021-02-14 20:16:02 [+0100], David Runge wrote:
> > > > The current config can be found on the AUR [1].
> > > 
> > > So this did make a difference. 
> > 
> > made _no_ difference. Sorry for the confusion.
> 
> David, did you had a chance to test the patch?

Hey Sebastian,

sorry for the long delay! I got busy with other packaging/
infrastructure things and nearly forgot about this one.

I have now tested with 5.11.2-rt9 with and without your proposed patch.

Without the patch [1], the behavior is as before, only the parent device
node of the controller (/dev/fw0) is created, but the attached audio
interface is not recognized.

With the patch applied [2], things get a little more exciting, as now
both the parent and the child node are created (so both /dev/fw0 and
/dev/fw1 show up).

However, starting jackd on the interface leads to a zombification of the
jackd process and the process never exits:

```
Starting JACK server using fw-fireface800-48000.conf profile...
no message buffer overruns
no message buffer overruns
no message buffer overruns
jackdmp 1.9.17
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2016 Grame.
Copyright 2016-2021 Filipe Coelho.
jackdmp comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
JACK server starting in realtime mode with priority 80
self-connect-mode is "Don't restrict self connect requests"
1615399142007837:  (ffado.cpp)[  92] ffado_streaming_init: libffado
2.4.4 built Nov 12 2020 17:24:24
jack@fw-fireface800-48000.service: start operation timed out.
Terminating.
jack@fw-fireface800-48000.service: State 'stop-sigterm' timed out.
Killing.
jack@fw-fireface800-48000.service: Killing process 1813 (jackd) with
signal SIGKILL.
jack@fw-fireface800-48000.service: Killing process 2021 (FW_ARMSTD) with
signal SIGKILL.
jack@fw-fireface800-48000.service: Processes still around after SIGKILL.
Ignoring.
jack@fw-fireface800-48000.service: State 'final-sigterm' timed out.
Killing.
jack@fw-fireface800-48000.service: Killing process 1813 (jackd) with
signal SIGKILL.
jack@fw-fireface800-48000.service: Processes still around after final
SIGKILL. Entering failed mode.
jack@fw-fireface800-48000.service: Failed with result 'timeout'.
jack@fw-fireface800-48000.service: Unit process 1813 (jackd) remains
running after unit stopped.
Failed to start JACK server using fw-fireface800-48000.conf profile.
```

If I can provide more info, please let me know!

Best,
David

[1] https://pkgbuild.com/~dvzrv/bugs/2021/03/linux-5.11.2-rt9-kernel.log
[2] https://pkgbuild.com/~dvzrv/bugs/2021/03/linux-5.11.2-rt9-kernel_firewire_ohci_patch.log

-- 
https://sleepmap.de

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]