19.1 Long boot time and errors

Questions about Grub, UEFI,the liveCD and the installer
Forum rules
Before you post please read how to get help
Post Reply
chripie
Level 1
Level 1
Posts: 4
Joined: Fri Dec 21, 2018 2:40 pm

19.1 Long boot time and errors

Post by chripie »

Hello,

I just finalized a clean install of Mint 19.1 Cinnamon.
There were no problems during installation and the first boot.

I started the update process and after installing the new version of the update manager it listed many programs, libraries etc to be updated - so I did.

On the next boot I just got a black screen and after retry it listed a lot of errors during the booting process.
After a minute I finally entered the normal gui.
Restart -> ~1 minute black screen - systemd-analyze told me that on the startup the "loader" needed about 40s -> finally entered the normal gui
Restart -> many errors during boot again - systemd-analyze told me that on the startup the "userspace" needed about 1m-> finally entered the normal gui

I googled but weren't able to find any solution, so I ask here for help.

In the following some outputs, which hopefully help to understand what's going on.

Code: Select all

System:    Host: Brix Kernel: 4.15.0-43-generic x86_64 bits: 64 compiler: gcc v: 7.3.0 Desktop: Cinnamon 4.0.8 
           Distro: Linux Mint 19.1 Tessa base: Ubuntu 18.04 bionic 
Machine:   Type: Desktop Mobo: GIGABYTE model: MFLP5IP-00 v: 1.x serial: <filter> UEFI: American Megatrends v: F1 
           date: 12/19/2017 
CPU:       Topology: Quad Core model: Intel Core i5-8250U bits: 64 type: MT MCP arch: Kaby Lake rev: A L2 cache: 6144 KiB 
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 28800 
           Speed: 700 MHz min/max: 400/3400 MHz Core speeds (MHz): 1: 744 2: 712 3: 701 4: 745 5: 706 6: 717 7: 770 8: 703 
Graphics:  Device-1: Intel UHD Graphics 620 vendor: Gigabyte driver: i915 v: kernel bus ID: 00:02.0 
           Display: x11 server: X.Org 1.19.6 driver: modesetting unloaded: fbdev,vesa resolution: 1680x1050~60Hz 
           OpenGL: renderer: Mesa DRI Intel UHD Graphics 620 (Kabylake GT2) v: 4.5 Mesa 18.0.5 direct render: Yes 
Audio:     Device-1: Intel Sunrise Point-LP HD Audio vendor: Gigabyte driver: snd_hda_intel v: kernel bus ID: 00:1f.3 
           Sound Server: ALSA v: k4.15.0-43-generic 
Network:   Device-1: Intel Ethernet I219-V vendor: Gigabyte driver: e1000e v: 3.2.6-k port: f040 bus ID: 00:1f.6 
           IF: enp0s31f6 state: up speed: 1000 Mbps duplex: full mac: <filter> 
           Device-2: Intel driver: iwlwifi v: kernel port: f040 bus ID: 02:00.0 
           IF: wlp2s0 state: down mac: <filter> 
Drives:    Local Storage: total: 111.79 GiB used: 9.54 GiB (8.5%) 
           ID-1: /dev/sda vendor: Crucial model: CT120BX500SSD1 size: 111.79 GiB 
Partition: ID-1: / size: 109.04 GiB used: 9.54 GiB (8.7%) fs: ext4 dev: /dev/sda2 
Sensors:   System Temperatures: cpu: 46.0 C mobo: 29.8 C 
           Fan Speeds (RPM): N/A 
Info:      Processes: 229 Uptime: 2m Memory: 7.65 GiB used: 883.4 MiB (11.3%) Init: systemd runlevel: 5 Compilers: gcc: 7.3.0 
           Shell: bash v: 4.4.19 inxi: 3.0.27 

Code: Select all

Startup finished in 8.524s (firmware) + 4.419s (loader) + 4.217s (kernel) + 1min 6.118s (userspace) = 1min 23.280s
graphical.target reached after 1min 6.101s in userspace

Code: Select all

    1min 1.084s lightdm.service
     1min 1.084s plymouth-quit-wait.service
          4.350s apt-daily.service
          3.946s systemd-journald.service
           802ms ufw.service
           373ms systemd-journal-flush.service
           303ms dev-sda2.device
           201ms NetworkManager.service
           196ms systemd-logind.service
           176ms systemd-timesyncd.service
           172ms networkd-dispatcher.service
           151ms ubuntu-system-adjustments.service
           149ms systemd-resolved.service
           144ms ModemManager.service
           132ms udisks2.service
           127ms upower.service
           118ms apparmor.service
