DMESG errors / kernel dump

hans66

New Member
Oct 14, 2023
7
0
1
I updated today 2 things (I should remember only do one at a time...)
- Update to BIOS 3.1 (Supermicro X13SAE-F)
- Latest Proxmox 8.2.2

dmesg shows a few errors / dumps - which where not there before (although I am not sure if above changes caused this, as I do not check dmesg too often).

Any ideas/help/suggestions for me?


Issue 1: (concerns me most)
Code:
[    5.935840] ------------[ cut here ]------------
[    5.935842] i915 0000:00:02.0: Port A asks to use VBT vswing/preemph tables
[    5.935858] WARNING: CPU: 4 PID: 1148 at drivers/gpu/drm/i915/display/intel_bios.c:2686 intel_bios_init+0x18b5/0x1f30 [i915]
[    5.935984] Modules linked in: snd_soc_acpi_intel_match(+) kvm_intel(+) snd_soc_acpi soundwire_generic_allocation soundwire_bus ipmi_ssif i915(+) snd_soc_core kvm snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel crct10dif_pclmul snd_intel_dspcfg polyval_clmulni snd_intel_sdw_acpi polyval_generic ghash_clmulni_intel sha256_ssse3 snd_hda_codec sha1_ssse3 aesni_intel drm_buddy snd_hda_core ttm crypto_simd snd_hwdep mei_pxp mei_hdcp cryptd drm_display_helper snd_pcm cec snd_timer rapl acpi_ipmi cmdlinepart spi_nor snd mei_me rc_core intel_cstate soundcore intel_pmc_core pcspkr mtd ipmi_si wmi_bmof cdc_acm mei ucsi_acpi i2c_algo_bit typec_ucsi ipmi_devintf typec intel_vsec ipmi_msghandler pmt_telemetry pmt_class joydev acpi_pad input_leds acpi_tad mac_hid vhost_net vhost vhost_iotlb tap vfio_pci vfio_pci_core irqbypass vfio_iommu_type1 vfio iommufd efi_pstore dmi_sysfs ip_tables x_tables autofs4 zfs(PO) spl(O) btrfs blake2b_generic xor raid6_pq rndis_host cdc_ether usbnet mii hid_generic usbmouse usbhid hid
[    5.936026]  dm_thin_pool dm_persistent_data dm_bio_prison dm_bufio libcrc32c xhci_pci nvme xhci_pci_renesas crc32_pclmul e1000e nvme_core xhci_hcd ahci i2c_i801 spi_intel_pci intel_lpss_pci igc spi_intel i2c_smbus nvme_auth libahci intel_lpss idma64 video wmi pinctrl_alderlake
[    5.936056] CPU: 4 PID: 1148 Comm: (udev-worker) Tainted: P           O       6.8.4-3-pve #1
[    5.936059] Hardware name: Supermicro Super Server/X13SAE-F, BIOS 3.1 12/25/2023
[    5.936062] RIP: 0010:intel_bios_init+0x18b5/0x1f30 [i915]
[    5.936182] Code: 8b 7c 24 08 48 8b 5f 50 48 85 db 75 03 48 8b 1f e8 20 47 6c ce 44 89 e9 48 89 da 48 c7 c7 58 e3 8b c1 48 89 c6 e8 8b 78 cd cd <0f> 0b e9 c0 fd ff ff 89 d1 c1 e1 1f 85 d1 0f 88 c0 fe ff ff 4c 89
[    5.936186] RSP: 0018:ffffa099009677d8 EFLAGS: 00010246
[    5.936189] RAX: 0000000000000000 RBX: ffff952802f113c0 RCX: 0000000000000000
[    5.936191] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
[    5.936193] RBP: ffffa09900967870 R08: 0000000000000000 R09: 0000000000000000
[    5.936195] R10: 0000000000000000 R11: 0000000000000000 R12: ffff95280b01c000
[    5.936197] R13: 0000000000000041 R14: ffff952814ad3de0 R15: 0000000000000000
[    5.936199] FS:  000079d275fe18c0(0000) GS:ffff9546ff400000(0000) knlGS:0000000000000000
[    5.936201] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[    5.936203] CR2: 00007e30e4e81f40 CR3: 0000000131a3e000 CR4: 0000000000f50ef0
[    5.936205] PKRU: 55555554
[    5.936206] Call Trace:
[    5.936208]  <TASK>
[    5.936210]  ? show_regs+0x6d/0x80
[    5.936214]  ? __warn+0x89/0x160
[    5.936218]  ? intel_bios_init+0x18b5/0x1f30 [i915]
[    5.936341]  ? report_bug+0x17e/0x1b0
[    5.936346]  ? asm_sysvec_call_function+0x1b/0x20
[    5.936350]  ? handle_bug+0x46/0x90
[    5.936353]  ? exc_invalid_op+0x18/0x80
[    5.936355]  ? asm_exc_invalid_op+0x1b/0x20
[    5.936359]  ? intel_bios_init+0x18b5/0x1f30 [i915]
[    5.936454]  ? intel_bios_init+0x18b5/0x1f30 [i915]
[    5.936566]  ? sched_set_fifo+0x56/0x90
[    5.936570]  intel_display_driver_probe_noirq+0x3b/0x240 [i915]
[    5.936674]  i915_driver_probe+0x650/0xbf0 [i915]
[    5.936749]  ? drm_privacy_screen_get+0x16d/0x190
[    5.936752]  ? acpi_dev_found+0x64/0x80
[    5.936757]  i915_pci_probe+0xc1/0x150 [i915]
[    5.936829]  local_pci_probe+0x44/0xb0
[    5.936834]  pci_device_probe+0xc5/0x260
[    5.936837]  really_probe+0x1c9/0x430
[    5.936841]  __driver_probe_device+0x8c/0x190
[    5.936844]  driver_probe_device+0x24/0xd0
[    5.936848]  __driver_attach+0x10b/0x210
[    5.936850]  ? __pfx___driver_attach+0x10/0x10
[    5.936853]  bus_for_each_dev+0x8a/0xf0
[    5.936856]  driver_attach+0x1e/0x30
[    5.936859]  bus_add_driver+0x156/0x260
[    5.936861]  driver_register+0x5e/0x130
[    5.936864]  __pci_register_driver+0x5e/0x70
[    5.936867]  i915_pci_register_driver+0x23/0x30 [i915]
[    5.936974]  i915_init+0x23/0xc0 [i915]
[    5.937080]  ? __pfx_i915_init+0x10/0x10 [i915]
[    5.937186]  do_one_initcall+0x5b/0x340
[    5.937191]  do_init_module+0x97/0x290
[    5.937195]  load_module+0x213a/0x22a0
[    5.937199]  init_module_from_file+0x96/0x100
[    5.937201]  ? init_module_from_file+0x96/0x100
[    5.937204]  idempotent_init_module+0x11c/0x2b0
[    5.937207]  __x64_sys_finit_module+0x64/0xd0
[    5.937208]  x64_sys_call+0x169c/0x24b0
[    5.937210]  do_syscall_64+0x81/0x170
[    5.937212]  ? irqentry_exit+0x43/0x50
[    5.937214]  entry_SYSCALL_64_after_hwframe+0x78/0x80
[    5.937216] RIP: 0033:0x79d2766ee719
[    5.937229] Code: 08 89 e8 5b 5d c3 66 2e 0f 1f 84 00 00 00 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d b7 06 0d 00 f7 d8 64 89 01 48
[    5.937232] RSP: 002b:00007fff46cabc18 EFLAGS: 00000246 ORIG_RAX: 0000000000000139
[    5.937235] RAX: ffffffffffffffda RBX: 000062c7bc6e2600 RCX: 000079d2766ee719
[    5.937236] RDX: 0000000000000000 RSI: 000079d276881efd RDI: 0000000000000013
[    5.937238] RBP: 000079d276881efd R08: 0000000000000000 R09: 000062c7bc6e1460
[    5.937239] R10: 0000000000000013 R11: 0000000000000246 R12: 0000000000020000
[    5.937241] R13: 0000000000000000 R14: 000062c7bc727280 R15: 000062c7bbbbfec1
[    5.937243]  </TASK>
[    5.937244] ---[ end trace 0000000000000000 ]---


Issue 2: happens only once...
Code:
[  154.934828] x86/split lock detection: #AC: CPU 1/KVM/3345 took a split_lock trap at address: 0xbfebd050
 

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!