[SOLVED] After Update, USB TV Tuner Passthrough locks system

LANPartyCEO

New Member
Jan 18, 2022
5
0
1
37
Hello,

I suppose this is more informational about an issue with a recent? update with proxmox and it causing issued with a Hauppage USB tv tuner.

Pre update to PVE 7.1-10 (specifically on 7.1-8 at the time), the device passed through without issue. After updating to PVE 7.1-10 (and any subsequent available updates along with it; note I do have the non-production repo active) The following error is generated when PVE tries to pass through the usb device (in device or port mode passthrough, same error) when starting the VM. The error not only causes the VM to fail to start, but also hangs a portion of systemd and seems to make some/all USB functionality freeze as well as preventing the functionality of the console view of all VM's and containers as well as prevent any shell/console window from opening functionally (it is just a gray window that opens) I was able to use the IPMI interface to manually edit the qemu and remove the passthrough, which allows everything to reboot and then run normally, minus the functionality provided by the tv tuner for the specific vm.

TO test, I am able to make a new vm on a pre 7.1-10 installation, and the passthrough works normal again when used with the usb device, so the device is not the issue but rather a pve update that was done.

Passing through any other device i have to test with (usb keyboard & usb UPS) do not produce this error on 7.1-10.

Hopefully it gets resolved, hopefully this info helps to do so.


The error:

Jan 17 20:46:31 NAS kernel: Oops: 0002 [#1] SMP NOPTI
Jan 17 20:46:31 NAS kernel: CPU: 7 PID: 23646 Comm: kvm Tainted: P O 5.13.19-3-pve #1
Jan 17 20:46:31 NAS kernel: Hardware name: Supermicro H8SGL/H8SGL, BIOS 3.5b 03/18/2016
Jan 17 20:46:31 NAS kernel: RIP: 0010:em28xx_close_extension+0x75/0xb0 [em28xx]
Jan 17 20:46:31 NAS kernel: Code: 89 e7 e8 4e 99 fa e5 48 8b 1b 48 81 fb 00 90 06 c1 75 cd 49 8b 84 24 f0 01 00 00 49 8b 94 24 e8 01 00 00 48 c7 c7 20 90 06 c1 <48> 89 42 08 48 89 10 48 b8 00 01 00 00 00 00 ad de 49 89 84 24 e8
Jan 17 20:46:31 NAS kernel: RSP: 0018:ffffb60928c13c48 EFLAGS: 00010246
Jan 17 20:46:31 NAS kernel: RAX: 0000000000000000 RBX: ffffffffc1069000 RCX: 0000000000000000
Jan 17 20:46:31 NAS kernel: RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffffffffc1069020
Jan 17 20:46:31 NAS kernel: RBP: ffffb60928c13c58 R08: 0000000000000003 R09: 0000000000000000
Jan 17 20:46:31 NAS kernel: R10: ffff9ce39ee9a001 R11: ffff9ce39ee9a000 R12: ffff9ce39ee9a000
Jan 17 20:46:31 NAS kernel: R13: ffffffffc10690d0 R14: ffffffffc10690d0 R15: ffff9ce357660430
Jan 17 20:46:31 NAS kernel: FS: 00007f6ccc6e61c0(0000) GS:ffff9cea3fd80000(0000) knlGS:0000000000000000
Jan 17 20:46:31 NAS kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jan 17 20:46:31 NAS kernel: CR2: 0000000000000008 CR3: 0000000199f32000 CR4: 00000000000406e0
Jan 17 20:46:31 NAS kernel: Call Trace:
Jan 17 20:46:31 NAS kernel: <TASK>
Jan 17 20:46:31 NAS kernel: em28xx_usb_disconnect.cold+0x8b/0xcb [em28xx]
Jan 17 20:46:31 NAS kernel: usb_unbind_interface+0x90/0x280
Jan 17 20:46:31 NAS kernel: __device_release_driver+0x181/0x240
Jan 17 20:46:31 NAS kernel: device_release_driver+0x29/0x40
Jan 17 20:46:31 NAS kernel: usb_driver_release_interface+0x46/0x90
Jan 17 20:46:31 NAS kernel: proc_ioctl.part.0+0x1be/0x200
Jan 17 20:46:31 NAS kernel: usbdev_ioctl+0xb6e/0x11e0
Jan 17 20:46:31 NAS kernel: ? __handle_mm_fault+0x1403/0x16f0
Jan 17 20:46:31 NAS kernel: __x64_sys_ioctl+0x91/0xc0
Jan 17 20:46:31 NAS kernel: do_syscall_64+0x61/0xb0
Jan 17 20:46:31 NAS kernel: ? do_syscall_64+0x6e/0xb0
Jan 17 20:46:31 NAS kernel: ? handle_mm_fault+0xda/0x2c0
Jan 17 20:46:31 NAS kernel: ? exit_to_user_mode_prepare+0x37/0x1b0
Jan 17 20:46:31 NAS kernel: ? irqentry_exit_to_user_mode+0x9/0x20
Jan 17 20:46:31 NAS kernel: ? irqentry_exit+0x19/0x30
Jan 17 20:46:31 NAS kernel: ? exc_page_fault+0x8f/0x170
Jan 17 20:46:31 NAS kernel: ? asm_exc_page_fault+0x8/0x30
Jan 17 20:46:31 NAS kernel: entry_SYSCALL_64_after_hwframe+0x44/0xae
Jan 17 20:46:31 NAS kernel: RIP: 0033:0x7f6ccbc6ccc7
Jan 17 20:46:31 NAS kernel: Code: 00 00 00 48 8b 05 c9 91 0c 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 99 91 0c 00 f7 d8 64 89 01 48
Jan 17 20:46:31 NAS kernel: RSP: 002b:00007ffe716ffc18 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
Jan 17 20:46:31 NAS kernel: RAX: ffffffffffffffda RBX: 000055a1cd303d00 RCX: 00007f6ccbc6ccc7
Jan 17 20:46:31 NAS kernel: RDX: 00007ffe716ffc20 RSI: 00000000c0105512 RDI: 0000000000000011
Jan 17 20:46:31 NAS kernel: RBP: 0000000000000011 R08: 00007ffe716ffc60 R09: 0000000000000007
Jan 17 20:46:31 NAS kernel: R10: 00007f6ccbd36b80 R11: 0000000000000246 R12: 000055a1ca9fed74
Jan 17 20:46:31 NAS kernel: R13: 000055a1cadce1c0 R14: 00007ffe716ffd90 R15: 0000000000000000
Jan 17 20:46:31 NAS kernel: </TASK>
Jan 17 20:46:31 NAS kernel: Modules linked in: overlay binfmt_misc veth rc_hauppauge em28xx_rc si2157 lgdt3306a i2c_mux em28xx_dvb dvb_core amd64_edac edac_mce_amd kvm_amd ccp kvm irqbypass crct10dif_pclmul ghash_clmulni_intel aesni_intel crypto_simd cryptd ipmi_si ipmi_devintf ipmi_msghandler serio_raw pcspkr input_leds joydev mgag200 drm_kms_helper cec rc_core k10temp fam15h_power em28xx i2c_algo_bit fb_sys_fops tveeprom syscopyarea sysfillrect sysimgblt videodev mc ebtable_filter ebtables ip_set ip6table_raw iptable_raw ip6table_filter ip6_tables iptable_filter bpfilter nf_tables softdog bonding tls nfnetlink_log nfnetlink mac_hid vhost_net vhost vhost_iotlb tap ib_iser rdma_cm iw_cm ib_cm nfsd ib_core auth_rpcgss nfs_acl iscsi_tcp libiscsi_tcp lockd libiscsi grace scsi_transport_iscsi drm sunrpc ip_tables x_tables autofs4 zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) btrfs blake2b_generic xor zstd_compress raid6_pq libcrc32c ses enclosure hid_generic usbmouse
Jan 17 20:46:31 NAS kernel: usbkbd usbhid hid ohci_pci pata_acpi crc32_pclmul psmouse pata_atiixp i2c_piix4 ohci_hcd ehci_pci ahci mpt3sas ehci_hcd nvme e1000e libahci raid_class qlcnic scsi_transport_sas nvme_core
Jan 17 20:46:31 NAS kernel: CR2: 0000000000000008
Jan 17 20:46:31 NAS kernel: ---[ end trace 0709bb4306312975 ]---
Jan 17 20:46:31 NAS kernel: RIP: 0010:em28xx_close_extension+0x75/0xb0 [em28xx]
Jan 17 20:46:31 NAS kernel: Code: 89 e7 e8 4e 99 fa e5 48 8b 1b 48 81 fb 00 90 06 c1 75 cd 49 8b 84 24 f0 01 00 00 49 8b 94 24 e8 01 00 00 48 c7 c7 20 90 06 c1 <48> 89 42 08 48 89 10 48 b8 00 01 00 00 00 00 ad de 49 89 84 24 e8
Jan 17 20:46:31 NAS kernel: RSP: 0018:ffffb60928c13c48 EFLAGS: 00010246
Jan 17 20:46:31 NAS kernel: RAX: 0000000000000000 RBX: ffffffffc1069000 RCX: 0000000000000000
Jan 17 20:46:31 NAS kernel: RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffffffffc1069020
Jan 17 20:46:31 NAS kernel: RBP: ffffb60928c13c58 R08: 0000000000000003 R09: 0000000000000000
Jan 17 20:46:31 NAS kernel: R10: ffff9ce39ee9a001 R11: ffff9ce39ee9a000 R12: ffff9ce39ee9a000
Jan 17 20:46:31 NAS kernel: R13: ffffffffc10690d0 R14: ffffffffc10690d0 R15: ffff9ce357660430
Jan 17 20:46:31 NAS kernel: FS: 00007f6ccc6e61c0(0000) GS:ffff9cea3fd80000(0000) knlGS:0000000000000000
Jan 17 20:46:31 NAS kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jan 17 20:46:31 NAS kernel: CR2: 0000000000000008 CR3: 0000000199f32000 CR4: 00000000000406e0
 
