Startup Extremly Slow with Ubuntu 18.04 and Mainline Kernel 4.16.9
Clash Royale CLAN TAG#URR8PPP up vote
0
down vote
favorite
I used to use mainline kernel 4.16.3, and most things worked fine. For testing purposes, I tried 4.16.9 by running sudo dpkg -i linux-image-unsigned-4.16.9-041609-generic_4.16.9-041609.201805161024_amd64.deb linux-modules-4.16.9-041609-generic_4.16.9-041609.201805161024_amd64.deb. With this kernel, booting took really long (more than 2 minutes) and produced the following output: https://nopaste.xyz/?4b741a33276d0461#B3BbGFMFUIhZAjBGivihzmK5oUu/1DsxKlTEPxtnvp8=
Disabling apt-daily.service like recommended in Ubuntu 16.04 slow boot (apt-daily.service) did not change anything (but systemd-analyze blame showed a similiar order, with apt-daily.service on top.
Due to the syslog, I assume there is some snappy incompatibility. Is my installation of the kernel somehow wrong or may this be a bug?
kernel
asked May 16 at 22:06
David Georg Reichelt
251112
add a comment |Â
up vote
0
down vote
favorite
I used to use mainline kernel 4.16.3, and most things worked fine. For testing purposes, I tried 4.16.9 by running sudo dpkg -i linux-image-unsigned-4.16.9-041609-generic_4.16.9-041609.201805161024_amd64.deb linux-modules-4.16.9-041609-generic_4.16.9-041609.201805161024_amd64.deb. With this kernel, booting took really long (more than 2 minutes) and produced the following output: https://nopaste.xyz/?4b741a33276d0461#B3BbGFMFUIhZAjBGivihzmK5oUu/1DsxKlTEPxtnvp8=
Disabling apt-daily.service like recommended in Ubuntu 16.04 slow boot (apt-daily.service) did not change anything (but systemd-analyze blame showed a similiar order, with apt-daily.service on top.
Due to the syslog, I assume there is some snappy incompatibility. Is my installation of the kernel somehow wrong or may this be a bug?
kernel
asked May 16 at 22:06
David Georg Reichelt
251112
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I used to use mainline kernel 4.16.3, and most things worked fine. For testing purposes, I tried 4.16.9 by running sudo dpkg -i linux-image-unsigned-4.16.9-041609-generic_4.16.9-041609.201805161024_amd64.deb linux-modules-4.16.9-041609-generic_4.16.9-041609.201805161024_amd64.deb. With this kernel, booting took really long (more than 2 minutes) and produced the following output: https://nopaste.xyz/?4b741a33276d0461#B3BbGFMFUIhZAjBGivihzmK5oUu/1DsxKlTEPxtnvp8=
Disabling apt-daily.service like recommended in Ubuntu 16.04 slow boot (apt-daily.service) did not change anything (but systemd-analyze blame showed a similiar order, with apt-daily.service on top.
Due to the syslog, I assume there is some snappy incompatibility. Is my installation of the kernel somehow wrong or may this be a bug?
kernel
asked May 16 at 22:06
David Georg Reichelt
251112
I used to use mainline kernel 4.16.3, and most things worked fine. For testing purposes, I tried 4.16.9 by running sudo dpkg -i linux-image-unsigned-4.16.9-041609-generic_4.16.9-041609.201805161024_amd64.deb linux-modules-4.16.9-041609-generic_4.16.9-041609.201805161024_amd64.deb. With this kernel, booting took really long (more than 2 minutes) and produced the following output: https://nopaste.xyz/?4b741a33276d0461#B3BbGFMFUIhZAjBGivihzmK5oUu/1DsxKlTEPxtnvp8=
Disabling apt-daily.service like recommended in Ubuntu 16.04 slow boot (apt-daily.service) did not change anything (but systemd-analyze blame showed a similiar order, with apt-daily.service on top.
Due to the syslog, I assume there is some snappy incompatibility. Is my installation of the kernel somehow wrong or may this be a bug?
kernel
asked May 16 at 22:06
David Georg Reichelt
251112
asked May 16 at 22:06
David Georg Reichelt
251112
asked May 16 at 22:06
David Georg Reichelt
251112
asked May 16 at 22:06
David Georg Reichelt
251112
251112
add a comment |Â
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
2
down vote
Unfortunately this is a bug. All the kernels from K4.16.3> onwards have the same problem this includes K4.16.9, plus the K4.17RC's. I don’t know why these have been allowed to be available to the public space. The frustration I have is that there is no explanation as to why. One can accept that sometimes kernels that are maintenance releases might have some minor bugs but nothing like this where the kernel crashes entire systems.
answered May 18 at 10:58
Cyteck
413
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
2
down vote
Unfortunately this is a bug. All the kernels from K4.16.3> onwards have the same problem this includes K4.16.9, plus the K4.17RC's. I don’t know why these have been allowed to be available to the public space. The frustration I have is that there is no explanation as to why. One can accept that sometimes kernels that are maintenance releases might have some minor bugs but nothing like this where the kernel crashes entire systems.
answered May 18 at 10:58
Cyteck
413
add a comment |Â
up vote
2
down vote
Unfortunately this is a bug. All the kernels from K4.16.3> onwards have the same problem this includes K4.16.9, plus the K4.17RC's. I don’t know why these have been allowed to be available to the public space. The frustration I have is that there is no explanation as to why. One can accept that sometimes kernels that are maintenance releases might have some minor bugs but nothing like this where the kernel crashes entire systems.
answered May 18 at 10:58
Cyteck
413
add a comment |Â
up vote
2
down vote
up vote
2
down vote
Unfortunately this is a bug. All the kernels from K4.16.3> onwards have the same problem this includes K4.16.9, plus the K4.17RC's. I don’t know why these have been allowed to be available to the public space. The frustration I have is that there is no explanation as to why. One can accept that sometimes kernels that are maintenance releases might have some minor bugs but nothing like this where the kernel crashes entire systems.
answered May 18 at 10:58
Cyteck
413
Unfortunately this is a bug. All the kernels from K4.16.3> onwards have the same problem this includes K4.16.9, plus the K4.17RC's. I don’t know why these have been allowed to be available to the public space. The frustration I have is that there is no explanation as to why. One can accept that sometimes kernels that are maintenance releases might have some minor bugs but nothing like this where the kernel crashes entire systems.
answered May 18 at 10:58
Cyteck
413
answered May 18 at 10:58
Cyteck
413
answered May 18 at 10:58
Cyteck
413
answered May 18 at 10:58
Cyteck
413
413
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1037139%2fstartup-extremly-slow-with-ubuntu-18-04-and-mainline-kernel-4-16-9%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password