Bsrgvty

Collinear Galois conjugates

Is there a Morita cocycle for the mapping class group Mod(g,n) when n > 1?

Boss wants me to ignore a software API license prohibiting mass download

Is there a command to install basic applications on Ubuntu 16.04?

Took GRE two times, same scores with minor differences - worth sending both?

Why did Gandalf use a sword against the Balrog?

What is my malfunctioning AI harvesting from humans?

Simplification of numbers

Understanding this peak detector circuit

How can I decide if my homebrew item should require attunement?

Word for an event that will likely never happen again

Is there any way to stop a user from creating executables and running them?

Why are Tucker and Malcolm not dead?

How many people would you need to pull a whale over cobblestone streets?

Creating multi-attribute primary key in table in ArcGIS Desktop

TEMPO: play a sound in animated GIF/PDF/SVG

When does Tiana, Ship's Caretaker check card type?

PhD advisor lost funding, need advice

How much maintenance time did it take to make an F4U Corsair ready for another flight?

A continuous water "planet" ring around a star

Why did I get only 5 points even though I won?

Heat equation: Squiggly lines

If a digital camera can be "hacked" in the ransomware sense, how best to protect it?

Generate Brainfuck for the numbers 1–255

Long boot Ubuntu 18

How do I investigate boot and partition issues?Ubuntu 15.04 network manager causing slow bootVery slow boot with Ubuntu 16.04 on XPS 13 with SSDSome services causes slower boot time Ubuntu 17.10Ubuntu 18.04 purple screen stays a long time before splashCan I improve boot time? dev-sda6.device service takes longLong boot time due to loaderUbuntu 18.04 is taking long to loadboot startup speedup Ubuntu 18.04Slow Boot time apt-daily-upgrade.service and apt-daily.service on Xubuntu 18.04 - ASUS K70IO laptopLong Kernel Boot Segment in 18.04

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;

1

Relatively (3 months old) fresh install and noticed long boot times since start.

Lately since i did a driver install, i been seeing a message during boot; something along the lines of kernel crash with a whole list of other output with green checkmarks.

it seems the more problematic longer boottimes started when i did : sudo ubuntu-drivers autoinstall

I already did some research and found a couple things, such as:

• 
  https://askubuntu.com/a/90046 , where my output is the following:
  http://paste.ubuntu.com/p/CW84Gy77ZQ/
  


• 
  systemd-analyze blame, output: https://pastebin.com/0p5FHdw7
  

Output of screen:
crash boot screen

output of: systemd-analyze critical-chain :

graphical.target @39.565s
└─multi-user.target @39.565s
 └─snapd.seeded.service @36.899s +123ms
 └─snapd.service @28.442s +8.454s
 └─basic.target @27.569s
 └─sockets.target @27.569s
 └─snapd.socket @27.540s +28ms
 └─sysinit.target @27.540s
 └─systemd-timesyncd.service @27.178s +361ms
 └─systemd-tmpfiles-setup.service @26.890s +251ms
 └─systemd-journal-flush.service @3.682s +23.206s
 └─systemd-remount-fs.service @3.026s +392ms
 └─systemd-journald.socket @3.021s
 └─system.slice @3.020s
 └─-.slice @3.017s

Any idea what i could try for my next step?

Thanks in advance!

boot 18.04 kernel crash

share|improve this question

edited Apr 15 at 15:13

Bart

asked Apr 15 at 7:25

BartBart

922 bronze badges

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  systemd-analyze blame where is the output of that?
  
  – Rinzwind
  Apr 15 at 7:28
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  You wrote "something along the lines of kernel crash with a whole list of other output " -- it may help to know precisely what that error message was. If it is only shown for a short time, you could take a photo using a smartphone or something in irder not to lose sight of the error message.
  
  – Elias
  Apr 15 at 7:39
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @Rinzwind, blame output: pastebin.com/0p5FHdw7
  
  – Bart
  Apr 15 at 7:41
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @Elias added the boot screen output
  
  – Bart
  Apr 15 at 8:20
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  But that "crash boot screen" picture does not look like a crash, it looks like things are working. Do you mean that it hangs at that point?
  
  – Elias
  Apr 15 at 8:23
  

  
  
  
  

 | 
show 2 more comments

1

Relatively (3 months old) fresh install and noticed long boot times since start.

Lately since i did a driver install, i been seeing a message during boot; something along the lines of kernel crash with a whole list of other output with green checkmarks.

it seems the more problematic longer boottimes started when i did : sudo ubuntu-drivers autoinstall

I already did some research and found a couple things, such as:

