On 2021-02-05 12:26:38 (+0100), Sebastian Andrzej Siewior wrote: > On 2021-02-01 09:34:41 [+0100], To David Runge wrote: > > + firewire maintainer > > > > On 2021-01-30 12:46:04 [+0100], David Runge wrote: > > > On 2021-01-29 18:04:14 (+0100), Sebastian Andrzej Siewior wrote: > > > > I don't see anything wrong. There is small difference in timing and > > > > then the RT version does not do a thing while !RT keeps reseting… > > > > Could you try non-RT with the > > > > threadirqs > > > > > > > > option? > > > > > > Yes, (sorry for not including that earlier D:) that fails the same way > > > as the realtime kernel: > > > https://pkgbuild.com/~dvzrv/bugs/2021/01/linux-5.4.91-kernel_threadirqs.log > > > > Could be specific to the chip or the ohci driver. Either way, the problem > > are the threaded interrupts. > > David, could you please try a v5.10 kernel with threadirqs? I've been > just told that it works there on a ppc64 box. I have now tried with our vanilla 5.10.13 kernel, as I have issues getting 5.10.12-rt26 to boot at all on my machine (will try to investigate that tomorrow). On 5.10.13 with threadirqs the controller is indeed initialized again (/dev/fw0 appears). However, no connected device is detected (i.e. /dev/fw1 does not appear). Here are the kernel logs with "firewire-ohci debug=-1": https://pkgbuild.com/~dvzrv/bugs/2021/01/linux-5.10.13.arch1_threadirqs-kernel.log Thanks for the follow-up! Best, David -- https://sleepmap.de
Attachment:
signature.asc
Description: PGP signature
