public inbox for linux-rt-users@vger.kernel.org
 help / color / mirror / Atom feed
From: David Runge <dave@sleepmap.de>
To: "Ahmed S. Darwish" <a.darwish@linutronix.de>
Cc: linux-rt-users@vger.kernel.org, linux1394-devel@lists.sourceforge.net
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: Thu, 28 Jan 2021 22:41:45 +0100	[thread overview]
Message-ID: <YBMvmU+kp11f7+wF@hmbx> (raw)
In-Reply-To: <YBJZk9/77+E0TRk4@lx-t490>

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

On 2021-01-28 07:28:35 (+0100), Ahmed S. Darwish wrote:
> On Sat, Jan 23, 2021 at 12:59:29PM +0100, David Runge wrote:
> ...
> Can you please send the full kernel log, with boot parameter
> "firewire_ohci.debug=-1", for mainline v5.4.91 vs. v5.4.91-rt50?

kernel log for mainline:
https://pkgbuild.com/~dvzrv/bugs/2021/01/linux-5.4.91-kernel.log

kernel log for rt (no dice :-/):
https://pkgbuild.com/~dvzrv/bugs/2021/01/linux-5.4.91.50.arch1-kernel.log

> Please also make sure to use the exact same defconfig for both, except
> with CONFIG_PREEMPT_RT=y for the -rt kenrel of course.

config diff:
https://pkgbuild.com/~dvzrv/bugs/2021/01/linux-5.4.91-lts_changed_vs_rt-lts.patch

> This will help in comparing apples to apples, as you were posting the
> results of different base kernels (vs. the -rt versions), and different
> defconfigs (vs. -rt) within such kernels.

The configuration for the 5.4.91 stock kernel has not been updated since
the 5.4.83, which is maybe a bit misleading.
Generally I enable anything that I can in the config for the realtime
kernel. However, some settings of course get switched off, as they are
not compatible.
The diff above is for a custom version I just made, just to make sure
and clear things out.

> Good luck,

Thanks, seems it's needed!

> P.S. Since this maybe is a timing issue, and ohci bus reset handling
> occurs at SCHED_OTHER workqueu context, were you by any chance running
> unreasonably-intensive realtime workloads by the time the driver was
> loaded?

Not that I am aware of. The driver neither initializes the device during
boot nor when later reloading.
There are no intense services running. The system is fairly
multi-purpose, so most things are started on demand.

Thanks!

David

-- 
https://sleepmap.de

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

  reply	other threads:[~2021-01-28 21:42 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 [this message]
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
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=YBMvmU+kp11f7+wF@hmbx \
    --to=dave@sleepmap.de \
    --cc=a.darwish@linutronix.de \
    --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