When testing inject uncorrected error, it crashed in CentOS kernel 4.18 but pass in upstream kernel 5.15 This issue may relate to: https://unix.stackexchange.com/questions/714922/inject-uncorrected-error-then-system-reboot https://unix.stackexchange.com/questions/715005/why-kernel-panic-when-panic-on-warn-0?noredirect=1#comment1354709_715005 Summary the call trace:

[   242.337362] kernel BUG at arch/x86/kernel/cpu/mce/core.c:1364!

I checked this kernel (CentOS 8.5.2111 kernel), the line 1364 is:

1363 out_ist:
1364 	nmi_exit();

P.S The code in the CentOS kernel looks quite different from the upstream kernel. then trigger BUG_ON(!in_nmi()); ( in my understanding )

#define nmi_exit()						\
	do {							\
		lockdep_hardirq_exit();				\
		rcu_nmi_exit();					\
		BUG_ON(!in_nmi());				\
		__preempt_count_sub(NMI_OFFSET + HARDIRQ_OFFSET);	\
		ftrace_nmi_exit();				\
		lockdep_on();					\
		printk_nmi_exit();				\
		arch_nmi_exit();				\
	} while (0)

Here is the CentOS 4.18 kernel download: https://vault.centos.org/8.5.2111/BaseOS/Source/SPackages/kernel-4.18.0-348.el8.src.rpm overall log:

[root@localhost GreenTea]# ./einj_mem_uc -f 'single'