Last edited:

oguz

Proxmox Retired Staff
Retired Staff
Nov 19, 2018
5,207
680
118
hi,

TO test, I am able to make a new vm on a pre 7.1-10 installation, and the passthrough works normal again when used with the usb device, so the device is not the issue but rather a pve update that was done.

Passing through any other device i have to test with (usb keyboard & usb UPS) do not produce this error on 7.1-10.
could you post the output from pveversion -v? (hint: use [code][/code] tags)
and also please your VM configuration: qm config VMID

would be also interesting if you could test the opt-in 5.15 kernel: apt install pve-kernel-5.15 and reboot, then see if the issue still occurs.
 

LANPartyCEO

New Member
Jan 18, 2022
5
0
1
37
Sure. Especially as you have provided the necessary commands that should be no issue.

Here are the first two requested commands:

$ pveversion -v
Code:
proxmox-ve: 7.1-1 (running kernel: 5.13.19-3-pve)
pve-manager: 7.1-10 (running version: 7.1-10/6ddebafe)
pve-kernel-helper: 7.1-8
pve-kernel-5.13: 7.1-6
pve-kernel-5.11: 7.0-10
pve-kernel-5.13.19-3-pve: 5.13.19-6
pve-kernel-5.13.19-2-pve: 5.13.19-4
pve-kernel-5.11.22-7-pve: 5.11.22-12
pve-kernel-5.11.22-5-pve: 5.11.22-10
pve-kernel-5.11.22-4-pve: 5.11.22-9
ceph-fuse: 15.2.14-pve1
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.22-pve2
libproxmox-acme-perl: 1.4.1
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.1-5
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.1-2
libpve-guest-common-perl: 4.0-3
libpve-http-server-perl: 4.1-1
libpve-storage-perl: 7.0-15
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.11-1
lxcfs: 4.0.11-pve1
novnc-pve: 1.3.0-1
proxmox-backup-client: 2.1.3-1
proxmox-backup-file-restore: 2.1.3-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.4-5
pve-cluster: 7.1-3
pve-container: 4.1-3
pve-docs: 7.1-2
pve-edk2-firmware: 3.20210831-2
pve-firewall: 4.2-5
pve-firmware: 3.3-4
pve-ha-manager: 3.3-1
pve-i18n: 2.6-2
pve-qemu-kvm: 6.1.0-3
pve-xtermjs: 4.12.0-1
qemu-server: 7.1-4
smartmontools: 7.2-1
spiceterm: 3.2-2
swtpm: 0.7.0~rc1+2
vncterm: 1.7-1
zfsutils-linux: 2.1.2-pve1

$ qm config 105
Code:
boot: order=ide2;net0
cores: 6
cpu: host
cpuunits: 2048
ide2: RAIDZ2_Dir:iso/debian-10.0.0-amd64-netinst.iso,media=cdrom,size=334M
memory: 4096
name: PlexMedaServer
net0: virtio=52:BF:38:7C:F2:54,bridge=vmbr0,firewall=1
numa: 1
onboot: 0
ostype: l26
scsi0: SSDM:vm-105-disk-0,size=40G,ssd=1
scsihw: virtio-scsi-pci
smbios1: uuid=587d21ff-83b4-445d-819c-16b4a4687577
sockets: 1
startup: order=4
usb0: host=3-1
vmgenid: b2f3b79f-0148-4872-9f71-ad52e24b1715

To note, I added back a USB device so it would display in the config, but the numbers are subject to change if i use a hub/direct plug (as i am sure you are aware). Point being, so long as i remove that USB Tuner device from the config, the VM will boot as normal. I have tried changing from host to device mode for the USB, but both produce the error. also, it needs to be in host mode to not detect it as a new device on a reboot.

I will post back after some hours as the backup jobs need to complete before i can continue testing.
 

LANPartyCEO

New Member
Jan 18, 2022
5
0
1
37
here is the result after running
Code:
 apt install pve-kernel-5.15

The same crash error still happens. I have included the data from the syslog from the time of plugging in the usb hub (currently working on a separate, dedicated, older instance of pve) from the temp system back to the server for testing:

Code Part 1 (USB Decive plugged in till VM Start)

