linux-kernel - Re: PROBLEM: PCIe Bus Error atleast

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Mon, 4 Nov 2019 10:38:23 +1100
From:   "Oliver O'Halloran" <oohall@...il.com>
To:     Jeffrin Thalakkottoor <jeffrin@...agiritech.edu.in>
Cc:     Russell Currey <ruscur@...sell.cc>,
        Sam Bobroff <sbobroff@...ux.ibm.com>,
        Bjorn Helgaas <bhelgaas@...gle.com>,
        linuxppc-dev <linuxppc-dev@...ts.ozlabs.org>,
        linux-pci@...r.kernel.org, lkml <linux-kernel@...r.kernel.org>
Subject: Re: PROBLEM: PCIe Bus Error atleast

On Sat, Nov 2, 2019 at 5:46 AM Jeffrin Thalakkottoor
<jeffrin@...agiritech.edu.in> wrote:
>
> hello ,
>
> i found a error message  as the output of "sudo dmesg -l err"
> i have attached related to that in this email.
> i  think i found this in 5.3.8 kernel

Use "uname -a" to get the current kernel version, architecture.

> But i think when i tried again today i could not reproduce it

That's unfortunate, but it might have just been a transient problem.
The log has a pile of these AER errors:

[  283.723848] pcieport 0000:00:1c.5: AER: PCIe Bus Error:
severity=Corrected, type=Data Link Layer, (Transmitter ID)
[  283.723855] pcieport 0000:00:1c.5: AER:   device [8086:9d15] error
status/mask=00001000/00002000
[  283.723859] pcieport 0000:00:1c.5: AER:    [12] Timeout

Which looks like a root port is getting a timeouts while trying to
talk to its downstream device. It's hard to say anything more without
knowing what the downstream device is, or what the system is. If this
is a laptop it might be due to buggy power management, but it might
just be flakey hardware.

Can you provide the full dmesg and the output of lspci -vv?

Oliver