PCIE bus error Systemd problem Asus Prime H310M-E R2.0 motherboard intel i7

Pythagorus · 05-16-2020, 05:52 AM

Hello all,

I had my old desktop die and needed to get work done, so I bought a system off the shelf from a computer shop, 8th gen i7 Asus Prime H310M-E R2.0 16 mg DDR4 Ram 2666, Nvidia 710 graphics. The motherboard has an M2 sata slot which is also pcie x2.

I've been using linux since 1998 but I'm just a reasonably competent self taught user.

The system seems to overheat on Linux. Running top from a screenshot I have CPU 6.0 us, 11.7 sy 0.0 ni 80.8 id, I take it that is 80% idle.

Systemd+ 997 root Pr 20 NI 0 446872 298632 shr 296984 S R %CPU 99.0 Mem 1.8

IrQ/122+ 184 root PR-51 NI 0 Virt 0 Res 0 SHR 0 S R %CPU 36.3

Don't know what most of that is but in comparison to my laptop which is running Ubuntu, Systemd is very very small on that.

When I booted the live Mint DVD I got a lot of scrolling on the screen at high speed, I managed to take a photo of it, it reads: 125.008462 pcieport 0000:00"1c.5: PCIE bus error: severity =Corrected, type=Physical Layer, (Receiver ID) device [8086:a295] error status/mask=00000001/00002000 [ 0] RxErr This is repeated but the 125.00number at the start is increasing while the device8086:a295 is the same.

Mint worked but there were some errors on the display including a little bar under the mouse pointer.

Manjaro worked with everything succeeding in the boot process but it would freeze and become unresponsive after about ten minutes, from the boot dvd and from after I installed it.

Fedora Workstation works but when it shuts down from the usb stick I see these pcie messages just before it closes.

All of them have high fan activity and the CPU is still hot when I get back into the BIOS, around 45 degrees. By contrast Fedora on the Laptop is very quiet with minimal cpu activity no errors and just the usual fans turning on briefly when there is a bit of activity.

I checked online and found a reference where CUPS was causing systemd problems, I ran a command to shut CUPS down but it made no difference. I would think in this case it is the pcie problem doing it.

I'm 80% happy with the system I bought but would like Linux on it. One option might be to take it back and pay for a motherboard replacement, any suggestions welcome on a good linux motherboard for i7 8th gen. Or better still a fix for this issue.

This is the motherboard: https://www.asus.com/au/Motherboards...-H310M-E-R2-0/

I found a list of Asus motherboards and Linux https://dlcdnimgs.asus.com/websites/...760.1586244757

That list does show models of the Prime running linux, possibly not my "E" variant due to the list being a few years old.

PRIME H310M-A R2.0 Fedora 28 N/A N/A Ubuntu 18.04
PRIME H310M-C N/A N/A RedHat 7.4 N/A
PRIME H310M-D N/A OpenSUSE 42.3 N/A N/A
PRIME H310M-D R2.0 Fedora 28 N/A N/A Ubuntu 18.04
PRIME H310M-DASH Fedora v27 OpenSUSE 15.0 RedHat 7.5 Ubuntu 18.04
PRIME H310-PLUS R2.0 Fedora 28 N/A N/A Ubuntu 18.04

Regards, David.

rokytnji · 05-16-2020, 06:08 AM

Has lmsensors been ran in Mint so you can post the output of the command

Code:

sensors

Usually when I have hardware acting weird. Like some harware component heating up and dropping the computer down. First thing I try is a canned kernel change.

Mint has the command

Code:

inxi

in it also. Can;t speak for the other distros mentioned.

Good luck.

rokytnji · 05-16-2020, 07:50 AM

Also forgot to mention. dmesg command is my friend when I situations like this.

I am not hip on systemd trouble shooting tools though, maybe some other member can help with that.

Redhat wants money for dmesg support so I'll have to show other link

https://www.thegeekstuff.com/2010/10...mand-examples/

Code:

harry@biker:~
$ dmesg --help

Usage:
 dmesg [options]

Display or control the kernel ring buffer.

Options:
 -C, --clear                 clear the kernel ring buffer
 -c, --read-clear            read and clear all messages
 -D, --console-off           disable printing messages to console
 -E, --console-on            enable printing messages to console
 -F, --file <file>           use the file instead of the kernel log buffer
 -f, --facility <list>       restrict output to defined facilities
 -H, --human                 human readable output
 -k, --kernel                display kernel messages
 -L, --color[=<when>]        colorize messages (auto, always or never)
                               colors are enabled by default
 -l, --level <list>          restrict output to defined levels
 -n, --console-level <level> set level of messages printed to console
 -P, --nopager               do not pipe output into a pager
 -p, --force-prefix          force timestamp output on each line of multi-line messages
 -r, --raw                   print the raw message buffer
 -S, --syslog                force to use syslog(2) rather than /dev/kmsg
 -s, --buffer-size <size>    buffer size to query the kernel ring buffer
 -u, --userspace             display userspace messages
 -w, --follow                wait for new messages
 -x, --decode                decode facility and level to readable string
 -d, --show-delta            show time delta between printed messages
 -e, --reltime               show local time and time delta in readable format
 -T, --ctime                 show human-readable timestamp (may be inaccurate!)
 -t, --notime                don't show any timestamp with messages
     --time-format <format>  show timestamp using the given format:
                               [delta|reltime|ctime|notime|iso]
Suspending/resume will make ctime and iso timestamps inaccurate.

 -h, --help                  display this help
 -V, --version               display version

Supported log facilities:
    kern - kernel messages
    user - random user-level messages
    mail - mail system
  daemon - system daemons
    auth - security/authorization messages
  syslog - messages generated internally by syslogd
     lpr - line printer subsystem
    news - network news subsystem

Supported log levels (priorities):
   emerg - system is unusable
   alert - action must be taken immediately
    crit - critical conditions
     err - error conditions
    warn - warning conditions
  notice - normal but significant condition
    info - informational
   debug - debug-level messages

For more details see dmesg(1).
harry@biker:~
$

Pythagorus · 05-17-2020, 05:44 AM

Quote:

Originally Posted by rokytnji

Has lmsensors been ran in Mint so you can post the output of the command

Code:

sensors

Usually when I have hardware acting weird. Like some harware component heating up and dropping the computer down. First thing I try is a canned kernel change.

Mint has the command

Code:

inxi

in it also. Can;t speak for the other distros mentioned.

Good luck.

I loaded Fedora Workstation as a live from USB stick and got as far as installing inxi and then ran inxi, moved the mouse over the screen to start a word processor and the mouse froze, control alt backspace didn't work, push the reboot key. Went to bios on reboot and by that time it was 38 degrees, not particularly hot, might have been say 50 in linux. I think the best line of approach is the data that systemd has some sort of problem, which we know from the output of top, and that IRQ the second item, has something to do with it.

This motherboard is two years old and I sort of thought that might help it have linux support, but there are so many motherboards that odd ones not widely used probably won't ever get supported.

I went to the Computer shop and discussed changing the motherboard, it is probably the cheapest part of the system. The guy suggested an MSI MAG B365M Mortar motherboard. Of course I need to check up on whether that would work with linux before putting it in. Thanks for your help and interest.