dmesg errors

Questions about hardware,drivers and peripherals
Forum rules
Before you post please read how to get help
Mithrandir
Level 2
Level 2
Posts: 66
Joined: Thu Jun 28, 2012 3:14 am

dmesg errors

Postby Mithrandir » Mon Nov 06, 2017 4:40 pm

Hi, I see some problems in my dmesg output.
I had to insert in grub the acpi_osi= parameter to configure the function keys on my laptop. I don't know if it is this the problem, but in the boot there is these errors:

Code: Select all

$ dmesg | grep fail
[    0.160500] ACPI Error: [_SB_.PCI0.RP01.PXSX] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359)
[    0.160508] ACPI Error: Method parse/execution failed [\] (Node ffffffff8e3f3640), AE_NOT_FOUND (20160930/psparse-543)
[    0.192422] ACPI Error: [_OSI] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359)
[    0.192428] ACPI Error: Method parse/execution failed [\_SB.PAGD._STA] (Node ffff8fd13b0d2668), AE_NOT_FOUND (20160930/psparse-543)
[    0.192446] ACPI Error: [_OSI] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359)
[    0.192448] ACPI Error: Method parse/execution failed [\_SB.PAGD._STA] (Node ffff8fd13b0d2668), AE_NOT_FOUND (20160930/psparse-543)
[    0.224085] ACPI Error: [_OSI] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359)
[    0.224091] ACPI Error: Method parse/execution failed [\_SB.PAGD._STA] (Node ffff8fd13b0d2668), AE_NOT_FOUND (20160930/psparse-543)
[    0.268603] ACPI Error: [_OSI] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359)
[    0.268608] ACPI Error: Method parse/execution failed [\_SB.PAGD._STA] (Node ffff8fd13b0d2668), AE_NOT_FOUND (20160930/psparse-543)
[    3.630631] tpm_crb: probe of MSFT0101:00 failed with error -16
[    3.766824] nvidia: module verification failed: signature and/or required key missing - tainting kernel
[    3.795531] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-7265D-26.ucode failed with error -2
[    3.796964] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-7265D-25.ucode failed with error -2
[    3.798038] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-7265D-24.ucode failed with error -2
[    3.798073] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-7265D-23.ucode failed with error -2

the complete output of dmesg is here: https://pastebin.com/hePxGgth
Anyone could help me to understand if I can improve the boot?
Thanks in advance!
Last edited by Mithrandir on Tue Nov 07, 2017 11:24 am, edited 1 time in total.

Mute Ant
Level 12
Level 12
Posts: 4111
Joined: Tue Sep 03, 2013 7:45 pm

Re: dmesg errors

Postby Mute Ant » Mon Nov 06, 2017 6:02 pm

"insert in grub the acpi_os= parameter " The parameter goes...

acpi_os=Linux

...or...

acpi_os=Windows

...those parse errors suggest you didn't actually specify an OS?
Armageddon only happens once, you know. They don’t let you go around again until you get it right.

Mithrandir
Level 2
Level 2
Posts: 66
Joined: Thu Jun 28, 2012 3:14 am

Re: dmesg errors

Postby Mithrandir » Tue Nov 07, 2017 4:02 am

Thanks Mute Ant, you're right, the howto that I followed didn't indicate nothing to insert as OS. I wrote now acpi_osi=Linux in the grub line. These the output:

Code: Select all

$ dmesg | grep fail
[    0.160367] ACPI Error: [_SB_.PCI0.RP01.PXSX] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359)
[    0.160375] ACPI Error: Method parse/execution failed [\] (Node ffffffff9cbf3640), AE_NOT_FOUND (20160930/psparse-543)
[    3.433820] tpm_crb: probe of MSFT0101:00 failed with error -16
[    3.576324] nvidia: module verification failed: signature and/or required key missing - tainting kernel
[    3.602824] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-7265D-26.ucode failed with error -2
[    3.603009] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-7265D-25.ucode failed with error -2
[    3.603215] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-7265D-24.ucode failed with error -2
[    3.603229] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-7265D-23.ucode failed with error -2
$ dmesg | grep rror
[    0.160367] ACPI Error: [_SB_.PCI0.RP01.PXSX] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359)
[    0.160375] ACPI Error: Method parse/execution failed [\] (Node ffffffff9cbf3640), AE_NOT_FOUND (20160930/psparse-543)
[    3.322958] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro
[    3.433820] tpm_crb: probe of MSFT0101:00 failed with error -16
[    3.602824] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-7265D-26.ucode failed with error -2
[    3.603009] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-7265D-25.ucode failed with error -2
[    3.603215] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-7265D-24.ucode failed with error -2
[    3.603229] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-7265D-23.ucode failed with error -2
[    4.149987] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro,data=ordered,commit=600

The whole dmesg output: https://pastebin.com/7Y69nYAs
With acpi_os=WIndows the output is similar. Could we solve these errors?
Last edited by Mithrandir on Tue Nov 07, 2017 10:17 am, edited 1 time in total.

Mute Ant
Level 12
Level 12
Posts: 4111
Joined: Tue Sep 03, 2013 7:45 pm

Re: dmesg errors

Postby Mute Ant » Tue Nov 07, 2017 7:39 am

I don't think we can solve them, partly because I don't get them on Mint 17.3 with kernel 3.19. Google...
"Namespace lookup failure, AE_NOT_FOUND"
...there's lots of geek-speak trying to find it and fix it...
https://bugzilla.redhat.com/show_bug.cgi?id=1413342
...you know it's desperate guessing when someone suggests upgrading the BIOS.

If the errors are spoiling your OS, consider regressing to something older. I went back to KDE Mint 17.3 last year... the new one is still shaking-down with systemd and Plasma 5... I found too many rough-edges to be comfortable using it.

If it's not spoiling your OS, just ignore it, maybe?
Armageddon only happens once, you know. They don’t let you go around again until you get it right.

Mithrandir
Level 2
Level 2
Posts: 66
Joined: Thu Jun 28, 2012 3:14 am

Re: dmesg errors

Postby Mithrandir » Tue Nov 07, 2017 9:43 am

The system works fine, so far it is the best system I have ever experienced on this machine. About these warnings... "if you can't beat them, join them" :D
I was only trying to improve the boot sequence. Regressing on a older system I believe it is not an option on a new machine like this (Asus UX303), I should find other problems.
Thanks for your help! =)

Hoser Rob
Level 9
Level 9
Posts: 2830
Joined: Sat Dec 15, 2012 8:57 am

Re: dmesg errors

Postby Hoser Rob » Tue Nov 07, 2017 10:02 am

acpi_os=Linux

... is wrong. The correct expression is ...

acpi_osi=Linux

Mithrandir
Level 2
Level 2
Posts: 66
Joined: Thu Jun 28, 2012 3:14 am

Re: dmesg errors

Postby Mithrandir » Tue Nov 07, 2017 10:20 am

yes, in the grub file it's correct. If you look at the dmesg in pastebin you see that it's correct. I was wrong to write here in the post, I corrected it now


Return to “Hardware Support”