strange kernel warnings

    • OMV 1.0
    • Resolved
    • strange kernel warnings

      Hi there,

      i have some strange error messages with:

      dmesg -t | grep -i 'error\|warn\|exception'

      can someone tell me if there is something to pay attention?
      The ACPI error seems to be ausus specific?!
      What is the meaning of the EXT4-fs and "aufs" message?

      thanks a lot for your help to get the omv running well

      Display Spoiler

      ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20140424/hwxface-580)
      ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20140424/hwxface-580)
      ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20140424/psargs-359)
      ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT3._GTF] (Node ffff88011f053a18), AE_NOT_FOUND (20140424/psparse-536)
      ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20140424/psargs-359)
      ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT4._GTF] (Node ffff88011f0679a0), AE_NOT_FOUND (20140424/psparse-536)
      ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20140424/psargs-359)
      ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT5._GTF] (Node ffff88011f067928), AE_NOT_FOUND (20140424/psparse-536)
      ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20140424/psargs-359)
      ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT3._GTF] (Node ffff88011f053a18), AE_NOT_FOUND (20140424/psparse-536)
      ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20140424/psargs-359)
      ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT4._GTF] (Node ffff88011f0679a0), AE_NOT_FOUND (20140424/psparse-536)
      ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20140424/psargs-359)
      ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT5._GTF] (Node ffff88011f067928), AE_NOT_FOUND (20140424/psparse-536)
      ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20140424/psargs-359)
      ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT0._GTF] (Node ffff88011f053b80), AE_NOT_FOUND (20140424/psparse-536)
      ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20140424/psargs-359)
      ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT0._GTF] (Node ffff88011f053b80), AE_NOT_FOUND (20140424/psparse-536)
      ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20140424/psargs-359)
      ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT2._GTF] (Node ffff88011f053a90), AE_NOT_FOUND (20140424/psparse-536)
      ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20140424/psargs-359)
      ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT2._GTF] (Node ffff88011f053a90), AE_NOT_FOUND (20140424/psparse-536)
      ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20140424/psargs-359)
      ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT1._GTF] (Node ffff88011f053b08), AE_NOT_FOUND (20140424/psparse-536)
      ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20140424/psargs-359)
      ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT1._GTF] (Node ffff88011f053b08), AE_NOT_FOUND (20140424/psparse-536)
      ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042f conflicts with OpRegion 0x0000000000000400-0x000000000000047f (\PMIO) (20140424/utaddress-258)
      ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054f conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20140424/utaddress-258)
      ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053f conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20140424/utaddress-258)
      ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052f conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20140424/utaddress-258)
      ACPI Warning: SystemIO range 0x000000000000f040-0x000000000000f05f conflicts with OpRegion 0x000000000000f040-0x000000000000f04f (\_SB_.PCI0.SBUS.SMBI) (20140424/utaddress-258)
      EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro
      aufs: module is from the staging directory, the quality is unknown, you have been warned.

      | backport-kernel-3.16 | asus-p8h77-i | intel-g840 | 4GB | ocz-vertex2-60G | 2*Hitachi7K1000-raid1-ext4
    • Looks like one of your drives gets remounted read-only, allthough i can't tell you why...

      Greetings
      David
      "Well... lately this forum has become support for everything except omv" [...] "And is like someone is banning Google from their browsers"

      Only two things are infinite, the universe and human stupidity, and I'm not sure about the former.


      Upload Logfile via WebGUI/CLI
      #openmediavault on freenode IRC | German & English | GMT+1
      Absolutely no Support via PM!

      I host parts of the omv-extras.org Repository, the OpenMediaVault Live Demo and the pre-built PXE Images. If you want you can take part and help covering the costs by having a look at my profile page.
    • No, it isn't critical. aufs is being phased out for overlayfs. But, it should never be removed from Wheezy kernels.
      omv 4.1.13 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.13
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • The answer from another forum:
      (EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro)


      It's not an error, it just tells you that the partition /dev/sda1 has been remounted with the mount option errors=remount-ro. It's nothing you need to worry about. It may happen e.g. during a normal system startup if /dev/sda1 is your root partition.

      The mount option means that the system should mount the partition
      read-only if an error occurs to minimize further damage or data loss and
      is used by default.
      | backport-kernel-3.16 | asus-p8h77-i | intel-g840 | 4GB | ocz-vertex2-60G | 2*Hitachi7K1000-raid1-ext4
    • I have the same errors.
      Is there a way to fix them?

      Source Code

      1. ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160108/psargs-359)
      2. ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT4._GTF] (Node ffff88081f4ee870), AE_NOT_FOUND (20160108/psparse-542)
      3. ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160108/psargs-359)
      4. ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT5._GTF] (Node ffff88081f4ee7f8), AE_NOT_FOUND (20160108/psparse-542)
      5. ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160108/psargs-359)
      6. ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT4._GTF] (Node ffff88081f4ee870), AE_NOT_FOUND (20160108/psparse-542)
      7. ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160108/psargs-359)
      8. ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT5._GTF] (Node ffff88081f4ee7f8), AE_NOT_FOUND (20160108/psparse-542)
      9. ACPI Warning: SystemIO range 0x000000000000F040-0x000000000000F05F conflicts with OpRegion 0x000000000000F040-0x000000000000F04F (\_SB.PCI0.SBUS.SMBI) (20160108/utaddress-255)
      10. EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro
      OMV v4.0
      Asus Z97-A/3.1; i3-4370
      32GB RAM Corsair Vengeance Pro
      4x3TB RAID10
    • tinh_x7 wrote:

      I have the same errors.
      Is there a way to fix them?

      Source Code

      1. ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160108/psargs-359)
      2. ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT4._GTF] (Node ffff88081f4ee870), AE_NOT_FOUND (20160108/psparse-542)
      3. ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160108/psargs-359)
      4. ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT5._GTF] (Node ffff88081f4ee7f8), AE_NOT_FOUND (20160108/psparse-542)
      5. ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160108/psargs-359)
      6. ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT4._GTF] (Node ffff88081f4ee870), AE_NOT_FOUND (20160108/psparse-542)
      7. ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160108/psargs-359)
      8. ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT5._GTF] (Node ffff88081f4ee7f8), AE_NOT_FOUND (20160108/psparse-542)
      9. ACPI Warning: SystemIO range 0x000000000000F040-0x000000000000F05F conflicts with OpRegion 0x000000000000F040-0x000000000000F04F (\_SB.PCI0.SBUS.SMBI) (20160108/utaddress-255)
      10. EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro
      AFAIK those messages have something to do with your bios. If there is a bios update from you motherboard manufacturer you could flash it and see if that solves those error lines.
    • Looks like the only way to fix is get a new bios (due to bios bug) or disable acpi. If you never turn off your server, disabling acpi might work. If you are compiling your own kernel and you don't use ATA, you could try disabling libata/ata. That would take some experimenting on your part.
      omv 4.1.13 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.13
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • I see.

      My server lately has this error message upon resume from hibernation, and sometimes prevent from hibernation.
      If I restart the computer, then later it hibernates without any issue.


      Source Code

      1. e1000e 0000:02:00.0 eth1: speed changed to 0 for port eth1
      2. e1000e 0000:07:00.0 eth2: speed changed to 0 for port eth2
      Any idea how to fix this?

      I'm using kernel 4.6.4.

      Display Spoiler
      bond0 Link encap:Ethernet HWaddr 68:05:ca:40:18:d5
      inet addr:192.168.1.97 Bcast:192.168.1.255 Mask:255.255.255.0
      UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
      RX packets:3181 errors:0 dropped:114 overruns:0 frame:0
      TX packets:8552 errors:0 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:1000
      RX bytes:1038348 (1014.0 KiB) TX bytes:10970210 (10.4 MiB)

      eth0 Link encap:Ethernet HWaddr 08:62:66:c7:3c:af
      BROADCAST MULTICAST MTU:1500 Metric:1
      RX packets:0 errors:0 dropped:0 overruns:0 frame:0
      TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:1000
      RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
      Interrupt:20 Memory:dff00000-dff20000

      eth1 Link encap:Ethernet HWaddr 68:05:ca:40:18:d5
      UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
      RX packets:2983 errors:0 dropped:0 overruns:0 frame:0
      TX packets:8534 errors:0 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:1000
      RX bytes:1009200 (985.5 KiB) TX bytes:10967906 (10.4 MiB)
      Interrupt:17 Memory:dfec0000-dfee0000

      eth2 Link encap:Ethernet HWaddr 68:05:ca:40:18:d5
      UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
      RX packets:198 errors:0 dropped:0 overruns:0 frame:0
      TX packets:18 errors:0 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:1000
      RX bytes:29148 (28.4 KiB) TX bytes:2304 (2.2 KiB)
      Interrupt:19 Memory:dfcc0000-dfce0000

      lo Link encap:Local Loopback
      inet addr:127.0.0.1 Mask:255.0.0.0
      inet6 addr: ::1/128 Scope:Host
      UP LOOPBACK RUNNING MTU:65536 Metric:1
      RX packets:9223 errors:0 dropped:0 overruns:0 frame:0
      TX packets:9223 errors:0 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:1
      RX bytes:1239183 (1.1 MiB) TX bytes:1239183 (1.1 MiB)

      tun0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
      inet addr:10.8.0.1 P-t-P:10.8.0.2 Mask:255.255.255.255
      UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
      RX packets:0 errors:0 dropped:0 overruns:0 frame:0
      TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:100
      RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

      OMV v4.0
      Asus Z97-A/3.1; i3-4370
      32GB RAM Corsair Vengeance Pro
      4x3TB RAID10

      The post was edited 1 time, last by tinh_x7 ().

    • The problem with using a non-standard kernel is that not many people are using them including me and the other mods. Hard to say what is causing the issue.
      omv 4.1.13 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.13
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!