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] [day] [month] [year] [list]
Date:   Sat, 10 Aug 2019 20:16:31 +0500
From:   Mikhail Gavrilov <mikhail.v.gavrilov@...il.com>
To:     bjorn@...gaas.com
Cc:     Keith Busch <keith.busch@...el.com>,
        Oza Pawandeep <poza@...eaurora.org>, linux-pci@...r.kernel.org,
        emteeelp@...il.com,
        Linux List Kernel Mailing <linux-kernel@...r.kernel.org>
Subject: Re: [Bug 201517] New: pcieport 0000:00:03.1: AER: Corrected error
 received: 0000:00:00.0

On Tue, 4 Dec 2018 at 04:36, Bjorn Helgaas <bjorn.helgaas@...il.com> wrote:
>
> [Forwarding this to linux-pci since nobody really monitors the bugzilla]
>
> Possibly the same issue reported here:
>
>   https://bugzilla.kernel.org/show_bug.cgi?id=109691
>   https://bugzilla.kernel.org/show_bug.cgi?id=111601
>   https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1588428/
>   https://lore.kernel.org/linux-pci/20160215171423.GA12641@localhost/
>
> I had a theory about the problem (see the lore.kernel link above), but
> that was before a lot of AER rework, and I haven't checked the code
> since then.


Thanks for the response.
I have tested the system several months with the kernel command line
"pci=noaer". And the error "pcieport 0000:00:03.1: AER: Corrected
error received: 0000:00:00.0" not happened all testing time.
Which is your theory about this issue?

--
Best Regards,
Mike Gavrilov.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