Code:
Jan 19 14:07:28 NAS kernel: usb 3-2: new full-speed USB device number 3 using ohci-pci
Jan 19 14:07:28 NAS kernel: usb 3-2: New USB device found, idVendor=0764, idProduct=0501, bcdDevice= 0.01
Jan 19 14:07:28 NAS kernel: usb 3-2: New USB device strings: Mfr=3, Product=1, SerialNumber=2
Jan 19 14:07:28 NAS kernel: usb 3-2: Product: CP1500PFCLCD
Jan 19 14:07:28 NAS kernel: usb 3-2: Manufacturer: CPS
Jan 19 14:07:28 NAS kernel: usb 3-2: SerialNumber: 000000000000
Jan 19 14:07:28 NAS kernel: hid-generic 0003:0764:0501.0004: hiddev0,hidraw2: USB HID v1.10 Device [CPS CP1500PFCLCD] on usb-0000:00:12.0-2/input0
Jan 19 14:07:30 NAS kernel: usb 1-1: new high-speed USB device number 4 using ehci-pci
Jan 19 14:07:30 NAS kernel: usb 1-1: device not accepting address 4, error -71
Jan 19 14:07:31 NAS kernel: usb 1-1: new high-speed USB device number 5 using ehci-pci
Jan 19 14:07:31 NAS kernel: usb 1-1: New USB device found, idVendor=05e3, idProduct=0610, bcdDevice=92.15
Jan 19 14:07:31 NAS kernel: usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Jan 19 14:07:31 NAS kernel: usb 1-1: Product: USB2.0 Hub
Jan 19 14:07:31 NAS kernel: usb 1-1: Manufacturer: GenesysLogic
Jan 19 14:07:31 NAS kernel: hub 1-1:1.0: USB hub found
Jan 19 14:07:31 NAS kernel: hub 1-1:1.0: 4 ports detected
Jan 19 14:07:31 NAS kernel: usb 1-1.4: new high-speed USB device number 6 using ehci-pci
Jan 19 14:07:31 NAS kernel: usb 1-1.4: New USB device found, idVendor=2040, idProduct=826d, bcdDevice= 1.00
Jan 19 14:07:31 NAS kernel: usb 1-1.4: New USB device strings: Mfr=3, Product=1, SerialNumber=2
Jan 19 14:07:31 NAS kernel: usb 1-1.4: Product: 955D
Jan 19 14:07:31 NAS kernel: usb 1-1.4: Manufacturer: HCW
Jan 19 14:07:31 NAS kernel: usb 1-1.4: SerialNumber: 0013946299
Jan 19 14:07:31 NAS kernel: mc: Linux media interface: v0.10
Jan 19 14:07:31 NAS kernel: videodev: Linux video capture interface: v2.00
Jan 19 14:07:31 NAS kernel: em28xx 1-1.4:1.0: New device HCW 955D @ 480 Mbps (2040:826d, interface 0, class 0)
Jan 19 14:07:31 NAS kernel: em28xx 1-1.4:1.0: DVB interface 0 found: bulk
Jan 19 14:07:31 NAS kernel: em28xx 1-1.4:1.0: chip ID is em28174
Jan 19 14:07:33 NAS kernel: em28xx 1-1.4:1.0: EEPROM ID = 26 00 01 00, EEPROM hash = 0x1699004e
Jan 19 14:07:33 NAS kernel: em28xx 1-1.4:1.0: EEPROM info:
Jan 19 14:07:33 NAS kernel: em28xx 1-1.4:1.0:     microcode start address = 0x0004, boot configuration = 0x01
Jan 19 14:07:33 NAS kernel: em28xx 1-1.4:1.0:     AC97 audio (5 sample rates)
Jan 19 14:07:33 NAS kernel: em28xx 1-1.4:1.0:     500mA max power
Jan 19 14:07:33 NAS kernel: em28xx 1-1.4:1.0:     Table at offset 0x27, strings=0x0a72, 0x187c, 0x086a
Jan 19 14:07:33 NAS kernel: em28xx 1-1.4:1.0: Identified as Hauppauge WinTV-dualHD 01595 ATSC/QAM (card=100)
Jan 19 14:07:33 NAS kernel: tveeprom: Hauppauge model 204201, rev B3I6, serial# 13946299
Jan 19 14:07:33 NAS kernel: tveeprom: tuner model is SiLabs Si2157 (idx 186, type 4)
Jan 19 14:07:33 NAS kernel: tveeprom: TV standards PAL(B/G) NTSC(M) PAL(I) SECAM(L/L') PAL(D/D1/K) ATSC/DVB Digital (eeprom 0xfc)
Jan 19 14:07:33 NAS kernel: tveeprom: audio processor is None (idx 0)
Jan 19 14:07:33 NAS kernel: tveeprom: has no radio, has IR receiver, has no IR transmitter
Jan 19 14:07:33 NAS kernel: em28xx 1-1.4:1.0: dvb set to bulk mode.
Jan 19 14:07:33 NAS kernel: em28xx 1-1.4:1.0: chip ID is em28174
Jan 19 14:07:34 NAS kernel: em28xx 1-1.4:1.0: EEPROM ID = 26 00 01 00, EEPROM hash = 0x1699004e
Jan 19 14:07:34 NAS kernel: em28xx 1-1.4:1.0: EEPROM info:
Jan 19 14:07:34 NAS kernel: em28xx 1-1.4:1.0:     microcode start address = 0x0004, boot configuration = 0x01
Jan 19 14:07:34 NAS kernel: em28xx 1-1.4:1.0:     AC97 audio (5 sample rates)
Jan 19 14:07:34 NAS kernel: em28xx 1-1.4:1.0:     500mA max power
Jan 19 14:07:34 NAS kernel: em28xx 1-1.4:1.0:     Table at offset 0x27, strings=0x0a72, 0x187c, 0x086a
Jan 19 14:07:34 NAS kernel: em28xx 1-1.4:1.0: Identified as Hauppauge WinTV-dualHD 01595 ATSC/QAM (card=100)
Jan 19 14:07:34 NAS kernel: tveeprom: Hauppauge model 204201, rev B3I6, serial# 13946299
Jan 19 14:07:34 NAS kernel: tveeprom: tuner model is SiLabs Si2157 (idx 186, type 4)
Jan 19 14:07:34 NAS kernel: tveeprom: TV standards PAL(B/G) NTSC(M) PAL(I) SECAM(L/L') PAL(D/D1/K) ATSC/DVB Digital (eeprom 0xfc)
Jan 19 14:07:34 NAS kernel: tveeprom: audio processor is None (idx 0)
Jan 19 14:07:34 NAS kernel: tveeprom: has no radio, has IR receiver, has no IR transmitter
Jan 19 14:07:34 NAS kernel: em28xx 1-1.4:1.0: dvb ts2 set to bulk mode.
Jan 19 14:07:34 NAS kernel: usbcore: registered new interface driver em28xx
Jan 19 14:07:34 NAS kernel: em28xx 1-1.4:1.0: Binding DVB extension
Jan 19 14:07:34 NAS kernel: i2c i2c-4: Added multiplexed i2c bus 7
Jan 19 14:07:34 NAS kernel: lgdt3306a 4-0059: LG Electronics LGDT3306A successfully identified
Jan 19 14:07:34 NAS kernel: si2157 7-0060: Silicon Labs Si2147/2148/2157/2158 successfully attached
Jan 19 14:07:34 NAS kernel: dvbdev: DVB: registering new adapter (1-1.4:1.0)
Jan 19 14:07:34 NAS kernel: em28xx 1-1.4:1.0: DVB: registering adapter 0 frontend 0 (LG Electronics LGDT3306A VSB/QAM Frontend)...
Jan 19 14:07:34 NAS kernel: dvbdev: dvb_create_media_entity: media entity 'LG Electronics LGDT3306A VSB/QAM Frontend' registered.
Jan 19 14:07:34 NAS kernel: dvbdev: dvb_create_media_entity: media entity 'dvb-demux' registered.
Jan 19 14:07:34 NAS kernel: em28xx 1-1.4:1.0: DVB extension successfully initialized
Jan 19 14:07:34 NAS kernel: em28xx 1-1.4:1.0: Binding DVB extension
Jan 19 14:07:34 NAS kernel: i2c i2c-6: Added multiplexed i2c bus 8
Jan 19 14:07:34 NAS kernel: lgdt3306a 6-000e: LG Electronics LGDT3306A successfully identified
Jan 19 14:07:34 NAS kernel: si2157 8-0062: Silicon Labs Si2147/2148/2157/2158 successfully attached
Jan 19 14:07:34 NAS kernel: dvbdev: DVB: registering new adapter (1-1.4:1.0)
Jan 19 14:07:34 NAS kernel: em28xx 1-1.4:1.0: DVB: registering adapter 1 frontend 0 (LG Electronics LGDT3306A VSB/QAM Frontend)...
Jan 19 14:07:34 NAS kernel: dvbdev: dvb_create_media_entity: media entity 'LG Electronics LGDT3306A VSB/QAM Frontend' registered.
Jan 19 14:07:34 NAS kernel: dvbdev: dvb_create_media_entity: media entity 'dvb-demux' registered.
Jan 19 14:07:34 NAS kernel: em28xx 1-1.4:1.0: DVB extension successfully initialized
Jan 19 14:07:34 NAS kernel: em28xx: Registered (Em28xx dvb Extension) extension
Jan 19 14:07:34 NAS kernel: em28xx 1-1.4:1.0: Registering input extension
Jan 19 14:07:34 NAS kernel: Registered IR keymap rc-hauppauge
Jan 19 14:07:34 NAS kernel: rc rc0: Hauppauge WinTV-dualHD 01595 ATSC/QAM as /devices/pci0000:00/0000:00:12.2/usb1/1-1/1-1.4/1-1.4:1.0/rc/rc0
Jan 19 14:07:34 NAS kernel: rc rc0: lirc_dev: driver em28xx registered at minor = 0, scancode receiver, no transmitter
Jan 19 14:07:34 NAS kernel: input: Hauppauge WinTV-dualHD 01595 ATSC/QAM as /devices/pci0000:00/0000:00:12.2/usb1/1-1/1-1.4/1-1.4:1.0/rc/rc0/input8
Jan 19 14:07:34 NAS kernel: em28xx 1-1.4:1.0: Input extension successfully initialized
Jan 19 14:07:34 NAS kernel: em28xx 1-1.4:1.0: Remote control support is not available for this card.
Jan 19 14:07:34 NAS kernel: em28xx: Registered (Em28xx Input Extension) extension
Jan 19 14:07:35 NAS systemd-logind[13746]: Watching system buttons on /dev/input/event5 (Hauppauge WinTV-dualHD 01595 ATSC/QAM)
Jan 19 14:08:11 NAS pvedaemon[16435]: <root@pam> update VM 105: -usb0 host=1-1.4,usb3=1
Jan 19 14:08:16 NAS pvedaemon[343820]: start VM 105: UPID:NAS:00053F0C:0000C9D4:61E861A0:qmstart:105:root@pam:
Jan 19 14:08:16 NAS pvedaemon[16435]: <root@pam> starting task UPID:NAS:00053F0C:0000C9D4:61E861A0:qmstart:105:root@pam:
Jan 19 14:08:17 NAS systemd[1]: Started 105.scope.
Jan 19 14:08:17 NAS systemd-udevd[343947]: Using default interface naming scheme 'v247'.
Jan 19 14:08:17 NAS systemd-udevd[343947]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Jan 19 14:08:18 NAS kernel: device tap105i0 entered promiscuous mode
Jan 19 14:08:18 NAS systemd-udevd[343946]: Using default interface naming scheme 'v247'.
Jan 19 14:08:18 NAS systemd-udevd[343946]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Jan 19 14:08:18 NAS systemd-udevd[343946]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Jan 19 14:08:18 NAS systemd-udevd[343947]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Jan 19 14:08:18 NAS kernel: fwbr105i0: port 1(fwln105i0) entered blocking state
Jan 19 14:08:18 NAS kernel: fwbr105i0: port 1(fwln105i0) entered disabled state
Jan 19 14:08:18 NAS kernel: device fwln105i0 entered promiscuous mode
Jan 19 14:08:18 NAS kernel: fwbr105i0: port 1(fwln105i0) entered blocking state
Jan 19 14:08:18 NAS kernel: fwbr105i0: port 1(fwln105i0) entered forwarding state
Jan 19 14:08:18 NAS kernel: vmbr0: port 5(fwpr105p0) entered blocking state
Jan 19 14:08:18 NAS kernel: vmbr0: port 5(fwpr105p0) entered disabled state
Jan 19 14:08:18 NAS kernel: device fwpr105p0 entered promiscuous mode
Jan 19 14:08:18 NAS kernel: vmbr0: port 5(fwpr105p0) entered blocking state
Jan 19 14:08:18 NAS kernel: vmbr0: port 5(fwpr105p0) entered forwarding state
Jan 19 14:08:18 NAS kernel: fwbr105i0: port 2(tap105i0) entered blocking state
Jan 19 14:08:18 NAS kernel: fwbr105i0: port 2(tap105i0) entered disabled state
Jan 19 14:08:18 NAS kernel: fwbr105i0: port 2(tap105i0) entered blocking state
Jan 19 14:08:18 NAS kernel: fwbr105i0: port 2(tap105i0) entered forwarding state
 

LANPartyCEO

New Member
Jan 18, 2022
5
0
1
37
Code part 2 (Error occurs)
Code:
Jan 19 14:08:18 NAS kernel: em28xx 1-1.4:1.0: Disconnecting em28xx #1
Jan 19 14:08:18 NAS kernel: em28xx 1-1.4:1.0: Disconnecting em28xx
Jan 19 14:08:18 NAS kernel: em28xx 1-1.4:1.0: Closing DVB extension
Jan 19 14:08:18 NAS kernel: em28xx 1-1.4:1.0: Closing DVB extension
Jan 19 14:08:18 NAS kernel: em28xx 1-1.4:1.0: Closing input extension
Jan 19 14:08:18 NAS kernel: em28xx 1-1.4:1.0: Closing input extension
Jan 19 14:08:18 NAS kernel: em28xx 1-1.4:1.0: Closing input extension
Jan 19 14:08:18 NAS kernel: em28xx 1-1.4:1.0: Freeing device
Jan 19 14:08:18 NAS kernel: BUG: kernel NULL pointer dereference, address: 0000000000000008
Jan 19 14:08:18 NAS kernel: #PF: supervisor write access in kernel mode
Jan 19 14:08:18 NAS kernel: #PF: error_code(0x0002) - not-present page
Jan 19 14:08:18 NAS kernel: PGD 0 P4D 0 
Jan 19 14:08:18 NAS kernel: Oops: 0002 [#1] SMP NOPTI
Jan 19 14:08:18 NAS kernel: CPU: 5 PID: 343941 Comm: kvm Tainted: P           O      5.15.12-1-pve #1
Jan 19 14:08:18 NAS kernel: Hardware name: Supermicro H8SGL/H8SGL, BIOS 3.5b       03/18/2016
Jan 19 14:08:18 NAS kernel: RIP: 0010:em28xx_close_extension+0x75/0xb0 [em28xx]
Jan 19 14:08:18 NAS kernel: Code: 89 e7 e8 ee 17 4e f5 48 8b 1b 48 81 fb 20 22 53 c1 75 cd 49 8b 84 24 f0 01 00 00 49 8b 94 24 e8 01 00 00 48 c7 c7 40 22 53 c1 <48> 89 42 08 48 89 10 48 b8 00 01 00 00 00 00 ad de 49 89 84 24 e8
Jan 19 14:08:18 NAS kernel: RSP: 0018:ffffb448be287be0 EFLAGS: 00010246
Jan 19 14:08:18 NAS kernel: RAX: 0000000000000000 RBX: ffffffffc1532220 RCX: 0000000080040003
Jan 19 14:08:18 NAS kernel: RDX: 0000000000000000 RSI: 0000000080040003 RDI: ffffffffc1532240
Jan 19 14:08:18 NAS kernel: RBP: ffffb448be287bf0 R08: 0000000000000001 R09: 0000000000000001
Jan 19 14:08:18 NAS kernel: R10: ffff9fae1798e001 R11: 0000000000000001 R12: ffff9fae1798e000
Jan 19 14:08:18 NAS kernel: R13: ffffffffc1532d30 R14: ffffffffc1532d30 R15: ffff9fb4bc5ebc30
Jan 19 14:08:18 NAS kernel: FS:  00007f65f6ffe1c0(0000) GS:ffff9fb43fd40000(0000) knlGS:0000000000000000
Jan 19 14:08:18 NAS kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jan 19 14:08:18 NAS kernel: CR2: 0000000000000008 CR3: 00000001e92e6000 CR4: 00000000000406e0
Jan 19 14:08:18 NAS kernel: Call Trace:
Jan 19 14:08:18 NAS kernel:  <TASK>
Jan 19 14:08:18 NAS kernel:  em28xx_usb_disconnect.cold+0x8b/0xcb [em28xx]
Jan 19 14:08:18 NAS kernel:  usb_unbind_interface+0x90/0x280
Jan 19 14:08:18 NAS kernel:  __device_release_driver+0x266/0x270
Jan 19 14:08:18 NAS kernel:  device_release_driver+0x29/0x40
Jan 19 14:08:18 NAS kernel:  usb_driver_release_interface+0x46/0x90
Jan 19 14:08:18 NAS kernel:  proc_ioctl.part.0+0x1bb/0x200
Jan 19 14:08:18 NAS kernel:  usbdev_ioctl+0x6e9/0x1470
Jan 19 14:08:18 NAS kernel:  ? usbdev_ioctl+0x1da/0x1470
Jan 19 14:08:18 NAS kernel:  ? __fget_files+0xa3/0xd0
Jan 19 14:08:18 NAS kernel:  __x64_sys_ioctl+0x91/0xc0
Jan 19 14:08:18 NAS kernel:  do_syscall_64+0x5c/0xc0
Jan 19 14:08:18 NAS kernel:  ? do_syscall_64+0x69/0xc0
Jan 19 14:08:18 NAS kernel:  ? syscall_exit_to_user_mode+0x27/0x50
Jan 19 14:08:18 NAS kernel:  ? do_syscall_64+0x69/0xc0
Jan 19 14:08:18 NAS kernel:  ? handle_mm_fault+0xd8/0x2c0
Jan 19 14:08:18 NAS kernel:  ? exit_to_user_mode_prepare+0x37/0x1b0
Jan 19 14:08:18 NAS kernel:  ? irqentry_exit_to_user_mode+0x9/0x20
Jan 19 14:08:18 NAS kernel:  ? irqentry_exit+0x19/0x30
Jan 19 14:08:18 NAS kernel:  ? exc_page_fault+0x89/0x160
Jan 19 14:08:18 NAS kernel:  ? asm_exc_page_fault+0x8/0x30
Jan 19 14:08:18 NAS kernel:  entry_SYSCALL_64_after_hwframe+0x44/0xae
Jan 19 14:08:18 NAS kernel: RIP: 0033:0x7f65f6584cc7
Jan 19 14:08:18 NAS kernel: Code: 00 00 00 48 8b 05 c9 91 0c 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 99 91 0c 00 f7 d8 64 89 01 48
Jan 19 14:08:18 NAS kernel: RSP: 002b:00007ffd28f07d98 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
Jan 19 14:08:18 NAS kernel: RAX: ffffffffffffffda RBX: 0000562859312fd0 RCX: 00007f65f6584cc7
Jan 19 14:08:18 NAS kernel: RDX: 00007ffd28f07da0 RSI: 00000000c0105512 RDI: 000000000000000e
Jan 19 14:08:18 NAS kernel: RBP: 000000000000000e R08: 00007ffd28f07de0 R09: 0000000000000007
Jan 19 14:08:18 NAS kernel: R10: 00007f65f664eb80 R11: 0000000000000246 R12: 0000562856e88d74
Jan 19 14:08:18 NAS kernel: R13: 00005628572581c0 R14: 00007ffd28f07f10 R15: 0000000000000000
Jan 19 14:08:18 NAS kernel:  </TASK>
Jan 19 14:08:18 NAS kernel: Modules linked in: rc_hauppauge em28xx_rc si2157 lgdt3306a i2c_mux em28xx_dvb dvb_core em28xx tveeprom videodev mc binfmt_misc tcp_diag inet_diag xt_nat xt_tcpudp xt_conntrack xt_MASQUERADE xfrm_user xfrm_algo nft_counter xt_addrtype nft_compat nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 overlay veth ebtable_filter ebtables ip_set ip6table_raw iptable_raw ip6table_filter ip6_tables iptable_filter bpfilter nf_tables softdog bonding tls nfnetlink_log nfnetlink amd64_edac edac_mce_amd kvm_amd ccp kvm irqbypass crct10dif_pclmul ghash_clmulni_intel aesni_intel crypto_simd cryptd pcspkr serio_raw ipmi_si ipmi_devintf ipmi_msghandler mgag200 drm_kms_helper cec fam15h_power rc_core i2c_algo_bit fb_sys_fops syscopyarea sysfillrect k10temp sysimgblt input_leds joydev mac_hid vhost_net vhost vhost_iotlb tap ib_iser rdma_cm iw_cm ib_cm nfsd ib_core auth_rpcgss iscsi_tcp nfs_acl libiscsi_tcp lockd libiscsi grace scsi_transport_iscsi drm sunrpc ip_tables x_tables
Jan 19 14:08:18 NAS kernel:  autofs4 zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) btrfs blake2b_generic xor ses zstd_compress enclosure raid6_pq libcrc32c hid_generic usbmouse usbkbd usbhid hid ohci_pci crc32_pclmul pata_acpi psmouse mpt3sas pata_atiixp ahci i2c_piix4 nvme ehci_pci ohci_hcd raid_class e1000e libahci ehci_hcd scsi_transport_sas nvme_core
Jan 19 14:08:18 NAS kernel: CR2: 0000000000000008
Jan 19 14:08:18 NAS kernel: ---[ end trace bf8957d0785edfc9 ]---
Jan 19 14:08:18 NAS kernel: RIP: 0010:em28xx_close_extension+0x75/0xb0 [em28xx]
Jan 19 14:08:18 NAS kernel: Code: 89 e7 e8 ee 17 4e f5 48 8b 1b 48 81 fb 20 22 53 c1 75 cd 49 8b 84 24 f0 01 00 00 49 8b 94 24 e8 01 00 00 48 c7 c7 40 22 53 c1 <48> 89 42 08 48 89 10 48 b8 00 01 00 00 00 00 ad de 49 89 84 24 e8
Jan 19 14:08:18 NAS kernel: RSP: 0018:ffffb448be287be0 EFLAGS: 00010246
Jan 19 14:08:18 NAS kernel: RAX: 0000000000000000 RBX: ffffffffc1532220 RCX: 0000000080040003
Jan 19 14:08:18 NAS kernel: RDX: 0000000000000000 RSI: 0000000080040003 RDI: ffffffffc1532240
Jan 19 14:08:18 NAS kernel: RBP: ffffb448be287bf0 R08: 0000000000000001 R09: 0000000000000001
Jan 19 14:08:18 NAS kernel: R10: ffff9fae1798e001 R11: 0000000000000001 R12: ffff9fae1798e000
Jan 19 14:08:18 NAS kernel: R13: ffffffffc1532d30 R14: ffffffffc1532d30 R15: ffff9fb4bc5ebc30
Jan 19 14:08:18 NAS kernel: FS:  00007f65f6ffe1c0(0000) GS:ffff9fb43fd40000(0000) knlGS:0000000000000000
Jan 19 14:08:18 NAS kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jan 19 14:08:18 NAS kernel: CR2: 0000000000000008 CR3: 00000001e92e6000 CR4: 00000000000406e0
Jan 19 14:08:21 NAS pvedaemon[16435]: VM 105 qmp command failed - VM 105 not running

for Ref:

pveversion -v

Code:
proxmox-ve: 7.1-1 (running kernel: 5.15.12-1-pve)
pve-manager: 7.1-10 (running version: 7.1-10/6ddebafe)
pve-kernel-5.15: 7.1-8
pve-kernel-helper: 7.1-8
pve-kernel-5.13: 7.1-6
pve-kernel-5.11: 7.0-10
pve-kernel-5.15.12-1-pve: 5.15.12-2
pve-kernel-5.13.19-3-pve: 5.13.19-6
pve-kernel-5.13.19-2-pve: 5.13.19-4
pve-kernel-5.11.22-7-pve: 5.11.22-12
pve-kernel-5.11.22-5-pve: 5.11.22-10
pve-kernel-5.11.22-4-pve: 5.11.22-9
ceph-fuse: 15.2.14-pve1
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.22-pve2
libproxmox-acme-perl: 1.4.1
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.1-5
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.1-2
libpve-guest-common-perl: 4.0-3
libpve-http-server-perl: 4.1-1
libpve-storage-perl: 7.0-15
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.11-1
lxcfs: 4.0.11-pve1
novnc-pve: 1.3.0-1
proxmox-backup-client: 2.1.3-1
proxmox-backup-file-restore: 2.1.3-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.4-5
pve-cluster: 7.1-3
pve-container: 4.1-3
pve-docs: 7.1-2
pve-edk2-firmware: 3.20210831-2
pve-firewall: 4.2-5
pve-firmware: 3.3-4
pve-ha-manager: 3.3-1
pve-i18n: 2.6-2
pve-qemu-kvm: 6.1.0-3
pve-xtermjs: 4.12.0-1
qemu-server: 7.1-4
smartmontools: 7.2-1
spiceterm: 3.2-2
swtpm: 0.7.0~rc1+2
vncterm: 1.7-1
zfsutils-linux: 2.1.2-pve1
 

oguz

Proxmox Retired Staff
Retired Staff
Nov 19, 2018
5,207
680
118
sorry for the late response and thank you for providing the outputs :)

Passing through any other device i have to test with (usb keyboard & usb UPS) do not produce this error on 7.1-10.
so it seems its the only device that causes the issue then...

from the kernel trace it seems to be an issue with the em28xx driver [0]. looking at the kernel changelogs there has been a patch fixing a possible null pointer dereference [1] (as the trace you've posted here), but the fix should be already included within our latest 5.15 kernels...

TO test, I am able to make a new vm on a pre 7.1-10 installation, and the passthrough works normal again when used with the usb device, so the device is not the issue but rather a pve update that was done.
in the meantime, could you also send the pveversion -v output from the working machine?

[0]: https://wiki.ubuntu.com/em28xx
[1]: https://lkml.org/lkml/2021/9/17/848
 

oguz

Proxmox Retired Staff
Retired Staff
Nov 19, 2018
5,207
680
118
yep it seems like a bug in the driver code (but another one that was introduced here [0]) [1] [2]

we might cherry-pick it, or wait for it to be included in an upstream release.

in the meantime you can try booting an older kernel version (like the one from your working box)

[0]: https://github.com/torvalds/linux/commit/2c98b8a3458df03abdc6945bbef67ef91d181938
[1]: https://lore.kernel.org/lkml/20220120193730.28155-1-paskripkin@gmail.com/
[2]: https://lore.kernel.org/lkml/12d7f37f-340f-f316-f876-b62a1bd20c52@elbmurf.de/
 
Last edited:

LANPartyCEO

New Member
Jan 18, 2022
5
0
1
37
No Worries. Thanks for getting back. Was just something i figured I wasn't the only one doing so I should but the data out there and help if i can.

I see....I would never have found that info so fast. Makes sense. What happens, happens. Hopefully it goes back soon. Otherwise i have a good temp solution (the BEST kind of permanent) and the backups dump to the main system so easy to move between the two.

Here's the working temp machine as requested. I just installed the latest iso and left it at that, which works fine.

Code:
pveversion -v
proxmox-ve: 7.1-1 (running kernel: 5.13.19-2-pve)
pve-manager: 7.1-7 (running version: 7.1-7/df5740ad)
pve-kernel-helper: 7.1-6
pve-kernel-5.13: 7.1-5
pve-kernel-5.13.19-2-pve: 5.13.19-4
ceph-fuse: 15.2.15-pve1
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.22-pve2
libproxmox-acme-perl: 1.4.0
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.1-5
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.0-14
libpve-guest-common-perl: 4.0-3
libpve-http-server-perl: 4.0-4
libpve-storage-perl: 7.0-15
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.11-1
lxcfs: 4.0.11-pve1
novnc-pve: 1.2.0-3
proxmox-backup-client: 2.1.2-1
proxmox-backup-file-restore: 2.1.2-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.4-4
pve-cluster: 7.1-2
pve-container: 4.1-2
pve-docs: 7.1-2
pve-edk2-firmware: 3.20210831-2
pve-firewall: 4.2-5
pve-firmware: 3.3-3
pve-ha-manager: 3.3-1
pve-i18n: 2.6-2
pve-qemu-kvm: 6.1.0-3
pve-xtermjs: 4.12.0-1
qemu-server: 7.1-4
smartmontools: 7.2-1
spiceterm: 3.2-2
swtpm: 0.7.0~rc1+2
vncterm: 1.7-1
zfsutils-linux: 2.1.1-pve3

Thanks again! Much appreciated.

-LAN
 

Frozenozone

New Member
Dec 31, 2021
16
3
3
53
This sounds like the issue I currently have. I believe that I upgraded a few days ago to 7.1-10 and has been driving me nuts today. Since this was a headless server, I hooked up a monitor to see if there is anything showing on the monitor. Low and behold, my 955D USB device was having issues. It never did before I upgraded. I was on 7.1-8 and I wish I could go back at this point.

I guess I could try upgrading to the newest pve version 5.15? Not too sure if that would help?

I am at or on version:
root@pve01:~# pveversion
pve-manager/7.1-10/6ddebafe (running kernel: 5.13.19-3-pve)
 

oguz

Proxmox Retired Staff
Retired Staff
Nov 19, 2018
5,207
680
118
This sounds like the issue I currently have. I believe that I upgraded a few days ago to 7.1-10 and has been driving me nuts today. Since this was a headless server, I hooked up a monitor to see if there is anything showing on the monitor. Low and behold, my 955D USB device was having issues. It never did before I upgraded. I was on 7.1-8 and I wish I could go back at this point.

I guess I could try upgrading to the newest pve version 5.15? Not too sure if that would help?

I am at or on version:
root@pve01:~# pveversion
pve-manager/7.1-10/6ddebafe (running kernel: 5.13.19-3-pve)

we're waiting for the fix to show up on the main tree from linus. don't think it'd change much to upgrade to the 5.15 kernel for you now, since it doesn't contain the fix.

you can try reverting to an older kernel version that you have installed on your machine until that's merged.

I was on 7.1-8 and I wish I could go back at this point.
just downgrade your kernel for now ;)
 

Frozenozone

New Member
Dec 31, 2021
16
3
3
53
Thank you for your response. I am kind of new to Proxmox and I am not too sure how to downgrade. I have run this command, "proxmox-boot-tool kernel list" and this is what is shows:

Automatically selected kernels:
5.13.19-2-pve
5.13.19-3-pve

Just so I know, was 5.13.19.3 installed when I upgraded to 7.1-10? I really didn't pay attention before the upgrade.

So, if I downgrade to 5.13.19.2 it will put me back to 7.1-8?

I found another one of your posts with commands.

proxmox-boot-tool kernel list
proxmox-boot-tool kernel add|remove <kernel-version>
proxmox-boot-tool refresh

Thanks again for the help!
 

Frozenozone

New Member
Dec 31, 2021
16
3
3
53
Maybe I don't understand how to downgrade. I have tried all the commands. What are the actual steps to downgrade or make a previous boot loader as default at boot.

Thanks
 
  • Like
Reactions: leesteken

oguz

Proxmox Retired Staff
Retired Staff
Nov 19, 2018
5,207
680
118
Maybe I don't understand how to downgrade. I have tried all the commands. What are the actual steps to downgrade or make a previous boot loader as default at boot.
you can choose the older kernel for boot.

the process is different for the two bootloaders we support (GRUB or systemd-boot) [0]

after determining which one you're using:
* for GRUB
run grep menuentry /boot/grub/grub.cfg and you will see the available entries in the boot menu.
then you can edit the GRUB_DEFAULT variable in the /etc/default/grub file:
Code:
# for example:
# add first the submenu, then '>' followed by the menuentry for the kernel you want to boot
GRUB_DEFAULT="gnulinux-advanced-62b81a8b-7278-439e-9df2-6c81c2e3441e>gnulinux-5.11.22-6-pve-advanced-62b81a8b-7278-439e-9df2-6c81c2e3441e"

then run update-grub and reboot. to check the booted kernel you can run uname -a or pveversion

* systemd-boot

just use our proxmox-boot-tool:
Code:
$ proxmox-boot-tool kernel list
$ proxmox-boot-tool kernel add|remove <kernel-version>
# for example:
# proxmox-boot-tool kernel add 5.11.22-6-pve
$ proxmox-boot-tool refresh
followed by reboot :)