0: single   vaddr = xxxxxxxx paddr = xxxxx[   242.248140] core: Uncorrected hardware memory error in user-access at xxxxxxxx
[   242.248410] {1}[Hardware Error]: Hardware error from APEI Generic Hardware Error Source: 0
[   242.257296] BUG: scheduling while atomic: einj_mem_uc/9237/0x00110000
a400
[   242.258700] Memory failure: xxxx: Killing einj_mem_uc:9237 due to hardware memory corruption
[   242.267021] {1}[Hardware Error]: event severity: recoverable
[   242.267022] {1}[Hardware Error]:  Error 0, type: recoverable
[   242.267023] {1}[Hardware Error]:  fru_text: Card01, ChnG, DIMM0
[   242.267023] {1}[Hardware Error]:   section_type: memory error
[   242.267024] {1}[Hardware Error]:   error_status: 0x0000000000000400
[   242.267024] {1}[Hardware Error]:   physical_address: 0x00000004805da400
[   242.267026] {1}[Hardware Error]:   node: 0 card: 6 module: 0 rank: 0 bank: 16 device: 0 row: 8835 column: 16 
[   242.267026] {1}[Hardware Error]:   error_type: 4, single-symbol chipkill ECC
[   242.267027] {1}[Hardware Error]:   DIMM location: _Node0_Channel6_Dimm0 CPU0_G0 
[   242.267053] Memory failure: xxxxx: already hardware poisoned
[   242.274392] Memory failure: xxxxx: recovery action for dirty LRU page: Recovered
[   242.285519] EDAC skx MC3: HANDLING MCE MEMORY ERROR
[   242.318662] ------------[ cut here ]------------
[   242.326171] EDAC skx MC3: CPU 0: Machine Check Event: 0x0 Bank 255: 0xb40000000000009f
[   242.337362] kernel BUG at arch/x86/kernel/cpu/mce/core.c:1364!
[   242.337366] invalid opcode: 0000 [#1] SMP NOPTI
[   242.337367] CPU: 139 PID: 9237 Comm: einj_mem_uc Kdump: loaded Tainted: G   M    W        --------- -  - 4.18.0-348.el8.x86_64 #1
[   242.337368] Hardware name: Foo Inc. Foo  BIOS 4C012 01/21/2022
[   242.345383] EDAC skx MC3: TSC 0x0 
[   242.345383] EDAC skx MC3: ADDR 0x4805da400 
[   242.353765] RIP: 0010:do_machine_check+0xb10/0xc70
[   242.353766] Code: 42 bf f4 01 00 00 e8 df 92 92 00 8b 05 b9 cb e2 01 41 39 c7 7e 2d 4c 89 ee 4c 89 e7 e8 09 ec ff ff 85 c0 74 dc e9 17 fe ff ff  0b 0f 0b 8b 35 1a 6c 7e 01 e9 05 fb ff ff c7 05 87 cb e2 01 01
[   242.353766] RSP: 0018:ff2f652d53383e58 EFLAGS: 00010046
[   242.353767] RAX: 0000000080000000 RBX: 00000000004805da RCX: 3ffffffffffffffe
[   242.353768] RDX: ff121aa3ffbeaf40 RSI: 0000000000000001 RDI: ff121a69005db000
[   242.360497] EDAC skx MC3: MISC 0x0 
[   242.360498] EDAC skx MC3: PROCESSOR 0:0x806f6 TIME 1529665988 SOCKET 0 APIC 0x0
[   242.369175] RBP: ff121a65a70f3c80 R08: ff121a6480000010 R09: 0000000000000000
[   242.369176] R10: 0000000000000002 R11: 0000000000000003 R12: 0000000000000000
[   242.369176] R13: 0000000000000000 R14: ff121aa3ffb95ce0 R15: 0000000000000014
[   242.369177] FS:  00007fe1bde23640(0000) GS:ff121aa3ffbc0000(0000) knlGS:0000000000000000
[   242.369177] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[   242.369177] CR2: 00007f50808270cc CR3: 00000001d0118001 CR4: 0000000000771ee0
[   242.369178] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[   242.369178] DR3: 0000000000000000 DR6: 00000000fffe07f0 DR7: 0000000000000400
[   242.369179] PKRU: 55555554
[   242.369179] Call Trace:
[   242.369182]  ? machine_check+0x25/0x40
[   242.374751] EDAC MC3: 1 UE memory read error on CPU_SrcID#0_MC#3_Chan#0_DIMM#0 (channel:0 slot:0 page:0x4805da offset:0x400 grain:32 -  err_code:0x0000:0x009f  SystemAddress:0x4805da400 ProcessorSocketId:0x0 MemoryControllerId:0x3 ChannelAddress:0x800bb400 ChannelId:0x0 RankAddress:0x2002ed00 PhysicalRankId:0x0 DimmSlotId:0x0 DimmRankId:0x0 Row:0x2283 Column:0x10 Bank:0x0 BankGroup:0x4 ChipSelect:0x0)
[   242.380013]  machine_check+0x2f/0x40
[   242.380015] RIP: 0033:0x403f5b
[   242.380015] Code: 89 05 cd 37 20 00 8b 05 c7 37 20 00 c3 53 48 8b 1d 92 37 20 00 e8 2b d5 ff ff 48 8d 84 1b 76 14 40 00 48 f7 db 48 21 d8 5b c3  be 07 c3 0f be 07 0f be 57 01 01 d0 c3 48 8b 47 ff c3 c6 07 61
[   242.380016] RSP: 002b:00007ffcfb9e6098 EFLAGS: 00010206
[   242.380016] RAX: 0000000000607280 RBX: 0000000000607280 RCX: 0000000001b7b010
[   242.380017] RDX: 0000000000000000 RSI: 0000000000000001 RDI: 00007fe1bde21400
[   242.380017] RBP: 00007fe1bde21400 R08: 0000000001b7b04a R09: 0000000000000000
[   242.380017] R10: 0000000000000000 R11: 0000000000000206 R12: 0000000000000001
[   242.380018] R13: 00007ffcfb9e6410 R14: 0000000000000000 R15: 0000000000000000
[   242.380018] Modules linked in: einj xt_CHECKSUM ipt_MASQUERADE xt_conntrack ipt_REJECT nft_compat nf_nat_tftp nft_objref nf_conntrack_tftp nft_counter tun bridge stp llc nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nf_tables_set nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 ip_set nf_tables nfnetlink sunrpc vfat fat sd_mod sg intel_rapl_msr intel_rapl_common i10nm_edac nfit libnvdimm x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel iTCO_wdt intel_pmt_telemetry intel_pmt_crashlog iTCO_vendor_support intel_pmt_class kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcspkr rapl intel_th_gth ipmi_ssif uas intel_th_pci isst_if_mbox_pci isst_if_mmio idxd usb_storage joydev intel_pmt intel_th i2c_i801 isst_if_common i2c_ismt wmi acpi_ipmi ipmi_si ipmi_devintf ipmi_msghandler acpi_pad acpi_power_meter xfs libcrc32c ast i2c_algo_bit drm_vram_helper drm_kms_helper syscopyarea sysfillrect
[   242.380033]  sysimgblt fb_sys_fops drm_ttm_helper ttm crc32c_intel nvme ahci drm nvme_core libahci libata t10_pi pinctrl_emmitsburg dm_mirror dm_region_hash dm_log dm_mod fuse
[    0.000000] Linux version 4.18.0-348.el8.x86_64 (mockbuild@x86-vm-09.build.eng.bos.redhat.com) (gcc version 8.5.0 20210514 (Red Hat 8.5.0-3) (GCC)) #1 SMP Mon Oct 4 12:17:22 EDT 2021

It seems (?) nmi_exit(); caused this panic, but why opcode is 0000? What is the root cause of this log kernel BUG at arch/x86/kernel/cpu/mce/core.c:1364! and why kernel reboot during call trace. **20220908 Update:**

#define nmi_enter()						\
	do {							\
		arch_nmi_enter();				\
		printk_nmi_enter();				\
		lockdep_off();					\
		ftrace_nmi_enter();				\
		BUG_ON(in_nmi() == NMI_MASK);			\
		__preempt_count_add(NMI_OFFSET + HARDIRQ_OFFSET);	\
		rcu_nmi_enter();				\
		lockdep_hardirq_enter();			\
	} while (0)

#define nmi_exit()						\
	do {							\
		lockdep_hardirq_exit();				\
		rcu_nmi_exit();					\
		BUG_ON(!in_nmi());				\
		__preempt_count_sub(NMI_OFFSET + HARDIRQ_OFFSET);	\
		ftrace_nmi_exit();				\
		lockdep_on();					\
		printk_nmi_exit();				\
		arch_nmi_exit();				\
	} while (0)

In my understanding, if second entry of do_machine_check() happened, it should not cause BUG_ON(!in_nmi()) triggered. ex:

__preempt_count_add(NMI_OFFSET + HARDIRQ_OFFSET);
__preempt_count_add(NMI_OFFSET + HARDIRQ_OFFSET);
BUG_ON(!in_nmi());

__preempt_count_add is not an OR operation.

static inline void __preempt_count_add(int val)
{
	u32 pc = READ_ONCE(current_thread_info()->preempt.count);
	pc += val;
	WRITE_ONCE(current_thread_info()->preempt.count, pc);
}

**Others:** Please note, there is no this line in the PASS ( upstream kernel 5.15 ) log.

[   242.257296] BUG: scheduling while atomic: einj_mem_uc/9237/0x00110000

Using recent distros and systems, for the default setup and also when setting the kernel command line to have

=tty0

there is no output on the console when the kernel panics. With a CentOS 7 system, I get panic output on the console. On my VM instance with this default kernel command line: BOOT_IMAGE=/vmlinuz-3.10.0-1062.1.2.el7.x86_64 root=/dev/mapper/centos-root ro crashkernel=auto rd.lvm.lv=centos/root rd.lvm.lv=centos/swap rhgb quiet LANG=en_US.UTF-8 This is seen on VMs and on two different bare metal systems. On the one system, I was able to see the panic output using its Serial Over Lan (SOL, via BMC on a Supermicro system). I'd guess an actual serial line would work too but that system doesn't have one. I'm able to get console output via

p > /proc/sysrq-trigger

and

9 > /proc/sysrq-trigger

or by echoing directly to the /dev/tty devices. But then a crash / panic induced via

c > /proc/sysrq-trigger

has no output, and I have one system that is likely panicing but I'm just not seeing it on the console. (The system that is panicing / hung takes 6 - 40 hours before it panics, it's been frustrating to finally figure out it's probably panic, and at this time I no longer have access to the system for further testing - when I do I'll set it up to use the SOL). Is there some kernel command line setting change I need to use? Did the kernel console code change so that it can no longer output to the console during a panic? The only old kernel I tried on CentOS 7 was 3.10.0-1160.114.2.el on both bare metal and in a virtualbox VM, and they get panic output on the console. These failed to output on the console on panic: Ubuntu 20.04 bare metal Supermicro and Intel systems, kernel 5.8.0-55-generic Ubuntu 22.04, kernels 5.15.0-119-generic, 6.8.0-38-generic, 6.8.0-40-generic on bare metal and virtualbox VM Using the default kernel command line for the Ubuntu 22.04 on VM: BOOT_IMAGE=/vmlinuz-5.15.0-30-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro Rockylinux 8 / 9 on virtualbox VM, not sure of kernel versions