.....
  

Code: Select all

...
[  108.744367] pcieport 0000:00:1c.0: AER: Corrected error received: id=00e0
[  108.744379] pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID)
[  108.744390] pcieport 0000:00:1c.0:   device [8086:9d10] error status/mask=00000001/00002000
[  108.744398] pcieport 0000:00:1c.0:    [ 0] Receiver Error         (First)
[  108.750122] pcieport 0000:00:1c.0: AER: Corrected error received: id=00e0
[  108.750134] pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID)
[  108.750145] pcieport 0000:00:1c.0:   device [8086:9d10] error status/mask=00000001/00002000
[  108.750153] pcieport 0000:00:1c.0:    [ 0] Receiver Error         (First)
[  108.762326] pcieport 0000:00:1c.0: AER: Corrected error received: id=00e0
[  108.762337] pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID)
[  108.762349] pcieport 0000:00:1c.0:   device [8086:9d10] error status/mask=00000001/00002000
[  108.762356] pcieport 0000:00:1c.0:    [ 0] Receiver Error         (First)
[  108.772440] pcieport 0000:00:1c.0: AER: Corrected error received: id=00e0
[  108.772452] pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID)
[  108.772463] pcieport 0000:00:1c.0:   device [8086:9d10] error status/mask=00000001/00002000
[  108.772471] pcieport 0000:00:1c.0:    [ 0] Receiver Error         (First)
[  108.773098] pcieport 0000:00:1c.0: AER: Corrected error received: id=00e0
[  108.773110] pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID)
[  108.773122] pcieport 0000:00:1c.0:   device [8086:9d10] error status/mask=00000001/00002000
[  108.773129] pcieport 0000:00:1c.0:    [ 0] Receiver Error         (First)
[  108.773846] pcieport 0000:00:1c.0: AER: Corrected error received: id=00e0
[  108.773857] pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID)
[  108.773867] pcieport 0000:00:1c.0:   device [8086:9d10] error status/mask=00000001/00002000
[  108.773875] pcieport 0000:00:1c.0:    [ 0] Receiver Error         (First)
[  108.782755] pcieport 0000:00:1c.0: AER: Corrected error received: id=00e0
[  108.782767] pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID)
[  108.782779] pcieport 0000:00:1c.0:   device [8086:9d10] error status/mask=00000001/00002000
[  108.782786] pcieport 0000:00:1c.0:    [ 0] Receiver Error         (First)
[  108.784463] pcieport 0000:00:1c.0: AER: Corrected error received: id=00e0
[  108.784476] pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID)
[  108.784487] pcieport 0000:00:1c.0:   device [8086:9d10] error status/mask=00000001/00002000
[  108.784494] pcieport 0000:00:1c.0:    [ 0] Receiver Error         (First)
[  108.785868] pcieport 0000:00:1c.0: AER: Corrected error received: id=00e0
[  108.785880] pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID)
[  108.785892] pcieport 0000:00:1c.0:   device [8086:9d10] error status/mask=00000001/00002000
[  108.785900] pcieport 0000:00:1c.0:    [ 0] Receiver Error         (First)
[  108.787415] pcieport 0000:00:1c.0: AER: Corrected error received: id=00e0
[  108.787426] pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID)
[  108.787436] pcieport 0000:00:1c.0:   device [8086:9d10] error status/mask=00000001/00002000
[  108.787444] pcieport 0000:00:1c.0:    [ 0] Receiver Error         (First)
[  108.789188] pcieport 0000:00:1c.0: AER: Corrected error received: id=00e0
[  108.789199] pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID)
[  108.789209] pcieport 0000:00:1c.0:   device [8086:9d10] error status/mask=00000001/00002000
[  108.789217] pcieport 0000:00:1c.0:    [ 0] Receiver Error         (First)
[  108.793054] pcieport 0000:00:1c.0: AER: Corrected error received: id=00e0
[  108.793065] pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID)
[  108.793076] pcieport 0000:00:1c.0:   device [8086:9d10] error status/mask=00000001/00002000
[  108.793083] pcieport 0000:00:1c.0:    [ 0] Receiver Error         (First)
[  108.793871] pcieport 0000:00:1c.0: AER: Corrected error received: id=00e0
[  108.793882] pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID)
[  108.793892] pcieport 0000:00:1c.0:   device [8086:9d10] error status/mask=00000001/00002000
[  108.793899] pcieport 0000:00:1c.0:    [ 0] Receiver Error         (First)
[  108.806854] pcieport 0000:00:1c.0: AER: Corrected error received: id=00e0
[  108.806866] pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID)
[  108.806877] pcieport 0000:00:1c.0:   device [8086:9d10] error status/mask=00000001/00002000
[  108.806885] pcieport 0000:00:1c.0:    [ 0] Receiver Error         (First)
[  108.816040] pcieport 0000:00:1c.0: AER: Corrected error received: id=00e0
[  108.816052] pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID)
[  108.816064] pcieport 0000:00:1c.0:   device [8086:9d10] error status/mask=00000001/00002000
[  108.816072] pcieport 0000:00:1c.0:    [ 0] Receiver Error         (First)
[  108.816402] pcieport 0000:00:1c.0: AER: Corrected error received: id=00e0
[  108.816413] pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID)
[  108.816423] pcieport 0000:00:1c.0:   device [8086:9d10] error status/mask=00000001/00002000
[  108.816431] pcieport 0000:00:1c.0:    [ 0] Receiver Error         (First)
[  108.819402] pcieport 0000:00:1c.0: AER: Corrected error received: id=00e0
[  108.819414] pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID)
[  108.819425] pcieport 0000:00:1c.0:   device [8086:9d10] error status/mask=00000001/00002000
[  108.819433] pcieport 0000:00:1c.0:    [ 0] Receiver Error         (First)
[  108.840807] pcieport 0000:00:1c.0: AER: Corrected error received: id=00e0
[  108.840819] pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID)
[  108.840831] pcieport 0000:00:1c.0:   device [8086:9d10] error status/mask=00000001/00002000
[  108.840838] pcieport 0000:00:1c.0:    [ 0] Receiver Error         (First)
[  108.846638] pcieport 0000:00:1c.0: AER: Corrected error received: id=00e0
[  108.846649] pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID)
[  108.846661] pcieport 0000:00:1c.0:   device [8086:9d10] error status/mask=00000001/00002000
[  108.846669] pcieport 0000:00:1c.0:    [ 0] Receiver Error         (First)
[  108.859530] pcieport 0000:00:1c.0: AER: Corrected error received: id=00e0
[  108.859542] pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID)
[  108.859553] pcieport 0000:00:1c.0:   device [8086:9d10] error status/mask=00000001/00002000
[  108.859561] pcieport 0000:00:1c.0:    [ 0] Receiver Error         (First)
[  108.860840] pcieport 0000:00:1c.0: AER: Corrected error received: id=00e0
[  108.860852] pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID)
[  108.860863] pcieport 0000:00:1c.0:   device [8086:9d10] error status/mask=00000001/00002000
[  108.860871] pcieport 0000:00:1c.0:    [ 0] Receiver Error         (First)
[  108.866417] pcieport 0000:00:1c.0: AER: Corrected error received: id=00e0
[  108.866429] pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID)
[  108.866440] pcieport 0000:00:1c.0:   device [8086:9d10] error status/mask=00000001/00002000
[  108.866448] pcieport 0000:00:1c.0:    [ 0] Receiver Error         (First)
...
Last edited by JeremyB on Sat Dec 22, 2018 5:54 am, edited 1 time in total.
Reason: code tags

