Odd error after OS update to 6.10/6.10.1

[Grissom]

Hi,

the system logs show below recurring error since the last OS update:

 

May 22 13:09:00 jhsrv kernel: WARNING: CPU: 6 PID: 101 at drivers/iommu/intel/iommu.c:2408 __domain_mapping+0x2e5/0x390
May 22 13:09:00 jhsrv kernel: Modules linked in: xt_CHECKSUM ipt_REJECT nf_reject_ipv4 ip6table_mangle ip6table_nat iptable_mangle vhost_net tun vhost vhost_iotlb tap xt_nat xt_tcpudp veth xt_conntrack nf_conntrack_netlink nfnetlink xt_addrtype br_netfilter xfs dm_crypt dm_mod dax md_mod iptable_nat xt_MASQUERADE nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 wireguard curve25519_x86_64 libcurve25519_generic libchacha20poly1305 chacha_x86_64 poly1305_x86_64 ip6_udp_tunnel udp_tunnel libblake2s blake2s_x86_64 libblake2s_generic libchacha ip6table_filter ip6_tables iptable_filter ip_tables x_tables bonding tg3 x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm sr_mod cdrom ipmi_ssif i2c_core crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel crypto_simd cryptd rapl intel_cstate intel_uncore nvme acpi_ipmi ahci libahci nvme_core ipmi_si thermal acpi_power_meter button [last unloaded: tg3]
May 22 13:09:00 jhsrv kernel: CPU: 6 PID: 101 Comm: kworker/u128:2 Tainted: G        W I       5.15.40-Unraid #1
May 22 13:09:00 jhsrv kernel: Hardware name: HP ProLiant MicroServer Gen8, BIOS J06 04/04/2019
May 22 13:09:00 jhsrv kernel: Workqueue: loop2 loop_rootcg_workfn
May 22 13:09:00 jhsrv kernel: RIP: 0010:__domain_mapping+0x2e5/0x390
May 22 13:09:00 jhsrv kernel: Code: 2b 48 8b 4c 24 08 48 89 c2 4c 89 e6 48 c7 c7 29 b1 11 82 e8 f2 86 2d 00 8b 05 34 9b df 00 85 c0 74 08 ff c8 89 05 28 9b df 00 <0f> 0b 8b 74 24 38 b8 34 00 00 00 8d 0c f6 83 e9 09 39 c1 0f 4f c8
May 22 13:09:00 jhsrv kernel: RSP: 0018:ffffc90000563760 EFLAGS: 00010246
May 22 13:09:00 jhsrv kernel: RAX: 0000000000000000 RBX: ffff888106710ca8 RCX: 0000000000000003
May 22 13:09:00 jhsrv kernel: RDX: 0000000000000000 RSI: ffffc900005635f0 RDI: 00000000066ccf78
May 22 13:09:00 jhsrv kernel: RBP: ffff888101f49600 R08: ffff888447f3c430 R09: 0000000000000000
May 22 13:09:00 jhsrv kernel: R10: 00000000000000cf R11: ffff888447fe40e6 R12: 00000000000af795
May 22 13:09:00 jhsrv kernel: R13: ffff888106710c90 R14: 0000000000001000 R15: 00000000af792000
May 22 13:09:00 jhsrv kernel: FS:  0000000000000000(0000) GS:ffff888436f80000(0000) knlGS:0000000000000000
May 22 13:09:00 jhsrv kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
May 22 13:09:00 jhsrv kernel: CR2: 000000c0022ff010 CR3: 000000000220a002 CR4: 00000000001706e0
May 22 13:09:00 jhsrv kernel: Call Trace:
May 22 13:09:00 jhsrv kernel: <TASK>
May 22 13:09:00 jhsrv kernel: intel_iommu_map_pages+0xf3/0x102
May 22 13:09:00 jhsrv kernel: __iommu_map+0x138/0x211
May 22 13:09:00 jhsrv kernel: __iommu_map_sg+0x8c/0x110
May 22 13:09:00 jhsrv kernel: iommu_dma_map_sg+0x21e/0x3bc
May 22 13:09:00 jhsrv kernel: __dma_map_sg_attrs+0x63/0x95
May 22 13:09:00 jhsrv kernel: dma_map_sg_attrs+0xa/0x12
May 22 13:09:00 jhsrv kernel: nvme_queue_rq+0x2d7/0x939 [nvme]
May 22 13:09:00 jhsrv kernel: ? btrfs_bio_counter_sub+0x1e/0x4c
May 22 13:09:00 jhsrv kernel: ? btrfs_map_bio+0x2f9/0x31f
May 22 13:09:00 jhsrv kernel: __blk_mq_try_issue_directly+0xf3/0x180
May 22 13:09:00 jhsrv kernel: ? btrfs_submit_direct+0x1b0/0x42e
May 22 13:09:00 jhsrv kernel: blk_mq_request_issue_directly+0x4c/0x7c
May 22 13:09:00 jhsrv kernel: blk_mq_try_issue_list_directly+0x41/0xba
May 22 13:09:00 jhsrv kernel: blk_mq_sched_insert_requests+0x8b/0xd9
May 22 13:09:00 jhsrv kernel: blk_mq_flush_plug_list+0xfb/0x12c
May 22 13:09:00 jhsrv kernel: blk_finish_plug+0x1f/0x2c
May 22 13:09:00 jhsrv kernel: __iomap_dio_rw+0x4cb/0x667
May 22 13:09:00 jhsrv kernel: iomap_dio_rw+0xa/0x25
May 22 13:09:00 jhsrv kernel: btrfs_file_write_iter+0x1cf/0x360
May 22 13:09:00 jhsrv kernel: lo_rw_aio.isra.0+0x1e7/0x234
May 22 13:09:00 jhsrv kernel: loop_process_work+0x58e/0x7f4
May 22 13:09:00 jhsrv kernel: ? __raw_spin_unlock+0x5/0x6
May 22 13:09:00 jhsrv kernel: ? finish_task_switch.isra.0+0x12f/0x207
May 22 13:09:00 jhsrv kernel: process_one_work+0x198/0x27a
May 22 13:09:00 jhsrv kernel: worker_thread+0x19c/0x240
May 22 13:09:00 jhsrv kernel: ? rescuer_thread+0x28b/0x28b
May 22 13:09:00 jhsrv kernel: kthread+0xde/0xe3
May 22 13:09:00 jhsrv kernel: ? set_kthread_struct+0x32/0x32
May 22 13:09:00 jhsrv kernel: ret_from_fork+0x22/0x30
May 22 13:09:00 jhsrv kernel: </TASK>
May 22 13:09:00 jhsrv kernel: ---[ end trace 29cb12a46cd17249 ]---
May 22 13:09:00 jhsrv kernel: DMAR: ERROR: DMA PTE for vPFN 0xaf796 already set (to af796003 not 1f69a8801)
May 22 13:09:00 jhsrv kernel: ------------[ cut here ]------------

 