I want to panic/reboot multiple servers at the same time via Ansible CLI, however, the command below gets stuck at execution. Could someone advise how to revise the command to achieve the concurrent panic/reboot?

ansible HostGroup -m shell -a 'echo b >/proc/sysrq-trigger'

https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-8/-/blob/ccf40dfacd314ab0fea16cfc6f4eded1a08e2710/arch/x86/kernel/cpu/mce/core.c#L1331 preempt_enable() before nmi_exit(), is this a OK code?

if ((m.cs & 3) == 3) {
        /* If this triggers there is no way to recover. Die hard. */
        BUG_ON(!on_thread_stack() || !user_mode(regs));
        local_irq_enable();
        preempt_enable();

        current->task_struct_rh->mce_ripv = !!(m.mcgstatus & MCG_STATUS_RIPV);
        current->task_struct_rh->mce_whole_page = whole_page(&m);

        if (kill_it || do_memory_failure(&m))
            force_sig(SIGBUS, current);
        preempt_disable();
        local_irq_disable();
    } else {
        if (!fixup_exception(regs, X86_TRAP_MC))
            mce_panic("Failed kernel mode recovery", &m, NULL);
    }

out_ist:
    nmi_exit();
}

In my understanding, the kernel can't preempt if preempt_count > 0, in this case, it is inside NMI, so preempt_count > 0. It is sending SIGBUS:

force_sig(SIGBUS, current);

seems unnecessary to do local_irq_enable and preempt_enable?

Every time seeing an invalid opcode, it always shows 0000, what does this 0000 mean? ex:

