similar to: How to update modules in iniramfs fastly

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

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?

On Mon, 26 Feb 2018, wuzhouhui wrote: > > -----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

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

On Sun, Feb 25, 2018 at 8:29 PM wuzhouhui <wuzhouhui14 at mails.ucas.ac.cn> wrote: > 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? `dracut` calls `mkinitrd` which rebuilds the initrd file. . . you could do it manually but that is prone to errors (

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

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

Hi, I am a developer who worked on CentOS. Recently I am working on porting one of my block drivers from CentOS 6.x to CentOS 7.x. In newest kernel (kernel-3.10.0-693.17.1.el7) I found there is an issue in submit_bio()'s first argument: void submit_bio(int rw, struct bio *bio) The type of bi_rw of struct bio is unsigned long, and the number of enum rq_flags_bits also exceeds 32, so we

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.

On 2019-05-07 04:50, Stephen John Smoogen wrote: > On Tue, 7 May 2019 at 04:06, wuzhouhui <wuzhouhui14 at mails.ucas.ac.cn> wrote: > >> 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).

OS: CentOS 6.5. After I set multicast_router of bridge and it's port to 2, like following: echo 2 > /sys/devices/virtual/net/eth81/bridge/multicast_router echo 2 > /sys/devices/virtual/net/bond2/brport/multicast_router Then soft lockup occured: Message from syslogd at node-0 at Jan 9 15:47:12 ... kernel:BUG: soft lockup - CPU#0 stuck for 61s! [swapper:0] And the call

Hi, I following the steps described in https://wiki.centos.org/Sources to get centos7.x kernel repo. But I'm wondering how to get centos6.x kernel repo. Because when checkout branch 'c6' and found that there is nothing. Thanks

Hi, I cloned https://git.centos.org/r/rpms/kernel.git and found that it only contains kernel version that CentOS released. So how do I get the kernel version that CentOS not release officialy, e.g. 3.10.0-341.el7 and 3.10.0-383.el7 (some kernel version I found in kernel.spec's changelog)? Thanks.

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

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

Forwarded to centos mailing list -----Original Messages----- From: wuzhouhui <wuzhouhui14 at mails.ucas.ac.cn> Sent Time: 2018-10-30 14:06:00 (Tuesday) To: "storage performance development kit" <spdk at lists.01.org> Cc: centos at centos.org, qemu-discuss at nongnu.org Subject: Re: [SPDK] VM boot failed sometimes if using vhost-user-blk with spdk I enable debug of

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