Bug 109691 - Asus X555U laptop will not boot without pci=nommconf boot parameter
Summary: Asus X555U laptop will not boot without pci=nommconf boot parameter
Status: NEW
Alias: None
Product: Drivers
Classification: Unclassified
Component: PCI (show other bugs)
Hardware: Intel Linux
: P1 normal
Assignee: drivers_pci@kernel-bugs.osdl.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-12-20 17:31 UTC by cspadijer
Modified: 2018-01-01 20:10 UTC (History)
6 users (show)

See Also:
Kernel Version: 4.2.0-22-generic
Tree: Mainline
Regression: No


Attachments
Collection of outputs from X555U laptop (28.21 KB, application/x-bzip)
2015-12-20 17:31 UTC, cspadijer
Details
Updated dmesg with pci=noaer (65.84 KB, text/plain)
2015-12-30 00:29 UTC, cspadijer
Details

Description cspadijer 2015-12-20 17:31:39 UTC
Created attachment 197891 [details]
Collection of outputs from X555U laptop

Good day.
I have updated this laptop to the latest vendor supplied BIOS 204 10/18/2015.

Attempted distribution: Ubuntu mate 15.10.
Had to use acpi=off boot parameter to install linux
Eventually found more hardware worked with the pci=nommconf boot parameter

With pci=nommconf the following still does not work:
- Realtec rtl8821ae 802.11ac wireless NIC PCIe will only run in 2.4GHz mode.  5GHz mode will not work.
- Laptop will not resume after suspend

Many boot errors show in dmesg:
ACPI: AE_NOT_FOUND errors
systemd: failed to insert module 'kdbus' function not implemented

If pci=nommconf not used as boot parameter there is a looping pci-e error message that I cant break out of.  From what I can read it says:
printk messages dropped pcieport 0000:00:... id=00E5(Receiver ID)

In the attached file is the following when pci=nommconf boot parameter used:
sudo output of: 
dmesg
uname -a
lspci -vvnn
dmidecode 
Tarball of /proc/acpi directory

Note: I am unable to resume from hibernate everything is frozen.  So I am not able to attach a copy of /var/log/kern.log.0
Comment 1 Zhang Rui 2015-12-28 13:32:17 UTC
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.
Comment 2 Bjorn Helgaas 2015-12-28 16:48:51 UTC
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
Comment 3 cspadijer 2015-12-30 00:29:10 UTC
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!
Comment 4 Bjorn Helgaas 2015-12-30 14:53:16 UTC
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.
Comment 5 cspadijer 2016-01-01 17:05:37 UTC
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!
Comment 6 Kelly Price 2016-03-19 13:12:56 UTC
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...
Comment 7 cspadijer 2016-05-12 02:33:48 UTC
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.

Note You need to log in before you can comment on or make changes to this bug.