[opensuse-factory] Very slow loading of kernel/initrd with os12.3
Hello, I have been testing openSUSE 12.3 since Beta 1 in VirtualBox and found everything great. I decided to install several physical machines with RC2 over the weekend. But now I experience a problem that was not there in virtualbox: Loading of the initrd via grub legacy from harddisk is **extremely slow** on all of the physical machines, e.g. on a very recent Core-i7 system it takes ~20 seconds, on an older Core2Duo up to 60 seconds! These times are only for loading the initrd, not booting the system! During these 20-60 seconds, the HDD led of the machines are constantly on/flashing. The problem exists even with the "stock" kernel and initrd from the oss repo under /boot/x86_64/loader, if I copy then to the boot partition and add them to grub. The problem does **not** exist if I boot the machine from CD or PXE! This is our disk layout: --------- # fdisk -l Disk /dev/sda: 500.1 GB, 500107862016 bytes 255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0x000ec0fc Device Boot Start End Blocks Id System /dev/sda1 * 2048 305151 151552 83 Linux /dev/sda2 305152 17092607 8393728 82 Linux swap / Solaris /dev/sda3 17092608 976773119 479840256 8e Linux LVM --------- The /boot partition is ext4. How do I debug this problem? Currently there is no further output except the grub screen showing ------ root (hd0,0) kernel ... initrd ... <flashing cursor> ------ We have not had this issue with openSUSE 12.2 or with 12.3 in Virtualbox. I guess I should open a bugzilla about this? Best regards, J Brauchle
Joschi Brauchle wrote:
Hello,
I have been testing openSUSE 12.3 since Beta 1 in VirtualBox and found everything great. I decided to install several physical machines with RC2 over the weekend.
But now I experience a problem that was not there in virtualbox: Loading of the initrd via grub legacy from harddisk is **extremely slow** on all of the physical machines, e.g. on a very recent Core-i7 system it takes ~20 seconds, on an older Core2Duo up to 60 seconds!
With lilo this could be due to lack of the "compact" option. Maybe grub has something similar? -- Per Jessen, Zürich (2.9°C) http://www.dns24.ch/ - free DNS hosting, made in Switzerland. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Monday 2013-03-04 13:44, Joschi Brauchle wrote:
But now I experience a problem that was not there in virtualbox: Loading of the initrd via grub legacy from harddisk is **extremely slow** on all of the physical machines, e.g. on a very recent Core-i7 system it takes ~20 seconds, on an older Core2Duo up to 60 seconds! These times are only for loading the initrd, not booting the system! During these 20-60 seconds, the HDD led of the machines are constantly on/flashing.
The problem exists even with the "stock" kernel and initrd from the oss repo under /boot/x86_64/loader, if I copy then to the boot partition and add them to grub. The problem does **not** exist if I boot the machine from CD or PXE!
Interesting that it happens not for CD. For me, loading images (kernel/initrd) from CD/USB and PXE via ISOLINUX/SYSLINUX/PXELINUX has always been a bottleneck, because they read in what feels like 512-ish byte blocks, and synchronously so, and probably doing that through INT 13h. (The story goes similar on SPARC with the SILO loader.) In VirtualBox, practically the same happens, but it is not as noticable because of the host system's cache which kicks in from the second time. Probably GRUB does small reads too, but you just do not notice it because latency with hard disks is so much lower. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 03/04/2013 02:34 PM, Jan Engelhardt wrote:
On Monday 2013-03-04 13:44, Joschi Brauchle wrote: Interesting that it happens not for CD.
Well, I may have to be careful with that statement or even revise it later. I tested a Beta1 DVD some time ago and thought it did not happen. But I only tested on the i7 machine and most likely I took the long loading time for regular DVD delay. Possibly the same for PXE boot... one simply expects and accepts a certain delay there in contrast to booting from HDD.
For me, loading images (kernel/initrd) from CD/USB and PXE via ISOLINUX/SYSLINUX/PXELINUX has always been a bottleneck, because they read in what feels like 512-ish byte blocks, and synchronously so, and probably doing that through INT 13h. (The story goes similar on SPARC with the SILO loader.)
In VirtualBox, practically the same happens, but it is not as noticable because of the host system's cache which kicks in from the second time.
Hm, ok,... but is the difference really *that* big? With virtualbox I cannot even see the lines from grub, it completes in <1 second. But if I boot the physical machine, it is more like ~10-20 seconds (on an i7 CPU with SATA HDD). Looking at the size of the stock initrd (~54MB), I would expect my HDD to be able to load this in 1 or 2 seconds at most, plus some CPU time to extract...
Probably GRUB does small reads too, but you just do not notice it because latency with hard disks is so much lower.
So what has changed from 11.4/12.2 to 12.3 in that area? On 11.4 and 12.2, loading the initrd takes just a handful of seconds (if at all), barely noticeable compared to the remaining boot process. But now with 12.3, loading the initrd is about 1/3 of the total boot time on a fast machine... It there anything I can do to get more verbose/debug output? Maybe from GRUB or from the kernel while it loads the initrd?
Am 04.03.2013 14:47, schrieb Joschi Brauchle:
Looking at the size of the stock initrd (~54MB), I would expect my HDD to be able to load this in 1 or 2 seconds at most, plus some CPU time to extract...
That size looks obscene. Thinking about that the BIOS loads these with some legacy compatibility non-interrupt non-dma mode, 5MB per second look realistic.
Probably GRUB does small reads too, but you just do not notice it because latency with hard disks is so much lower.
So what has changed from 11.4/12.2 to 12.3 in that area?
How big is the initrd on those? A SLES11SP1 xen domU has a 3.3MB initrd, a SP2 xen dom0 has 4.3MB (surely depends on the hardware). My 12.2 at home has a 7.8MB initrd, this Factory laptop has a 30MB initrd. Something has gone seriously wrong since 12.2 I'd say :-)
On 11.4 and 12.2, loading the initrd takes just a handful of seconds (if at all), barely noticeable compared to the remaining boot process.
Compare the sizes, I'm pretty sure this will shed some light on the issue.
But now with 12.3, loading the initrd is about 1/3 of the total boot time on a fast machine...
The machine is not really "fast" while grub is running. Everything is in some "allow 20 year old software to run" compatibility mode. -- Stefan Seyfried "If your lighter runs out of fluid or flint and stops making fire, and you can't be bothered to figure out about lighter fluid or flint, that is not Zippo's fault." -- bkw -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 03/04/2013 05:16 PM, Stefan Seyfried wrote:
Am 04.03.2013 14:47, schrieb Joschi Brauchle:
On 11.4 and 12.2, loading the initrd takes just a handful of seconds (if at all), barely noticeable compared to the remaining boot process.
Compare the sizes, I'm pretty sure this will shed some light on the issue.
Yep, your right. In our configuration, the initrd of 11.4 is 11MB 12.2 is 17MB 12.3 is 32MB Hm, well then I guess there is nothing to be done about this delay? Is grub2 any faster than grub loading the initrd?
В Mon, 04 Mar 2013 17:54:45 +0100 Joschi Brauchle <joschi.brauchle@tum.de> пишет:
Yep, your right. In our configuration, the initrd of 11.4 is 11MB 12.2 is 17MB 12.3 is 32MB
Hm, well then I guess there is nothing to be done about this delay?
Is it possible to reduce size?
Is grub2 any faster than grub loading the initrd?
On BIOS it reads in max 64K - 512 bytes chunks. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
В Mon, 04 Mar 2013 15:01:40 -0300 Cristian Rodríguez <crrodriguez@opensuse.org> пишет:
El 04/03/13 14:07, Andrey Borzenkov escribió:
Is it possible to reduce size?
Yes, build with initrd with dracut -H --force --xz
Does not mkinitrd already does the same as "dracut -H"? So difference would come from compression only? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 03/04/2013 10:54 AM, Joschi Brauchle wrote:
On 03/04/2013 05:16 PM, Stefan Seyfried wrote:
Am 04.03.2013 14:47, schrieb Joschi Brauchle:
On 11.4 and 12.2, loading the initrd takes just a handful of seconds (if at all), barely noticeable compared to the remaining boot process.
Compare the sizes, I'm pretty sure this will shed some light on the issue.
Yep, your right. In our configuration, the initrd of 11.4 is 11MB 12.2 is 17MB 12.3 is 32MB
Hm, well then I guess there is nothing to be done about this delay? Is grub2 any faster than grub loading the initrd?
The size difference between 12.2 and 12.3 may be due to having debugging enabled for the RC version. On my 12.3 system, initrd for 3.7.9-1.4 is 33 MB. I'm actually using 3.9-rc1 from the wireless-testing repo with an initrd size of 37 MB. With grub2, it loads in 2-3 seconds on an HP dv2815 laptop with a modest AMD Turion CPU at 2 GHz. The difference might be grub2, or it might be due to poor performance for an i7 running in 8686-compatibility mode. I doubt that Intel spent much time optimizing those operations. Larry -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 03/04/2013 06:23 PM, Larry Finger wrote:
With grub2, it loads in 2-3 seconds on an HP dv2815 laptop with a modest AMD Turion CPU at 2 GHz.
The difference might be grub2, or it might be due to poor performance for an i7 running in 8686-compatibility mode. I doubt that Intel spent much time optimizing those operations.
Larry
So, out of curiosity I switched to grub2 and voila, initrd is loaded in "no time", i.e. faster than I can see on the screen really. No more 10 second delay with grub2. Switching back to grub reverts to slow boot. I was not seeing any need to switch to grub2 until now, but this speed difference (especially if it reduces boot times to normal on older Core2Duo machines) makes a significant difference. Is there any explanation for this (beyond what was already discussed)? I feel like there must be something wrong with grub on 12.3 and not that it is a simple "initrd size" issue... as mentioned initially, on 11.4 initrd loads instantly (11MB) but on 12.3 (32MB) takes in the order of 30-60 seconds. Sure it's 3 times as big, but takes about 30 times as long to load.
On Monday 2013-03-04 17:54, Joschi Brauchle wrote:
Compare the sizes, I'm pretty sure this will shed some light on the issue.
Yep, your right. In our configuration, the initrd of 11.4 is 11MB 12.2 is 17MB 12.3 is 32MB
Depends on which one you look at. But what is evident is that the installer initrd is 34 MB, 4-10x the size of the one generated for a running system, because it carries a lot of modules and part of the installer. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
So here is something interesting: I can reproduce and create slow and fast loading initrd's (with grub) on my machine! 1. Slow loading initrd but reinstalling kernel: # zypper in -f kernel-desktop ...<cut> (1/1) Installing: kernel-desktop-3.7.10-1.1.1 .........................................................................................................[done] Additional rpm output: Kernel image: /boot/vmlinuz-3.7.10-1.1-desktop Initrd image: /boot/initrd-3.7.10-1.1-desktop Root device: /dev/system/slash (mounted on / as ext4) /usr device: /dev/system/usr (mounted on /usr as ext4) Resume device: /dev/sda2 Kernel Modules: thermal_sys thermal processor fan dm-mod dm-snapshot scsi_dh scsi_dh_alua scsi_dh_rdac scsi_dh_emc scsi_dh_hp_sw xhci-hcd hid-logitech-dj linear Features: acpi dm plymouth block usb lvm2 resume.userspace resume.kernel --> Result: Slow boot with 10+ seconds delay at loading initrd 2. Fast loading initrd, just run: # mkinitrd Kernel image: /boot/vmlinuz-3.7.10-1.1-desktop Initrd image: /boot/initrd-3.7.10-1.1-desktop Root device: /dev/system/slash (mounted on / as ext4) /usr device: /dev/system/usr (mounted on /usr as ext4) Resume device: /dev/sda2 Kernel Modules: thermal_sys thermal processor fan dm-mod dm-snapshot scsi_dh scsi_dh_alua scsi_dh_rdac scsi_dh_emc scsi_dh_hp_sw xhci-hcd hid-logitech-dj linear Features: acpi dm plymouth block usb lvm2 resume.userspace resume.kernel --> Result: Fast boot with no delay! I unpacked both initrd's (into dirs "zypper" and "mkinitrd"): # diff -wuir zypper/ mkinitrd/ Only in zypper/bin: cat Only in zypper/bin: chmod Only in zypper/bin: cp Only in zypper/bin: date Only in zypper/bin: dmesg Only in zypper/bin: ls Only in zypper/bin: mkdir Only in zypper/bin: mknod Only in zypper/bin: mount Only in zypper/bin: mv Only in zypper/bin: rm Only in zypper/bin: sed Only in zypper/bin: sleep Only in zypper/bin: umount Only in zypper/bin: uname diff -wuir zypper/etc/adjtime mkinitrd/etc/adjtime --- zypper/etc/adjtime 2013-03-04 20:00:08.125172787 +0100 +++ mkinitrd/etc/adjtime 2013-03-04 20:04:38.492049355 +0100 @@ -1,3 +1,3 @@ --0.236439 1362423098 0.000000 -1362423098 +-0.236439 1362423464 0.000000 +1362423464 UTC diff -wuir zypper/mkinitrd.config mkinitrd/mkinitrd.config --- zypper/mkinitrd.config 2013-03-04 20:00:07.609173198 +0100 +++ mkinitrd/mkinitrd.config 2013-03-04 20:04:38.178049423 +0100 @@ -1 +1 @@ --k /boot/vmlinuz-3.7.10-1.1-desktop -i /boot/initrd-3.7.10-1.1-desktop +
Am 04.03.2013 20:07, Joschi Brauchle wrote:
So here is something interesting: I can reproduce and create slow and fast loading initrd's (with grub) on my machine!
I've seen the same behavior on 12.1 (or so) already, and I think I've also seen a bug report about it (I just cannot find it right now). It happened about on every second kernel update, and as for you, calling mkinitrd manually solved it. I never fully debugged it, but I think this might not be a new problem of 12.3. Philipp -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am 04.03.2013 20:18, schrieb Philipp Wagner:
Am 04.03.2013 20:07, Joschi Brauchle wrote:
So here is something interesting: I can reproduce and create slow and fast loading initrd's (with grub) on my machine!
I've seen the same behavior on 12.1 (or so) already, and I think I've also seen a bug report about it (I just cannot find it right now). It happened about on every second kernel update, and as for you, calling mkinitrd manually solved it. I never fully debugged it, but I think this might not be a new problem of 12.3.
It might also be pure luck: every call of mkinitrd creates a new binary blob which is placed differently in the filesystem. One time it might be better suited for grub's (pretty primitive) ext2 filesystem driver, the other time it might be ill suited. Just a guess, have not encountered this issue. -- Stefan Seyfried "If your lighter runs out of fluid or flint and stops making fire, and you can't be bothered to figure out about lighter fluid or flint, that is not Zippo's fault." -- bkw -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Monday 2013-03-04 20:31, Stefan Seyfried wrote:
Am 04.03.2013 20:18, schrieb Philipp Wagner:
Am 04.03.2013 20:07, Joschi Brauchle wrote:
So here is something interesting: I can reproduce and create slow and fast loading initrd's (with grub) on my machine!
I've seen the same behavior on 12.1 (or so) already, and I think I've also seen a bug report about it (I just cannot find it right now). It happened about on every second kernel update, and as for you, calling mkinitrd manually solved it. I never fully debugged it, but I think this might not be a new problem of 12.3.
It might also be pure luck: every call of mkinitrd creates a new binary blob which is placed differently in the filesystem. One time it might be better suited for grub's (pretty primitive) ext2 filesystem driver, the other time it might be ill suited.
"ill suited" how? Above/below the classic 1G/4G/32G barrier? If you have a "slow" and a "fast" initrd, please show filefrag -v /path/to/it for each of them. Maybe it turns something up. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
I have created a bugreport here on the original problem of slow loading of initrd here: https://bugzilla.novell.com/show_bug.cgi?id=808611 It includes the filefrag output. Best regards, J Brauchle On 03/06/2013 10:09 PM, Jan Engelhardt wrote:
filefrag -v
Joschi Brauchle wrote:
Hm, well then I guess there is nothing to be done about this delay? Is grub2 any faster than grub loading the initrd?
--- Using lilo and booting from disk avoids initrd all together. My kernel finishes mounting the file systems and going to the rc3 scripts in ... [ 9.898467] bio: create slab <bio-1> at 1 [ 10.320156] bio: create slab <bio-2> at 2 [ 12.848010] XFS (sdc2): Mounting Filesystem [ 12.931568] XFS (sdc2): Ending clean mount [ 12.943116] XFS (sdc3): Mounting Filesystem [ 13.010923] XFS (sdc3): Ending clean mount [ 13.023323] XFS (dm-3): Mounting Filesystem [ 13.255004] XFS (dm-3): Ending clean mount [ 13.274569] XFS (dm-8): Mounting Filesystem [ 13.479838] XFS (dm-8): Ending clean mount [ 13.485791] XFS (dm-9): Mounting Filesystem [ 13.672531] XFS (dm-9): Ending clean mount [ 13.736404] XFS (dm-0): Mounting Filesystem [ 13.987004] XFS (dm-0): Ending clean mount [ 14.005284] XFS (dm-7): Mounting Filesystem [ 14.164613] XFS (dm-7): Ending clean mount [ 14.170473] XFS (dm-1): Mounting Filesystem [ 14.337261] XFS (dm-1): Ending clean mount [ 14.365884] XFS (dm-6): Mounting Filesystem [ 14.534075] XFS (dm-6): Ending clean mount booting with all file systems mounted in 14.53 seconds... But that is systemVinit script based and booting with no initrd. The kernel I need to boot with is 5.4MB...in 12.1. It's really too bad that openSuse developers claim users have no interest in booting directly from the harddisk w/o initrd.... Unix vendors had the option to compile a kernel for direct boot about 20 years ago -- it took a while to regen the needed files, but you didn't do it every day...now days, a kernel gen takes a few minutes. AFter initial boot, about 15 seconds later I have login via console or net. Of that 15, about 7-8 seconds is cifs timing out because my workstations no longer mount after the switch to smb2 -- which I still haven't figured out... so the game a whack-a-mole continues... It really doesn't have to be all one way... -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 06/03/13 17:52, Linda Walsh wrote:
Joschi Brauchle wrote:
Hm, well then I guess there is nothing to be done about this delay? Is grub2 any faster than grub loading the initrd? --- Using lilo and booting from disk avoids initrd all together. My kernel finishes mounting the file systems and going to the rc3 scripts in ... [pruned]
AFter initial boot, about 15 seconds later I have login via console or net.
Of that 15, about 7-8 seconds is cifs timing out because my workstations no longer mount after the switch to smb2 -- which I still haven't figured out...
so the game a whack-a-mole continues...
It really doesn't have to be all one way...
On my installation 12.3 RC2 boots VERY quickly and, after I type in my password, I get to the desktop screen within seconds. BUT, but, it takes *forever* (?15 seconds) to get the Mixer, knemo, clipboard tool, and the HPLIP Status Service widgets to appear on the taskbar; the rest of the taskbar is populated as soon as the desktop appears following typing in the password. BC -- Using openSUSE 12.2 x86_64 KDE 4.10.00 & kernel 3.8.2-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel Corsair "Vengeance" RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX550Ti 1GB DDR5 GPU -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Basil Chupin wrote:
On 06/03/13 17:52, Linda Walsh wrote:
so the game a whack-a-mole continues...
It really doesn't have to be all one way...
On my installation 12.3 RC2 boots VERY quickly and, after I type in my password, I get to the desktop screen within seconds.
BUT, but, it takes *forever* (?15 seconds) to get the Mixer, knemo, clipboard tool, and the HPLIP Status Service widgets to appear on the taskbar; the rest of the taskbar is populated as soon as the desktop appears following typing in the password.
I don't run a desktop on mine, so that save time on my end. But I do run named, ntp, sendmail, samba, (it serves as a domain controller -- well, not so well these days, but still does the file serving), spamassassin takes a while to start 6 of the boot seconds is the fsck and mount of 30TB+ of storage, but when it works right winbind provides single-signon for my server and my windows workstations which are served by this machine (and have their roaming profiles on it), also starts up imap with full indexing that doesn't take 90% of the cpu (Tbird's indexing is notoriously bad after 2.x) socks and squid proxies, minidlna media server, webserver.... Normally uptime is 24/7 with only 1 unscheduled downtime in the past year (I hosed my glibc...had to restore from backup -- does daily backups, and daily snapshots for the windows clients so they see "previous versions" of files in their samba home dirs. (a near 2000 line perl script).... The fact that it only takes 15 seconds I find amazing. When I had a laptop it came up faster and booted to a desktop. Windows XP was about 10-15 seconds and that was 10 years ago. My cpu's are only 2.4GHz, slow by some standards...I know if I got all the kinks out it would come up faster, but it's level of performance is satisfactory for as often as I boot it. kmixer and such wouldn't even work on my server -- no sound and no graphics...(1024x768)... different tasks... for a desktop, your setup is great, but wouldn't work for me. This is just a guess -- but a strong reason why I DON'T want an initrd -- and it would slow me down -- is that it does a bunch of things for desktop systems, that my current boot skips -- because it's setting up as a server. But that's just a guess.... That's been the nice thing about Suse over the years -- has had something for everyone. I don't want to see that go... -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wed, Mar 6, 2013 at 5:01 AM, Basil Chupin <blchupin@iinet.net.au> wrote:
BUT, but, it takes *forever* (?15 seconds) to get the Mixer, knemo, clipboard tool, and the HPLIP Status Service widgets to appear on the taskbar; the rest of the taskbar is populated as soon as the desktop appears following typing in the password.
I get the same on 12.2, so it isn't new. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wednesday 2013-03-06 07:52, Linda Walsh wrote:
Joschi Brauchle wrote:
Hm, well then I guess there is nothing to be done about this delay? Is grub2 any faster than grub loading the initrd?
--- Using lilo and booting from disk avoids initrd all together. My kernel finishes mounting the file systems and going to the rc3 scripts in ...
The time window in question is the one before the kernel runs. The rest is irrelevant. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Jan Engelhardt wrote:
On Wednesday 2013-03-06 07:52, Linda Walsh wrote:
Joschi Brauchle wrote:
Hm, well then I guess there is nothing to be done about this delay? Is grub2 any faster than grub loading the initrd?
Using lilo and booting from disk avoids initrd all together. My kernel finishes mounting the file systems and going to the rc3 scripts in ...
The time window in question is the one before the kernel runs. The rest is irrelevant.
---- The time before?... you mean after the boot menu and first kernel output? But that's less than 1 second .. maybe a half? I also just found out that they 15 sec, was a time for complete boot-- since the other output on tty was intermixed -- only in the log is it serialized ... I saw it take nearly 25 seconds, later, due to a long scan in rpmconfigcheck... -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Thursday 2013-03-07 18:18, Linda Walsh wrote:
Jan Engelhardt wrote:
On Wednesday 2013-03-06 07:52, Linda Walsh wrote:
Joschi Brauchle wrote:
Hm, well then I guess there is nothing to be done about this delay? Is grub2 any faster than grub loading the initrd?
Using lilo and booting from disk avoids initrd all together. My kernel finishes mounting the file systems and going to the rc3 scripts in ...
The time window in question is the one before the kernel runs. The rest is irrelevant.
---- The time before?... you mean after the boot menu and first kernel output?
Yeah precisely. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (11)
-
Andrey Borzenkov -
Basil Chupin -
Claudio Freire -
Cristian Rodríguez -
Jan Engelhardt -
Joschi Brauchle -
Larry Finger -
Linda Walsh -
Per Jessen -
Philipp Wagner -
Stefan Seyfried