kernel BUG at arch/x86/kernel/cpu/mce/core.c:1364!
invalid opcode: 0000 [#1] SMP NOPTI

0000 means opcode is 0000, or execution result is 0000, or error code is 0000, or something else? btw, I can't find the kernel code where it prints this line, only: https://elixir.bootlin.com/linux/latest/source/lib/bug.c#L204

if (file)
		pr_crit("kernel BUG at %s:%u!\n", file, line);

not sure this place is the right place to print it.

https://github.com/torvalds/linux/blob/bf272460d744112bacd4c4d562592decbf0edf64/arch/x86/kernel/cpu/mce/core.c#L1543

if ((m.cs & 3) == 3) {
		/* If this triggers there is no way to recover. Die hard. */
		BUG_ON(!on_thread_stack() || !user_mode(regs));

as above, what is die hard? what is die soft? Will the rest of the code continues running after BUG_ON() execution?

While trying to install KISS Linux (a distribution which doesn't use (or at least doesn't by default) an initramfs), a distribution that requires you to build your own kernel, I always get the same kernel panic message, no matter what configuration I try. I tried enabling all the right device drivers for my SATA/SCSI/ATA controllers to no avail. I'm still unsure if the problem is my GRUB configuration or my kernel configuration, or some mix of both. I found a post here saying that to find the root device without an initramfs, you have to use PARTUUID for the root kernel parameter, like this: root=PARTUUID=SSSSSSSS-PP. I tried that (along with several different kernel configurations), but nothing seems to work. No matter what I did nothing about the kernel panic message would change, and the logs would be the exact same.

[~] λ lspci
00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] RS780 Host Bridge
00:02.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] RS780 PCI to PCI bridge (ext gfx port 0)
00:05.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] RS780/RS880 PCI to PCI bridge (PCIE port 1)
00:06.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] RS780 PCI to PCI bridge (PCIE port 2)
00:07.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] RS780/RS880 PCI to PCI bridge (PCIE port 3)
00:11.0 SATA controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 SATA Controller [IDE mode]
00:12.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
00:12.1 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0 USB OHCI1 Controller
00:12.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller
00:13.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
00:13.1 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0 USB OHCI1 Controller
00:13.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller
00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 SMBus Controller (rev 3c)
00:14.1 IDE interface: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 IDE Controller
00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA)
00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 LPC host controller
00:14.4 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 PCI to PCI Bridge
00:14.5 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI2 Controller
00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 0
00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 1
00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 2
00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 3
00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 4
00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 5
01:00.0 VGA compatible controller: NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] (rev a1)
01:00.1 Audio device: NVIDIA Corporation GP106 High Definition Audio Controller (rev a1)
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06)
03:00.0 USB controller: Renesas Technology Corp. uPD720201 USB 3.0 Host Controller (rev 03)
04:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 02)

[~] λ sudo lsblk
NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda      8:0    0 111.8G  0 disk
├─sda1   8:1    0    50M  0 part
├─sda2   8:2    0 111.3G  0 part
└─sda3   8:3    0   499M  0 part
sdb      8:16   0 931.5G  0 disk
└─sdb1   8:17   0 931.5G  0 part /
sdc      8:32   0 931.5G  0 disk
├─sdc1   8:33   0 443.2G  0 part /home/void/hdd1
├─sdc2   8:34   0   250G  0 part
└─sdc3   8:35   0 238.3G  0 part /mnt/kiss
sdd      8:48   0 931.5G  0 disk
└─sdd1   8:49   0 931.5G  0 part

I am facing a Kernel panic from which I am not able to solve my way out. I saw some posts regarding the same but none seems to be conclusive. I am trying on a Raspberry Pi 4B hardware to build and use my own Bootloader and Linux version. **U-Boot: v2020.07** **Linux Kernel: v5.8.9** Used busybox to prepare my Root-FS which seems to be mounted, as per what I see on console. This is where I get stuck at the end: Can you please help on what the issue could be in my case?

Please help me solve this issue! I have already uninstalled rust but that did not solve the problem... Here is the code: error: failed to run custom build command for libdbus-sys v0.2.1 Caused by: process didn't exit successfully: /home/flowet/.cache/yay/mullvad-vpn/src/mullvadvpn-app/target/release/build/libdbus-sys-2e5f442eec395f29/build-script-build (exit code: 101) --- stderr thread 'main' panicked at 'called Result::unwrap() on an Err value: Command { command: "\"pkg-config\" \"--libs\" \"--cflags\" \"dbus-1\" \"dbus-1 >= 1.6\"", cause: Os { code: 2, kind: NotFound, message: "No such file or directory" } }', /home/flowet/.cargo/registry/src/github.com-1ecc6299db9ec823/libdbus-sys-0.2.1/build.rs:6:70 note: run with RUST_BACKTRACE=1 environment variable to display a backtrace

