Bug 109691

There are a couple of problems here
1. "pci=nommconf" is needed to boot
2. tpm_crb driver calltrace in dmesg
3. ieee80211_tx calltrace in dmesg
4. hibernate failure

IMO, any of the first three problems may break hibernation, thus we should try to fix the first three issues separately and then check how hibernation goes on this laptop.

Move to PCI category to get Problem 1 fixed first.

Thank you very much for this report.  It's a pretty serious problem when we can't boot at all.

"pcieport 0000:00:... id=00E5(Receiver ID)" looks like an AER message.  Please try turning off AER with "pci=noaer".  If you can boot with "pci=noaer" and without "pci=nommconf", please attach the dmesg log.

Here's a report of another similar AER problem:

  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521173

Created attachment 198481 [details]
Updated dmesg with pci=noaer

It booted no problem after replacing pci=nommconf with pci=noaer as suggested.  See updated dmesg.txt as requested.

Thanks!

Great, thank you!  I understand the AER bug (see http://lkml.kernel.org/r/20151229155822.GA17321@localhost); now we just need to figure out a fix.

Excellent.
Thanks Bjorn.  
Great to see you have isolated the problem.

All the best in 2016!

Any other details you require from me let me know I will update this post.

Cheers!

Looks like I have this same problem (with the same hardware).  Adding my name to the list, using Ubuntu's Xubuntu 15.10 distro.  The pci=noaer works, although pci=nomsi also works.

Strangely enough, Knoppix 7.6.1 boots just fine.  Hmmm...

Just an update.
confirmed Kelly Price's discovery: Knoppix 7.6.1 with kernel 4.2.6 boots fine.
Thanks Kelly.

I flash updated the BIOS to latest vendor supplied version 206 (2016/02/24).

Latest Ubuntu 16.04 with kernel 4.4 still has the same problem.

Hello to all. I have the same problem, and this has affected me for a long time now. I described it in detail here, with output, videos, photos etc:

https://ubuntuforums.org/showthread.php?t=2460318

I hope this adds useful information to draw attention to the bug in question.

As the ASUS X541UVK is a different device, please create a new bug report with all the necessary information included/attached.

Riccardo, would you mind booting with just "pci=noaer" to see if that works around the problem?  Your photo at https://i.imgur.com/PPZ49lL.jpg suggests that it might.

Created attachment 299043 [details]
Patch for the AER message spew

Hello Folks,

I have been working on a patch for the AER message spew. I have a potential patch ready for the problem, but unfortunately, I do not have a system that outputs the same AER errors so I am unable to test it out.

It would really help if anyone could please test this patch and see if it solved the AER message spew.

Thanks,
Naveen Naidu

(In reply to Naveen Naidu from comment #11)
> Created attachment 299043 [details]
> Patch for the AER message spew
> 
> Hello Folks,
> 
> I have been working on a patch for the AER message spew. I have a potential
> patch ready for the problem, but unfortunately, I do not have a system that
> outputs the same AER errors so I am unable to test it out.
> 
> It would really help if anyone could please test this patch and see if it
> solved the AER message spew.
> 
> Thanks,
> Naveen Naidu

Forgot to mention! This patch would make the "pci=noaer" unnecessary.

Created attachment 299047 [details]
attachment-6460-0.html

Hi Naveen.
Absolutely, I can test.
I can try it out this weekend.


Chris

⁣Get BlueMail for Android ​

On Oct 1, 2021, 2:35 AM, at 2:35 AM, bugzilla-daemon@bugzilla.kernel.org wrote:
>https://bugzilla.kernel.org/show_bug.cgi?id=109691
>
>Naveen Naidu (naveennaidu479@gmail.com) changed:
>
>           What    |Removed                     |Added
>----------------------------------------------------------------------------
>               CC|                            |naveennaidu479@gmail.com
>
>--- Comment #11 from Naveen Naidu (naveennaidu479@gmail.com) ---
>Created attachment 299043 [details]
>  --> https://bugzilla.kernel.org/attachment.cgi?id=299043&action=edit
>Patch for the AER message spew
>
>Hello Folks,
>
>I have been working on a patch for the AER message spew. I have a
>potential
>patch ready for the problem, but unfortunately, I do not have a system
>that
>outputs the same AER errors so I am unable to test it out.
>
>It would really help if anyone could please test this patch and see if
>it
>solved the AER message spew.
>
>Thanks,
>Naveen Naidu
>
>-- 
>You may reply to this email to add a comment.
>
>You are receiving this mail because:
>You reported the bug.

Comment on attachment 299043 [details]
Patch for the AER message spew

I apologize, please ignore this patch. I realized there is a bug in the patch. I have fixed it now and will upload it. I apologized for the inconvenience caused. I do not know how to delete this patch, so I'll reupload a new patch. Apologies again ^^'

Created attachment 299071 [details]
Patch for the AER message spew

This is the correct patch. Please use this and ignore the previous patch.

Created attachment 299073 [details]
Patch for the AER message spew

Created attachment 299081 [details]
attachment-4100-0.html

Okay sounds good.
I will try it soon.

Chris

⁣Get BlueMail for Android ​

On Oct 3, 2021, 2:03 AM, at 2:03 AM, bugzilla-daemon@bugzilla.kernel.org wrote:
>https://bugzilla.kernel.org/show_bug.cgi?id=109691
>
>Naveen Naidu (naveennaidu479@gmail.com) changed:
>
>           What    |Removed                     |Added
>----------------------------------------------------------------------------
> Attachment #299043 [details]|0                           |1
>        is obsolete|                            |
>
>--- Comment #15 from Naveen Naidu (naveennaidu479@gmail.com) ---
>Created attachment 299071 [details]
>  --> https://bugzilla.kernel.org/attachment.cgi?id=299071&action=edit
>Patch for the AER message spew
>
>This is the correct patch. Please use this and ignore the previous
>patch.
>
>--
>You may reply to this email to add a comment.
>
>You are receiving this mail because:
>You reported the bug.

Are you good with me using kernel: 5.11.0-37-generic  or would you 
prefer I use a different kernel?
The X555U is currently running Linux Mint 20.2 Cinnamon.

FYI:
I tried removing pci=noaer and it does boot now (without your patch).
It has been a while since I tried removing pci=noaer and new kernels get 
installed all the time so not sure what kernel first started allowing it 
to boot without needing that line.
However, there are still many errors on boot.

dmesg --level=err,warn
[    0.105337] x86/cpu: VMX (outside TXT) disabled by BIOS
[    0.110761] MDS CPU bug present and SMT on, data leak possible. See 
https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html for 
more details.
[    0.110761]  #3
[    0.114598] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
[    0.135583] ACPI BIOS Error (bug): Could not resolve symbol 
[\_SB.PCI0.RP01.PXSX], AE_NOT_FOUND (20201113/psargs-330)
[    0.135597] ACPI Error: Skipping While/If block (20201113/psloop-427)
[    0.527786] tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not 
cover the entire command/response buffer. [mem 0xfed40000-0xfed4087f 
flags 0x200] vs fed40080 f80
[    0.527874] tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not 
cover the entire command/response buffer. [mem 0xfed40000-0xfed4087f 
flags 0x200] vs fed40080 f80
[    0.736009] i8042: PNP: PS/2 appears to have AUX port disabled, if 
this is incorrect please boot with i8042.nopnp
[    0.738042] platform eisa.0: EISA: Cannot allocate resource for mainboard
[    0.738044] platform eisa.0: Cannot allocate resource for EISA slot 1
[    0.738045] platform eisa.0: Cannot allocate resource for EISA slot 2
[    0.738046] platform eisa.0: Cannot allocate resource for EISA slot 3
[    0.738048] platform eisa.0: Cannot allocate resource for EISA slot 4
[    0.738049] platform eisa.0: Cannot allocate resource for EISA slot 5
[    0.738050] platform eisa.0: Cannot allocate resource for EISA slot 6
[    0.738051] platform eisa.0: Cannot allocate resource for EISA slot 7
[    0.738052] platform eisa.0: Cannot allocate resource for EISA slot 8
[    1.268806] r8169 0000:02:00.0: can't disable ASPM; OS doesn't have 
ASPM control
[    1.329939] i2c_hid i2c-ELAN1000:00: supply vdd not found, using 
dummy regulator
[    1.329973] i2c_hid i2c-ELAN1000:00: supply vddl not found, using 
dummy regulator
[    1.611704] ata1.00: supports DRM functions and may not be fully 
accessible
[    1.613394] ata1.00: supports DRM functions and may not be fully 
accessible
[    5.726419] elan_i2c i2c-ELAN1000:00: supply vcc not found, using 
dummy regulator
[    6.376762] nvidia: loading out-of-tree module taints kernel.
[    6.376775] nvidia: module license 'NVIDIA' taints kernel.
[    6.376776] Disabling lock debugging due to kernel taint

[    6.884240] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 470.63.01  
Tue Aug  3 20:44:16 UTC 2021
[    6.958699] nvidia_uvm: module uses symbols from proprietary module 
nvidia, inheriting taint.
[    8.533945] ACPI Warning: \_SB.PCI0.RP01.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20201113/nsarguments-61)

Chris

On 2021-10-03 2:03 a.m., bugzilla-daemon@bugzilla.kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=109691
>
> Naveen Naidu (naveennaidu479@gmail.com) changed:
>
>             What    |Removed                     |Added
> ----------------------------------------------------------------------------
>   Attachment #299043 [details]|0                           |1
>          is obsolete|                            |
>
> --- Comment #15 from Naveen Naidu (naveennaidu479@gmail.com) ---
> Created attachment 299071 [details]
>    --> https://bugzilla.kernel.org/attachment.cgi?id=299071&action=edit
> Patch for the AER message spew
>
> This is the correct patch. Please use this and ignore the previous patch.
>

(In reply to cspadijer from comment #18)
> Are you good with me using kernel: 5.11.0-37-generic  or would you 
> prefer I use a different kernel?
> The X555U is currently running Linux Mint 20.2 Cinnamon.
> 
> FYI:
> I tried removing pci=noaer and it does boot now (without your patch).
> It has been a while since I tried removing pci=noaer and new kernels get 
> installed all the time so not sure what kernel first started allowing it 
> to boot without needing that line.
> However, there are still many errors on boot.

The original bug seems to be solved now. As there are over ten comments already, could you mark it as fixed, and create new issues?

> dmesg --level=err,warn
> [    0.105337] x86/cpu: VMX (outside TXT) disabled by BIOS
> [    0.110761] MDS CPU bug present and SMT on, data leak possible. See 
> https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html for 
> more details.

Is GNU/Linux applying the latest microcode updates?

> [    0.110761]  #3

Cosmetic error.

> [    0.114598] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
> [    0.135583] ACPI BIOS Error (bug): Could not resolve symbol 
> [\_SB.PCI0.RP01.PXSX], AE_NOT_FOUND (20201113/psargs-330)
> [    0.135597] ACPI Error: Skipping While/If block (20201113/psloop-427)
> [    0.527786] tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not
> cover the entire command/response buffer. [mem 0xfed40000-0xfed4087f flags
> 0x200] vs fed40080 f80
> [    0.527874] tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not
> cover the entire command/response buffer. [mem 0xfed40000-0xfed4087f flags
> 0x200] vs fed40080 f80

Firmware issues.

> [    0.736009] i8042: PNP: PS/2 appears to have AUX port disabled, if this is
> incorrect please boot with i8042.nopnp

Can be ignored.

> [    0.738042] platform eisa.0: EISA: Cannot allocate resource for mainboard
> [    0.738044] platform eisa.0: Cannot allocate resource for EISA slot 1
> [    0.738045] platform eisa.0: Cannot allocate resource for EISA slot 2
> [    0.738046] platform eisa.0: Cannot allocate resource for EISA slot 3
> [    0.738048] platform eisa.0: Cannot allocate resource for EISA slot 4
> [    0.738049] platform eisa.0: Cannot allocate resource for EISA slot 5
> [    0.738050] platform eisa.0: Cannot allocate resource for EISA slot 6
> [    0.738051] platform eisa.0: Cannot allocate resource for EISA slot 7
> [    0.738052] platform eisa.0: Cannot allocate resource for EISA slot 8

Is there an EISA slot?

> [    1.268806] r8169 0000:02:00.0: can't disable ASPM; OS doesn't have ASPM
> control

Can be ignored.

> [    1.329939] i2c_hid i2c-ELAN1000:00: supply vdd not found, using dummy
> regulator
> [    1.329973] i2c_hid i2c-ELAN1000:00: supply vddl not found, using dummy
> regulator

Please contact the Linux folks about this. But first try the latest Linux mainline version.

> [    1.611704] ata1.00: supports DRM functions and may not be fully
> accessible
> [    1.613394] ata1.00: supports DRM functions and may not be fully
> accessible
> [    5.726419] elan_i2c i2c-ELAN1000:00: supply vcc not found, using dummy
> regulator
> [    6.376762] nvidia: loading out-of-tree module taints kernel.
> [    6.376775] nvidia: module license 'NVIDIA' taints kernel.
> [    6.376776] Disabling lock debugging due to kernel taint
> 
> [    6.884240] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 470.63.01  Tue
> Aug  3 20:44:16 UTC 2021
> [    6.958699] nvidia_uvm: module uses symbols from proprietary module
> nvidia, inheriting taint.
> [    8.533945] ACPI Warning: \_SB.PCI0.RP01.PEGP._DSM: Argument #4 type
> mismatch - Found [Buffer], ACPI requires [Package] (20201113/nsarguments-61)

Firmware issue.

> Chris

I do not see any AER messages, so please create new issues.

> On 2021-10-03 2:03 a.m., bugzilla-daemon@bugzilla.kernel.org wrote:

[…]

Please remove the citation/quotes when replying by email in the future, when not using interleaved style when replying.

Created attachment 299107 [details]
attachment-9243-0.html

Hi Paul.

Okay yes.  I will mark as fixed and open up new for other issues you clarified as linux.  Thanks for your help.

For the firmware issues should I be reaching out to the vendors?

Chris

⁣Get BlueMail for Android ​

On Oct 5, 2021, 7:13 AM, at 7:13 AM, bugzilla-daemon@bugzilla.kernel.org wrote:
>https://bugzilla.kernel.org/show_bug.cgi?id=109691
>
>--- Comment #19 from Paul Menzel
>(pmenzel+bugzilla.kernel.org@molgen.mpg.de) ---
>(In reply to cspadijer from comment #18)
>> Are you good with me using kernel: 5.11.0-37-generic  or would you
>> prefer I use a different kernel?
>> The X555U is currently running Linux Mint 20.2 Cinnamon.
>>
>> FYI:
>> I tried removing pci=noaer and it does boot now (without your patch).
>> It has been a while since I tried removing pci=noaer and new kernels
>get
>> installed all the time so not sure what kernel first started allowing
>it
>> to boot without needing that line.
>> However, there are still many errors on boot.
>
>The original bug seems to be solved now. As there are over ten comments
>already, could you mark it as fixed, and create new issues?
>
>> dmesg --level=err,warn
>> [    0.105337] x86/cpu: VMX (outside TXT) disabled by BIOS
>> [    0.110761] MDS CPU bug present and SMT on, data leak possible.
>See
>> https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html
>for
>> more details.
>
>Is GNU/Linux applying the latest microcode updates?
>
>> [    0.110761]  #3
>
>Cosmetic error.
>
>> [    0.114598] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
>> [    0.135583] ACPI BIOS Error (bug): Could not resolve symbol
>> [\_SB.PCI0.RP01.PXSX], AE_NOT_FOUND (20201113/psargs-330)
>> [    0.135597] ACPI Error: Skipping While/If block
>(20201113/psloop-427)
>> [    0.527786] tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does
>not
>> cover the entire command/response buffer. [mem 0xfed40000-0xfed4087f
>flags
>> 0x200] vs fed40080 f80
>> [    0.527874] tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does
>not
>> cover the entire command/response buffer. [mem 0xfed40000-0xfed4087f
>flags
>> 0x200] vs fed40080 f80
>
>Firmware issues.
>
>> [    0.736009] i8042: PNP: PS/2 appears to have AUX port disabled, if
>this is
>> incorrect please boot with i8042.nopnp
>
>Can be ignored.
>
>> [    0.738042] platform eisa.0: EISA: Cannot allocate resource for
>mainboard
>> [    0.738044] platform eisa.0: Cannot allocate resource for EISA
>slot 1
>> [    0.738045] platform eisa.0: Cannot allocate resource for EISA
>slot 2
>> [    0.738046] platform eisa.0: Cannot allocate resource for EISA
>slot 3
>> [    0.738048] platform eisa.0: Cannot allocate resource for EISA
>slot 4
>> [    0.738049] platform eisa.0: Cannot allocate resource for EISA
>slot 5
>> [    0.738050] platform eisa.0: Cannot allocate resource for EISA
>slot 6
>> [    0.738051] platform eisa.0: Cannot allocate resource for EISA
>slot 7
>> [    0.738052] platform eisa.0: Cannot allocate resource for EISA
>slot 8
>
>Is there an EISA slot?
>
>> [    1.268806] r8169 0000:02:00.0: can't disable ASPM; OS doesn't
>have ASPM
>> control
>
>Can be ignored.
>
>> [    1.329939] i2c_hid i2c-ELAN1000:00: supply vdd not found, using
>dummy
>> regulator
>> [    1.329973] i2c_hid i2c-ELAN1000:00: supply vddl not found, using
>dummy
>> regulator
>
>Please contact the Linux folks about this. But first try the latest
>Linux
>mainline version.
>
>> [    1.611704] ata1.00: supports DRM functions and may not be fully
>> accessible
>> [    1.613394] ata1.00: supports DRM functions and may not be fully
>> accessible
>> [    5.726419] elan_i2c i2c-ELAN1000:00: supply vcc not found, using
>dummy
>> regulator
>> [    6.376762] nvidia: loading out-of-tree module taints kernel.
>> [    6.376775] nvidia: module license 'NVIDIA' taints kernel.
>> [    6.376776] Disabling lock debugging due to kernel taint
>>
>> [    6.884240] NVRM: loading NVIDIA UNIX x86_64 Kernel Module
>470.63.01  Tue
>> Aug  3 20:44:16 UTC 2021
>> [    6.958699] nvidia_uvm: module uses symbols from proprietary
>module
>> nvidia, inheriting taint.
>> [    8.533945] ACPI Warning: \_SB.PCI0.RP01.PEGP._DSM: Argument #4
>type
>> mismatch - Found [Buffer], ACPI requires [Package]
>(20201113/nsarguments-61)
>
>Firmware issue.
>
>> Chris
>
>I do not see any AER messages, so please create new issues.
>
>> On 2021-10-03 2:03 a.m., bugzilla-daemon@bugzilla.kernel.org wrote:
>
>[…]
>
>Please remove the citation/quotes when replying by email in the future,
>when
>not using interleaved style when replying.
>
>--
>You may reply to this email to add a comment.
>
>You are receiving this mail because:
>You reported the bug.

[Please remove the quote next time from your reply. If you look at the Web interface, the comments get needlessly long because of that.]

(In reply to cspadijer from comment #20)

[…]

> Okay yes.  I will mark as fixed and open up new for other issues you
> clarified as linux.  Thanks for your help.

Thank you.

> For the firmware issues should I be reaching out to the vendors?

Yes, only the vendors can fix the firmware, unless you use FLOSS firmware like coreboot based firmware for example.

Unfortunately, my track record of getting vendors to fix their firmware is not so good, as you are only one customer using this weird operating system and not Microsoft Windows. But fingers crossed.

Additionally you might want to point them to the Firmware Test Suite (FWTS) [1].


[1]: https://wiki.ubuntu.com/FirmwareTestSuite/

Created attachment 299109 [details]
attachment-15734-0.html

Okay great.

Thanks for the link to FirmwareTestSuite.

Chris

⁣Get BlueMail for Android ​

On Oct 5, 2021, 9:25 AM, at 9:25 AM, bugzilla-daemon@bugzilla.kernel.org wrote:
>https://bugzilla.kernel.org/show_bug.cgi?id=109691
>
>--- Comment #21 from Paul Menzel
>(pmenzel+bugzilla.kernel.org@molgen.mpg.de) ---
>[Please remove the quote next time from your reply. If you look at the
>Web
>interface, the comments get needlessly long because of that.]
>
>(In reply to cspadijer from comment #20)
>
>[…]
>
>> Okay yes.  I will mark as fixed and open up new for other issues you
>> clarified as linux.  Thanks for your help.
>
>Thank you.
>
>> For the firmware issues should I be reaching out to the vendors?
>
>Yes, only the vendors can fix the firmware, unless you use FLOSS
>firmware like
>coreboot based firmware for example.
>
>Unfortunately, my track record of getting vendors to fix their firmware
>is not
>so good, as you are only one customer using this weird operating system
>and not
>Microsoft Windows. But fingers crossed.
>
>Additionally you might want to point them to the Firmware Test Suite
>(FWTS)
>[1].
>
>
>[1]: https://wiki.ubuntu.com/FirmwareTestSuite/
>
>--
>You may reply to this email to add a comment.
>
>You are receiving this mail because:
>You reported the bug.

An upstream kernel since 4.2.0-22-generic has resolved the issue with this make/model of laptop.
Laptop successfully boots now without the pci=nommconf boot parameter.