Received: by 2002:a05:6a10:9848:0:0:0:0 with SMTP id x8csp3045702pxf; Sun, 21 Mar 2021 16:54:35 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyVkcaZ/ki1Hr3Fdrbf8H+X+r+KOXe2RdoIQCuSEjhtvzwEbp90dJzP2gO1eUYPSp2Cwa1r X-Received: by 2002:a17:906:1985:: with SMTP id g5mr15737140ejd.285.1616370875157; Sun, 21 Mar 2021 16:54:35 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1616370875; cv=none; d=google.com; s=arc-20160816; b=IJXu0MYLlLsiF80PeTF0JEewp92v7G2aph2/+VOGJqS2pTefcsFbhhJVtu2B0jCBoN 2lGwIfLFDkQGk8sUsZP2XWOTLP/tWIEatRUHYzmbCuSDIKFkaF/g+bLrIDzsuw0d3M4k NFhZDxSYftmq7L3x7PKvbmPaU1MW9PkLmw2SYTlH5YUI8mrHmDM/MKKF+8Pfm6NAAIvC B8mKhK4+wlrSetEyUZRUevGMsuv7B8J3nNyn9Yoc5lH7Ja8AB0tmL9hYGA27XtiOWDO6 bq7VhjTnBtcUdsPRJ0wu7+Ui8gdrUBahXgW3WU6VYuNMib69yEu8UXCU2fELG1JdAuLK MWMg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:message-id:subject:to:from:date :dkim-signature; bh=cmoNwZODaEKzKo1ySie/1YtHY0TReznW+vr1fAuPKW4=; b=WDExdGFp6uCMJASc3mB/H+3wOVJf2bc6yhyPuXgEvKF/b7uL28U58qVBFf5XHS+tT3 4evPyn64wmH04fomdiZjEsuRQonXwNJpj1xsBdD0ELbSLRgJzvEQZEqbvvj1W0e4U4NS GTVkllpBr6ab4KtX4C3BZKDKqRNPNakLz7WqdfK6u9FjIWwWPno2ldRbNINs8QqiTn6I 37ykJnCu4STWXBu87nfcD8sEtAYqfXzE6KhY/TKCGbhdANqRpXBdO5X3tN8u4fVtZ9NI r00mN0+yOCUSsO9nyppYdlGYqhp6Qht64y2UGKjn+gPJHiNc/dNDPF9Why8Ors6COs8q AnLQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@vfemail.net header.s=2018 header.b=o0xKFnkc; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id bt17si9802009edb.424.2021.03.21.16.54.13; Sun, 21 Mar 2021 16:54:35 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=fail header.i=@vfemail.net header.s=2018 header.b=o0xKFnkc; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229951AbhCUWwM (ORCPT + 99 others); Sun, 21 Mar 2021 18:52:12 -0400 Received: from nl101-3.vfemail.net ([149.210.219.33]:45555 "EHLO nl101-3.vfemail.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229879AbhCUWvp (ORCPT ); Sun, 21 Mar 2021 18:51:45 -0400 X-Greylist: delayed 400 seconds by postgrey-1.27 at vger.kernel.org; Sun, 21 Mar 2021 18:51:45 EDT DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=vfemail.net; h=date:from :to:subject:message-id:mime-version:content-type; s=2018; bh=5hS d3hGGCIyg0B2WQAm0WqjGTwWPd0h197Oz9aFGe1c=; b=o0xKFnkc510cY0IG4UD jVvJJNaBSwE0TIjXXbcHiBMetYA8IUMmwQeVy8Hi/Jtu0CXylS5Va872SdsrQyMr 7Ycs/hn4nrWM6H1fGYqWBS/CVuWpHPvyGWqlD7iqO+hQYbFx6rcHdHQU8+Cxgb7a 9fqKkRvDuyg3VUUtt6o+dG/4= Received: (qmail 19554 invoked from network); 21 Mar 2021 22:44:39 -0000 Received: by simscan 1.4.0 ppid: 19497, pid: 19520, t: 0.3653s scanners:none Received: from unknown (HELO bmwxMDEudmZlbWFpbC5uZXQ=) (aGdudGt3aXNAdmZlbWFpbC5uZXQ=@MTkyLjE2OC4xLjE5Mg==) by nl101.vfemail.net with ESMTPA; 21 Mar 2021 22:44:39 -0000 Date: Sun, 21 Mar 2021 18:44:37 -0400 From: David Niklas To: LKML Subject: OT: How to report a HW bug Message-ID: <20210321184437.56ae13a7@Zen-II-x12.niklas.com> X-Mailer: Claws Mail 3.17.1 (GTK+ 2.24.31; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="MP_/iE4b0d3R3u.MaKMtlr248Qg" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --MP_/iE4b0d3R3u.MaKMtlr248Qg Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Disposition: inline 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 --MP_/iE4b0d3R3u.MaKMtlr248Qg Content-Type: text/plain Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=lspci-aic-ASM1166.txt 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- SERR-