I manage a RHEL 8.2 server hosted in Azure and whenever I reboot the server, it goes to Kernel Panic. I am getting the below error message. Starting Reboot... [1892395.172835] printk: systemd-shutdow: 45 output lines suppressed due to ratelimiting [1892395.182765] systemd-shutdown: Syncing filesystems and block devices. [1892395.200269] systemd-shutdown: Sending SIGTERM to remaining processes... [1892395.207060] systemd-journald: Received SIGTERM from PID 1 (systemd-shutdow). [1892395.227451] systemd-shutdown: Sending SIGKILL to remaining processes... [1892395.237894] systemd-shutdown: Unmounting file systems. [1892395.242465] : Remounting '/var' read-only in with options '(null)'. [1892395.281287] EXT4-fs (dm-4): re-mounted. Opts: (null) [1892395.297105] : Unmounting '/var'. [1892395.371209] : Remounting '/storage' read-only in with options 'attr2,inode64,noquota'. [1892395.740647] : Unmounting '/storage'. [1892396.026064] XFS (sda2): Unmounting Filesystem [1892396.100906] : Remounting '/usr' read-only in with options '(null)'. [1892396.184728] EXT4-fs (dm-1): re-mounted. Opts: (null) [1892396.210664] : Remounting '/' read-only in with options '(null)'. [1892396.231700] EXT4-fs (dm-5): re-mounted. Opts: (null) [1892396.236991] systemd-shutdown: All filesystems unmounted. [1892396.241123] systemd-shutdown: Deactivating swaps. [1892396.244523] systemd-shutdown: All swaps deactivated. [1892396.249026] systemd-shutdown: Detaching loop devices. [1892396.252787] systemd-shutdown: All loop devices detached. [1892396.256663] systemd-shutdown: Detaching DM devices. [1892396.313043] printk: shutdown: 14 output lines suppressed due to ratelimiting [1892396.357695] dracut Warning: Killing all remaining processes dracut Warning: Killing all remaining processes [1892396.975761] dracut Warning: Unmounted /oldroot/usr. [1892396.992162] BUG: unable to handle kernel paging request at 00007770000069a8 [1892396.993004] PGD 0 P4D 0 [1892396.993004] Oops: 0000 [#1] SMP PTI [1892396.993004] CPU: 0 PID: 2350587 Comm: umount Not tainted 4.18.0-193.6.3.el8_2.x86_64 #1 [1892396.993004] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090007 06/02/2017 [1892396.993004] RIP: 0010:__list_del_entry_valid+0x2d/0x4c [1892396.993004] Code: 48 8b 57 08 48 b9 00 01 00 00 00 00 ad de 48 39 c8 0f 84 5a 00 00 00 48 b9 00 02 00 00 00 00 ad de 48 39 ca 0f 84 7d 00 00 00 8b 32 48 39 fe 0f 85 5d 00 00 00 48 8b 50 08 48 39 f2 0f 85 42 [1892396.993004] RSP: 0018:ffff9b58c3f3bd90 EFLAGS: 00010203 [1892396.993004] RAX: 0000000000002028 RBX: ffff8c0f9333f000 RCX: dead000000000200 [1892396.993004] RDX: 00007770000069a8 RSI: ffff8c0f9e6be400 RDI: ffff8c0f9333ecc0 [1892396.993004] RBP: ffff8c0f97a85150 R08: 0000000000000000 R09: 0000000000000000 [1892396.993004] R10: ffff9b58c3f3be18 R11: 0000000000000000 R12: ffff8c0f9333ecc0 [1892396.993004] R13: ffff8c0f980df8c0 R14: 0000000000000000 R15: ffffffffab0b5530 [1892396.993004] FS: 00007f9485309080(0000) GS:ffff8c0f9dc00000(0000) knlGS:0000000000000000 [1892396.993004] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [1892396.993004] CR2: 00007770000069a8 CR3: 0000000874618005 CR4: 00000000003606f0 [1892396.993004] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [1892396.993004] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [1892396.993004] Call Trace: [1892396.993004] audit_tree_freeing_mark+0x148/0x2d0 [1892396.993004] fsnotify_destroy_marks+0x6b/0xe0 [1892396.993004] fsnotify_unmount_inodes+0xab/0x1a0 [1892396.993004] ? __dentry_kill+0x121/0x170 [1892396.993004] ? _cond_resched+0x15/0x30 [1892396.993004] ? dentry_kill+0x4d/0x190 [1892396.993004] generic_shutdown_super+0x32/0x100 [1892396.993004] kill_block_super+0x21/0x50 [1892396.993004] deactivate_locked_super+0x34/0x70 [1892396.993004] cleanup_mnt+0x3b/0x70 [1892396.993004] task_work_run+0x8a/0xb0 [1892396.993004] exit_to_usermode_loop+0xeb/0xf0 [1892396.993004] do_syscall_64+0x198/0x1a0 [1892396.993004] entry_SYSCALL_64_after_hwframe+0x65/0xca [1892396.993004] RIP: 0033:0x7f948433aebb [1892396.993004] Code: ff 2b 00 f7 d8 64 89 01 48 83 c8 ff c3 66 90 f3 0f 1e fa 31 f6 e9 05 00 00 00 0f 1f 44 00 00 f3 0f 1e fa b8 a6 00 00 00 0f 05 3d 01 f0 ff ff 73 01 c3 48 8b 0d 9d ff 2b 00 f7 d8 64 89 01 48 [1892396.993004] RSP: 002b:00007ffd36c12a48 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6 [1892396.993004] RAX: 0000000000000000 RBX: 000055b28656e970 RCX: 00007f948433aebb [1892396.993004] RDX: 0000000000000001 RSI: 0000000000000000 RDI: 000055b28656eb50 [1892396.993004] RBP: 0000000000000000 R08: 000055b28656eb70 R09: 00007f94843bcc80 [1892396.993004] R10: 0000000000000000 R11: 0000000000000246 R12: 000055b28656eb50 [1892396.993004] R13: 00007f94850e7184 R14: 0000000000000000 R15: 00000000ffffffff [1892396.993004] Modules linked in: vfat msdos fat ccm arc4 libarc4 md4 sha512_ssse3 sha512_generic cmac nls_utf8 cifs dns_resolver overlay nf_conntrack_ipv4 nf_defrag_ipv4 nft_counter xt_owner xt_conntrack nf_conntrack nft_compat fuse nf_tables nfnetlink binfmt_misc xfs libcrc32c intel_rapl_msr intel_rapl_common sb_edac kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel intel_rapl_perf hv_balloon hv_utils hyperv_fb i2c_piix4 joydev pcspkr auth_rpcgss sunrpc ip_tables ext4 mbcache jbd2 ata_generic sd_mod sg hv_storvsc hv_netvsc hyperv_keyboard scsi_transport_fc hid_hyperv ata_piix libata crc32c_intel hv_vmbus serio_raw dm_mirror dm_region_hash dm_log dm_mod [1892396.993004] CR2: 00007770000069a8 [1892396.993004] ---[ end trace fe4fc9dab223a18d ]--- [1892396.993004] RIP: 0010:__list_del_entry_valid+0x2d/0x4c [1892396.993004] Code: 48 8b 57 08 48 b9 00 01 00 00 00 00 ad de 48 39 c8 0f 84 5a 00 00 00 48 b9 00 02 00 00 00 00 ad de 48 39 ca 0f 84 7d 00 00 00 8b 32 48 39 fe 0f 85 5d 00 00 00 48 8b 50 08 48 39 f2 0f 85 42 [1892396.993004] RSP: 0018:ffff9b58c3f3bd90 EFLAGS: 00010203 [1892396.993004] RAX: 0000000000002028 RBX: ffff8c0f9333f000 RCX: dead000000000200 [1892396.993004] RDX: 00007770000069a8 RSI: ffff8c0f9e6be400 RDI: ffff8c0f9333ecc0 [1892396.993004] RBP: ffff8c0f97a85150 R08: 0000000000000000 R09: 0000000000000000 [1892396.993004] R10: ffff9b58c3f3be18 R11: 0000000000000000 R12: ffff8c0f9333ecc0 [1892396.993004] R13: ffff8c0f980df8c0 R14: 0000000000000000 R15: ffffffffab0b5530 [1892396.993004] FS: 00007f9485309080(0000) GS:ffff8c0f9dc00000(0000) knlGS:0000000000000000 [1892396.993004] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [1892396.993004] CR2: 00007770000069a8 CR3: 0000000874618005 CR4: 00000000003606f0 [1892396.993004] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [1892396.993004] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [1892396.993004] Kernel panic - not syncing: Fatal exception [1892396.993004] Kernel Offset: 0x28e00000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff) [1892396.993004] ---[ end Kernel panic - not syncing: Fatal exception ]--- [?25lUse the ^ and v keys to change the selection. Looks like the below is the cause for panic [1892396.357695] dracut Warning: Killing all remaining processes dracut Warning: Killing all remaining processes [1892396.975761] dracut Warning: Unmounted /oldroot/usr. [1892396.992162] BUG: unable to handle kernel paging request at 00007770000069a8 [1892396.993004] PGD 0 P4D 0 [1892396.993004] Oops: 0000 [#1] SMP PTI [1892396.993004] CPU: 0 PID: 2350587 Comm: umount Not tainted 4.18.0-193.6.3.el8_2.x86_64 #1 [1892396.993004] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090007 06/02/2017 [1892396.993004] RIP: 0010:__list_del_entry_valid+0x2d/0x4c Please help me to fix this. Thank you.

 Please, can someone give me step-by-step instructions how to get back into my Linux Cinnamon operating system. I updated the definitions. After a reboot this issue appeared.

After updating more than ~1000 things my installation of RHEL 2.6.32-220.el6.x86_64. I get the following kernel panic message: > Kernel Panic - Not syncing : VFS: unable to mount root fs on unknown-block (0,0) I am able to boot with the bootloader by selecting the previous version. I've tried: dracut -f initramfs-2.6.32-754.23.1.el6.x86_64.img 2.6.32-754.23.1.el6.x86_64 and: dracut --regenerate-all also my grub.conf file was missing initrd below the new (1st) kernel: initrd /initramfs-2.6.32-754.23.1.el6.x86_64.img So I added it. I still get the kernel panic afterwards. I've tried to yum update on the old kernel and it will not update complaining about:

Error: Package: VirtualGL-2.5.2-1.el6.x86_64 (epel)
           Requires: libturbojpeg.so(TURBOJPEG_1.0)(64bit)
           Available: turbojpeg-1.2.1-2.el6.x86_64 (epel)
               libturbojpeg.so(TURBOJPEG_1.0)(64bit)
           Installed: turbojpeg-1.11-20081028.x86_64 (installed)
               Not found
Error: Package: VirtualGL-2.5.2-1.el6.x86_64 (epel)
           Requires: libturbojpeg.so(TURBOJPEG_1.1)(64bit)
           Available: turbojpeg-1.2.1-2.el6.x86_64 (epel)
               libturbojpeg.so(TURBOJPEG_1.1)(64bit)
           Installed: turbojpeg-1.11-20081028.x86_64 (installed)
               Not found
Error: Package: VirtualGL-2.5.2-1.el6.x86_64 (epel)
           Requires: libturbojpeg.so(TURBOJPEG_1.2)(64bit)
           Available: turbojpeg-1.2.1-2.el6.x86_64 (epel)
               libturbojpeg.so(TURBOJPEG_1.2)(64bit)
           Installed: turbojpeg-1.11-20081028.x86_64 (installed)
               Not found


** Found 2 pre-existing rpmdb problem(s), 'yum check' output follows:
1:tcl-8.5.7-6.el6.i686 is a duplicate with tcl-8.4.13-4.el5.i386
1:tk-8.5.7-5.el6.i686 is a duplicate with tk-8.4.13-5.el5_1.1.i386

Since I updated the system originally, will the old kernel still need the 1000 updates? In other words are the files that were updated the same files that the old kernel uses when booting?

recently, i moved fedora29 into the desktop harddrive from external hard drive (Miraculously, i installed fedora29 on external hard drive anyway ^^:) as installed as soon, it was too slow. i added up second swap partition on the secondary hard disk(/dev/sda1:4TB) after that, my computer was always busy with hdd led on(hdd is too busy to work). then i removed the second swap partition, the secondary disk from the /etc/fstab. Since then, my computer became unstable..like write-error , kernel panic...etcdm-0(maybe mounted disk name with /etc/fstab) How could i fix the problem??? /etc/fstab /dev/mapper/fedora-root / ext4 defaults 1 1 UUID=9b493611-0fb7-491b-9fc0-ae42f5a54a3f /boot ext4 defaults 1 2 /dev/mapper/fedora-home /home ext4 defaults 1 2 /dev/mapper/fedora-swap swap swap defaults 0 0 blkid: /dev/sda1: UUID="5fedba61-5bf3-4c50-9818-bc63b771306a" TYPE="ext4" PARTLABEL="primary" PARTUUID="84d63caf-ab6d-4350-af92-39e87755a96d" /dev/sdb1: UUID="9b493611-0fb7-491b-9fc0-ae42f5a54a3f" TYPE="ext4" PARTUUID="9b543e06-01" /dev/sdb2: UUID="qnCBLA-tzkn-Lt0E-m9ed-4Ujj-W1A2-OAtoFG" TYPE="LVM2_member" PARTUUID="9b543e06-02" /dev/mapper/fedora-root: UUID="5a09dd9f-03c5-474f-8e13-08aa5cde26a4" TYPE="ext4" /dev/mapper/fedora-swap: UUID="28a3e920-5418-4799-9e18-5e501b838447" TYPE="swap" /dev/mapper/fedora-home: UUID="b3c099eb-83e1-4328-98bf-e8f46c59e35f" TYPE="ext4". df -h Filesystem Size Used Avail Use% Mounted on devtmpfs 2.0G 0 2.0G 0% /dev tmpfs 2.0G 0 2.0G 0% /dev/shm tmpfs 2.0G 1.1M 2.0G 1% /run tmpfs 2.0G 0 2.0G 0% /sys/fs/cgroup /dev/mapper/fedora-root 49G 19G 29G 39% / tmpfs 2.0G 4.0K 2.0G 1% /tmp /dev/sdb1 1008M 203M 737M 22% /boot /dev/mapper/fedora-home 52G 9.0G 41G 19% /home tmpfs 395M 0 395M 0% /run/user/0

I'm trying to get any Distro to even boot into a Live Session. since this isn't working i'm to0 scared to even try installing one. Hoever every distro i tried Gives a "Kernel panic" or a freeze during boot Ubuntu 18.04 LTS (kernal 4.15) - Kernel Panic >
Fedora 28 (kernel 4.17) - Kernel Panic
SlackEX 14.2 (Kernel 4.14) - Freeze black screen
Debian 9.4 (Kernel 4.9 ) - Freeze >
Relevant Specs?:
Intel I7 8750H (Intel UHD 630 Graphics)
Nvidia 1070 GTX
NVME M.2 SSD Toshiba 256 GB WD 1TB
USB31(Gen2 10gbps)

I have dualboot on my laptop with windows being the primary OS. Today after my linux os froze I hard rebooted the laptop. After that I got a kernel panic. I've been trying to solve it using GRUB. I did: #first set root = (hd0,msdos3) #this is where my linux os is #second linux /boot/vmlinuz-4.13.0-45-generic root=/dev/ and at this point I don't see sda or any sdX folder which I can mount to root. Can it be in another folder or should I look somewhere else? I'm following these instrunctions that a friend of mine told me to follow. set root = (linux partition) linux /boot/vmlinuz... root=/dev/sda1 initrd /boot/initrd.img... boot

I'm having a _really_ weird issue with oVirt. I download ISOs, and they'll work for about ~3 boots, and then they just start kernel panic'ing out of nowhere. The error is as follows: Kernel panic - not syncing: No init found. Try passing init= option to kernel. Removing quiet doesn't add more visible debug info. This has so far happened on around five different downloads of CentOS. I've verified the checksum of the ISO with the one provided on the CentOS website, and it's fine. Everything is hosted in an ISO domain, as an NFS share. Unfortunately, this happens with Glance templates as well, mainly CentOS. Debian Buster worked the first time, after a couple other ISOs failed, but I haven't repeatedly tried it. I'm running on the latest oVirt version (4.2.2), with the hosted engine, and this only started after updating from 4.2.0. Thanks in advance!

As though I had not had some 10 years of on-and-off Linux experience, I patiently awaited the release of laptops with the new AMD Ryzen "APU" chips, planning to install Linux, after speculative execution vulnerabilities made Intel look bad. So I bought the shiny new Lenovo IdeaPad 720s 13" AMD Ryzen 5 edition, which would be a perfect laptop if it worked. I installed elementary OS Loki (reskinned Ubuntu), got everything up and running (except Wifi), and closed the laptop. I opened it again to see a blank console with the infamous blinking cursor. So like anyone else trying to run Linux a new laptop, I installed the newest kernel (as of mid-January) which was a dramatically improved experience from four years ago (last time), booted up Elementary again, closed the laptop, opened it, and... screen turned off. Reboot indicated an unclean shutdown. After I reproduced the issue a couple of times, my Lenovo recovery partition kicked in, deleted GRUB, and booted into Windows. I was definitely going to post this question/bug report earlier, but I'm lazy. Sorry. Has anyone else had success running Linux on a Ryzen laptop? Is there a bug report open? Suspend issues are usually a kernel thing, right? Should I open a bug somewhere (after trying the newest kernel)?

My system(CentOS6) crashed, and I got a vmcore. Now I want to know how to get /proc/net/dev in vmcore, or how can I get net statistics counter data(e.g, netstat -s)? I trigger a crash on CentOS7, and I can find some counters after run net and struct commands: crash> net NET_DEVICE NAME IP ADDRESS(ES) ffff881053f97000 lo 127.0.0.1 ffff88084ece0000 eth0 xxx.xxx.xxx.xxx ffff88084e480000 eth1 xxx.xxx.xxx.xxx crash> struct net_device ffff88084ece0000 ...... stats = { rx_packets = 122192214759, tx_packets = 122785688757, rx_bytes = 140670240738618, tx_bytes = 136965095362827, rx_errors = 0, tx_errors = 0, rx_dropped = 0, ...... But it doesn't make sense in CentOS6, I just get 0 for all counters: crash> net NET_DEVICE NAME IP ADDRESS(ES) ffff881028a10020 lo 127.0.0.1 ffff8820253a4020 eth0 xxx.xxx.xxx.xxx ffff8820253a8020 eth1 xxx.xxx.xxx.xxx ...... stats = { rx_packets = 0, tx_packets = 0, rx_bytes = 0, tx_bytes = 0, rx_errors = 0, tx_errors = 0, rx_dropped = 0, ...... Does it mean that on CentOS6 net counters are NOT stored in memory? Thanks!

I recently got a pc and I installed debian jessie. And everything is going well, the problem is when I try to shut down the pc, because it freezes, the same happens if I try to restart, suspend. The pc is an acer Aspire E 15 and processor: intel celeron 2.16Ghz dual-core. In the log that implements to know what was happening tells me the following: Someone who knows what's going on?

My problem If I transfer file with rsync using tapes,or disk(usb,e-sata,firewire) linux hang,no way to resume if not using powerbutton(brutal shutdown!) sysrq-trigger don't work,ssh don't answer,keyboard and screen no input. I have a M5A97 R2.0 Asus board,with 16G ram Crucial. I 've ordered a couple of other ram by kingston In your opinion can be a hw problem,or ram problem? Using the program ramtest no error given. I have tried also this solution ..but hang anyway. Your opinion? I forgot,hang happen on every transfer especially with big files(over 10G) I tried different kernel versions..same problem.