• 
  https://askubuntu.com/a/90046 , where my output is the following:
  http://paste.ubuntu.com/p/CW84Gy77ZQ/
  


• 
  systemd-analyze blame, output: https://pastebin.com/0p5FHdw7
  

Output of screen:
crash boot screen

output of: systemd-analyze critical-chain :

graphical.target @39.565s
└─multi-user.target @39.565s
 └─snapd.seeded.service @36.899s +123ms
 └─snapd.service @28.442s +8.454s
 └─basic.target @27.569s
 └─sockets.target @27.569s
 └─snapd.socket @27.540s +28ms
 └─sysinit.target @27.540s
 └─systemd-timesyncd.service @27.178s +361ms
 └─systemd-tmpfiles-setup.service @26.890s +251ms
 └─systemd-journal-flush.service @3.682s +23.206s
 └─systemd-remount-fs.service @3.026s +392ms
 └─systemd-journald.socket @3.021s
 └─system.slice @3.020s
 └─-.slice @3.017s

Any idea what i could try for my next step?

Thanks in advance!

boot 18.04 kernel crash

share|improve this question

edited Apr 15 at 15:13

Bart

asked Apr 15 at 7:25

BartBart

922 bronze badges

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  systemd-analyze blame where is the output of that?
  
  – Rinzwind
  Apr 15 at 7:28
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  You wrote "something along the lines of kernel crash with a whole list of other output " -- it may help to know precisely what that error message was. If it is only shown for a short time, you could take a photo using a smartphone or something in irder not to lose sight of the error message.
  
  – Elias
  Apr 15 at 7:39
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @Rinzwind, blame output: pastebin.com/0p5FHdw7
  
  – Bart
  Apr 15 at 7:41
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @Elias added the boot screen output
  
  – Bart
  Apr 15 at 8:20
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  But that "crash boot screen" picture does not look like a crash, it looks like things are working. Do you mean that it hangs at that point?
  
  – Elias
  Apr 15 at 8:23
  

  
  
  
  

 | 
show 2 more comments

Relatively (3 months old) fresh install and noticed long boot times since start.

Lately since i did a driver install, i been seeing a message during boot; something along the lines of kernel crash with a whole list of other output with green checkmarks.

it seems the more problematic longer boottimes started when i did : sudo ubuntu-drivers autoinstall

I already did some research and found a couple things, such as:

• 
  https://askubuntu.com/a/90046 , where my output is the following:
  http://paste.ubuntu.com/p/CW84Gy77ZQ/
  


• 
  systemd-analyze blame, output: https://pastebin.com/0p5FHdw7
  

Output of screen:
crash boot screen

output of: systemd-analyze critical-chain :

graphical.target @39.565s
└─multi-user.target @39.565s
 └─snapd.seeded.service @36.899s +123ms
 └─snapd.service @28.442s +8.454s
 └─basic.target @27.569s
 └─sockets.target @27.569s
 └─snapd.socket @27.540s +28ms
 └─sysinit.target @27.540s
 └─systemd-timesyncd.service @27.178s +361ms
 └─systemd-tmpfiles-setup.service @26.890s +251ms
 └─systemd-journal-flush.service @3.682s +23.206s
 └─systemd-remount-fs.service @3.026s +392ms
 └─systemd-journald.socket @3.021s
 └─system.slice @3.020s
 └─-.slice @3.017s

Any idea what i could try for my next step?

Thanks in advance!

boot 18.04 kernel crash

share|improve this question

edited Apr 15 at 15:13

Bart

asked Apr 15 at 7:25

BartBart

922 bronze badges

graphical.target @39.565s
└─multi-user.target @39.565s
 └─snapd.seeded.service @36.899s +123ms
 └─snapd.service @28.442s +8.454s
 └─basic.target @27.569s
 └─sockets.target @27.569s
 └─snapd.socket @27.540s +28ms
 └─sysinit.target @27.540s
 └─systemd-timesyncd.service @27.178s +361ms
 └─systemd-tmpfiles-setup.service @26.890s +251ms
 └─systemd-journal-flush.service @3.682s +23.206s
 └─systemd-remount-fs.service @3.026s +392ms
 └─systemd-journald.socket @3.021s
 └─system.slice @3.020s
 └─-.slice @3.017s

share|improve this question

edited Apr 15 at 15:13

Bart

asked Apr 15 at 7:25

BartBart

922 bronze badges

share|improve this question

edited Apr 15 at 15:13

Bart

asked Apr 15 at 7:25

BartBart

922 bronze badges

asked Apr 15 at 7:25

BartBart

922 bronze badges

asked Apr 15 at 7:25

BartBart

922 bronze badges