[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1041144: marked as done (firewire_ohci 0000:0c:00.0: register access failure for FireWire (IEEE 1394): O2 Micro, Inc. 1394 OHCI Compliant Host Controller (rev 05))

Your message dated Tue, 01 Aug 2023 01:09:37 +0200
with message-id <6531216.tM3a2QDmDi@bagend>
and subject line Re: Debian's BTS is not for regular user questions
has caused the Debian Bug report #1041144,
regarding firewire_ohci 0000:0c:00.0: register access failure for FireWire (IEEE 1394): O2 Micro, Inc. 1394 OHCI Compliant Host Controller (rev 05)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1041144: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041144
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-image-6.1.0-10-amd64
Version: 6.1.37-1
In the journal we find the following error (the line “firewire_ohci … failure” is red, the line “firewire_ohci … 0x10” is bright white, and the remaining three lines are grey-white as usual): 

…
Jul 15 03:35:14 AnonymizedMachneName kernel: sdhci: Secure Digital Host Controller Interface driver 
Jul 15 03:35:14 AnonymizedMachneName kernel: PTP clock support registered
Jul 15 03:35:14 AnonymizedMachneName kernel: sdhci: Copyright(c) Pierre Ossman Jul 15 03:35:14 AnonymizedMachneName kernel: firewire_ohci 0000:0c:00.0: register access failure Jul 15 03:35:14 AnonymizedMachneName kernel: firewire_ohci 0000:0c:00.0: added OHCI v1.10 device as card 0, 8 IR + 8 IT contexts, quirks 0x10 
…
The computer is Dell Mobile Precision M6700. BIOS is at its latest available version A20. As the machine experiences high-level issues later at boot (e.g., some services can't start), we wish to be sure about the contribution of the error here. How much do we have to worry?
The outputs of modprobing the driver and lspci are attached. Perhaps, the driver could be a bit cleverer for the particular hardware “Dell 1394 OHCI Compliant Host Controller” and not issue a user-visible error in first place. 

Gratefully,
AlMa
0c:00.0 FireWire (IEEE 1394): O2 Micro, Inc. 1394 OHCI Compliant Host Controller (rev 05) (prog-if 10 [OHCI])
	Subsystem: Dell 1394 OHCI Compliant Host Controller
	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: 32 bytes
	Interrupt: pin A routed to IRQ 19
	IOMMU group: 15
	Region 0: Memory at f7c03000 (32-bit, non-prefetchable) [size=4K]
	Capabilities: [a0] Power Management version 3
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [80] Express (v1) Endpoint, MSI 00
		DevCap:	MaxPayload 128 bytes, PhantFunc 0, Latency L0s <4us, L1 <64us
			ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset- SlotPowerLimit 10W
		DevCtl:	CorrErr- NonFatalErr- FatalErr- UnsupReq-
			RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+
			MaxPayload 128 bytes, MaxReadReq 128 bytes
		DevSta:	CorrErr+ NonFatalErr- FatalErr- UnsupReq+ AuxPwr- TransPend-
		LnkCap:	Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s <64ns, L1 unlimited
			ClockPM+ Surprise- LLActRep- BwNot- ASPMOptComp-
		LnkCtl:	ASPM L0s Enabled; RCB 64 bytes, Disabled- CommClk-
			ExtSynch- ClockPM+ AutWidDis- BWInt- AutBWInt-
		LnkSta:	Speed 2.5GT/s, Width x1
			TrErr- Train- SlotClk- DLActive- BWMgmt- ABWMgmt-
	Capabilities: [100 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-
	Capabilities: [200 v1] Advanced Error Reporting
		UESta:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
		UEMsk:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
		UESvrt:	DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
		CESta:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr+
		CEMsk:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr+
		AERCap:	First Error Pointer: 00, ECRCGenCap- ECRCGenEn- ECRCChkCap- ECRCChkEn-
			MultHdrRecCap- MultHdrRecEn- TLPPfxPres- HdrLogCap-
		HeaderLog: 00000000 00000000 00000000 00000000
	Kernel driver in use: firewire_ohci
	Kernel modules: firewire_ohci

# modprobe -v firewire_ohci debug=-1 2>&1
insmod /lib/modules/6.1.0-10-amd64/kernel/drivers/firewire/firewire-ohci.ko debug=-1
[ 6997.901108] firewire_ohci 0000:0c:00.0: added OHCI v1.10 device as card 5, 8 IR + 8 IT contexts, quirks 0x10
[ 6997.901120] firewire_ohci 0000:0c:00.0: IRQ 00040000 regAccessFail
[ 6997.902591] firewire_ohci 0000:0c:00.0: register access failure
[ 6997.903295] firewire_ohci 0000:0c:00.0: IRQ 00030010 selfID AR_req busReset
[ 6997.904508] firewire_ohci 0000:0c:00.0: IRQ 00020000 busReset
[ 6997.904531] firewire_ohci 0000:0c:00.0: IRQ 00020000 busReset
[ 6997.906641] firewire_ohci 0000:0c:00.0: IRQ 00020000 busReset
[ 6997.906651] firewire_ohci 0000:0c:00.0: AR evt_bus_reset, generation 1
[ 6997.906657] firewire_ohci 0000:0c:00.0: IRQ 00020000 busReset
[ 6997.908958] firewire_ohci 0000:0c:00.0: IRQ 00020000 busReset
[ 6997.908984] firewire_ohci 0000:0c:00.0: IRQ 00020000 busReset
[ 6997.909006] firewire_ohci 0000:0c:00.0: IRQ 00020000 busReset
[ 6997.909044] firewire_ohci 0000:0c:00.0: IRQ 00020000 busReset
[ 6997.909091] firewire_ohci 0000:0c:00.0: IRQ 00020000 busReset
# [ 6997.914578] firewire_ohci 0000:0c:00.0: IRQ 00020000 busReset
[ 6997.914609] firewire_ohci 0000:0c:00.0: IRQ 00020000 busReset
[ 6997.914634] firewire_ohci 0000:0c:00.0: IRQ 00020000 busReset
[ 6997.917379] firewire_ohci 0000:0c:00.0: IRQ 00020000 busReset
[ 6997.917406] firewire_ohci 0000:0c:00.0: IRQ 00020000 busReset
[ 6997.917423] firewire_ohci 0000:0c:00.0: IRQ 00020000 busReset
[ 6997.920802] firewire_ohci 0000:0c:00.0: IRQ 00020000 busReset
[ 6997.920823] firewire_ohci 0000:0c:00.0: IRQ 00020000 busReset
[ 6997.920840] firewire_ohci 0000:0c:00.0: IRQ 00020000 busReset
[ 6997.923896] firewire_ohci 0000:0c:00.0: IRQ 00020000 busReset
[ 6997.925292] firewire_ohci 0000:0c:00.0: IRQ 00020000 busReset
[ 6997.926671] firewire_ohci 0000:0c:00.0: IRQ 00020000 busReset
[ 6997.927953] firewire_ohci 0000:0c:00.0: IRQ 00020000 busReset
[ 6997.928982] firewire_ohci 0000:0c:00.0: IRQ 00020000 busReset
[ 6997.930342] firewire_ohci 0000:0c:00.0: IRQ 00020000 busReset
[ 6997.931326] firewire_ohci 0000:0c:00.0: IRQ 00020000 busReset
[ 6997.932286] firewire_ohci 0000:0c:00.0: IRQ 00020000 busReset
[ 6997.933139] firewire_ohci 0000:0c:00.0: IRQ 00020000 busReset
[ 6997.934349] firewire_ohci 0000:0c:00.0: IRQ 00020000 busReset
[ 6997.935605] firewire_ohci 0000:0c:00.0: IRQ 00020000 busReset
[ 6997.936851] firewire_ohci 0000:0c:00.0: IRQ 00020000 busReset
[ 6997.937779] firewire_ohci 0000:0c:00.0: IRQ 00020000 busReset
[ 6997.939030] firewire_ohci 0000:0c:00.0: IRQ 00020000 busReset
[ 6997.939810] firewire_ohci 0000:0c:00.0: 1 selfIDs, generation 1, local node ID ffc0
[ 6997.940587] firewire_ohci 0000:0c:00.0: selfID 0: 807f8842, phy 0 [-..] S400 gc=63 +0W Lci
[ 6998.453197] firewire_core 0000:0c:00.0: created device fw0: GUID 0027c741444fc000, S400

--- End Message ---
--- Begin Message --- 
On Sat, 15 Jul 2023 03:13:51 +0200 AlMa <AlMa0@ro.ru> wrote:
> In the journal I see two yellow lines (which, probably, constitute 
> warnings) directly following one another:
> … 
> Later in the journal we see a white line
> … 
> 
> As the machine (Dell Mobile Precision M6700) experiences various 
> high-level issues later in the boot process, I'm unsure about the 
> contribution of the two issues in the log.  Which software or hardware 
> problems do these warnings inform us about?  Any fix or remedy?

You filed various bugs talking about yellow and white lines of which you 
suspect that yellow may be a warning (which you should be able to find out by 
yourself if that's the case).

The Debian BTS is not meant to ask questions like "what could this message 
tell us?". Put it in a search engine or use one of the MANY user support 
options for that. Computers/Linux put various debug/informational/warning msgs 
in various logs, which _could_ be helpful in case there's an actual ERROR.

But the only *potential* error I see here is "various high-level issues", 
which is so vague so that's completely useless and inactionable.

So I'm going to close this and similar vague bug reports, which aren't 
actually bug reports, but just questions.
And all those ACPI errors? Contact the machine vendor as they're the only ones 
who could resolve such issue. Linux is only reporting that there are issues.

"If we believe Jean Delvare" ... and Jean Delvare response in that bug report:
"This is not a support forum, sorry. If you need help, use support forums and 
mailing lists." ...

From 'bug' #1041191: "Will the fingerprint sensor not work?"
I _assume_ you have the device/machine, so why don't you try it out?
*IF* it turns out it doesn't work then you first use a search engine to see if 
you can make it work yourself by trying out various hints you'll undoubtedly 
find and if that doesn't make it work, *THEN* you have something to file a bug 
about.

You filed *8* different 'bugs' which (almost?) all are about a Dell Mobile 
Precision M6700 ... and not once did you say what actual problem you 
experienced?!?

If you file a bug, you're (basically) asking (several) people to read about a 
problem you're having and then subsequently (potentially) spend time to fix 
that/those problem(s).
Please be more considerate with other people's time and only file bugs for 
*actual* problems and then provide enough information/context so that they
can actually (potentially) act upon it and help you fix that problem.

I initially intended to respond to some actual problems you (also) reported, 
but I've already spend way too much time on these non-issues, so I'm done.

Attachment: signature.asc
Description: This is a digitally signed message part.


--- End Message ---
Reply to: