Proxmox dont boot after upgrade from 6.5.11-8-pve to 6.5.13-1-pve

drmx91

New Member
Mar 6, 2024
1
0
1
Hello,

i'm new on linux, and i running a home lab dor about one year, with passthrought of some HDDs and VGA from CPU to a VM with jellyfin.
Last week, made the upgrade from the kernel 6.5.11-8-pve to the 6.5.13-1-pve. After this, the machine dont initialize correctily. When i select the 6.5.11-8 on the boot screen, all works perfectly. I try isolate the error on the logs, and i see that on the new kernel the initialization stops in this lines:

Mar 05 14:44:06 tower systemd-journald[572]: Journal started
Mar 05 14:44:06 tower systemd-journald[572]: Runtime Journal (/run/log/journal/bb8a5b55c20f4f44a4605a7b1e619dd7) is 8.0M, max 635.9M, 627.9M free.
Mar 05 14:44:06 tower systemd-modules-load[573]: Inserted module 'vfio'
Mar 05 14:44:06 tower dmeventd[583]: dmeventd ready for processing.
Mar 05 14:44:06 tower systemd-modules-load[573]: Inserted module 'vfio_pci'
Mar 05 14:44:06 tower systemd-modules-load[573]: Inserted module 'vhost_net'
Mar 05 14:44:06 tower systemd[1]: Starting systemd-journal-flush.service - Flush Journal to Persistent Storage.
Mar 05 14:44:06 tower systemd: Starting systemd-udevd.service - Rule-based Manager for Device Events and Files...
Mar 05 14:44:06 tower systemd: Started systemd-journald.service - Journal Service.


On the old kernel - the one thats works -, the log contains much more lines after this lines, and looks like that the PCI passtrought its not work propriely

Mar 05 14:26:55 tower systemd[1]: Starting systemd-journal-flush.service - Flush Journal to Persistent Storage...
Mar 05 14:26:55 tower systemd-journald[574]: Time spent on flushing to /var/log/journal/bb8a5b55c20f4f44a4605a7b1e619dd7 is 16.474ms for 1086 entries.
Mar 05 14:26:55 tower systemd-journald[574]: System Journal (/var/log/journal/bb8a5b55c20f4f44a4605a7b1e619dd7) is 166.9M, max 4.0G, 3.8G free.
Mar 05 14:26:55 tower systemd-journald[574]: Received client request to flush runtime journal.
Mar 05 14:26:55 tower dmeventd[588]: Monitoring thin pool samsung-samsung-tpool.
Mar 05 14:26:55 tower systemd-udevd[593]: Using default interface naming scheme 'v252'.
Mar 05 14:26:55 tower lvm[565]: 4 logical volume(s) in volume group "samsung" monitored
Mar 05 14:26:55 tower systemd[1]: Started systemd-udevd.service - Rule-based Manager for Device Events and Files.
Mar 05 14:26:55 tower systemd[1]: Finished systemd-journal-flush.service - Flush Journal to Persistent Storage.
Mar 05 14:26:55 tower systemd[1]: Finished systemd-udev-trigger.service - Coldplug All udev Devices.
Mar 05 14:26:55 tower lvm[635]: PV /dev/nvme1n1 online, VG samsung is complete.
Mar 05 14:26:55 tower lvm[635]: VG samsung finished
Mar 05 14:26:55 tower systemd[1]: Starting ifupdown2-pre.service - Helper to synchronize boot up for ifupdown...
Mar 05 14:26:55 tower systemd[1]: Starting systemd-udev-settle.service - Wait for udev To Complete Device Initialization...
Mar 05 14:26:55 tower systemd[1]: Finished lvm2-monitor.service - Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling.
Mar 05 14:26:55 tower udevadm[852]: systemd-udev-settle.service is deprecated. Please fix zfs-import-scan.service, zfs-import-cache.service not to pull it in.
Mar 05 14:26:55 tower kernel: ee1004 0-0050: 512 byte EE1004-compliant SPD EEPROM, read-only
Mar 05 14:26:55 tower kernel: ee1004 0-0051: 512 byte EE1004-compliant SPD EEPROM, read-only
Mar 05 14:26:55 tower kernel: ee1004 0-0052: 512 byte EE1004-compliant SPD EEPROM, read-only
Mar 05 14:26:55 tower kernel: ee1004 0-0053: 512 byte EE1004-compliant SPD EEPROM, read-only
Mar 05 14:26:55 tower kernel: mei_me 0000:00:16.0: enabling device (0000 -> 0002)
Mar 05 14:26:55 tower kernel: input: PC Speaker as /devices/platform/pcspkr/input/input6
Mar 05 14:26:55 tower systemd[1]: Reached target local-fs-pre.target - Preparation for Local File Systems.
Mar 05 14:26:55 tower kernel: asus_wmi: ASUS WMI generic driver loaded
Mar 05 14:26:55 tower kernel: asus_wmi: Initialization: 0x0
Mar 05 14:26:55 tower kernel: asus_wmi: BIOS WMI version: 0.0
Mar 05 14:26:55 tower kernel: asus_wmi: SFUN value: 0x0
Mar 05 14:26:55 tower kernel: eeepc-wmi eeepc-wmi: Detected AsusMbSwInterface, not ASUSWMI, use DSTS
Mar 05 14:26:55 tower kernel: input: Eee PC WMI hotkeys as /devices/platform/eeepc-wmi/input/input7
Mar 05 14:26:55 tower kernel: spi-nor spi0.0: w25q128 (16384 Kbytes)
Mar 05 14:26:55 tower kernel: RAPL PMU: API unit is 2^-32 Joules, 3 fixed counters, 655360 ms ovfl timer
Mar 05 14:26:55 tower kernel: RAPL PMU: hw unit of domain pp0-core 2^-14 Joules
Mar 05 14:26:55 tower kernel: RAPL PMU: hw unit of domain package 2^-14 Joules
Mar 05 14:26:55 tower kernel: RAPL PMU: hw unit of domain pp1-gpu 2^-14 Joules
Mar 05 14:26:55 tower kernel: cryptd: max_cpu_qlen set to 1000
Mar 05 14:26:55 tower systemd[1]: Listening on systemd-rfkill.socket - Load/Save RF Kill Switch Status /dev/rfkill Watch.
Mar 05 14:26:55 tower kernel: Creating 1 MTD partitions on "0000:00:1f.5":
Mar 05 14:26:55 tower kernel: 0x000000000000-0x000001000000 : "BIOS"
Mar 05 14:26:55 tower kernel: AVX2 version of gcm_enc/dec engaged.
Mar 05 14:26:55 tower kernel: AES CTR mode by8 optimization enabled
Mar 05 14:26:55 tower kernel: snd_hda_intel 0000:00:1f.3: enabling device (0000 -> 0002)
Mar 05 14:26:55 tower (udev-worker)[636]: event7: Failed to call EVIOCSKEYCODE with scan code 0x7c, and key code 190: Invalid argument
Mar 05 14:26:55 tower kernel: i915 0000:00:02.0: [drm] VT-d active for gfx access
Mar 05 14:26:55 tower kernel: Console: switching to colour dummy device 80x25
Mar 05 14:26:55 tower kernel: i915 0000:00:02.0: vgaarb: deactivate vga console
Mar 05 14:26:55 tower kernel: i915 0000:00:02.0: [drm] Using Transparent Hugepages
Mar 05 14:26:55 tower kernel: i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem
Mar 05 14:26:55 tower kernel: i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/adls_dmc_ver2_01.bin (v2.1)
Mar 05 14:26:55 tower kernel: mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_ops [i915])
Mar 05 14:26:55 tower kernel: i915 0000:00:02.0: [drm] GT0: GuC firmware i915/tgl_guc_70.bin version 70.13.1
Mar 05 14:26:55 tower kernel: i915 0000:00:02.0: [drm] GT0: HuC firmware i915/tgl_huc.bin version 7.9.3
Mar 05 14:26:55 tower kernel: intel_tcc_cooling: Programmable TCC Offset detected
Mar 05 14:26:55 tower kernel: intel_rapl_msr: PL4 support detected.
Mar 05 14:26:55 tower kernel: intel_rapl_common: Found RAPL domain package
Mar 05 14:26:55 tower kernel: intel_rapl_common: Found RAPL domain core
Mar 05 14:26:55 tower kernel: intel_rapl_common: Found RAPL domain uncore


If somebody can help me, will be glad!
Thanks
 

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!

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!