hope this helps!

[0]: https://pve.proxmox.com/wiki/Host_Bootloader#sysboot_determine_bootloader_used
 

volodin73

New Member
Feb 7, 2022
2
0
1
36
hello i have the same problem!!! Help!!!
pveversion -v
proxmox-ve: 7.1-1 (running kernel: 5.13.19-4-pve)
pve-manager: 7.1-10 (running version: 7.1-10/6ddebafe)
pve-kernel-helper: 7.1-9
pve-kernel-5.13: 7.1-7
pve-kernel-5.13.19-4-pve: 5.13.19-8
pve-kernel-5.13.19-3-pve: 5.13.19-7
pve-kernel-5.13.19-2-pve: 5.13.19-4
ceph-fuse: 14.2.21-1
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown: residual config
ifupdown2: 3.1.0-1+pmx3
libjs-extjs: 7.0.0-1
libknet1: 1.22-pve2
libproxmox-acme-perl: 1.4.1
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.1-6
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.1-2
libpve-guest-common-perl: 4.0-3
libpve-http-server-perl: 4.1-1
libpve-storage-perl: 7.0-15
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.11-1
lxcfs: 4.0.11-pve1
novnc-pve: 1.3.0-1
proxmox-backup-client: 2.1.5-1
proxmox-backup-file-restore: 2.1.5-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.4-5
pve-cluster: 7.1-3
pve-container: 4.1-3
pve-docs: 7.1-2
pve-edk2-firmware: 3.20210831-2
pve-firewall: 4.2-5
pve-firmware: 3.3-4
pve-ha-manager: 3.3-3
pve-i18n: 2.6-2
pve-qemu-kvm: 6.1.1-1
pve-xtermjs: 4.16.0-1
qemu-server: 7.1-4
smartmontools: 7.2-1
spiceterm: 3.2-2
swtpm: 0.7.0~rc1+2
vncterm: 1.7-1
zfsutils-linux: 2.1.2-pve1
root@proxmox:~# uname -r
5.13.19-4-pve

