Hi,
I got a panic when running CentOS-6.5:
crash> bt
PID: 106074 TASK: 8839c1e32ae0 CPU: 4 COMMAND: "flushd4[cbd-sd-"
#0 [8839c2a91900] machine_kexec at 81038fa9
#1 [8839c2a91960] crash_kexec at 810c5992
#2 [8839c2a91a30] oops_end at 81515c90
ed, 18 Oct 2017, wuzhouhui wrote:
Does anyone have encountered same problem or advice?
Expect minimal help when running custom kernel modules on painfully old
CentOS
kernels?
jh
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailma
Fine, it seems that upgrade kernel is the only effective solution.
> On 18 Oct 2017, at 10:00 PM, Stephen John Smoogen <smo...@gmail.com> wrote:
>
> On 18 October 2017 at 04:50, wuzhouhui <wuzhouhu...@mails.ucas.ac.cn> wrote:
>> I googled this issue and found so m
Never mind, commit 1a040eaca1a2 (bridge: fix multicast router rlist endless
loop)
fixes it.
> -原始邮件-
> 发件人: wuzhouhui <wuzhouhu...@mails.ucas.ac.cn>
> 发送时间: 2018-01-10 15:19:09 (星期三)
> 收件人: centos@centos.org
> 抄送: wuzhouhui14 <wuzhouhu...@mails.ucas.ac.cn>
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@node-0 at Jan 9
Forward mail to centos-devel mailing list for getting more attentions!
Sorry for disturbing.
> -Original Messages-
> From: wuzhouhui <wuzhouhu...@mails.ucas.ac.cn>
> Sent Time: 2018-02-07 13:44:07 (Wednesday)
> To: centos@centos.org
> Cc: wuzhouhui14 <wuzh
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
When start service libvirtd by
service libvirtd start
the network will broke for a while and then reconnected. Following is
/var/log/messages:
Feb 24 13:28:51 node-0 kernel: lo: Dropping TSO features since no CSUM feature.
Feb 24 13:28:51 node-0 kernel: lo: Disabled Privacy Extensions
Feb
Never mind, I have found the reason. When libvirtd started, it will create
bridge virbr0 and then write 1 to /proc/sys/net/ipv4/ip_forward (0 in default).
Set ip_forward from 0 to 1 will cause ixgbe driver reset NIC, so the network
broke for a while.
> -Original Messages-
> From:
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!
___
CentOS mailing list
CentOS@centos.org
> -Original Messages-
> From: "Steven Tardy" <sjt5a...@gmail.com>
> Sent Time: 2018-02-26 10:48:48 (Monday)
> To: "CentOS mailing list" <centos@centos.org>
> Cc:
> Subject: Re: [CentOS] How to update modules in iniramfs fastly
>
quot;CentOS mailing list" <centos@centos.org>
> Cc:
> Subject: Re: [CentOS] How to update modules in iniramfs fastly
>
> On Mon, 26 Feb 2018, wuzhouhui wrote:
>
> > > -Original Messages-
> > > From: "Steven Tardy" <sjt5a...@gmail.
OS: CentOS 6.5
Crash: crash-7.1.0-6.el6.x86_64
Kdump: kexec-tools-2.0.0-273.el6.x86_64
GDB: gdb-7.2-60.el6_4.1.x86_64
/etc/kdump.conf: core_collector makedumpfile -c --message-level 1 -d 31
Kernel crashed by panic("string"), but I can't see any register in vmcore:
crash> bt
PID: 53331 TASK:
LTP version: ltp-full-20180118
Kernel version: 3.10.0-693.el7.x86_64
Reproduce procedure:
1. cd ltp-full-20180118; ./configure; make && make install
2. cd /opt/ltp; ./runltp
Trace:
[ 377.516270] BUG: unable to handle kernel NULL pointer dereference at
(null)
[ 377.521746] IP:
> -Original Messages-
> From: "Leon Fauster" <leonfaus...@googlemail.com>
> Sent Time: 2018-02-26 22:20:51 (Monday)
> To: "CentOS mailing list" <centos@centos.org>
> Cc:
> Subject: Re: [CentOS] How to update modules in iniramfs fastly
Forwarded to centos mailing list
-Original Messages-
From: wuzhouhui
Sent Time: 2018-10-30 14:06:00 (Tuesday)
To: "storage performance development kit"
Cc: centos@centos.org, qemu-disc...@nongnu.org
Subject: Re: [SPDK] VM boot failed sometimes if using vhost-user-blk with spdk
Who told you there is kernel-3.10.0-693.17.6.el7 available? You can't find
these two rpms in vault.centos.org means that centos.org never release
them at all.
> -Original Messages-
> From: qw
> Sent Time: 2018-11-10 15:54:25 (Saturday)
> To: centos@centos.org
> Cc:
> Subject: [CASS
...
[ 176.025679] random: crng init done
[ 411.168635] netem: version 1.3
[ 456.059840] [ cut here ]
[ 456.059849] WARNING: CPU: 4 PID: 1918 at net/ipv4/tcp_output.c:1048
tcp_set_skb_tso_segs+0xeb/0x100
[ 456.059851] Modules linked in: sch_netem cirrus ttm
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
___
CentOS mailing list
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)?
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.
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
will uninstall old version after install new one, how to disable it?
> -Original Messages-
> From: "Gianluca Cecchi"
> 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
>
> -Original Messages-
> From: "Benjamin Hauger"
> Sent Time: 2019-03-28 01:31:40 (Thursday)
> To: wuzhouhui , centos@centos.org
> Cc:
> Subject: Re: [CentOS] How to specify kernel version when restart kdump
>
> What do you mean? Wouldn't the k
Hi,
Sometimes, I found one of my Mellanox NIC renamed to rename6, instead
of eth1. The right names of NICs in my system should be:
eth0Mellanox NIC
eth1Mellanox NIC
eth2Intel NIC
eth3Intel NIC
eth4Intel NIC
eth5Intel NIC
eth0
ng kernel version when start kdump service.
Thanks.
>
>
> On 3/25/19 7:19 PM, wuzhouhui wrote:
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
> -Original Messages-
> From: wuzhouhui
> Sent Time: 2019-03-29 10:06:06 (Friday)
> To: "centos mailing list"
> Cc:
> Subject: Re: [CentOS] How to specify kernel version when restart kdump
>
> > -Original Messages-
> > From: "Gian
Hi,
When I build a mpt3sas rpm package, I found something interesting:
1. package name is prefixed with kmod- automatically
2. so many requirements are added automatically, most of them are kabi
So my question is rpmbuild how to know he is building kernel module package?
Based on which
> On Apr 12, 2019, at 11:12 PM, Gordon Messmer wrote:
>
> On 4/12/19 7:04 AM, wuzhouhui wrote:
>> So my question is rpmbuild how to know he is building kernel module package?
>> Based on which condition?
>
>
> I believe the %kernel_module_package macro def
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.
t;
3.2 Install kernel-3.10.0-327.el7.x86_64.rpm with "rpm -i --force --nodeps"
4. Reboot
Then we'll see the system boot and running as normal. And /etc/grub.conf
updated automatically.
> -Original Messages-
> From: wuzhouhui
> Sent Time: 2019-05-07 16:05:54 (Tuesday)
> -Original Messages-
> From: "Steven Tardy"
> Sent Time: 2019-04-28 13:02:18 (Sunday)
> To: "CentOS mailing list"
> Cc:
> Subject: Re: [CentOS] Who is responsible to load NIC driver when boot up
>
> On Sat, Apr 27, 2019 at 11:44 PM wuzhou
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.
___
CentOS mailing list
CentOS@centos.org
> -Original Messages-
> From: "Stephen John Smoogen"
> Sent Time: 2019-04-28 21:54:13 (Sunday)
> To: "CentOS mailing list"
> Cc:
> Subject: Re: [CentOS] Who is responsible to load NIC driver when boot up
>
> On Sun, 28 Apr 2019 at 01:22
34 matches
Mail list logo
