From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on sa.local.altlinux.org X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.1 From: Sergey To: ALT Linux Community general discussions Date: Tue, 12 Apr 2016 17:37:01 +0400 User-Agent: KMail/1.9.10 (enterprise35 0.20100827.1168748) References: <201602271535.26446.a_s_y@sama.ru> In-Reply-To: <201602271535.26446.a_s_y@sama.ru> X-KMail-QuotePrefix: > MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 8bit Content-Disposition: inline Message-Id: <201604121737.01126.a_s_y@sama.ru> Subject: [Comm] =?utf-8?b?bWFrZS1pbml0cmQsINC70LjRiNC90LjQtSDRhNCw0LnQu9GL?= =?utf-8?q?_=28RAM_disk_is_too_big_to_fit_between_the_kernel_and_the_15M-1?= =?utf-8?q?6M_memory_hole=29?= X-BeenThere: community@lists.altlinux.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: ALT Linux Community general discussions List-Id: ALT Linux Community general discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Apr 2016 13:37:14 -0000 Archived-At: List-Archive: List-Post: On Saturday 27 February 2016, Sergey wrote: > Заодно причина интереса: хочется посмотреть, что попадает туда ввиду такого > вот предупреждения от lilo: > > # update-kernel > Try to install new kernel kernel-image-ovz-el-2.6.32-alt138 and update its modules [y]/n? > ... > Packed modules: ata_generic ata_piix crc-t10dif ext3 jbd libata mbcache pata_acpi scsi_mod sd_mod > ... > Warning: The initial RAM disk is too big to fit between the kernel and >    the 15M-16M memory hole.  It will be loaded in the highest memory as >    though the configuration file specified "large-memory" and it will >    be assumed that the BIOS supports memory moves above 16M. > Added 2.6.32-ovz-el-alt138 ? Дошли руки. Для ovz-el-alt140 получилась вот такая разница для p7/x86_64, на двух идентичных интеловских платформах (правда, с несколько различным набором пакетов): 48a49 > ./etc/modprobe.d/alsa-modindex.conf 67a69,70 > ./etc/syslog.conf > ./etc/syslog.d 70d72 < ./etc/udev/rules.d/50-firmware.rules 72d73 < ./etc/udev/rules.d/60-cdrom_id.rules 74,76d74 < ./etc/udev/rules.d/64-device-mapper.rules < ./etc/udev/rules.d/64-md-raid.rules < ./etc/udev/rules.d/70-permissions.rules 140a139 > ./lib/initrd/modules/015-syslog 151a151,160 > ./lib/ld-2.17.so > ./lib/ld-linux.so.2 > ./lib/libc-2.17.so > ./lib/libc.so.6 > ./lib/libnss_dns-2.17.so > ./lib/libnss_dns.so.2 > ./lib/libnss_files-2.17.so > ./lib/libnss_files.so.2 > ./lib/libresolv-2.17.so > ./lib/libresolv.so.2 200a210 > ./sbin/klogd 204a215 > ./sbin/syslogd 218a230,234 > ./var/log > ./var/log/initramfs > ./var/run > ./var/run/klogd.pid > ./var/run/syslogd.pid Интересно, зачем make-initrd втянул /lib/* и klogd/syslogd во втором случае ? На всякий случай поменял klogd/syslogd на syslog-ng (как на первом сервере), набор /lib/* попал в initrd точно так же. На первом ещё нет OpenVZ - ядро просто так ставил. update-kernel-0.9.5-alt1 -- С уважением, Сергей.