similar to: Kexec / Kdump - xen-3.0.4-testing-13098

I want to know if I buy a Tyan Transport GX28 (B2881) will it work with a TDM400 card? As the expansion slots are only (2) 64-bit 133/100MHz PCI-X. I never tried PCI 2.2 compliant card in a PCI-X slot so I don't know if it can even fit in the slot and if it does will it be seen? Thanks Martin Roy

> On 12/26/2012 06:18 PM, Daniel Kiper wrote: > > Add i386 kexec/kdump implementation. > > > > v2 - suggestions/fixes: > > - allocate transition page table pages below 4 GiB > > (suggested by Jan Beulich). > > Why? Sadly all addresses are passed via unsigned long variable to kexec hypercall. Daniel

> On 12/26/2012 06:18 PM, Daniel Kiper wrote: > > Add i386 kexec/kdump implementation. > > > > v2 - suggestions/fixes: > > - allocate transition page table pages below 4 GiB > > (suggested by Jan Beulich). > > Why? Sadly all addresses are passed via unsigned long variable to kexec hypercall. Daniel

Hi all, Here I am sending as attachments patches enabling kexec/kdump support in Xen PV domU. Only x84_64 architecture is supported. There is no support for i386 but some code could be easily reused. Here is a description of patches: - kexec-tools-2.0.3_20120522.patch: patch for kexec-tools which cleanly applies to version 2.0.3, - kexec-kernel-only_20120522.patch: main kexec/kdump kernel

Hi all, Here I am sending as attachments patches enabling kexec/kdump support in Xen PV domU. Only x84_64 architecture is supported. There is no support for i386 but some code could be easily reused. Here is a description of patches: - kexec-tools-2.0.3_20120522.patch: patch for kexec-tools which cleanly applies to version 2.0.3, - kexec-kernel-only_20120522.patch: main kexec/kdump kernel

Hi all, Here I am sending as attachments patches enabling kexec/kdump support in Xen PV domU. Only x84_64 architecture is supported. There is no support for i386 but some code could be easily reused. Here is a description of patches: - kexec-tools-2.0.3_20120522.patch: patch for kexec-tools which cleanly applies to version 2.0.3, - kexec-kernel-only_20120522.patch: main kexec/kdump kernel

Add guide to using the kexec and kdump facility in xen. Signed-off-by: Simon Horman <horms@verge.net.au> --- I the work on this document using an ia64 machine and qemu emulating x86_32. I am yet to verify it on x86_32 hardware or x86_64. Index: xen-unstable.hg/docs/misc/kexec_and_kdump.txt =================================================================== --- /dev/null 1970-01-01

You posted to xen-ia64-devel & xen-ia64 (deleted the wrong word?) rather than xen-devel so I added that to the CC. On Thu, 2007-09-20 at 13:38 +0900, Simon Horman wrote: > On IA64 alloc_bootmem_low() can''t be called this early. > > Before alloc_bootmem_low() can be called init_bootmem(), which is called in > find_memory(). However xen_machine_kexec_setup_resources() is

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

Hello, I've encountered recurring issue with samba crashes when creating initial Time Machine backup on samba share from Mac. Whole scenario, details about software and logs are below. On Mac client: connected to smb share with "valid user" account; added smb share as Time Machine disk. Time machine has been set for automatic backup, I've selected Back Up Now. Connection dies

Ok rebooted All running ok now. Great thanks a lot! In system.log Jun 15 21:38:54 c01 com.apple.xpc.launchd[1] (org.networkupstools.upsmon): Unknown key for Boolean: SuccessfulExit Jun 15 21:38:54 c01 com.apple.xpc.launchd[1] (org.networkupstools.upsmon): This service is defined to be constantly running and is inherently inefficient. What is the purpose of Boolean: SuccessfulExit?

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 >

> -----Original Messages----- > From: "Benjamin Hauger" <hauger at noao.edu> > Sent Time: 2019-03-28 01:31:40 (Thursday) > To: wuzhouhui <wuzhouhui14 at mails.ucas.ac.cn>, centos at centos.org > Cc: > Subject: Re: [CentOS] How to specify kernel version when restart kdump > > What do you mean? Wouldn't the kernel version always be the actual >

OK... maybe I got a little anxious and ran out and bought a Tyan GX28 with dual Opteron (dual core) processors. (It is a nice server ;) ) I did neglect to find out that you can not manually set the IRQ's on this motherboard. I am now stuck sharing an IRQ with the ethernet controller and no foreseeable end to my dilemma. I have a Digium TE210P and zttest consistently runs at 99.97% which

This removes the custom kdump configurations by emptying the configuration file /etc/kdump.conf. Signed-off-by: Wanlong Gao <gaowanlong@cn.fujitsu.com> --- sysprep/Makefile.am | 1 + sysprep/sysprep_operation_kdump_config.ml | 44 +++++++++++++++++++++++++++++++ 2 files changed, 45 insertions(+) create mode 100644 sysprep/sysprep_operation_kdump_config.ml diff

> -----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] How to specify kernel version when restart kdump > > kdump operates by booting a fresh kernel to capture the context of a > crashed kernel, and so the only way for kdump to

Consider the following output [R2.2.0; Windows XP] > set.seed(160706) > X <- matrix(rnorm(40),nrow=10,ncol=4) > Xpc <- princomp(X,cor=FALSE) > summary(Xpc,loadings=TRUE, cutoff=0) Importance of components: Comp.1 Comp.2 Comp.3 Comp.4 Standard deviation 1.2268300 0.9690865 0.7918504 0.55295970 Proportion of Variance 0.4456907 0.2780929

Requires "kdump support" patch for ovirt-node Signed-off-by: Alan Pevec <apevec at redhat.com> --- common-blacklist.ks | 2 +- common-pkgs.ks | 2 ++ ovirt-node-image.ks | 10 +++++++++- 3 files changed, 12 insertions(+), 2 deletions(-) diff --git a/common-blacklist.ks b/common-blacklist.ks index 2452237..af7fa07 100644 --- a/common-blacklist.ks +++

Hello, I am new in this mailing,please if somebody knows how to make kdump able to load in startup. i will be very thankful, -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20090409/d3435a68/attachment-0002.html>

Hi, Is there a way to specify kernel version when (re)start kdump service? Suppose I have install a new kernel and kdump will generate kdump.img for new kernel in next boot. But I want kdump to generate kdump.img for new kernel immediately, is it possible? Thanks.