log:
Feb 07 16:47:49 proxmox2 kernel: usb 1-1.6: USB disconnect, device number 3
Feb 07 16:47:49 proxmox2 kernel: BUG: kernel NULL pointer dereference, address: 0000000000000030
Feb 07 16:47:49 proxmox2 kernel: #PF: supervisor read access in kernel mode
Feb 07 16:47:49 proxmox2 kernel: #PF: error_code(0x0000) - not-present page
Feb 07 16:47:49 proxmox2 kernel: PGD 0 P4D 0
Feb 07 16:47:49 proxmox2 kernel: Oops: 0000 [#1] SMP PTI
Feb 07 16:47:49 proxmox2 kernel: CPU: 0 PID: 27655 Comm: kworker/0:2 Tainted: P O 5.13.19-4-pve #1
Feb 07 16:47:49 proxmox2 kernel: Hardware name: System manufacturer System Product Name/P8H77-M PRO, BIOS 1505 10/17/2014
Feb 07 16:47:49 proxmox2 kernel: Workqueue: usb_hub_wq hub_event
Feb 07 16:47:49 proxmox2 kernel: RIP: 0010:blk_mq_cancel_work_sync+0x5/0x60
Feb 07 16:47:49 proxmox2 kernel: Code: 4c 89 f7 e8 9d 13 00 00 e9 4b ff ff ff 48 8b 45 d0 49 89 85 e8 00 00 00 31 c0 eb a0 b8 ea ff ff ff eb c1 66 90 0f 1f 44 00 00 <48> 83 7f 30 00 74 45 55 48 89 e5 41 54 49 89 fc 48 8d bf f8 04 00
Feb 07 16:47:49 proxmox2 kernel: RSP: 0000:ffffa3c14dadf9c0 EFLAGS: 00010246
Feb 07 16:47:49 proxmox2 kernel: RAX: 0000000000000000 RBX: ffff943b49102b00 RCX: 0000000000000282
Feb 07 16:47:49 proxmox2 kernel: RDX: ffff943b4044bb40 RSI: ffffffff965a7766 RDI: 0000000000000000
Feb 07 16:47:49 proxmox2 kernel: RBP: ffffa3c14dadf9d8 R08: 0000000000000282 R09: ffffa3c14dadfa08
Feb 07 16:47:49 proxmox2 kernel: R10: 0000000000000000 R11: ffff943b4d9834c0 R12: ffff943b4044b8a0
Feb 07 16:47:49 proxmox2 kernel: R13: 0000000000000000 R14: 0000000000000000 R15: ffff943b4b0f8998
Feb 07 16:47:49 proxmox2 kernel: FS: 0000000000000000(0000) GS:ffff943f4be00000(0000) knlGS:0000000000000000
Feb 07 16:47:49 proxmox2 kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Feb 07 16:47:49 proxmox2 kernel: CR2: 0000000000000030 CR3: 000000010659c001 CR4: 00000000001706f0
Feb 07 16:47:49 proxmox2 kernel: Call Trace:
Feb 07 16:47:49 proxmox2 kernel: <TASK>
Feb 07 16:47:49 proxmox2 kernel: ? disk_release+0x24/0xa0
Feb 07 16:47:49 proxmox2 kernel: device_release+0x3b/0xa0
Feb 07 16:47:49 proxmox2 kernel: kobject_put+0x94/0x1b0
Feb 07 16:47:49 proxmox2 kernel: put_device+0x13/0x20
Feb 07 16:47:49 proxmox2 kernel: put_disk+0x1b/0x20
Feb 07 16:47:49 proxmox2 kernel: sg_device_destroy+0x54/0x90
Feb 07 16:47:49 proxmox2 kernel: sg_remove_device+0x128/0x170
Feb 07 16:47:49 proxmox2 kernel: device_del+0x138/0x3e0
Feb 07 16:47:49 proxmox2 kernel: ? kobject_put+0xae/0x1b0
Feb 07 16:47:49 proxmox2 kernel: device_unregister+0x1b/0x60
Feb 07 16:47:49 proxmox2 kernel: __scsi_remove_device+0x110/0x150
Feb 07 16:47:49 proxmox2 kernel: scsi_forget_host+0x5f/0x70
Feb 07 16:47:49 proxmox2 kernel: scsi_remove_host+0x77/0x110
Feb 07 16:47:49 proxmox2 kernel: usb_stor_disconnect+0x50/0xd0 [usb_storage]
Feb 07 16:47:49 proxmox2 kernel: usb_unbind_interface+0x90/0x280
Feb 07 16:47:49 proxmox2 kernel: __device_release_driver+0x181/0x240
Feb 07 16:47:49 proxmox2 kernel: device_release_driver+0x29/0x40
Feb 07 16:47:49 proxmox2 kernel: bus_remove_device+0xe1/0x150
Feb 07 16:47:49 proxmox2 kernel: device_del+0x19c/0x3e0
Feb 07 16:47:49 proxmox2 kernel: usb_disable_device+0xcb/0x1f0
Feb 07 16:47:49 proxmox2 kernel: usb_disconnect.cold+0x7f/0x20f
Feb 07 16:47:49 proxmox2 kernel: hub_event+0xb9a/0x1900
Feb 07 16:47:49 proxmox2 kernel: ? dequeue_entity+0xdb/0x450
Feb 07 16:47:49 proxmox2 kernel: process_one_work+0x220/0x3c0
Feb 07 16:47:49 proxmox2 kernel: worker_thread+0x53/0x420
Feb 07 16:47:49 proxmox2 kernel: ? process_one_work+0x3c0/0x3c0
Feb 07 16:47:49 proxmox2 kernel: kthread+0x12b/0x150
Feb 07 16:47:49 proxmox2 kernel: ? set_kthread_struct+0x50/0x50
Feb 07 16:47:49 proxmox2 kernel: ret_from_fork+0x22/0x30
Feb 07 16:47:49 proxmox2 kernel: </TASK>
Feb 07 16:47:49 proxmox2 kernel: Modules linked in: uas usb_storage tcp_diag inet_diag nf_conntrack_netlink xt_nat xt_tcpudp xt_conntrack nft_chain_nat xt_MASQUERADE nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xfrm_user xfrm_algo nft_counter xt_addrtype nft_compat overlay veth rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache netfs ebtable_filter ebtables ip_set ip6table_raw iptable_raw ip6table_filter ip6_tables iptable_filter bpfilter sctp ip6_udp_tunnel udp_tunnel nf_tables bonding tls softdog nfnetlink_log nfnetlink intel_rapl_msr intel_rapl_common x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_hda_codec_hdmi snd_hda_codec_realtek kvm snd_hda_codec_generic ledtrig_audio irqbypass snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi i915 snd_hda_codec crct10dif_pclmul snd_hda_core ghash_clmulni_intel snd_hwdep cryptd snd_pcm rapl intel_cstate snd_timer drm_kms_helper snd ppdev joydev cec mei_hdcp input_leds rc_core soundcore i2c_algo_bit at24 fb_sys_fops syscopyarea eeepc_wmi
Feb 07 16:47:49 proxmox2 kernel: sysfillrect mei_me sysimgblt asus_wmi mei sparse_keymap parport_pc pcspkr mac_hid parport wmi_bmof zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) vhost_net vhost vhost_iotlb tap ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi drm sunrpc ip_tables x_tables autofs4 raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid0 multipath linear raid1 hid_generic usbkbd usbhid hid pata_acpi crc32_pclmul i2c_i801 i2c_smbus lpc_ich ahci libahci r8169 realtek xhci_pci xhci_pci_renesas ehci_pci ehci_hcd xhci_hcd wmi video
Feb 07 16:47:49 proxmox2 kernel: CR2: 0000000000000030
Feb 07 16:47:49 proxmox2 kernel: ---[ end trace 03c8701a65a8062b ]---
Feb 07 16:47:49 proxmox2 kernel: RIP: 0010:blk_mq_cancel_work_sync+0x5/0x60
Feb 07 16:47:49 proxmox2 kernel: Code: 4c 89 f7 e8 9d 13 00 00 e9 4b ff ff ff 48 8b 45 d0 49 89 85 e8 00 00 00 31 c0 eb a0 b8 ea ff ff ff eb c1 66 90 0f 1f 44 00 00 <48> 83 7f 30 00 74 45 55 48 89 e5 41 54 49 89 fc 48 8d bf f8 04 00
Feb 07 16:47:49 proxmox2 kernel: RSP: 0000:ffffa3c14dadf9c0 EFLAGS: 00010246
Feb 07 16:47:49 proxmox2 kernel: RAX: 0000000000000000 RBX: ffff943b49102b00 RCX: 0000000000000282
Feb 07 16:47:49 proxmox2 kernel: RDX: ffff943b4044bb40 RSI: ffffffff965a7766 RDI: 0000000000000000
Feb 07 16:47:49 proxmox2 kernel: RBP: ffffa3c14dadf9d8 R08: 0000000000000282 R09: ffffa3c14dadfa08
Feb 07 16:47:49 proxmox2 kernel: R10: 0000000000000000 R11: ffff943b4d9834c0 R12: ffff943b4044b8a0
Feb 07 16:47:49 proxmox2 kernel: R13: 0000000000000000 R14: 0000000000000000 R15: ffff943b4b0f8998
Feb 07 16:47:49 proxmox2 kernel: FS: 0000000000000000(0000) GS:ffff943f4be00000(0000) knlGS:0000000000000000
Feb 07 16:47:49 proxmox2 kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Feb 07 16:47:49 proxmox2 kernel: CR2: 0000000000000030 CR3: 000000010659c001 CR4: 00000000001706f0
 

