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

[David Runge <dave@sleepmap.de>]

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

On 2021-09-09 09:46:06 (+0900), Takashi Sakamoto wrote:
> On Wed, Sep 08, 2021 at 07:30:14PM +0200, David Runge wrote:
> > I am using '-1' (all) in the 2nd link in my previous mail. It appears to
> > not show a different output in the kernel logs from when I set it to '5'
> > though. There seems to be something wrong...
> > I'm adding the options in a .conf file below /etc/modprobe.d/, e.g.:
> > 
> > ```
> > options firewire-ohci debug=5
> > ```
> > 
> > The only output I get from that is:
> > 
> > ```
> > firewire_ohci 0000:05:00.0: enabling device (0000 -> 0002)
> > firewire_ohci 0000:05:00.0: added OHCI v1.10 device as card 0, 8 IR + 8 IT contexts, quirks 0x2
> > firewire_core 0000:05:00.0: created device fw0: GUID 7856341278563412, S800
> > firewire_ohci 0000:05:00.0: isochronous cycle inconsistent
> > firewire_core 0000:05:00.0: created device fw1: GUID 000a3500ada83262, S400
> > firewire_core 0000:05:00.0: phy config: new root=ffc0, gap_count=5
> > ```
> 
> Before printing 'created device fw1', Linux FireWire subsystem already
> initiates asynchronous transactions to retrieve content of configuration
> ROM located in 0x'ffff'f000'0400 of node address space. If you can see
> no transaction record but see the print, it means to fail configuration
> of the parameter of firewire-ohci module.
> 
> I think your system uses initramfs. Any node for storage function in
> IEEE 1394 bus is available as initial boot disk, thus it's reasonable
> that the designer of your initramfs puts firewire-ohci/firewire-core
> modules into it. In the case, we can not configure module by
> '/etc/modprobe.d/*' since the modules are already loaded before mounting
> root file system.
> 
> I think the design of initramfs differs depending on distribution, thus
> you need to find instruction for the way to configure module parameter
> by yourself.
> 
> Instead, I suggest you to configure the module via sysfs after booting,
> like:
> 
> ```
> # echo 5 > /sys/module/firewire_ohci/parameters/debug
> ```

I have played around with adding the configuration and the module
explicitly to the initramfs (we're using mkinitcpio on Arch Linux).
However, this did not change anything in the output provided by
journalctl [1].

A boot with the vanilla 5.14.2 (no threadirqs) and debug=-1 set for
firewire-ohci logs everything successfully [2].

My assumption is that the debug parameter is either not considered or
the module hangs far before there's any further output when on linux-rt.


Unrelated sidenote: I am currently booted into vanilla 5.14.2 (no
threadirqs) and the device works well using pipewire and the ALSA driver
snd-fireface.
Good job to everyone involved! I'm very happy about the results! \o/

Best,
David

[1] https://pkgbuild.com/~dvzrv/bugs/2021/09/linux-5.14.1.19.realtime1-firewire-ohci-debug--1-initramfs-kernel.log
[2] https://pkgbuild.com/~dvzrv/bugs/2021/09/linux-5.14.2.arch1-firewire-ohci-debug--1-initramfs-kernel.log

-- 
https://sleepmap.de

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