From: zless <zless@dmesg.site>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] [OT] AER: Corrected error received: 0000:00:03.0
Date: Fri, 28 Sep 2018 12:26:09 +0300 [thread overview]
Message-ID: <1679871.TQ8tpZyCyR@callisto> (raw)
In-Reply-To: <c6dcce4c-9472-f5dc-2f50-10688d26ae5b@alstadheim.priv.no>
În ziua de vineri, 28 septembrie 2018, la 10:05:28 EEST, Håkon Alstadheim a
scris:
>
> Den 28. sep. 2018 00:02, skrev Mick:
> > On Thursday, 27 September 2018 21:51:42 BST Håkon Alstadheim wrote:
> >> (Sorry for the OT, don't know where to go for generic hardware questions)
> >>
> >> I'm wondering if my main board dying? On sept. 1 I started getting error
> >> messages like the ones at the end of this mail. I just noticed them. I
> >> am including logs from as far back as I have, just for completeness.
> >>
> >> This mainboard:
> >>
> >> # smbios-sys-info
> >> Libsmbios version: 2.3.2
> >> Product Name: Z10PE-D8 WS
> >> Vendor: ASUSTeK COMPUTER INC.
> >> BIOS Version: 3703
> >>
> >> ... has given me a lot of grief, so I've been mucking about with it
> >> quite a lot. I don't know if I did anything on september 1. Could it be
> >> some bios-setting I've changed, or som firmware corruption ? Other
> >> weirdness happening recently is sensors have started having episodes of
> >> all values totally bogus, and one pwm fan-sensor seems to be permanently
> >> slightly loony.
> >>
> >> OS running is kept up-to-date ~amd64 gentoo-sources running as Dom0
> >> under Xen-4.11 latest.
> >>
> >> ------------------
> >>
> >>
> >> 0:root@gentoo log # zgrep 'pcieport 0000:00:03.0' kern.log* | sed -e
> >> 's/^[^:]*://' | sort -M
> >> Aug 19 19:38:55 gentoo kernel: [ 1.181466] pcieport 0000:00:03.0: AER
> >> enabled with IRQ 134
> >> Aug 19 19:38:55 gentoo kernel: [ 1.181700] pcieport 0000:00:03.0:
> >> Signaling PME with IRQ 134
> > Did you enable CONFIG_PCIEAER_INJECT in your kernel?
> Yes, enabled already.
> >
> > What do you get when you boot with the kernel option:
> >
> > pcie_ports=auto
> >
> Still happens I'm afraid.
>
> # cat /proc/cmdline
> placeholder root=LABEL=SAS-GENTOO ro
> xen-pciback.hide=(02:00.*)(04:00.*)(05:00.*)(08:00.*)(81:00.*)(82:00.*)
> usbcore.autosuspend=-1 scsi_mod.use_blk_mq=1 xen-netback.max-queues=8
> xen-pciback.permissive=1 xen-pciback.verbose_request=1
> xen-blkback.max_persistent_grants=1024 intel_iommu=on domodules domdadm
> console=tty1 pcie_ports=auto
I "solved" a similar case with 'pci=noaer' on the kernel command line.
I quote solved above because even to this day I have no idea what those
messages were trying to tell me.
I always had CONFIG_PCIEAER_INJECT not enabled though.
next prev parent reply other threads:[~2018-09-28 9:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-27 20:51 [gentoo-user] [OT] AER: Corrected error received: 0000:00:03.0 Håkon Alstadheim
2018-09-27 22:02 ` Mick
2018-09-28 7:05 ` Håkon Alstadheim
2018-09-28 9:26 ` zless [this message]
2018-09-28 9:53 ` Mick
2018-10-01 3:50 ` mad.scientist.at.large
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=1679871.TQ8tpZyCyR@callisto \
--to=zless@dmesg.site \
--cc=gentoo-user@lists.gentoo.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