Do I need to be concerned about this error in dmesg

[GCandy77]

Hi,

 

Im trying to figure out why steam sends my pc into kernel panic/overload when I run it and I ran the sudo dmesg command and came across a few errors that im not to sure if I need to be concerned about ?

 

The 1st is -

 

ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F conflicts with OpRegion 0x0000000000000400-0x000000000000047F (\PMIO) (20200528/utaddress-204)
[    2.693013] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[    2.693016] ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054F conflicts with OpRegion 0x0000000000000500-0x000000000000057F (\_SB.PCI0.LPCB.GPBX) (20200528/utaddress-204)
[    2.693018] ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20200528/utaddress-204)
[    2.693020] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[    2.693021] ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000000500-0x000000000000057F (\_SB.PCI0.LPCB.GPBX) (20200528/utaddress-204)
[    2.693023] ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20200528/utaddress-204)
[    2.693024] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[    2.693025] ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x000000000000057F (\_SB.PCI0.LPCB.GPBX) (20200528/utaddress-204)
[    2.693027] ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x000000000000050F (\_GPE.GPIO) (20200528/utaddress-204)
[    2.693029] ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20200528/utaddress-204)

 

and the 2nd -

 

systemd[1]: /lib/systemd/system/dbus.service:12: Unit configured to use KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update your service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed.
[    5.284235] systemd[1]: /lib/systemd/system/plymouth-start.service:17: Unit configured to use KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update your service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed.

 

 

Apart from the pre-mentioned issue with steam ... everything seems to be working fine, so Im wondering do I need to worry about this or not?

 

Also im still learning Linux .. Is dmesg a log of all the system initializing sequence / Os booting up & if not what is it generally used for ?

 

Thx for reading

 

[mahyar]

full specs?

seems like a driver error

[mahyar]

also what distro are you using?

[GCandy77]

pop os 20.10

i5 2500, r9 290 , 16 gb ram,

using the oibaf drivers

 

Is that what you mean?

[GCandy77]

I dont know if this helps

 

but when I ran uname -ar  it tells me this

 

Linux pop-os 5.8.0-7630-generic #32~1609193707~20.10~781bb80-Ubuntu SMP Tue Jan 5 21:29:56 UTC 2 x86_64 x86_64 x86_64 GNU/Linux

 

The steam issues started x2 days ago, so Im suspecting that maybe once again a kernel change is causing havoc with my GPU drivers, u think that this could be the case?

 

 

[Dutch_Master]

Do the following, in a terminal:

sudo su <enter password on request>
apt-get update && apt-get dist-upgrade
exit

The 1st line gives you "permanent" root powers, the 2nd line completely updates your system and the last line drops your privileges back to normal. (which is what you want, root is very dangerous if you don't know what you're doing!)

[Nayr438]

What is the output of the following

• dmesg | grep 'conflict\|acpi\|error'

 

What motherboard are you using?

 

2 hours ago, GCandy77 said:

Also im still learning Linux .. Is dmesg a log of all the system initializing sequence / Os booting up & if not what is it generally used for ?

dmesg is a tool the prints a log of the kernel output buffer.

[GCandy77]

3 hours ago, Nayr438 said:

dmesg is a tool the prints a log of the kernel output buffer.

Thx

 

Output of the command is

 

r@pop-os:~$ sudo dmesg | grep 'conflict\|acpi\|error'
[sudo] password for r:
[    0.064444] ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1])
[    0.162557] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
[    0.181123] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI HPX-Type3]
[    0.181279] acpi PNP0A08:00: _OSC: platform does not support [PCIeHotplug SHPCHotplug PME]
[    0.181424] acpi PNP0A08:00: _OSC: OS now controls [AER PCIeCapability LTR]
[    0.181425] acpi PNP0A08:00: FADT indicates ASPM is unsupported, using BIOS configuration
[    0.212436] clocksource: acpi_pm: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns
[    2.693010] ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F conflicts with OpRegion 0x0000000000000400-0x000000000000047F (\PMIO) (20200528/utaddress-204)
[    2.693016] ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054F conflicts with OpRegion 0x0000000000000500-0x000000000000057F (\_SB.PCI0.LPCB.GPBX) (20200528/utaddress-204)
[    2.693018] ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20200528/utaddress-204)
[    2.693021] ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000000500-0x000000000000057F (\_SB.PCI0.LPCB.GPBX) (20200528/utaddress-204)
[    2.693023] ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20200528/utaddress-204)
[    2.693025] ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x000000000000057F (\_SB.PCI0.LPCB.GPBX) (20200528/utaddress-204)
[    2.693027] ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x000000000000050F (\_GPE.GPIO) (20200528/utaddress-204)
[    2.693029] ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20200528/utaddress-204)
[    2.693031] lpc_ich: Resource conflict(s) found affecting gpio_ich
[    3.838425] system76_acpi: loading out-of-tree module taints kernel.
[    3.838451] system76_acpi: module verification failed: signature and/or required key missing - tainting kernel
[    5.363606] EXT4-fs (sda3): re-mounted. Opts: errors=remount-ro
[    6.257724] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: errors=remount-ro

 

 

