December 5, 20241 yr 4 hours ago, giganode said: The plugin is verified to work under rc1. You may have a different problem. Can you provide more details? So I get the following error. Quote Dec 5 06:50:29 Sesame kernel: i915 0000:00:02.0: vgaarb: VGA decodes changed: olddecodes=none,decodes=none:owns=none Dec 5 06:50:29 Sesame kernel: i915 0000:03:00.0: vgaarb: VGA decodes changed: olddecodes=none,decodes=none:owns=io Dec 5 06:50:30 Sesame kernel: i915 0000:00:02.0: Disabled 1 VFs Dec 5 06:50:32 Sesame kernel: pci 0000:00:02.1: [8086:4680] type 00 class 0x030000 Dec 5 06:50:32 Sesame kernel: pci 0000:00:02.1: DMAR: Skip IOMMU disabling for graphics Dec 5 06:50:32 Sesame kernel: pci 0000:00:02.1: Adding to iommu group 32 Dec 5 06:50:32 Sesame kernel: pci 0000:00:02.1: vgaarb: bridge control possible Dec 5 06:50:32 Sesame kernel: pci 0000:00:02.1: vgaarb: VGA device added: decodes=io+mem,owns=none,locks=none Dec 5 06:50:32 Sesame kernel: i915 0000:00:02.0: vgaarb: VGA decodes changed: olddecodes=none,decodes=none:owns=none Dec 5 06:50:32 Sesame kernel: i915 0000:03:00.0: vgaarb: VGA decodes changed: olddecodes=none,decodes=none:owns=io Dec 5 06:50:32 Sesame kernel: i915 0000:00:02.1: enabling device (0004 -> 0006) Dec 5 06:50:32 Sesame kernel: i915 0000:00:02.1: Running in SR-IOV VF mode Dec 5 06:50:32 Sesame kernel: i915 0000:00:02.1: [drm] *ERROR* GT0: IOV: Unable to confirm version 1.13 (0000000000000000) Dec 5 06:50:32 Sesame kernel: i915 0000:00:02.1: [drm] *ERROR* GT0: IOV: Found interface version 0.1.13.4 Dec 5 06:50:32 Sesame kernel: i915 0000:00:02.1: [drm] VT-d active for gfx access Dec 5 06:50:32 Sesame kernel: i915 0000:00:02.1: [drm] Using Transparent Hugepages Dec 5 06:50:32 Sesame kernel: i915 0000:00:02.1: [drm] *ERROR* GT0: IOV: Unable to confirm version 1.13 (0000000000000000) Dec 5 06:50:32 Sesame kernel: i915 0000:00:02.1: [drm] *ERROR* GT0: IOV: Found interface version 0.1.13.4 Dec 5 06:50:32 Sesame kernel: i915 0000:00:02.1: GuC firmware PRELOADED version 0.0 submission:SR-IOV VF Dec 5 06:50:32 Sesame kernel: i915 0000:00:02.1: HuC firmware PRELOADED Dec 5 06:50:32 Sesame kernel: i915 0000:00:02.1: [drm] Protected Xe Path (PXP) protected content support initialized Dec 5 06:50:32 Sesame kernel: i915 0000:00:02.1: [drm] PMU not supported for this GPU. Dec 5 06:50:32 Sesame kernel: [drm] Initialized i915 1.6.0 20201103 for 0000:00:02.1 on minor 2 Dec 5 06:50:32 Sesame kernel: i915 0000:00:02.0: Enabled 1 VFs Unraid eventually just locks up and I have to power cycle the machine. As soon as I uninstall the plugin, everything is fine. It worked fine on 7.0.0 beta 2. It's just now it locks up. It also takes forever to start the array before it locks up. Edited December 5, 20241 yr by PaulW08
December 5, 20241 yr Author 20 minutes ago, PaulW08 said: So I get the following error. Unraid eventually just locks up and I have to power cycle the machine. As soon as I uninstall the plugin, everything is fine. It worked fine on 7.0.0 beta 2. It's just now it locks up. It also takes forever to start the array before it locks up. Apparently, this section doesn't help. Can you recreate the situation and upload Diagnostics?
December 5, 20241 yr 14 hours ago, PaulW08 said: This plugin does not seem to work on 7.0.0-rc.1. In the release notes of 7.0.0-rc.1 it does mention: i can confirm it works fine here with rc1, tested on a n100m with a windows 11 VM
December 5, 20241 yr 47 minutes ago, alturismo said: i can confirm it works fine here with rc1, tested on a n100m with a windows 11 VM Hmm, I wonder if it's because I am also using an ARC 380 along with the iGPU. I can remove the card and test and do the diagnostics later tonight.
December 5, 20241 yr Author 2 minutes ago, PaulW08 said: Hmm, I wonder if it's because I am also using an ARC 380 along with the iGPU. I can remove the card and test and do the diagnostics later tonight. Yes! You should do that. This might be the "problem". Edited December 5, 20241 yr by giganode
December 6, 20241 yr Seems to work fine with the A380 Removed and just running only the iGPU. I would prefer to have both in my system at the same time though for AV1 encoding with some of my docker containers. Here's diagnostics with the A380 and anonymous. I took one with the personal info as well if I need to send this directly to someone. sesame-diagnostics-20241206-0713-A380-INSTALLED.zip
December 6, 20241 yr 1 hour ago, PaulW08 said: I would prefer to have both in my system at the same time though for AV1 encoding with some of my docker containers. This is not possible if you use the plugin AFAIK. You have either the choice no SRIOV and using both cards at the same time or SRIOV without the A380.
December 6, 20241 yr 3 hours ago, ich777 said: This is not possible if you use the plugin AFAIK. You have either the choice no SRIOV and using both cards at the same time or SRIOV without the A380. Ahhh, I had no idea. Okay this makes a lot more sense now.
December 15, 20241 yr Hoping someone may be able to point me in right direction. I was an Alderlake early adopter and at the same time I started with Unraid with no knowledge whatsoever. I remember having to blacklist i915 or more correctly followed others instructions just to get the system up. Im still on this 12th gen machine and whilst everything relating to HW acceleration has been working for at least 18 months in Frigate and Plex I cannot now seem to delete the i915 blacklist whch I presume is neccessary to split out the vga in IOMMU and to then show the possible 7 VFs in the plugin? I have sr-iov enabled in BIOS. (do I also need to enable multi monitor in BIOS?) I have latest intel GPU plugin installed There is no other GFX card installed I am on 7.0 rc1 with no other issues Ive tried deleting i915.conf from the modprobe.d directory entirely, I've tried deleting the 'blacklist i915' line from the i915.conf file and keeping an empty i915.conf file but each time I reboot it reappears and is shown as 'blacklist i915' in the system drivers page and the i915 driver is 'disabled'. My go is stock as is my syslinux.cfg. Ive checked user scripts just in case I added something there years ago but nothing. I don't know where else to look to identify from where this is being generated.
December 15, 20241 yr 30 minutes ago, coasterman said: but each time I reboot it reappears and is shown as 'blacklist i915' in the system drivers page and the i915 driver is 'disabled'. This is done by design since the plugin enables your iGPU with the correct parameters and therefore it needs to blacklist the iGPU, however it can't enable the i915 driver with the correct parameters when you delete the i915.conf file every time. Please reboot once more and this should do the trick ...and don't remove the i915.conf file, the plugin will handle everything, if the file is not in place then you have to reboot twice your you create the file manually with the blacklist and reboot. The plugin is designed to make it as easy as possible for users to utilize SR-IOV alongside with transcoding in containers. It would be also be helpful to have your Diagnostics of a reboot after you rebooted where the plugin was able to actually activate the iGPU.
December 15, 20241 yr Thank you worked perfectly. User error entirely, I was just anticipating it was more going to be more complicated than it was and went down wrong path from there. Great addition to my Unraid set up and can use Photoshop in a VM without limitations and no more lip sync issues when playing video files. Couldn't be happier😀
December 22, 20241 yr Hello, I successfully have SR-IOV working on my 12th gen Unraid box. I have the iGPU and a GTX1080 passed through to a Win11 VM and both have drivers loaded properly. Everything is great except when I reboot, I get this: Event: VM Autostart disabled Subject: vfio-pci-errors Description: VM Autostart disabled due to vfio-bind error Importance: alert Please review /var/log/vfio-pci-errors cat /var/log/vfio-pci-errors Error: Device 0000:00:02.1 does not exist, unable to bind device But it's there: lspci | grep 2.1 00:02.1 Display controller: Intel Corporation AlderLake-S GT1 (rev 0c) This looks correct: cat /boot/config/vfio-pci.cfg BIND=0000:01:00.0|10de:1b80 0000:01:00.1|10de:10f0 0000:00:02.1|8086:4680 I have tried unchecking, and rechecking a box and clicking bind, but doesn't seem to help. vfio-pci.cfg looks correct to me. Stumped as to what is causing this error. dmesg | grep i915 [ 70.705977] i915 0000:00:02.0: enabling device (0006 -> 0007) [ 70.706075] i915 0000:00:02.0: Running in SR-IOV PF mode [ 70.706747] i915 0000:00:02.0: [drm] VT-d active for gfx access [ 70.706778] i915 0000:00:02.0: [drm] Using Transparent Hugepages [ 70.707598] mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_component_ops [i915]) [ 70.709737] i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/adls_dmc_ver2_01.bin (v2.1) [ 70.729806] i915 0000:00:02.0: [drm] GT0: GuC firmware i915/tgl_guc_70.bin version 70.13.1 [ 70.729809] i915 0000:00:02.0: [drm] GT0: HuC firmware i915/tgl_huc.bin version 7.9.3 [ 70.732863] i915 0000:00:02.0: [drm] GT0: HuC: authenticated for all workloads! [ 70.733265] i915 0000:00:02.0: [drm] GT0: GUC: submission enabled [ 70.733265] i915 0000:00:02.0: [drm] GT0: GUC: SLPC enabled [ 70.733606] i915 0000:00:02.0: [drm] GuC RC: enabled [ 70.734088] mei_pxp 0000:00:16.0-fbf6fcf1-96cf-4e2e-a6a6-1bab8cbe36b1: bound 0000:00:02.0 (ops i915_pxp_tee_component_ops [i915]) [ 70.734152] i915 0000:00:02.0: [drm] Protected Xe Path (PXP) protected content support initialized [ 70.734696] [drm] Initialized i915 1.6.0 20201103 for 0000:00:02.0 on minor 0 [ 70.734878] i915 0000:00:02.0: 7 VFs could be associated with this PF [ 70.735333] i915 0000:00:02.0: [drm] Cannot find any crtc or sizes [ 70.735536] i915 0000:00:02.0: [drm] Cannot find any crtc or sizes [ 72.922645] i915 0000:00:02.1: enabling device (0000 -> 0002) [ 72.922655] i915 0000:00:02.1: Running in SR-IOV VF mode [ 72.923632] i915 0000:00:02.1: [drm] *ERROR* GT0: IOV: Unable to confirm version 1.4 (0000000000000000) [ 72.923707] i915 0000:00:02.1: [drm] *ERROR* GT0: IOV: Found interface version 0.1.4.1 [ 72.924184] i915 0000:00:02.1: [drm] VT-d active for gfx access [ 72.924193] i915 0000:00:02.1: [drm] Using Transparent Hugepages [ 72.924627] i915 0000:00:02.1: [drm] *ERROR* GT0: IOV: Unable to confirm version 1.4 (0000000000000000) [ 72.924637] i915 0000:00:02.1: [drm] *ERROR* GT0: IOV: Found interface version 0.1.4.1 [ 72.924868] i915 0000:00:02.1: GuC firmware PRELOADED version 0.0 submission:SR-IOV VF [ 72.924869] i915 0000:00:02.1: HuC firmware PRELOADED [ 72.926964] i915 0000:00:02.1: [drm] Protected Xe Path (PXP) protected content support initialized [ 72.926966] i915 0000:00:02.1: [drm] PMU not supported for this GPU. [ 72.926998] [drm] Initialized i915 1.6.0 20201103 for 0000:00:02.1 on minor 1 [ 72.927071] i915 0000:00:02.0: Enabled 1 VFs [ 74.010166] i915 0000:00:02.1: [drm] *ERROR* tlb invalidation response timed out for seqno 23 [ 121.310200] i915 0000:00:02.0: VF1 FLR [ 121.605273] i915 0000:00:02.0: VF1 FLR xbmcdown-diagnostics-20241222-1021.zip Edited December 22, 20241 yr by cscoppa diagnostics
December 22, 20241 yr Author 15 minutes ago, cscoppa said: Hello, I successfully have SR-IOV working on my 12th gen Unraid box. I have the iGPU and a GTX1080 passed through to a Win11 VM and both have drivers loaded properly. Everything is great except when I reboot, I get this: Event: VM Autostart disabled Subject: vfio-pci-errors Description: VM Autostart disabled due to vfio-bind error Importance: alert Please review /var/log/vfio-pci-errors cat /var/log/vfio-pci-errors Error: Device 0000:00:02.1 does not exist, unable to bind device But it's there: lspci | grep 2.1 00:02.1 Display controller: Intel Corporation AlderLake-S GT1 (rev 0c) This looks correct: cat /boot/config/vfio-pci.cfg BIND=0000:01:00.0|10de:1b80 0000:01:00.1|10de:10f0 0000:00:02.1|8086:4680 I have tried unchecking, and rechecking a box and clicking bind, but doesn't seem to help. vfio-pci.cfg looks correct to me. Stumped as to what is causing this error. dmesg | grep i915 [ 70.705977] i915 0000:00:02.0: enabling device (0006 -> 0007) [ 70.706075] i915 0000:00:02.0: Running in SR-IOV PF mode [ 70.706747] i915 0000:00:02.0: [drm] VT-d active for gfx access [ 70.706778] i915 0000:00:02.0: [drm] Using Transparent Hugepages [ 70.707598] mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_component_ops [i915]) [ 70.709737] i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/adls_dmc_ver2_01.bin (v2.1) [ 70.729806] i915 0000:00:02.0: [drm] GT0: GuC firmware i915/tgl_guc_70.bin version 70.13.1 [ 70.729809] i915 0000:00:02.0: [drm] GT0: HuC firmware i915/tgl_huc.bin version 7.9.3 [ 70.732863] i915 0000:00:02.0: [drm] GT0: HuC: authenticated for all workloads! [ 70.733265] i915 0000:00:02.0: [drm] GT0: GUC: submission enabled [ 70.733265] i915 0000:00:02.0: [drm] GT0: GUC: SLPC enabled [ 70.733606] i915 0000:00:02.0: [drm] GuC RC: enabled [ 70.734088] mei_pxp 0000:00:16.0-fbf6fcf1-96cf-4e2e-a6a6-1bab8cbe36b1: bound 0000:00:02.0 (ops i915_pxp_tee_component_ops [i915]) [ 70.734152] i915 0000:00:02.0: [drm] Protected Xe Path (PXP) protected content support initialized [ 70.734696] [drm] Initialized i915 1.6.0 20201103 for 0000:00:02.0 on minor 0 [ 70.734878] i915 0000:00:02.0: 7 VFs could be associated with this PF [ 70.735333] i915 0000:00:02.0: [drm] Cannot find any crtc or sizes [ 70.735536] i915 0000:00:02.0: [drm] Cannot find any crtc or sizes [ 72.922645] i915 0000:00:02.1: enabling device (0000 -> 0002) [ 72.922655] i915 0000:00:02.1: Running in SR-IOV VF mode [ 72.923632] i915 0000:00:02.1: [drm] *ERROR* GT0: IOV: Unable to confirm version 1.4 (0000000000000000) [ 72.923707] i915 0000:00:02.1: [drm] *ERROR* GT0: IOV: Found interface version 0.1.4.1 [ 72.924184] i915 0000:00:02.1: [drm] VT-d active for gfx access [ 72.924193] i915 0000:00:02.1: [drm] Using Transparent Hugepages [ 72.924627] i915 0000:00:02.1: [drm] *ERROR* GT0: IOV: Unable to confirm version 1.4 (0000000000000000) [ 72.924637] i915 0000:00:02.1: [drm] *ERROR* GT0: IOV: Found interface version 0.1.4.1 [ 72.924868] i915 0000:00:02.1: GuC firmware PRELOADED version 0.0 submission:SR-IOV VF [ 72.924869] i915 0000:00:02.1: HuC firmware PRELOADED [ 72.926964] i915 0000:00:02.1: [drm] Protected Xe Path (PXP) protected content support initialized [ 72.926966] i915 0000:00:02.1: [drm] PMU not supported for this GPU. [ 72.926998] [drm] Initialized i915 1.6.0 20201103 for 0000:00:02.1 on minor 1 [ 72.927071] i915 0000:00:02.0: Enabled 1 VFs [ 74.010166] i915 0000:00:02.1: [drm] *ERROR* tlb invalidation response timed out for seqno 23 [ 121.310200] i915 0000:00:02.0: VF1 FLR [ 121.605273] i915 0000:00:02.0: VF1 FLR xbmcdown-diagnostics-20241222-1021.zip 175.97 kB · 0 downloads Don't bind the iGPU to vfio on boot.
December 22, 20241 yr 9 minutes ago, giganode said: Don't bind the iGPU to vfio on boot. I'm not binding the main device, only the 2.1 sub-device so it can be passed through to the VM. Not sure I understand your reply...
December 22, 20241 yr Author 38 minutes ago, cscoppa said: I'm not binding the main device, only the 2.1 sub-device so it can be passed through to the VM. Not sure I understand your reply... Okay Also don't bind VFs from the iGPU to vfio.
December 22, 20241 yr 50 minutes ago, giganode said: Okay Also don't bind VFs from the iGPU to vfio. So how do I get the iGPU to show up in the Win11 VM without binding it? I'm using the iGPU in Windows for hardware acceleration in Blue Iris. (working great, just the startup error above) Sorry if I'm slow, can I still pass through this iGPU sub-device to the VM without binding it? Edited December 22, 20241 yr by cscoppa
December 22, 20241 yr Author 34 minutes ago, cscoppa said: So how do I get the iGPU to show up in the Win11 VM without binding it? I'm using the iGPU in Windows for hardware acceleration in Blue Iris. (working great, just the startup error above) Sorry if I'm slow, can I still pass through this iGPU sub-device to the VM without binding it? Yes, normally you should be able to just select it in the dropdown menu. Take a look here: 00:02.0 is my IGPU and 00:02.1 & 00:02.1 are my VFs.
December 22, 20241 yr 37 minutes ago, cscoppa said: Sorry if I'm slow, can I still pass through this iGPU sub-device to the VM without binding it? short, yes and also recommended todo so @giganode was faster
December 22, 20241 yr Awesome, thanks guys, I'll give this a shot. Sorry for being dense, I didn't realize it would still show up in the drop-down list in VM manager without being binded first. EDIT: That did the trick! Unbinded, still getting passed through to the VM. You learn something new every day. Edited December 22, 20241 yr by cscoppa
December 22, 20241 yr Author 4 minutes ago, cscoppa said: Awesome, thanks guys, I'll give this a shot. Sorry for being dense, I didn't realize it would still show up in the drop-down list in VM manager without being binded first. No worries. You're welcome
December 22, 20241 yr 53 minutes ago, giganode said: Yes, normally you should be able to just select it in the dropdown menu. Take a look here: 00:02.0 is my IGPU and 00:02.1 & 00:02.1 are my VFs. If you want VNC to keep working too (eg for emergency access when the network config is broken for whatever reason), you'll have to add a second graphics card to the VM and set it to "Virtual". There's a plus button to add another graphics card. Edited December 22, 20241 yr by Daniel15
December 22, 20241 yr 1 minute ago, Daniel15 said: If you want VNC to keep working too (eg for emergency access when the network config is broken for whatever reason), you'll have to add a second graphics card to the VM and set it to "Virtual". There's a plus button to add another graphics card. Thanks, I might try this. Right now there's 2 cards, the Nvidia and the Intel, so I'd be adding a 3rd for the "virtual" ... guessing that would be VNC.
January 5, 20251 yr thanks to giganode, Simon et al. for this great work. I have the VM's working using this plugin. Though.............(always a catch) 1) I have a Supermicro X13-SAE-f with a i5-14500T, the objective was to get away from my previous dual E5 Xeon with 2080Ti graphics card, monster with water cooling, excessive noise, hence why I choose something with iGPU. Plex and all that jazz is working, though I really miss my VM that I used to output directly from the graphics card to my 42" TV 2) I feel somewhat deceived now that iGPU even with using this plugin, the output from the motherboard HDMI can't be used to display the VM. Unless a workaround using a DisplayLink USB-> HDMI converter (with what seems dubious results).......... 2x questions: 1) Why can't the VM output be passed through to the physical HDMI port on the motherboard? Will it be something possible to do with more jiggery-pockery with all this plug-in etc? 2) What is the best option moving forward, the less optimal solution of a USB->HDMI converter, or is it better just to install a cheap, low energy consumption GPU card, pass this through and display the VM via the HDMI cable connected to the GPU HDMI output ? I don't need high end gaming, just something to surf the net from my couch, watch some Youtube videos etc etc..............I've spent way too much time with this iGPU passthrough and trying to get monitor/TV output directly from the HDMI MB port. thanks again guys, reading this thread has given me some peace, at least being able to invoke the "sunk-cost fallacy", and realise if the pros haven't been able to do it, then I myself with my 1993 Fortran programming studies, I was pushing the proverbially uphill.
January 5, 20251 yr 3 hours ago, HelveticUp-Over said: Why can't the VM output be passed through to the physical HDMI port on the motherboard? short, as its not designed therefore, vgpu's are for VM's to get workload on a vgpu instead cpu (rendering) you can read about it in many places 3 hours ago, HelveticUp-Over said: What is the best option moving forward, the less optimal solution of a USB->HDMI converter, or is it better just to install a cheap, low energy consumption GPU card, pass this through and display the VM via the HDMI cable connected to the GPU HDMI output ? either the USB Solution, a dedicated dGPU or 3/ use a streaming solution like parsec, moonlight, ... you may have already some player on your tv like shield tv, atv, ... which then can be used as "frontend" ...
January 6, 20251 yr I'm trying to upgrade from Unraid 6.12.4 to 6.12.14 but I'm getting a general protection fault when the SR-IOV plugin is installed. I've tried deleting it and reinstalling it, too. I have to start in safe mode and delete the plugin to get the system to properly boot. Any suggestions? Jan 5 19:32:49 DanHome kernel: Setting dangerous option enable_guc - tainting kernel Jan 5 19:32:49 DanHome kernel: i915 0000:00:02.0: Running in SR-IOV PF mode Jan 5 19:32:49 DanHome kernel: i915 0000:00:02.0: [drm] VT-d active for gfx access Jan 5 19:32:49 DanHome kernel: general protection fault, probably for non-canonical address 0x783230252f7b1f70: 0000 [#1] PREEMPT SMP NOPTI Jan 5 19:32:49 DanHome kernel: CPU: 2 PID: 19823 Comm: modprobe Tainted: P U O 6.1.118-Unraid #1 Jan 5 19:32:49 DanHome kernel: Hardware name: ASUSTeK COMPUTER INC. System Product Name/Pro WS W680M-ACE SE, BIOS 3602 05/24/2024 Jan 5 19:32:49 DanHome kernel: RIP: 0010:osq_lock+0x59/0xdb Jan 5 19:32:49 DanHome kernel: Code: dd 89 55 10 48 89 4d 00 89 45 14 41 87 04 24 85 c0 75 07 b0 01 e9 89 00 00 00 ff c8 48 98 48 03 1c c5 60 cb 16 82 48 89 5d 08 <48> 89 2b 65 48 8b 14 25 80 cb 01 00 8b 45 10 85 c0 75 d6 48 8b 02 Jan 5 19:32:49 DanHome kernel: RSP: 0018:ffffc90028837a50 EFLAGS: 00010202 Jan 5 19:32:49 DanHome kernel: RAX: ffffffffffff8880 RBX: 783230252f7b1f70 RCX: 0000000000000000 Jan 5 19:32:49 DanHome kernel: RDX: 0000000000000000 RSI: ffffffff820dabd1 RDI: ffffffff820db0e6 Jan 5 19:32:49 DanHome kernel: RBP: ffff889fff4aed40 R08: ffff88819e414000 R09: ffffffff829583f0 Jan 5 19:32:49 DanHome kernel: R10: 00003fffffffffff R11: fefefefefefefeff R12: ffff88810867349c Jan 5 19:32:49 DanHome kernel: R13: ffff888102072000 R14: ffff888102072000 R15: 0000000000000002 Jan 5 19:32:49 DanHome kernel: FS: 0000150688b9b740(0000) GS:ffff889fff480000(0000) knlGS:0000000000000000 Jan 5 19:32:49 DanHome kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Jan 5 19:32:49 DanHome kernel: CR2: 0000150687fd8000 CR3: 00000001a6ee4000 CR4: 0000000000750ee0 Jan 5 19:32:49 DanHome kernel: PKRU: 55555554 Jan 5 19:32:49 DanHome kernel: Call Trace: Jan 5 19:32:49 DanHome kernel: <TASK> Jan 5 19:32:49 DanHome kernel: ? __die_body+0x1a/0x5c Jan 5 19:32:49 DanHome kernel: ? die_addr+0x38/0x51 Jan 5 19:32:49 DanHome kernel: ? exc_general_protection+0x30f/0x345 Jan 5 19:32:49 DanHome kernel: ? asm_exc_general_protection+0x22/0x30 Jan 5 19:32:49 DanHome kernel: ? osq_lock+0x59/0xdb Jan 5 19:32:49 DanHome kernel: __mutex_lock.constprop.0+0x74/0x2eb Jan 5 19:32:49 DanHome kernel: ? _dev_info+0x6c/0x87 Jan 5 19:32:49 DanHome kernel: device_del+0x37/0x31d Jan 5 19:32:49 DanHome kernel: ? i915_ggtt_probe_hw+0x6c4/0x6ef [i915] Jan 5 19:32:49 DanHome kernel: platform_device_del+0x21/0x70 Jan 5 19:32:49 DanHome kernel: platform_device_unregister+0xf/0x19 Jan 5 19:32:49 DanHome kernel: sysfb_disable+0x2b/0x54 Jan 5 19:32:49 DanHome kernel: aperture_remove_conflicting_pci_devices+0x1e/0x82 Jan 5 19:32:49 DanHome kernel: i915_driver_probe+0x6b3/0xb35 [i915] Jan 5 19:32:49 DanHome kernel: ? slab_free_freelist_hook.constprop.0+0x3b/0xaf Jan 5 19:32:49 DanHome kernel: local_pci_probe+0x3d/0x81 Jan 5 19:32:49 DanHome kernel: pci_device_probe+0x18f/0x1e3 Jan 5 19:32:49 DanHome kernel: ? sysfs_do_create_link_sd+0x71/0xb7 Jan 5 19:32:49 DanHome kernel: really_probe+0x115/0x282 Jan 5 19:32:49 DanHome kernel: __driver_probe_device+0xc0/0xf2 Jan 5 19:32:49 DanHome kernel: driver_probe_device+0x1f/0x77 Jan 5 19:32:49 DanHome kernel: ? __device_attach_driver+0x97/0x97 Jan 5 19:32:49 DanHome kernel: __driver_attach+0xd7/0xee Jan 5 19:32:49 DanHome kernel: ? __device_attach_driver+0x97/0x97 Jan 5 19:32:49 DanHome kernel: bus_for_each_dev+0x6e/0xa7 Jan 5 19:32:49 DanHome kernel: bus_add_driver+0xd8/0x1d0 Jan 5 19:32:49 DanHome kernel: driver_register+0x99/0xd7 Jan 5 19:32:49 DanHome kernel: i915_init+0x1d/0x80 [i915] Jan 5 19:32:49 DanHome kernel: ? 0xffffffffa1431000 Jan 5 19:32:49 DanHome kernel: do_one_initcall+0x82/0x19f Jan 5 19:32:49 DanHome kernel: ? kmalloc_trace+0x43/0x52 Jan 5 19:32:49 DanHome kernel: do_init_module+0x4b/0x1d4 Jan 5 19:32:49 DanHome kernel: __do_sys_init_module+0xb6/0xf9 Jan 5 19:32:49 DanHome kernel: do_syscall_64+0x65/0x7b Jan 5 19:32:49 DanHome kernel: entry_SYSCALL_64_after_hwframe+0x6e/0xd8 Jan 5 19:32:49 DanHome kernel: RIP: 0033:0x150688cbadfa Jan 5 19:32:49 DanHome kernel: Code: 48 8b 0d 21 20 0d 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 49 89 ca b8 af 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d ee 1f 0d 00 f7 d8 64 89 01 48 Jan 5 19:32:49 DanHome kernel: RSP: 002b:00007ffc0b17f458 EFLAGS: 00000246 ORIG_RAX: 00000000000000af Jan 5 19:32:49 DanHome kernel: RAX: ffffffffffffffda RBX: 00000000004293b0 RCX: 0000150688cbadfa Jan 5 19:32:49 DanHome kernel: RDX: 000000000042f640 RSI: 00000000005244b8 RDI: 0000150687ab4010 Jan 5 19:32:49 DanHome kernel: RBP: 000000000042f640 R08: 0000000000000007 R09: 000000000042fa30 Jan 5 19:32:49 DanHome kernel: R10: 0000000000000005 R11: 0000000000000246 R12: 0000150687ab4010 Jan 5 19:32:49 DanHome kernel: R13: 0000000000000016 R14: 00000000004294e0 R15: 000000000042f640 Jan 5 19:32:49 DanHome kernel: </TASK> Jan 5 19:32:49 DanHome kernel: Modules linked in: i915(O+) drm_buddy drm_display_helper intel_gtt vhost_net vhost tap kvm_intel kvm xt_CHECKSUM ipt_REJECT nf_reject_ipv4 ip6table_mangle iptable_mangle vhost_iotlb wireguard curve25519_x86_64 libcurve25519_generic libchacha20poly1305 chacha_x86_64 poly1305_x86_64 ip6_udp_tunnel udp_tunnel libchacha macvlan nft_compat xt_nat veth xt_conntrack nf_conntrack_netlink xfrm_user xfrm_algo xt_addrtype br_netfilter xt_MASQUERADE xt_tcpudp xt_mark xfs tun nf_tables nfnetlink ip6table_nat iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nfsd auth_rpcgss oid_registry lockd grace sunrpc md_mod tcp_diag inet_diag ipmi_devintf nct6775 nct6775_core hwmon_vid ip6table_filter ip6_tables iptable_filter ip_tables x_tables efivarfs 8021q garp mrp bridge stp llc zfs(PO) intel_rapl_msr intel_rapl_common iosf_mbi x86_pkg_temp_thermal intel_powerclamp coretemp zunicode(PO) zzstd(O) zlua(O) zavl(PO) ast crct10dif_pclmul icp(PO) drm_vram_helper crc32_pclmul crc32c_intel Jan 5 19:32:49 DanHome kernel: i2c_algo_bit ghash_clmulni_intel drm_ttm_helper sha512_ssse3 ttm sha256_ssse3 sha1_ssse3 drm_kms_helper aesni_intel crypto_simd cryptd drm zcommon(PO) mei_pxp znvpair(PO) mei_hdcp rapl agpgart ipmi_ssif syscopyarea intel_cstate spl(O) wmi_bmof i2c_i801 tpm_crb sr_mod sysfillrect mei_me cdc_ether i2c_smbus tpm_tis sysimgblt nvme ahci intel_uncore acpi_ipmi input_leds i2c_core fb_sys_fops usbnet video tpm_tis_core igc atlantic mei libahci nvme_core cdrom joydev led_class mii vmd thermal wmi fan ipmi_si tpm backlight acpi_pad intel_pmc_core acpi_tad button unix [last unloaded: kvm] Jan 5 19:32:49 DanHome kernel: ---[ end trace 0000000000000000 ]--- Jan 5 19:32:49 DanHome kernel: RIP: 0010:osq_lock+0x59/0xdb Jan 5 19:32:49 DanHome kernel: Code: dd 89 55 10 48 89 4d 00 89 45 14 41 87 04 24 85 c0 75 07 b0 01 e9 89 00 00 00 ff c8 48 98 48 03 1c c5 60 cb 16 82 48 89 5d 08 <48> 89 2b 65 48 8b 14 25 80 cb 01 00 8b 45 10 85 c0 75 d6 48 8b 02 Jan 5 19:32:49 DanHome kernel: RSP: 0018:ffffc90028837a50 EFLAGS: 00010202 Jan 5 19:32:49 DanHome kernel: RAX: ffffffffffff8880 RBX: 783230252f7b1f70 RCX: 0000000000000000 Jan 5 19:32:49 DanHome kernel: RDX: 0000000000000000 RSI: ffffffff820dabd1 RDI: ffffffff820db0e6 Jan 5 19:32:49 DanHome kernel: RBP: ffff889fff4aed40 R08: ffff88819e414000 R09: ffffffff829583f0 Jan 5 19:32:49 DanHome kernel: R10: 00003fffffffffff R11: fefefefefefefeff R12: ffff88810867349c Jan 5 19:32:49 DanHome kernel: R13: ffff888102072000 R14: ffff888102072000 R15: 0000000000000002 Jan 5 19:32:49 DanHome kernel: FS: 0000150688b9b740(0000) GS:ffff889fff480000(0000) knlGS:0000000000000000 Jan 5 19:32:49 DanHome kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Jan 5 19:32:49 DanHome kernel: CR2: 0000150687fd8000 CR3: 00000001a6ee4000 CR4: 0000000000750ee0 Jan 5 19:32:49 DanHome kernel: PKRU: 55555554 Jan 5 19:32:49 DanHome kernel: note: modprobe[19823] exited with preempt_count 1
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.