Attachments

  • изображение_viber_2022-02-07_17-38-22-164.jpg
    изображение_viber_2022-02-07_17-38-22-164.jpg
    492.9 KB · Views: 3

volodin73

New Member
Feb 7, 2022
2
0
1
36
usb flash drives break the linux proxmox ,
HASP keys work fine
I am waiting for kernel update next time
 

Frozenozone

New Member
Dec 31, 2021
16
3
3
53
you can choose the older kernel for boot.

the process is different for the two bootloaders we support (GRUB or systemd-boot) [0]

after determining which one you're using:
* for GRUB
run grep menuentry /boot/grub/grub.cfg and you will see the available entries in the boot menu.
then you can edit the GRUB_DEFAULT variable in the /etc/default/grub file:
Code:
# for example:
# add first the submenu, then '>' followed by the menuentry for the kernel you want to boot
GRUB_DEFAULT="gnulinux-advanced-62b81a8b-7278-439e-9df2-6c81c2e3441e>gnulinux-5.11.22-6-pve-advanced-62b81a8b-7278-439e-9df2-6c81c2e3441e"

then run update-grub and reboot. to check the booted kernel you can run uname -a or pveversion

* systemd-boot

just use our proxmox-boot-tool:
Code:
$ proxmox-boot-tool kernel list
$ proxmox-boot-tool kernel add|remove <kernel-version>
# for example:
# proxmox-boot-tool kernel add 5.11.22-6-pve
$ proxmox-boot-tool refresh
followed by reboot :)