sudo lshw output for motherboard is

 

description: Motherboard
       product: P8H61-M LE/USB3
       vendor: ASUSTeK COMPUTER INC.
       physical id: 0
       version: Rev x.0x
       serial: 111623390003247
       slot: To be filled by O.E.M.
     *-firmware
          description: BIOS
          vendor: American Megatrends Inc.
          physical id: 0
          version: 4601
          date: 09/18/2013
          size: 64KiB
          capacity: 4MiB
          capabilities: pci upgrade shadowing cdboot bootselect socketedrom edd int13floppy1200 int13floppy720 int13floppy2880 int5printscreen int9keyboard int14serial int17printer acpi usb biosbootspecification

 

 

I do have a weird audio issue that I never resolved it happens in windows 7 & 10 too so I know it not a linux issue .... every now n then the audio would switch from speaker to earphones - even when there were no earphones plugged in .. I could not figure the issue out and went out and bought a sound card, but the issue remains?    It happens so little that i never really got round to fixing it, so that may be the answer to one of the error.

 

The one I concerned about is the "KillMode=none. This is unsafe" one as Im aware systemd is an important component of linux, but am unsure if its a concern?

 

I will try dutch masters suggestion n see if that changes anything

[Chunchunmaru_]

Those are just ACPI errors, nothing you can do about it, or to worry about.

A BIOS or kernel update may change the dmesg output

[GCandy77]

14 hours ago, Chunchunmaru_ said:

Those are just ACPI errors, nothing you can do about it, or to worry about.

A BIOS or kernel update may change the dmesg output

Ok thx

 

You have any idea about the "systemd / KillMode=none" errors?  .... My reading had reached its limit of understanding regarding this one

[Wild Penquin]

The most important question which is needed to be asked, is: what is the actual problem you are facing?

 

It seems you have an idea about what the problem is and are trying to solve the problem that way, but it also seems this idea is way off track. This is a really common mistake people make: assume you know what you are doing (when you don't). Hence: we need the answer to the question above!

 

EDIT: In essence, the problem is similar to this. Also, this part on the same guide seems relevant. I think I've seen better examples of a similar, badly formed question, in other how-to-ask-questions guides, but can't find them right now.

 

Also:
 

On 1/7/2021 at 11:01 PM, GCandy77 said:

 

Im trying to figure out why steam sends my pc into kernel panic/overload

 

How have you determined there is a kernel panic? What do you mean by a Kernel overload (there is no such thing/term in common usage AFAIK)?

 

For Kernel panics, you should get literally that in the system log (Google will find some examples, look for example here) - unless the Kernel panics in such a way it can not use journald, in which case you need a serial adapter or something similar. For other Kernel (non-panic) bugs, you should get sections with ------[ cut here ]-------- which are ending in ---[end trace SOMEHEXSTRING ]--- .

 

Nothing in your log messages points to any kind of real error / problem IMHO. The syslog (and dmesg) gets spammed by all kinds of stuff, warnings etc; ACPI errors/warnings are very common (as the whole spec seems to be a mess and/or manufacturers don't adhere to the spec or something ... but I'm just a layman and don't know about the details that much). The KillMode=none is probably just some feature / option configured that way in the relevant systemd service unit (in a bit outdated way). The sensible way to make sure is to look at the .service file and look up the systemd documentation.

 

What you can do when you face something weird in the logs, is to Google search them up and try to find the relevant documentation. But you also need to be sure (well, at least have a good hunch) the errors are actually relevant. If looking up at irrelevant error messages and their documentation, you are just wasting time (but yeah... this step can be difficult and time consuming!).

 

Generally: Dmesg messages are really useful only if your system does not seem to initialize correctly; for example, if some device (sound, display, mouse/keyboard ...)  is not working properly etc.. Conversely: If everything seems to work fine after a boot, but you get some oddball crashes / hangs / other problems, you should look into the system log messages right before the problem surfaces (not dmesg errors, as they are probably totally irrelevant - though, this is not always the case).

Edited January 10, 2021 by Wild Penquin
Emphasis / minor additions in (); TYPOs