similar to: How to specify kernel version when restart kdump

On Thu, Mar 28, 2019 at 6:55 AM wuzhouhui <wuzhouhui14 at mails.ucas.ac.cn> wrote: > > -----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

> -----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 >

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]

> -----Original Messages----- > From: "Gianluca Cecchi" <gianluca.cecchi at gmail.com> > Sent Time: 2019-03-28 16:59:19 (Thursday) > [...] > The command line fo CentOS 6 clearly misses the kernel version to build > initrd file for, so the correct command should be: > > /sbin/mkdumprd -d -f > "/boot/initrd-2.6.32-642.13.1.el6.x86_64kdump.img"

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-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

On Thu, Mar 28, 2019 at 9:24 AM Gianluca Cecchi <gianluca.cecchi at gmail.com> wrote: > > > 1) In CentOS 6 we have the classical SysV service > file: /etc/rc.d/init.d/kdump > > Supposing you have just installed 2.6.32-642.13.1.el6.x86_64 kernel > > [snip] > > and at the end it runs this command if it doesn't find one: > $MKDUMPRD $kdump_initrd

> -----Original Messages----- > From: "Steven Tardy" <sjt5atra at gmail.com> > Sent Time: 2018-02-26 10:48:48 (Monday) > To: "CentOS mailing list" <centos at centos.org> > Cc: > Subject: Re: [CentOS] How to update modules in iniramfs fastly > > On Sun, Feb 25, 2018 at 8:29 PM wuzhouhui <wuzhouhui14 at mails.ucas.ac.cn> > wrote:

> Am 26.02.2018 um 06:46 schrieb wuzhouhui <wuzhouhui14 at mails.ucas.ac.cn>: > >> -----Original Messages----- >> From: "Steven Tardy" <sjt5atra at gmail.com> >> Sent Time: 2018-02-26 10:48:48 (Monday) >> To: "CentOS mailing list" <centos at centos.org> >> Cc: >> Subject: Re: [CentOS] How to update modules in

> -----Original Messages----- > From: "Steven Tardy" <sjt5atra at gmail.com> > Sent Time: 2019-04-28 13:02:18 (Sunday) > To: "CentOS mailing list" <centos at centos.org> > Cc: > Subject: Re: [CentOS] Who is responsible to load NIC driver when boot up > > On Sat, Apr 27, 2019 at 11:44 PM wuzhouhui <wuzhouhui14 at mails.ucas.ac.cn> >

I know dracut can update modules in initramfs, but I think it is too slow. So I'm wondering what is the fastest way to update modules in initramfs of CentOS 7? Thanks!

Fine, it seems that upgrade kernel is the only effective solution. > On 18 Oct 2017, at 10:00 PM, Stephen John Smoogen <smooge at gmail.com> wrote: > > On 18 October 2017 at 04:50, wuzhouhui <wuzhouhui14 at mails.ucas.ac.cn> wrote: >> I googled this issue and found so many people have encountered, but most of >> them just said "the newer kernel doesn't

I googled this issue and found so many people have encountered, but most of them just said "the newer kernel doesn't have this problem, so upgrade kernel". We can't upgrade kernel easily, so we need to *really* solve this problem. On 10/18/2017 04:41 PM, John Hodrien wrote: > On Wed, 18 Oct 2017, wuzhouhui wrote: > >> Does anyone have encountered same problem or

Hi I have a small question about NIC driver (e.g. i40e) loading. Who is responsible to load i40e driver? And how does he knows we should load i40e, instead of ixgbe? Thanks.

On Sun, 28 Apr 2019 at 01:22, wuzhouhui <wuzhouhui14 at mails.ucas.ac.cn> wrote: > > -----Original Messages----- > > From: "Steven Tardy" <sjt5atra at gmail.com> > > Sent Time: 2019-04-28 13:02:18 (Sunday) > > To: "CentOS mailing list" <centos at centos.org> > > Cc: > > Subject: Re: [CentOS] Who is responsible to load NIC

I seem to be struggling with setting up kdump to debug Xen/dom0 freeze. According to http://xenbits.xen.org/docs/unstable/misc/kexec_and_kdump.txt the "crashkernel=" parameter must be passed to the Xen hypervisor. When it is passed to Xen I dont see "Crash Kernel" under System RAM in /proc/iomem inside dom0. I am missing something obvious here. Could someone please explain why

Hi, Recently, I encountered a interesting phenomenon that CentOS 6.3 running as normal even if I (my colleague, actually) installed a kernel that build for CentOS 7.x (e.g. kernel-3.10.0-327.el7.x86_64.rpm). I found kernel is mismatch accidentally when I using "uname -r" to check kernel version. So my question is what the harmness we will get if I install a el7 rpm into a el6 system?

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, I have a specific needs that requires yum do not to uninstall old version when install new one. For example, I found that yum install kernel will install new kernel, and old kernel will remained. But yum install <something-else> will uninstall old version after install new one, how to disable it? Thanks.

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