Re: Possible regression with the FW643 chipset
AreYouLoco? via linux1394-devel <[email protected]> Fri, 20 Jun 2025 20:34:42 +0200
| Newsgroups | gmane.linux.kernel.firewire.devel |
|---|---|
| Message-ID | <[email protected]> |
So here it happened again. Kernel 6.12.32-rt-amd64 (Debian Trixie): Here is log after soft reboot: ``` areyouloco@studio:~$ sudo dmesg -w | grep -i firewire [ 1.120409] firewire_ohci 0000:03:00.0: added OHCI v1.10 device as card 0, 8 IR + 8 IT contexts, quirks 0x0, physUB [ 17.057643] libahci sha256_ssse3 sha1_ssse3 xhci_pci libata xhci_hcd ehci_pci iTCO_wdt sdhci_pci intel_pmc_bxt firewire_ohci ehci_hcd cqhci iTCO_vendor_support aesni_intel tg3 sdhci firewire_core scsi_mod gf128mul usbcore watchdog thunderbolt crypto_simd i2c_i801 mmc_core libphy cryptd i2c_smbus crc_itu_t lpc_ich scsi_common usb_common video wmi ``` And thats it related to firewire. Notice. No mention of fw0 or OHCI device added. Now I do: ``` areyouloco@studio:~$ sudo modprobe -r firewire_ohci areyouloco@studio:~$ sudo modprobe -r firewire_core areyouloco@studio:~$ sleep 2 areyouloco@studio:~$ sudo modprobe firewire-ohci ``` And then in dmesg I get: ``` [ 141.661165] firewire_ohci 0000:03:00.0: removing fw-ohci device [ 141.661261] firewire_ohci 0000:03:00.0: removed fw-ohci device [ 155.721784] firewire_ohci 0000:03:00.0: added OHCI v1.10 device as card 0, 8 IR + 8 IT contexts, quirks 0x0, physUB [ 156.245972] firewire_core 0000:03:00.0: created device fw0: GUID 003ee1fffe873194, S800 [ 156.245992] firewire_core 0000:03:00.0: phy config: new root=ffc1, gap_count=5 [ 159.293474] firewire_core 0000:03:00.0: created device fw1: GUID 000ff2050000145b, S400 ``` This is all I got for now. For firewire-ohci module in my kernel I see parameter possible to set: "parm: debug:Verbose logging, deprecated in v6.11 kernel or later. (default = 0, AT/AR events = 1, self-IDs = 2, IRQs = 4, or a combination, or all = -1) (int)" Is it still a way to debug further? I've read somewhere there was a replacement for this debug parameter via some calls. Machine is MacBook Pro Mid-2012 13''. But I also got other MBP and some full-size PCIe card also with that same chipset. On the other MBP behavior is similar I didn't check with PC yet. I might do that if requested. Hope it helps anyhow. I am getting kernel 6.15 to try out. On 6/20/25 3:12 PM, Takashi Sakamoto wrote: > Hi, > > On Fri, Jun 20, 2025 at 08:52:42AM +0930, Jonathan Woithe wrote: >> Alternatively, are there any FW643 users who have no problem with device >> detection under a 6.12.x (or later) kernel? If so this would conclusively >> rule out a kernel issue. > I can not regenerate the issue with the kernel modules provided by the > stock kernel in Ubuntu 25.04 amd64 (v6.14). The machine consists of > > * ASUSTeK COMPUTER INC. TUF GAMING X570-PLUS > * AMD Ryzen™ 7 5700G with Radeon™ Graphics × 16 > > > ``` > $ dpkg -S /lib/modules/6.14.0-15-generic/kernel/drivers/firewire/* > linux-modules-extra-6.14.0-15-generic: /lib/modules/6.14.0-15-generic/kernel/drivers/firewire/firewire-core.ko.zst > linux-modules-extra-6.14.0-15-generic: /lib/modules/6.14.0-15-generic/kernel/drivers/firewire/firewire-net.ko.zst > linux-modules-extra-6.14.0-15-generic: /lib/modules/6.14.0-15-generic/kernel/drivers/firewire/firewire-ohci.ko.zst > linux-modules-extra-6.14.0-15-generic: /lib/modules/6.14.0-15-generic/kernel/drivers/firewire/firewire-sbp2.ko.zst > linux-modules-extra-6.14.0-15-generic: /lib/modules/6.14.0-15-generic/kernel/drivers/firewire/nosy.ko.zst > > $ sudo lspci -vvnn > 06:00.0 FireWire (IEEE 1394) [0c00]: LSI Corporation FW643 [TrueFire] PCIe 1394b Controller [11c1:5901] (rev 06) (prog-if 10 [OHCI]) > Subsystem: LSI Corporation FW643 [TrueFire] PCIe 1394b Controller [11c1:5900] > Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- > Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- > Latency: 0, Cache Line Size: 64 bytes > Interrupt: pin A routed to IRQ 40 > IOMMU group: 20 > Region 0: Memory at fc600000 (64-bit, non-prefetchable) [size=4K] > Capabilities: [44] Power Management version 3 > Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+) > Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME+ > Capabilities: [4c] MSI: Enable- Count=1/1 Maskable- 64bit+ > Address: 0000000000000000 Data: 0000 > Capabilities: [60] Express (v1) Endpoint, IntMsgNum 0 > DevCap: MaxPayload 256 bytes, PhantFunc 0, Latency L0s <4us, L1 <64us > ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset- SlotPowerLimit 0W TEE-IO- > DevCtl: CorrErr+ NonFatalErr+ FatalErr+ UnsupReq+ > RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop- > MaxPayload 128 bytes, MaxReadReq 512 bytes > DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr+ TransPend- > LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s <512ns, L1 <64us > ClockPM+ Surprise- LLActRep- BwNot- ASPMOptComp- > LnkCtl: ASPM Disabled; RCB 64 bytes, LnkDisable- CommClk+ > ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- > LnkSta: Speed 2.5GT/s, Width x1 > TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- > Capabilities: [100 v1] Advanced Error Reporting > UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- > ECRC- UnsupReq- ACSViol- UncorrIntErr- BlockedTLP- AtomicOpBlocked- TLPBlockedErr- > PoisonTLPBlocked- DMWrReqBlocked- IDECheck- MisIDETLP- PCRC_CHECK- TLPXlatBlocked- > UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- > ECRC- UnsupReq- ACSViol- UncorrIntErr- BlockedTLP- AtomicOpBlocked- TLPBlockedErr- > PoisonTLPBlocked- DMWrReqBlocked- IDECheck- MisIDETLP- PCRC_CHECK- TLPXlatBlocked- > UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ > ECRC- UnsupReq- ACSViol- UncorrIntErr- BlockedTLP- AtomicOpBlocked- TLPBlockedErr- > PoisonTLPBlocked- DMWrReqBlocked- IDECheck- MisIDETLP- PCRC_CHECK- TLPXlatBlocked- > CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr- CorrIntErr- HeaderOF- > CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr+ CorrIntErr- HeaderOF- > AERCap: First Error Pointer: 00, ECRCGenCap+ ECRCGenEn- ECRCChkCap+ ECRCChkEn- > MultHdrRecCap- MultHdrRecEn- TLPPfxPres- HdrLogCap- > HeaderLog: 00000000 00000000 00000000 00000000 > Capabilities: [140 v1] Virtual Channel > Caps: LPEVC=0 RefClk=100ns PATEntryBits=1 > Arb: Fixed- WRR32- WRR64- WRR128- > Ctrl: ArbSelect=Fixed > Status: InProgress- > VC0: Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans- > Arb: Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256- > Ctrl: Enable+ ID=0 ArbSelect=Fixed TC/VC=01 > Status: NegoPending- InProgress- > VC1: Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans- > Arb: Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256- > Ctrl: Enable- ID=1 ArbSelect=Fixed TC/VC=00 > Status: NegoPending- InProgress- > Capabilities: [170 v1] Device Serial Number 12-34-56-10-12-30-00-86 > Kernel driver in use: firewire_ohci > Kernel modules: firewire_ohci > > ``` > > My Phonic FireFly 808 Universal is detected successfully even after the > reported steps. > > > Thanks > > Takashi Sakamoto > > > _______________________________________________ > mailing list [email protected] > https://lists.sourceforge.net/lists/listinfo/linux1394-devel _______________________________________________ mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/linux1394-devel