hope this helps!

[0]: https://pve.proxmox.com/wiki/Host_Bootloader#sysboot_determine_bootloader_used
Thank you oguz. So, what is weird is that if I run this command "/etc/default/grub" in the shell to edit the grub file I get permissions denied? I can edit the file if I ssh into the server and can get to the file that way. I went ahead and tried to update the file via ssh and ran the update-grub in the shell and rebooted. I still am not able to get the old kernel to boot. It keeps defaulting to the newest kernel.
 

oguz

Proxmox Retired Staff
Retired Staff
Nov 19, 2018
5,207
680
118
if I run this command "/etc/default/grub" in the shell to edit the grub file I get permissions denied?

you need to use an editor of your choice, like nano or vi to edit that file: nano /etc/default/grub, make your changes and then hit Ctrl-X to confirm and save :)

. I went ahead and tried to update the file via ssh and ran the update-grub in the shell and rebooted. I still am not able to get the old kernel to boot. It keeps defaulting to the newest kernel.

can you post the contents of the file here? (hint: use [code][/code] tags ;) )
 

Frozenozone

New Member
Dec 31, 2021
16
3
3
53
I am very sorry for that. I am not thinking clearly for some reason and I have always used vi. Not too sure why or what I was thinking. Anyway, here is the contents of that file...

