Neuer Kernel fehlerhaft!

S

SRCH

New Member
Sep 6, 2024
10
0
1
Hallo,

ich habe updates gemacht die letzten Tage und mein Server hat sich wieder aufgehängt.
Ihr habt vermutlich wieder einen Bug im neuen Kernel! :-(

Nov 11 09:17:01 ms01 CRON[205711]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Nov 11 09:17:01 ms01 CRON[205712]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Nov 11 09:17:01 ms01 CRON[205711]: pam_unix(cron:session): session closed for user root
Nov 11 09:20:09 ms01 pvestatd[1524]: auth key pair too old, rotating..
Nov 11 09:32:25 ms01 pmxcfs[1396]: [dcdb] notice: data verification successful
Nov 11 10:17:01 ms01 CRON[227124]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Nov 11 10:17:01 ms01 CRON[227125]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Nov 11 10:17:01 ms01 CRON[227124]: pam_unix(cron:session): session closed for user root
Nov 11 10:32:25 ms01 pmxcfs[1396]: [dcdb] notice: data verification successful
Nov 11 10:36:01 ms01 kernel: hrtimer: interrupt took 19914 ns
Nov 11 11:17:01 ms01 CRON[248814]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Nov 11 11:17:01 ms01 CRON[248815]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Nov 11 11:17:01 ms01 CRON[248814]: pam_unix(cron:session): session closed for user root
Nov 11 11:32:25 ms01 pmxcfs[1396]: [dcdb] notice: data verification successful
-- Reboot --
Nov 11 11:53:52 ms01 kernel: Linux version 6.8.12-4-pve (build@proxmox) (gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT_DYNAMIC PMX 6.8.12-4 (2024-11-06T15:04Z) ()
Nov 11 11:53:52 ms01 kernel: Command line: BOOT_IMAGE=/vmlinuz-6.8.12-4-pve root=ZFS=/ROOT/pve-1 ro root=ZFS=rpool/ROOT/pve-1 boot=zfs quiet split_lock_detect=off
Nov 11 11:53:52 ms01 kernel: KERNEL supported cpus:
Nov 11 11:53:52 ms01 kernel: Intel GenuineIntel
Nov 11 11:53:52 ms01 kernel: AMD AuthenticAMD
Nov 11 11:53:52 ms01 kernel: Hygon HygonGenuine
Nov 11 11:53:52 ms01 kernel: Centaur CentaurHauls
Nov 11 11:53:52 ms01 kernel: zhaoxin Shanghai
Nov 11 11:53:52 ms01 kernel: x86/tme: not enabled by BIOS
Nov 11 11:53:52 ms01 kernel: x86/split lock detection: disabled
Nov 11 11:53:52 ms01 kernel: BIOS-provided physical RAM map:
Nov 11 11:53:52 ms01 kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009dfff] usable
Nov 11 11:53:52 ms01 kernel: BIOS-e820: [mem 0x000000000009e000-0x000000000009efff] reserved
Nov 11 11:53:52 ms01 kernel: BIOS-e820: [mem 0x000000000009f000-0x000000000009ffff] usable
Nov 11 11:53:52 ms01 kernel: BIOS-e820: [mem 0x00000000000a0000-0x00000000000fffff] reserved
Nov 11 11:53:52 ms01 kernel: BIOS-e820: [mem 0x0000000000100000-0x000000003e592fff] usable
Nov 11 11:53:52 ms01 kernel: BIOS-e820: [mem 0x000000003e593000-0x000000003e593fff] reserved
Nov 11 11:53:52 ms01 kernel: BIOS-e820: [mem 0x000000003e594000-0x000000003f39cfff] usable
Nov 11 11:53:52 ms01 kernel: BIOS-e820: [mem 0x000000003f39d000-0x000000004249cfff] reserved
Nov 11 11:53:52 ms01 kernel: BIOS-e820: [mem 0x000000004249d000-0x00000000425a5fff] ACPI data
Nov 11 11:53:52 ms01 kernel: BIOS-e820: [mem 0x00000000425a6000-0x00000000426d4fff] ACPI NVS
Nov 11 11:53:52 ms01 kernel: BIOS-e820: [mem 0x00000000426d5000-0x0000000043efefff] reserved
Nov 11 11:53:52 ms01 kernel: BIOS-e820: [mem 0x0000000043eff000-0x0000000043efffff] usable
Nov 11 11:53:52 ms01 kernel: BIOS-e820: [mem 0x0000000043f00000-0x000000004a3fffff] reserved
Nov 11 11:53:52 ms01 kernel: BIOS-e820: [mem 0x000000004b000000-0x00000000503fffff] reserved
Nov 11 11:53:52 ms01 kernel: BIOS-e820: [mem 0x00000000c0000000-0x00000000cfffffff] reserved
Nov 11 11:53:52 ms01 kernel: BIOS-e820: [mem 0x00000000fe000000-0x00000000fe010fff] reserved
Nov 11 11:53:52 ms01 kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
Nov 11 11:53:52 ms01 kernel: BIOS-e820: [mem 0x00000000fed00000-0x00000000fed00fff] reserved
Nov 11 11:53:52 ms01 kernel: BIOS-e820: [mem 0x00000000fed20000-0x00000000fed7ffff] reserved
Nov 11 11:53:52 ms01 kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
Nov 11 11:53:52 ms01 kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Nov 11 11:53:52 ms01 kernel: BIOS-e820: [mem 0x0000000100000000-0x00000010afbfffff] usable
Nov 11 11:53:52 ms01 kernel: NX (Execute Disable) protection: active
Nov 11 11:53:52 ms01 kernel: APIC: Static calls initialized
Nov 11 11:53:52 ms01 kernel: e820: update [mem 0x37119018-0x3712ae57] usable ==> usable
Nov 11 11:53:52 ms01 kernel: e820: update [mem 0x37119018-0x3712ae57] usable ==> usable
Nov 11 11:53:52 ms01 kernel: extended physical RAM map:
Nov 11 11:53:52 ms01 kernel: reserve setup_data: [mem 0x0000000000000000-0x000000000009dfff] usable
Nov 11 11:53:52 ms01 kernel: reserve setup_data: [mem 0x000000000009e000-0x000000000009efff] reserved
Nov 11 11:53:52 ms01 kernel: reserve setup_data: [mem 0x000000000009f000-0x000000000009ffff] usable
Nov 11 11:53:52 ms01 kernel: reserve setup_data: [mem 0x00000000000a0000-0x00000000000fffff] reserved
Nov 11 11:53:52 ms01 kernel: reserve setup_data: [mem 0x0000000000100000-0x0000000037119017] usable
Nov 11 11:53:52 ms01 kernel: reserve setup_data: [mem 0x0000000037119018-0x000000003712ae57] usable
Nov 11 11:53:52 ms01 kernel: reserve setup_data: [mem 0x000000003712ae58-0x000000003e592fff] usable
Nov 11 11:53:52 ms01 kernel: reserve setup_data: [mem 0x000000003e593000-0x000000003e593fff] reserved
Nov 11 11:53:52 ms01 kernel: reserve setup_data: [mem 0x000000003e594000-0x000000003f39cfff] usable
Nov 11 11:53:52 ms01 kernel: reserve setup_data: [mem 0x000000003f39d000-0x000000004249cfff] reserved
Nov 11 11:53:52 ms01 kernel: reserve setup_data: [mem 0x000000004249d000-0x00000000425a5fff] ACPI data
Nov 11 11:53:52 ms01 kernel: reserve setup_data: [mem 0x00000000425a6000-0x00000000426d4fff] ACPI NVS
Nov 11 11:53:52 ms01 kernel: reserve setup_data: [mem 0x00000000426d5000-0x0000000043efefff] reserved
Nov 11 11:53:52 ms01 kernel: reserve setup_data: [mem 0x0000000043eff000-0x0000000043efffff] usable
Nov 11 11:53:52 ms01 kernel: reserve setup_data: [mem 0x0000000043f00000-0x000000004a3fffff] reserved
Nov 11 11:53:52 ms01 kernel: reserve setup_data: [mem 0x000000004b000000-0x00000000503fffff] reserved
Nov 11 11:53:52 ms01 kernel: reserve setup_data: [mem 0x00000000c0000000-0x00000000cfffffff] reserved
Nov 11 11:53:52 ms01 kernel: reserve setup_data: [mem 0x00000000fe000000-0x00000000fe010fff] reserved
Nov 11 11:53:52 ms01 kernel: reserve setup_data: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
Nov 11 11:53:52 ms01 kernel: reserve setup_data: [mem 0x00000000fed00000-0x00000000fed00fff] reserved
Nov 11 11:53:52 ms01 kernel: reserve setup_data: [mem 0x00000000fed20000-0x00000000fed7ffff] reserved
Nov 11 11:53:52 ms01 kernel: reserve setup_data: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
Nov 11 11:53:52 ms01 kernel: reserve setup_data: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Nov 11 11:53:52 ms01 kernel: reserve setup_data: [mem 0x0000000100000000-0x00000010afbfffff] usable
Nov 11 11:53:52 ms01 kernel: efi: EFI v2.8 by American Megatrends
Nov 11 11:53:52 ms01 kernel: efi: ACPI=0x42630000 ACPI 2.0=0x42630014 TPMFinalLog=0x425ff000 SMBIOS=0x43b94000 SMBIOS 3.0=0x43b93000 MEMATTR=0x371b0418 ESRT=0x3c028918 MOKvar=0x43bd6000 RNG=0x424d2018 TPMEventLog=0x3712b018
Nov 11 11:53:52 ms01 kernel: random: crng init done
Nov 11 11:53:52 ms01 kernel: efi: Remove mem84: MMIO range=[0xc0000000-0xcfffffff] (256MB) from e820 map
Nov 11 11:53:52 ms01 kernel: e820: remove [mem 0xc0000000-0xcfffffff] reserved
Nov 11 11:53:52 ms01 kernel: efi: Not removing mem85: MMIO range=[0xfe000000-0xfe010fff] (68KB) from e820 map
Nov 11 11:53:52 ms01 kernel: efi: Not removing mem86: MMIO range=[0xfec00000-0xfec00fff] (4KB) from e820 map
Nov 11 11:53:52 ms01 kernel: efi: Not removing mem87: MMIO range=[0xfed00000-0xfed00fff] (4KB) from e820 map
Nov 11 11:53:52 ms01 kernel: efi: Not removing mem89: MMIO range=[0xfee00000-0xfee00fff] (4KB) from e820 map
Nov 11 11:53:52 ms01 kernel: efi: Remove mem90: MMIO range=[0xff000000-0xffffffff] (16MB) from e820 map
Nov 11 11:53:52 ms01 kernel: e820: remove [mem 0xff000000-0xffffffff] reserved
Nov 11 11:53:52 ms01 kernel: secureboot: Secure boot enabled
Nov 11 11:53:52 ms01 kernel: Kernel is locked down from EFI Secure Boot mode; see man kernel_lockdown.7
Nov 11 11:53:52 ms01 kernel: SMBIOS 3.5.0 present.
Nov 11 11:53:52 ms01 kernel: DMI: Micro Computer (HK) Tech Limited Venus Series/AHWSA, BIOS AHWSA.1.22 03/12/2024
Nov 11 11:53:52 ms01 kernel: tsc: Detected 3000.000 MHz processor
Nov 11 11:53:52 ms01 kernel: tsc: Detected 2995.200 MHz TSC
Nov 11 11:53:52 ms01 kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Nov 11 11:53:52 ms01 kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
Nov 11 11:53:52 ms01 kernel: last_pfn = 0x10afc00 max_arch_pfn = 0x400000000
Nov 11 11:53:52 ms01 kernel: total RAM covered: 128192M
Nov 11 11:53:52 ms01 kernel: Found optimal setting for mtrr clean up
Nov 11 11:53:52 ms01 kernel: gran_size: 64K chunk_size: 64K num_reg: 8 lose cover RAM: 0G
Nov 11 11:53:52 ms01 kernel: MTRR map: 5 entries (3 fixed + 2 variable; max 23), built from 10 variable MTRRs
Nov 11 11:53:52 ms01 kernel: x86/PAT: Configuration [0-7]: WB WC UC- UC WB WP UC- WT
Nov 11 11:53:52 ms01 kernel: e820: update [mem 0x4c000000-0xffffffff] usable ==> reserved
Nov 11 11:53:52 ms01 kernel: last_pfn = 0x43f00 max_arch_pfn = 0x400000000
Nov 11 11:53:52 ms01 kernel: esrt: Reserving ESRT space from 0x000000003c028918 to 0x000000003c0289c8.
Nov 11 11:53:52 ms01 kernel: e820: update [mem 0x3c028000-0x3c028fff] usable ==> reserved
Nov 11 11:53:52 ms01 kernel: Using GB pages for direct mapping
Nov 11 11:53:52 ms01 kernel: secureboot: Secure boot enabled
 
Wo liest du, dass es am kernel liegen soll? man sieht ja gar nicht warum da ein Reboot kam.
 
  • Like
Reactions: Johannes S
Was steht denn im Kernel Log? Ich sehe nur einen Reboot ohne Ursache. Es muss nicht immer gleich der Kernel schuld sein, mit den Kernelupdates kommen auch oft Treiberupdates und einige Peripherie möchte dann auch gern ein Firmwareupdate. Broadcom Netzwerkkarten sind da bekannt für, wenn Treiber und Firmware zu weit auseinander sind.
Ich habe schon ein paar Server mit dem neuen Update ohne Fehler, daher gehe ich nicht von einem generellem Kernelbug aus.
 
  • Like
Reactions: news and Johannes S
Danke nochmals für den Hinweis. Ich habe gerade nachgesehen beim Serverhersteller, und es gibt schon wieder ein BIOS update.:(
Dann werde ich das mal aufspielen und hoffen es ist alles gelöst....
1731354676279.png
 
Aber auch Firmware der Netzwerkkarten mal checken.
 
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back