User avatar
SuperBoby
Level 3
Level 3
Posts: 106
Joined: Wed Nov 21, 2018 2:33 pm

Re: 19.1 Long boot time and errors

Post by SuperBoby »

It looks like something is wrong with a PCI device. What cards do you have in your PCI slots ?
LMDE 3 Cindy x64 on :
Lenovo Thinkpad T410, X220 Tablet, X61

JeremyB
Level 20
Level 20
Posts: 11589
Joined: Fri Feb 21, 2014 8:17 am

Re: 19.1 Long boot time and errors

Post by JeremyB »

Are there any options in BIOS for PCI Active State Power Management(ASPM)?

chripie
Level 1
Level 1
Posts: 4
Joined: Fri Dec 21, 2018 2:40 pm

Re: 19.1 Long boot time and errors

Post by chripie »

It looks like something is wrong with a PCI device. What cards do you have in your PCI slots ?
It's a very small barbebone PC, so there are no additional expansion slots.
As far as I know the built-in wifi and the bluetooth are connected internally the (one and only?) PCIe slot.

Are there any options in BIOS for PCI Active State Power Management(ASPM)?
The only option which is about Power Management is called "ERP lowest power state mode" and is set to disabled.


The long booting error with spamming masses of errors on the console for about a minute happens randomly.
The last boot was quick and seemed to be clean.
The only error message can be found in dmesg:

