From: David Runge <dave@sleepmap.de>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Kristian Hoegsberg <krh@bitplanet.net>,
linux1394-devel@lists.sourceforge.net,
linux-rt-users@vger.kernel.org,
"Ahmed S. Darwish" <a.darwish@linutronix.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, 8 Sep 2021 19:30:14 +0200 [thread overview]
Message-ID: <YTjzKftQmFtPLYUR@hmbx> (raw)
In-Reply-To: <YTgdLkTs7wEmj8fh@workstation>
[-- Attachment #1: Type: text/plain, Size: 1952 bytes --]
Hi Takashi,
thanks for the prompt and detailed response!
Unfortunately I lack the knowledge about the driver and its inner
workings to be able to provide a patch for this issue myself.
If anyone reading this who is able to suggest a fix, I'd be happy to
test it!
On 2021-09-08 11:17:18 (+0900), Takashi Sakamoto wrote:
> I guess we have issue in the softIRQ context or timer wheel context
> instead of hwIRQ context, if the OHCI 1394 controller you use has
> no quirk (I suggest you to give information about the controller).
>
> I'd like you to check it. The firewire-ohci module has 'debug' parameter.
>
> ``
> $ modinfo firewire-ohci
> ...
> parm: debug:Verbose logging (default = 0, AT/AR events = 1, self-IDs = 2, IRQs = 4, busReset events = 8, or a combination, or all = -1) (int)
> ``
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
```
This is with starting with the audio interface connected and on. I have
to switch it off and on again to get recognized, but then the driver
crashes (full kernel log [1])
[1] https://pkgbuild.com/~dvzrv/bugs/2021/09/linux-5.14.1.19.realtime1-firewire-ohci-debug-kernel.log
Best,
David
--
https://sleepmap.de
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-09-08 17:30 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-23 11:59 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
2021-01-28 6:28 ` Ahmed S. Darwish
2021-01-28 21:41 ` David Runge
2021-01-29 17:04 ` Sebastian Andrzej Siewior
2021-01-30 11:46 ` David Runge
2021-02-01 8:34 ` Sebastian Andrzej Siewior
2021-02-05 11:26 ` Sebastian Andrzej Siewior
2021-02-05 23:22 ` David Runge
2021-02-07 9:58 ` David Runge
2021-02-08 9:19 ` Sebastian Andrzej Siewior
2021-02-14 19:16 ` David Runge
2021-02-18 8:38 ` Sebastian Andrzej Siewior
2021-02-18 9:27 ` Sebastian Andrzej Siewior
2021-03-08 14:12 ` Sebastian Andrzej Siewior
2021-03-10 18:15 ` David Runge
2021-09-07 23:17 ` David Runge
2021-09-08 2:17 ` Takashi Sakamoto
2021-09-08 17:30 ` David Runge [this message]
2021-09-09 0:46 ` Takashi Sakamoto
2021-09-12 18:44 ` David Runge
2021-09-10 11:55 ` Sebastian Andrzej Siewior
2021-09-11 9:46 ` Takashi Sakamoto
2021-09-12 18:53 ` David Runge
2022-01-05 21:01 ` Holger Dehnhardt
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=YTjzKftQmFtPLYUR@hmbx \
--to=dave@sleepmap.de \
--cc=a.darwish@linutronix.de \
--cc=bigeasy@linutronix.de \
--cc=krh@bitplanet.net \
--cc=linux-rt-users@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).