mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Niklas <Hgntkwis@vfemail.net>
To: LKML <linux-kernel@vger.kernel.org>
Subject: OT: How to report a HW bug
Date: Sun, 21 Mar 2021 18:44:37 -0400	[thread overview]
Message-ID: <20210321184437.56ae13a7@Zen-II-x12.niklas.com> (raw)

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

Hello,

I'm asking how to report a bug in the physical HW here because I can't
think of anywhere else to ask where there might be people who have done
this before.

The HW in question is an AMD 3900X and ASRock Taichi B550 MB. I have
turned both CPU and MB in for warranty and the defect remains.

What happens is this:
1: I get my ASM1166 6 port SATA PCIe 2.0 expansion card and plug it into
the second 16 lane wide PCIe port (my GPU is in the top one). It is
connected to the CPU's PCIe lanes.
2: I try to boot. I get several errors regarding memory and chipset
initialization errors. In particular. The last is error code 94. The
system fails to POST and reboots.
3: I place the AIC into the lowest PCIe port (also 16 lanes wide), and
the system boots without a problem. The AIC works correctly. The AIC is
then electrically connected to the chipset, not the CPU.

I'm attaching the output of lspci for the AIC. Here's the AIC I purchased:
https://www.ebay.com/itm/PCIE-SATA-3-0-PCI-E-SATA-Card-PCI-E-PCI-Express-SATA-Controller-6-Ports-SATA3-X4/114295190520

IMHO, the problem could be:
The Chipset, because it doesn't initialize.
The CPU, because it's PCIe lanes go as far as the second PCIe 16 lane
port).
The PCIe 4.0 re-drivers, because they might be malfunctioning.
The card, because it might abuse the PCIe 2.0 protocol.

So, who should I report this to? AMD or ASRock?
Is there anything I can do to further isolate this problem?
Is what I have written sufficient, or would you recommend that I add some
other info?
Is there any difficulty to trying to file a report with AMD and ASRock
which you would have any suggestions about working around?

Thanks,
David

[-- Attachment #2: lspci-aic-ASM1166.txt --]
[-- Type: text/plain, Size: 2748 bytes --]

03:00.0 SATA controller: ASMedia Technology Inc. Device 1166 (rev 02) (prog-if 01 [AHCI 1.0])
	Subsystem: ZyDAS Technology Corp. Device 2116
	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 49
	Region 0: Memory at fca82000 (32-bit, non-prefetchable) [size=8K]
	Region 5: Memory at fca80000 (32-bit, non-prefetchable) [size=8K]
	Expansion ROM at fca00000 [disabled] [size=512K]
	Capabilities: [40] 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: [50] MSI: Enable+ Count=1/1 Maskable- 64bit+
		Address: 00000000fee1b000  Data: 0023
	Capabilities: [80] Express (v2) Endpoint, MSI 00
		DevCap:	MaxPayload 512 bytes, PhantFunc 0, Latency L0s <64ns, L1 <1us
			ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset- SlotPowerLimit 26.000W
		DevCtl:	Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
			RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+
			MaxPayload 512 bytes, MaxReadReq 512 bytes
		DevSta:	CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend-
		LnkCap:	Port #0, Speed 8GT/s, Width x2, ASPM L0s L1, Exit Latency L0s <4us, L1 <64us
			ClockPM+ Surprise- LLActRep- BwNot- ASPMOptComp+
		LnkCtl:	ASPM Disabled; RCB 64 bytes Disabled- CommClk+
			ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
		LnkSta:	Speed 8GT/s, Width x2, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
		DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, OBFF Not Supported
		DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled
		LnkCtl2: Target Link Speed: 8GT/s, EnterCompliance- SpeedDis+
			 Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
			 Compliance De-emphasis: -6dB
		LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete+, EqualizationPhase1+
			 EqualizationPhase2+, EqualizationPhase3+, LinkEqualizationRequest-
	Capabilities: [100 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- NonFatalErr-
		CEMsk:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
		AERCap:	First Error Pointer: 00, GenCap- CGenEn- ChkCap- ChkEn-
	Capabilities: [130 v1] #19
	Kernel driver in use: ahci


                 reply	other threads:[~2021-03-21 22:52 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20210321184437.56ae13a7@Zen-II-x12.niklas.com \
    --to=hgntkwis@vfemail.net \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®