Unable to turn on user SVA feature when intel_iommu=on,sm_on #46
Comments
|
Hi, I have the same problem. Have you solved it? |
|
@fyu1 @davejiang looks like this is caused by iommu not getting enabled. Is there any BIOS or other configuration that needs to be changed from default? Following is the cpu and kernel. |
|
PRI is not enabled and thus SVA cannot be enabled: Could you remove "iommu=pt" in the kernel option? |
|
Did somebody solve this issue? I am just using The IAA User Guide specifies that DSA/IAX option should be enabled under IOAT in the BIOS. As far as I can tell that is related to the I/O acceleration technology DMA engine, so perhaps this is relevant (?). As I am using a Dell motherboard/BIOS however, there does not seem to be an equivalent to this option. |
|
@Jonas-Heinrich can you give more details of the CPU/Platform, what you are trying to do and what errors are you getting? @fyu1 do you know what is going on? |
|
I have the same problem as @Jonas-Heinrich . |
|
@ramesh-thomas @fyu1 I sent you an email from my TU Munich (TUM) address with more details, there's some parts that I cannot share here. I got it working by setting "EDKII Menu -> Socket Configuration -> IIO Configuration -> Opt-Out Illegal MSI Mitigation: Enable" in the BIOS of another machine. As I had to find out, this option is not available on e.g. Dell motherboards (to the best of my knowledge). |
|
@eiclpy @Jonas-Heinrich please work with @fyu1 to get this issue resolved and update this issue with your findings. Thanks. |
|
Hi,I have the same problem.I ran the command as the dsa user guide,but something is not right.Here is my information.Thanks!@ramesh-thomas @fyu1 CPU:Intel(R) Xeon(R) Platinum 8475BL $ accel-config -v
4.1.3.git71676025
$ cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-6.1.27+ root=UUID=424deffb-478e-4611-834c-609e9ba58e75 ro vga=792 console=tty0 console=ttyS0,115200n8 net.ifnames=0 noibrs crashkernel=0M-1G:0M,1G-4G:192M,4G-128G:384M,128G-:512M nvme_core.io_timeout=4294967295 nvme_core.admin_timeout=4294967295 intel_iommu=on,sm_on
$ sudo dmesg | grep idxd
[ 5.275363] idxd 0000:00:06.0: Unable to turn on user SVA feature.
[ 5.279597] idxd 0000:00:06.0: Failed to initialize perfmon. No PMU support: -19
[ 5.288915] idxd 0000:00:06.0: Intel(R) Accelerator Device (v0)
[ 5.289087] idxd 0000:00:07.0: Unable to turn on user SVA feature.
[ 5.290949] idxd 0000:00:07.0: Failed to initialize perfmon. No PMU support: -19
[ 5.292351] idxd 0000:00:07.0: Intel(R) Accelerator Device (v0)
$ sudo dmesg | grep iommu
[ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-6.1.27+ root=UUID=424deffb-478e-4611-834c-609e9ba58e75 ro vga=792 console=tty0 console=ttyS0,115200n8 net.ifnames=0 noibrs crashkernel=0M-1G:0M,1G-4G:192M,4G-128G:384M,128G-:512M nvme_core.io_timeout=4294967295 nvme_core.admin_timeout=4294967295 intel_iommu=on,sm_on
[ 0.022942] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-6.1.27+ root=UUID=424deffb-478e-4611-834c-609e9ba58e75 ro vga=792 console=tty0 console=ttyS0,115200n8 net.ifnames=0 noibrs crashkernel=0M-1G:0M,1G-4G:192M,4G-128G:384M,128G-:512M nvme_core.io_timeout=4294967295 nvme_core.admin_timeout=4294967295 intel_iommu=on,sm_on
[ 0.629394] iommu: Default domain type: Passthrough
$ sudo lspci -vvv -s 00:06.0
00:06.0 System peripheral: Intel Corporation Device 0b25
Subsystem: Intel Corporation Device 2010
Physical Slot: 6
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Region 0: Memory at fa248000 (64-bit, prefetchable) [size=8K]
Region 2: Memory at fa24a000 (64-bit, prefetchable) [size=8K]
Expansion ROM at fea12000 [disabled] [size=2K]
Capabilities: [40] MSI-X: Enable+ Count=2 Masked-
Vector table: BAR=0 offset=00000600
PBA: BAR=0 offset=00000000
Capabilities: [50] Express (v2) Root Complex Integrated Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0
ExtTag- RBE- FLReset-
DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- TransPend-
DevCap2: Completion Timeout: Not Supported, TimeoutDis+ NROPrPrP- LTR-
10BitTagComp- 10BitTagReq- OBFF Not Supported, ExtFmt+ EETLPPrefix+, MaxEETLPPrefixes 1
EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit-
FRS-
AtomicOpsCap: 32bit- 64bit- 128bitCAS-
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- LTR- OBFF Disabled,
AtomicOpsCtl: ReqEn-
Kernel driver in use: idxd
Kernel modules: idxd
(I lost many capabilities compared with others)
$ cat /sys/bus/dsa/devices/dsa0/pasid_enabled
0
$accel-config load-config -c contrib/configs/app_profile.conf -e
dsa0 is active. Skipping...
(why i can't config my dsa device) |
|
"dsa0 is active. Skipping..." The device was already enabled. You can give the -f option to disable enabled devices. |
|
I get an error instead of a warning when I configure the device. @fyu1 @ramesh-thomas |
|
Thank you!I have disabled the dsa0, and run the command again.But I get a new error message.@ramesh-thomas(I am root) $ accel-config load-config -c contrib/configs/app_profile.conf -e
libaccfg: accfg_device_set_read_buffer_limit: dsa0: write failed: Operation not permitted
device set read_buffer_limit value failed
Parse json and set device fail: -1
$ ls /sys/bus/dsa/devices/dsa0
cdev_major engine0.1 group0.0 max_tokens op_cap subsystem
clients engine0.2 max_batch_size max_transfer_size pasid_enabled token_limit
cmd_status engine0.3 max_engines max_work_queues power uevent
configurable errors max_groups max_work_queues_size read_buffer_limit version
engine0.0 gen_cap max_read_buffers numa_node state wq0.0 |
|
I had the exact same problem as you, did you solve it? @eiclpy |
|
Does anyone have any update on fixing this. I also have the very same issue of PRICtl being disabled and it shows "Unable to turn on SVA feature" when I boot up. |
|
For anybody who has seen 'SVM disabled, incompatible paging mode' in the kernel message, try disable 5-level pagetable and reboot. (add 'no5lvl' to your kernel command line) |
I rebooted the system with "intel_iommu=on,sm_on" but the "Unable to turn on user SVA function" is still there.
CPU: Intel(R) Xeon(R) Gold 6448H
System: Ubuntu 22.04
Kernel: 6.2.0-34-generic
The text was updated successfully, but these errors were encountered: