Re: Fwd: Adding timeouts to device access?
AreYouLoco? via linux1394-devel <[email protected]> Sun, 06 Jul 2025 11:06:07 +0000
| Newsgroups | gmane.linux.kernel.firewire.devel |
|---|---|
| Message-ID | <[email protected]> |
I think I got it! I got interested in firewire-ohci quirks and my dmesg reported 0x0 for quirks by default. And when reading thru: <https://github.com/torvalds/linux/blob/1f988d0788f50d8464f957e793fab356e2937369/drivers/firewire/ohci.c#L330> It seems that it should apply 0x4 and 0x10 so 0x14. I've created: /etc/modprobe.d/firewire-ohci-quirks.conf options firewire-ohci quirks=0x14 And now it seems to work fine each time. And also hot-plug started to work! So the issue is that quirks that suppose to be applied are not for some reason. Could someone verify this on their end?! On July 5, 2025 4:11:06 PM UTC, AreYouLoco? via linux1394-devel <[email protected]> wrote: >Just to note I am on exact same kernel version. > >Takashi さん tried to reproduce it on 6.14 and couldn't. > >I think I am going to try some cutting edge distro like Arch with newer kernel and see there. Kernel 6.15 from experimental Debian repo didnt boot for me. > >There were reports and from my own experience that it worked before on older kernels presumably 6.5.something. > > >On July 3, 2025 4:58:59 AM UTC, "小太" <[email protected]> wrote: >>On Thu, 3 Jul 2025 at 04:43, AreYouLoco? <[email protected]> wrote: >> >>> Hi, >>> >>> I am observing similar problems reported already to the list also with >>> Agere but with FW643 and FW643E chipsets. >>> >>> Similarity here is OPs probes with unloading firewire-ohci. I am doing >>> same attempts to restore detection of devices. And truely I couldn't find a >>> pattern what combination works. And sometimes modprobe -r firewire-ohci >>> hangs for me as well and also normal reboot in that case hangs as well. >>> >>> I just do 10seconds power button then. >>> >>> So there seem to be some pattern with Agere chipsets not cooperating. >>> >>> May I ask OP: which kernel version are you on? >>> >> >>It's been happening for at least half a year now so it's not a recent issue >>by any means - I've just been too lazy to debug it given how infrequently >>it occurs for me >> >>But my current kernel version is 6.12.32 >> >>$ uname -a >>Linux home.kota.moe 6.12.32-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.12.32-1 >>(2025-06-07) x86_64 GNU/Linux