pve kernel: BUG: kernel NULL pointer dereference, address: 0000000000000160

M

mattes

New Member
Proxmox Subscriber
Aug 23, 2024
2
0
1
Dörverden/Niedersachsen
www.prospekthalter.com
Habe ein Problem mit Kernel 6.8.8-4.
Bekomme ständig den Fehler:
pve kernel: BUG: kernel NULL pointer dereference, address: 0000000000000160
Das System ist dann nicht mehr ansprechbar. Nur eine Power Reset per IPMI hilft.
  1. memtest+ wurde gemacht ---> PASS
  2. SSD NVME check mit badblocks ---> PASS
  3. update apt install amd64-microcode
  4. BIOS update
Wie in anderen Threads habe ich den Server mit Kernel 6.5.13-6 gestartet.
Mal sehen, wie lange er durchhält.

Syslog
Code: 
Aug 22 22:03:24 pve kernel: BUG: kernel NULL pointer dereference, address: 0000000000000160
Aug 22 22:03:24 pve kernel: #PF: supervisor read access in kernel mode


Code: 
proxmox-ve: 8.2.0 (running kernel: 6.5.13-6-pve)
pve-manager: 8.2.3 (running version: 8.2.3/b4648c690591095f)
proxmox-kernel-helper: 8.1.0
pve-kernel-6.2: 8.0.5
proxmox-kernel-6.8: 6.8.8-4
proxmox-kernel-6.8.8-4-pve-signed: 6.8.8-4
proxmox-kernel-6.8.4-3-pve-signed: 6.8.4-3
proxmox-kernel-6.5.13-6-pve-signed: 6.5.13-6
proxmox-kernel-6.5: 6.5.13-6
proxmox-kernel-6.5.13-5-pve-signed: 6.5.13-5
proxmox-kernel-6.5.11-8-pve-signed: 6.5.11-8
proxmox-kernel-6.5.11-7-pve-signed: 6.5.11-7
proxmox-kernel-6.2.16-20-pve: 6.2.16-20
proxmox-kernel-6.2: 6.2.16-20
proxmox-kernel-6.2.16-18-pve: 6.2.16-18
proxmox-kernel-6.2.16-12-pve: 6.2.16-12
proxmox-kernel-6.2.16-10-pve: 6.2.16-10
pve-kernel-6.2.16-3-pve: 6.2.16-3
amd64-microcode: 3.20230808.1.1~deb12u1
ceph-fuse: 17.2.7-pve3
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx9
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-4
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.5.1
libproxmox-backup-qemu0: 1.4.1
libproxmox-rs-perl: 0.3.3
libpve-access-control: 8.1.4
libpve-apiclient-perl: 3.3.2
libpve-cluster-api-perl: 8.0.7
libpve-cluster-perl: 8.0.7
libpve-common-perl: 8.2.1
libpve-guest-common-perl: 5.1.3
libpve-http-server-perl: 5.1.0
libpve-network-perl: 0.9.8
libpve-rs-perl: 0.8.9
libpve-storage-perl: 8.2.3
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 6.0.0-1
lxcfs: 6.0.0-pve2
novnc-pve: 1.4.0-3
proxmox-backup-client: 3.2.3-1
proxmox-backup-file-restore: 3.2.3-1
proxmox-firewall: 0.5.0
proxmox-kernel-helper: 8.1.0
proxmox-mail-forward: 0.2.3
proxmox-mini-journalreader: 1.4.0
proxmox-widget-toolkit: 4.2.3
pve-cluster: 8.0.7
pve-container: 5.1.10
pve-docs: 8.2.2
pve-edk2-firmware: 4.2023.08-4
pve-esxi-import-tools: 0.7.1
pve-firewall: 5.0.7
pve-firmware: 3.13-1
pve-ha-manager: 4.0.5
pve-i18n: 3.2.2
pve-qemu-kvm: 8.1.5-6
pve-xtermjs: 5.3.0-3
qemu-server: 8.2.3
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.4-pve1
 
Old Kernel 6.5.13-6 throws that from my Shop Container

Code: 
Aug 23 08:24:33 pve kernel: php-fpm5.6[418248]: segfault at 18 ip 00007bcaeabbdfd9 sp 00007fff86dcf7a0 error 4
Aug 23 08:24:33 pve kernel: php-fpm5.6[419424]: segfault at 30 ip 0000577cd6f7fc7e sp 00007fff86dd0a50 error 4
Aug 23 08:24:33 pve kernel:  in libpthread-2.31.so[7bcaeabb6000+10000]
Aug 23 08:24:33 pve kernel:  in php-fpm5.6[577cd6dbd000+238000]
Aug 23 08:24:33 pve kernel:  likely on CPU 55 (core 23, socket 0)
Aug 23 08:24:33 pve kernel: Code: d0 b8 10 00 00 00 c3 66 2e 0f 1f 84 00 00 00 00 00 c7 47 08 01 00 00 00 eb cd 0f 1f 80 00 00 00 00 55 49 89 f8 53 48 83 ec 08 <8b> 57 18 64 8b 04 25 d0 02 00 00 8b 5f 1c 39 c2 0f 84 c1 00 00 00
Aug 23 08:24:33 pve kernel:  likely on CPU 29 (core 29, socket 0)
Aug 23 08:24:33 pve kernel: Code: 88 85 1c 00 48 8d 85 40 02 00 00 44 0f b6 a5 54 02 00 00 c6 85 54 02 00 00 01 48 89 04 24 66 0f 1f 44 00 00 48 8b 03 48 89 df <ff> 10 85 c0 7e f4 83 f8 02 74 37 83 f8 03 74 22 83 f8 01 75 e5 44

A long time we have no problems with these old PHP Version.
I have do an apt upgrade in the container to get new versions of the PHP 5.6.
So I have to plan a Shop update to the new PHP Version and so on.
I hear from other Threads that does not solve the problem.
 
Last edited:
You must log in or register to reply here.
Top Bottom