similar to: Memory for crash kernel

when I run dmesg PE2950 Dell Server I see the following line Linux version 2.6.18-92.1.6.el5 (mockbuild at builder15.centos.org) (gcc version 4.1.2 20071124 (Red Hat 4.1.2-42)) #1 SMP Wed J un 25 13:45:47 EDT 2008 Command line: ro root=/dev/VolGroup00/LogVol00 rhgb quiet BIOS-provided physical RAM map: BIOS-e820: 0000000000000000 - 00000000000a0000 (usable) BIOS-e820: 0000000000100000 -

I installed Centos 5.2 on DELL 2650 server (fresh install).? After installed finish, I reboot server and get following messages and server hang: ? Memory for crash kernel (0x0 to 0x0) notwithin permissible range Redhat nash version 5.1.19.6 starting ? ? Anyone know why? ? Thanks. ? _______________________________________________________________________________________________________

Hi, I'm usually booting all machines here with 'vga=788 quiet' options in menu.lst, so I see what services start, but it's not too verbose at the same time. One message that puzzles me is the very first one after GRUB starts init: "Memory for crash kernel (0x0 to 0x0) notwithin permissible range." Anyone knows what that means? Niki

Hello! I am running CentOS-5 with latest kernel available by deault (2.6.23). I installed it on a Dell XPS machine having Intel Quad processors (4 parallel cpus). I use it to run a computational program and I need to keep the program running for 1-2 months continuously. I generally boot it in runlevel-3 with network ON without X and use ssh from another machine to connect and run the program

Hi all, After an electric breaking, my server (Centos 5.2 x86_64 with all updates) can not boot. The error message on screen is: ----------------------------------------------------------------------------------------------------------- Memory for crash kernel (0x0 to 0x0) notwithin permissible range <0> HARDWARE ERROR CPU 1: Machine Check Exception: 7 Bank 4: .... RIP 10:<.....>

Hi, Am trying to build SMP kernel. Took kernel-2.6.18-194.src.rpm, extracted, rpmbuilded with SMP option. Successfully compile the new kernel and when using that kernel to boot up, following errors were shown up(highlighted in bold & red color): My kernel config file has ACPI and PCI configs enabled. Any pointers to what caused the problem are appreciated. ******************************

This (CentOS5.1) box is my new imap server. Using system-config-security-level I opened port 143 tcp, and mail is readable throughout the LAN. I want a Roaming account on my laptop so that I can read mail while away from home. I have set up the account in kmail, and I know that that part is correct, as it worked on my old, less-secured, imap server. However, I haven't been able so far

My HP MicroServer crashes with a kernel panic when booted into kernel-3.10.0-327.3.1.el7.x86_64, but runs perfectly under kernel-3.10.0-229.20.1.el7.x86_64 . I've been trying to save the panic message with kdump, but am not sure how one can configure kdump to do this, if indeed that is possible. -- Timothy Murphy gayleard /at/ eircom.net School of Mathematics, Trinity College, Dublin

Hi folks, I've been trying to wrap my head around this for a bit, done my googling and archive searching but I still can't seem to 'get' it. Here goes: I've a spare drive in my CentOS5.1 box, which (for testing now) I mount manually under /mnt/backup I want to backup the /home tree to that box nightly via rsync (cronjob), so I tried this: rsync -avrogz /home/

Hi , Can any one please let me know how to capture all the boot messages of the Guest OS into a text file? I do xm create -c /etc/xen/hvm.cfg to boot the guest OS. Thanks Kishore _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

Hi, I am running Centos5.1, trying to configure samba now. I am quite new in this area and hope help from the list. I could not connect to it from a windows xp pc >From the console, I log in and do a >smbclient -L localhost -U% Domain=[MYGROUP] OS=[Unix] Server=[Samba 3.0.25b-0.el5.4] Sharename Type Comment --------- ---- ------- samba

What do you mean? Wouldn't the kernel version always be the actual running version of the kernel that was booted? Ben On 3/26/19 6:16 PM, wuzhouhui wrote: >> -----Original Messages----- >> From: "Benjamin Hauger" <hauger at noao.edu> >> Sent Time: 2019-03-27 00:15:21 (Wednesday) >> To: centos at centos.org >> Cc: >> Subject: Re: [CentOS]

Hi there, I have a Dell T3400 Workstation with CentOS5.1 as dom0. I have hidden a network interface in dom0 to pass it to domU. The domU can come up with the NIC when it''s OS is CentOS5.1 or RHEL5. But when it comes to RedHat4.5 , the NIC can not be found. As I type the command "lspci" in RHEL4.5 domU, it returned: pcilib: Cannot open /proc/bus/pci

kdump operates by booting a fresh kernel to capture the context of a crashed kernel, and so the only way for kdump to dump a kernel is to crash it and cause kdump to invoke its post-crash kernel. You can manually force a running kernel to panic (and invoke a correctly-configured kdump) with the following command sequence: > echo 1 > /proc/sys/kernel/sysrq > echo c >

Howdy, Running a round of updates from 6.3 to 6.4 and I'm seeing the following on all the servers. Want to make sure I'm not going to end up with a kernel panic if I reboot into the new kernel or have any other issues. Apr 22 11:10:21 www kdump: kexec: unloaded kdump kernel Apr 22 11:10:21 www kdump: stopped Apr 22 11:10:21 www kdump: mkdumprd: failed to make kdump initrd Apr 22

Hi all, Is there a way to 'automatically' recreate users/permissions when moving from RH8 (yes, I know...way old) to CentOS5.1 or is it just simpler to recreate the users manually? Total users on this system is < 20. Thanks in advance, -Ray

Hi All, I need help getting my jailtime centos 5.1 network going on my dom0 ubuntu feisty with domU centos5.1. I do this: ifconfig eth0 192.168.0.14 netmask 255.255.255.0 up I can then ping myself. When I try to ping another ip like on the host or other servers I get: ping 192.168.0.110 PING 192.168.0.110 (192.168.0.110) 56(84) bytes of data. >From 192.168.0.14 icmp_seq=2 Destination Host

Hi, This set of patches contains initial kexec/kdump implementation for Xen v2 (previous version were posted to few people by mistake; sorry for that). Currently only dom0 is supported, however, almost all infrustructure required for domU support is ready. Jan Beulich suggested to merge Xen x86 assembler code with baremetal x86 code. This could simplify and reduce a bit size of kernel code.

Hi, This set of patches contains initial kexec/kdump implementation for Xen v2 (previous version were posted to few people by mistake; sorry for that). Currently only dom0 is supported, however, almost all infrustructure required for domU support is ready. Jan Beulich suggested to merge Xen x86 assembler code with baremetal x86 code. This could simplify and reduce a bit size of kernel code.

Hi, This set of patches contains initial kexec/kdump implementation for Xen v2 (previous version were posted to few people by mistake; sorry for that). Currently only dom0 is supported, however, almost all infrustructure required for domU support is ready. Jan Beulich suggested to merge Xen x86 assembler code with baremetal x86 code. This could simplify and reduce a bit size of kernel code.