Any idea?

 

Grissom

[JorgeB]

Disable VT-d in the BIOS, that error would likely already been there since updating to v6.10, and it can cause other issues, more info below:

 

https://forums.unraid.net/topic/123620-unraid-os-version-6100-available/?do=findComment&comment=1128822

 

[Grissom]

But AFAIK this is needed for VMs and my processor should support it...Intel® Xeon® CPU E3-1265L V2

[JorgeB]

CPU is not the problem, it's a NIC problem when VT-d is enable, you can still run VMs with VT-d disabled, just can't pass-through any hardware, and like it mentions in the linked thread there's a risk of filesystem corruption if you continue to run the server like that, if you really need VT-d you should go back to v6.9.2 for now.

[Grissom]

OK...that worked. Thanks a bunch!

 

It seems that xauth can't be found. When I try to start DoubleCommander, it can't load .Xauthority

 

Failed to open authorization file ".Xauthority": No such file or directory

 

Furthermore it can't find xauth. Can I reinstall that somehow?

[JorgeB]

11 hours ago, Grissom said:

It seems that xauth can't be found. When I try to start DoubleCommander, it can't load .Xauthority

 

Failed to open authorization file ".Xauthority": No such file or directory

 

Sorry don't known what any of that is, if it's a docker best bet is to ask for help in the existing docker support thread, if there is one:

 

 

 

[Squid]

@JorgeB Why is your icon for Update not correct?

[JorgeB]

9 minutes ago, Squid said:

 Why is your icon for Update not correct?

It's an old screenshot I have saved for this.

[JorgeB]

Updated for next time

 

[Squid]

lol.  Wasn't a big deal, but the pic struck me as being off a bit, so looked at my own system.  Not the first 5 minutes of my life that I won't get back (nor will it be the last)