Code:
# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full documentation of the options in this file, see:
#   info -f grub -n 'Simple configuration'

GRUB_DEFAULT="gnulinux-advanced-5ef11c8f-a4e0-4232-9b2d-d6612e543492>gnulinux-5.13.19-2-pve-advanced-5ef11c8f-a4e0-4232-9b2d-d6612e543492"
GRUB_DEFAULT=0
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet amd_iommu=on"
GRUB_CMDLINE_LINUX=""

# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"

# Uncomment to disable graphical terminal (grub-pc only)
#GRUB_TERMINAL=console

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
#GRUB_GFXMODE=640x480

# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
#GRUB_DISABLE_LINUX_UUID=true

# Uncomment to disable generation of recovery mode menu entries
#GRUB_DISABLE_RECOVERY="true"

# Uncomment to get a beep at grub start
#GRUB_INIT_TUNE="480 440 1"
 

oguz

Proxmox Retired Staff
Retired Staff
Nov 19, 2018
5,207
680
118
Code:
GRUB_DEFAULT="gnulinux-advanced-5ef11c8f-a4e0-4232-9b2d-d6612e543492>gnulinux-5.13.19-2-pve-advanced-5ef11c8f-a4e0-4232-9b2d-d6612e543492"
GRUB_DEFAULT=0

remove the duplicate GRUB_DEFAULT line and it should boot the other one :)
 

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 your own in 60 seconds.

Buy now!