SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,110
Original Poster
Rep:
Quote:
Originally Posted by Lysander666
I've noticed in -current, in my install anyway, that the huge kernel takes significantly less time to boot.
Timing it, generic takes 67 seconds from kernel boot to login prompt, whereas the huge kernel takes just 47 seconds [this is with the latest, 4.19.40].
What could be the reason for this? I always thought one of the reasons to use generic was that it is faster to boot, but these days, in 2019, maybe there is less reason to use generic.
Agreed, as was discussed by the authors of posts #56 through #62 (approximately) on pages two and three of this thread.
Last edited by cwizardone; 05-06-2019 at 08:13 AM.
Timing it, generic takes 67 seconds from kernel boot to login prompt, whereas the huge kernel takes just 47 seconds
If you pass init=/bin/bash argument, more precise measure can be done.
This way you're timing the boot of Slackware runlevel 4, and not the kernel boot which should only take a couple of seconds to initialize.
For comparison, cold boot > xdm login takes around 9 seconds here, while cold boot > /bin/bash takes 5. If I were to measure full install with all rc executables, it would take more than a minute.
I think the diff is because generic setup loads many individual modules from disk, and huge deploys them in memory from a single file.
Huge kernel, 4.19.40, run level 3, from start to command prompt, 16:37 seconds.
It's faster than that with overclocked memory and root on ssd. Traditional disk takes time to spin, and some memory is just slow.
All this adds a few seconds, depending on hardware. That's not even counting the time added by various checks, optional features such as randomization, memory poisoning, etc.
Accelerating the boot sequence is ongoing process, there's always room for more optimization.
Quote:
Originally Posted by cwizardone
That was good, but let's do it one more time and his time with FEELING! Put some emotion in it!
I don't get your joke, care to explain what's going on here?
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,110
Original Poster
Rep:
Quote:
Originally Posted by elcore
...I don't get your joke, care to explain what's going on here?
Oops, sorry about that.
I guess one would have had to play in a band or orchestra to get it. You have practiced a piece over and over and just when you think it has all come together the conductor taps his baton on his music stand and says.........
Quote:
That was good, but let's do it one more time and this time with FEELING! Put some emotion in it!
It was all in references to the recent rapid kernel updates.
Get it?
Last edited by cwizardone; 05-06-2019 at 01:34 PM.
Reason: Typo.
Linux 5.1.2
From: Greg KH
Date: Tue May 14 2019 - 14:06:11 EST
I'm announcing the release of the 5.1.2 kernel.
All users of the 5.1 kernel series must upgrade. Well, kind of, let me rephrase that...
All users of Intel processors made since 2011 must upgrade.
Note, this release, and the other stable releases that are all being
released right now at the same time, just went out all contain patches
that have only seen the "public eye" for about 5 minutes. So be
forwarned, they might break things, they might not build, but hopefully
they fix things. Odds are we will be fixing a number of small things in
this area for the next few weeks as things shake out on real hardware
and workloads. So don't think you are done updating your kernel, you
never are done with that
As for what specifically these changes fix, I'll let the tech news sites
fill you in on the details. Or go read the excellently written Xen
Security Advisory 297: https://xenbits.xen.org/xsa/advisory-297.html
That should give you a good idea of what a number of people have been
dealing with for many many many months now.
Many thanks goes out to Thomas Gleixner for going above and beyond to do
the backports to the 5.1, 5.0, 4.19, and 4.14 kernel trees, and to Ben
Hutchings for doing the 4.9 work. And of course to all of the
developers who have been working on this in secret and doing reviews of
the many different proposals and versions of the patches.
As I said before just over a year ago, Intel once again owes a bunch of
people a lot of drinks for fixing their hardware bugs, in our
software...
Anyway, as usual, the updated 5.1.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-5.1.y
and can be browsed at the normal kernel.org git web browser: https://git.kernel.org/?p=linux/kern....git;a=summary
thanks,
greg k-h
------------
Kernel updates 5.1.2, 5.0.16, 4.19.43, 4.14.119 and 4.9.176 are available at
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