Code: Select all

[    2.822131] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[    2.823278] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20170831/psargs-364)
[    2.823286] No Local Variables are initialized for Method [_GTF]
[    2.823287] No Arguments are initialized for method [_GTF]
[    2.823288] ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.PRT0._GTF, AE_NOT_FOUND (20170831/psparse-550)
[    2.826106] ata1.00: ATA-9: CT120BX500SSD1,  M6CR013, max UDMA/133
[    2.826107] ata1.00: 234441648 sectors, multi 1: LBA48 NCQ (depth 31/32), AA
[    2.831103] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20170831/psargs-364)
[    2.831110] No Local Variables are initialized for Method [_GTF]
[    2.831111] No Arguments are initialized for method [_GTF]
[    2.831112] ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.PRT0._GTF, AE_NOT_FOUND (20170831/psparse-550)
[    2.835673] ata1.00: configured for UDMA/133
[    2.835769] scsi 0:0:0:0: Direct-Access     ATA      CT120BX500SSD1   R013 PQ: 0 ANSI: 5
[    2.835896] sd 0:0:0:0: Attached scsi generic sg0 type 0
[    2.835923] sd 0:0:0:0: [sda] 234441648 512-byte logical blocks: (120 GB/112 GiB)
[    2.835933] sd 0:0:0:0: [sda] Write Protect is off
[    2.835934] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[    2.835950] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    2.837043]  sda: sda1 sda2
[    2.837237] sd 0:0:0:0: [sda] Attached SCSI disk

JeremyB
Level 20
Level 20
Posts: 11589
Joined: Fri Feb 21, 2014 8:17 am

Re: 19.1 Long boot time and errors

Post by JeremyB »

Try

Code: Select all

xed admin:///etc/default/grub
change the line with "quiet splash" to make it "quiet splash pcie_aspm=off"
Save and do

Code: Select all

sudo update-grub
Reboot

chripie
Level 1
Level 1
Posts: 4
Joined: Fri Dec 21, 2018 2:40 pm

Re: 19.1 Long boot time and errors

Post by chripie »

Jeremy, I had some more search on the web and found also your suggested "solution".
As far as I understand the option "pcie_aspm=off" disabled the energy saving states?
I struggle to call that a solution, more a supression. Is there any idea what cause the errors?

There were also other recommendations such as "pci=noaer" and "pci=nomsi", but I don't understand what they do.

I also had an additional look, which pci device was causing the trouble during boot:

Code: Select all

lspci -nn | grep 8086:9d10
00:1c.0 PCI bridge [0604]: Intel Corporation Sunrise Point-LP PCI Express Root Port [8086:9d10] (rev f1)

JeremyB
Level 20
Level 20
Posts: 11589
Joined: Fri Feb 21, 2014 8:17 am

Re: 19.1 Long boot time and errors

Post by JeremyB »

I would think that the kernel doesn't like the ASPM and that is why the errors occur. A description for the other suggestions can be found https://askubuntu.com/a/952790

I checked my dmesg and found

Code: Select all

ACPI FADT declares the system doesn't support PCIe ASPM, so disable it

chripie
Level 1
Level 1
Posts: 4
Joined: Fri Dec 21, 2018 2:40 pm

Re: 19.1 Long boot time and errors

Post by chripie »

So there is still a chance that the kernel might be able to handle the ASPM in the future?
Ok, for now I'll try to disable the aspm. Does it only effects the PCIe devices (wifi, bluetooth etc) or also other power managements e.g. CPU?

Thanks for help!

Btw: I didn't experience the problem on the previous Linux Mint 19 (Tara).

Post Reply

Return to “Installation & Boot”