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

Hi all,

As a follow-up to the previous conversation, I have now also tried
5.14.1-rt19 (packaged as 5.14.1.19.realtime1) in the hopes that ALSA
driver improvements for my Fireface800 will allow me to use pipewire
going forward.

Unfortunately, firewire-ohci and/or firewire-core are still freezing
upon trying to make use of the connected device which is connected with
the card using the chip in question (see title).

Upon first boot the /dev/fw0 and /dev/fw1 nodes did not show up
initially [1] (log without using -1 debug parameter), which is why I
switched the device off and on again.
Afterwards the device nodes were created, so I attempted to use aplay -l
to check whether the device was detected. The command hung forever (also
starting jackd) and I had to reboot eventually. Using alsamixer I was
able to select the Fireface800 device from the list of devices though.

Upon 2nd boot I used the -1 debug parameter for firewire-ohci [2].
The device nodes were created automatically, but neither aplay -l nor
alsamixer showed the audio interface. The attempt to switch the device
off and on again and afterwards to remove the firewire-ohci module lead
to another freeze and a successive reboot.

If I can provide further information, please let me know!

I hope I can try the vanilla 5.14.1 kernel tomorrow to see how it
behaves in regards to firewire-ohci (judging from the past it will
probably work though).

Best,
David

P.S.: I have added Kristian Hoegsberg in CC, who is mentioned as the
author of firewire-ohci and firewire-core.

[1] https://pkgbuild.com/~dvzrv/bugs/2021/09/linux-5.14.1.19.realtime1-kernel.log
[2] https://pkgbuild.com/~dvzrv/bugs/2021/09/linux-5.14.1.19.realtime1-restart_device_kernel.log

-- 
https://sleepmap.de