Kernel 6.19.5 boot regression with IOMMU enabled [urgent]

Xariann · Yesterday 12:57:28

I am reporting a boot regression in kernel 6.19.5 currently in [testing]. I cannot access the Arch GitLab to file an issue there.

ISSUE:
System fails to boot with kernel 6.19.5 (both linux and linux-zen) unless IOMMU is disabled via kernel parameter. Kernel 6.18.13 boots without issue. This is a transcription of the error:

[ 2.503040] AMD-Vi: Event logged [IO_PAGE_FAULT device=0000:11:00.0 domain=0x
0000 address=0x109a0440 flags=0x0070]
[ 2.504562] AMD-Vi: Event logged [IO_PAGE_FAULT device=0000:11:00.0 domain=0x
0000 address=0x109800440 flags=0x0070]
[ 2.507118] AMD-Vi: Event logged [IO_PAGE_FAULT device=0000:11:00.0 domain=0x
0000 address=0x1090c0440 flags=0x0070]
[ 2.553161] AMD-Vi: Event logged [IO_PAGE_FAULT device=0000:10:00.0 domain=0x
0000 address=0x102f05000 flags=0x0050]
[ 2.557813] AMD-Vi: Event logged [IO_PAGE_FAULT device=0000:13:00.3 domain=0x
0000 address=0x102f76000 flags=0x0050]
[ 2.559277] AMD-Vi: Event logged [IO_PAGE_FAULT device=0000:13:00.4 domain=0x
0000 address=0x102f00000 flags=0x0050]
[ 2.561592] AMD-Vi: Event logged [IO_PAGE_FAULT device=0000:14:00.0 domain=0x
0000 address=0x102fa7000 flags=0x0050]
[ 2.654533] AMD-Vi: Event logged [IO_PAGE_FAULT device=0000:10:00.0 domain=0x0000 address=0x102f32000 flags=0x0050]
[ 2.802265] AMD-Vi: Event logged [IO_PAGE_FAULT device=0000:11:00.0 domain=0x0000 address=0x109800000 flags=0x0050]
[ 3.159996] xhci_hcd 0000:13:00.3: PM: suspend_common(): xhci_pci_suspend returns -110
[ 3.160118] xhci_hcd 0000:13:00.3: can't suspend (hcd_pci_runtime_suspend returned -110)
[ 17.785815] xhci_hcd 0000:10:00.0: Abort failed to stop command ring: -110
[ 17.785817] xhci_hcd 0000:10:00.0: xHCI host controller not responding, assume dead
[ 17.785823] xhci_hcd 0000:10:00.0: HC died; cleaning up
[ 17.785923] xhci_hcd 0000:10:00.0: Error while assigning device slot ID: Command Aborted
[ 17.785949] ata1: softreset failed (1st FIS failed)
[ 17.786091] xhci_hcd 0000:10:00.0: Max number of devices this xHCI host supports is 127.
[ 17.786081] usb usb1-port4: couldn't allocate usb_device
[ 17.793553] AMD-Vi: Event logged [IO_PAGE_FAULT device=0000:11:00.0 domain=0x0000 address=0x109800440 flags=0x0070]
[ 18.090752] AMD-Vi: Event logged [IO_PAGE_FAULT device=0000:11:00.0 domain=0x0000 address=0x109800000 flags=0x0050]

AFFECTED HARDWARE:
Motherboard: B650M DS3H
CPU: Ryzen 9800x3D
GPU: AMD 9070

REGRESSION TIMELINE:
- 6.18.13: works fine
- 6.19-rc through 6.19.3: regression present, system unbootable
- 6.19.4: upstream appears to include fix (patch already present when attempting manual application)
- 6.19.5 in Arch [testing]: regression still present

FIX AVAILABLE:
https://lore.kernel.org/lkml/2026022708 … theas.dev/ resolves this issue. CachyOS kernel 6.19.5 includes this patch and boots successfully.

CONCERN:
The current number of signoffs in [testing] may push this to [core] with the regression intact. This affected multiple users as documented in CachyOS forums prior to kernel 6.19.5.

REQUEST:
Please apply the referenced patch before promoting 6.19.5 to [core] to prevent widespread boot failures.

I am an Arch tester currently awaiting GitLab access to file this formally. Once again apologies if this is not the correct channel.

Xariann

cryptearth · Yesterday 14:05:13

hint: avoid wording as "urgent" or similar - in the past these were heavily abused and hence often cause topics with such names to be ignored
if something is actually important then this forum can handle please use good old mailing lists: https://lists.archlinux.org/mailman3/lists/
also: please use bbcode code tags for console output

gromit · Yesterday 14:57:40

Please file a bug here: https://gitlab.archlinux.org/archlinux/ … x/-/issues

seth · Yesterday 15:02:24

6.19.4: upstream appears to include fix (patch already present when attempting manual application)

https://github.com/gregkh/linux/commits … mu/iommu.c
https://github.com/gregkh/linux/commits … mu/iommu.c
https://github.com/torvalds/linux/commi … mu/iommu.c

Patch is from 27 Feb 2026 and afaict hasn't been picked up anywhere yet?

I am an Arch tester currently awaiting GitLab access to file this formally.

Ping back if you don't have an account tomorrow 7:00 UTC or after

@gromit, according to the OP they can't (unless you added their account)

Last edited by seth (Yesterday 15:03:17)

Xariann · Yesterday 17:27:23

seth wrote:

6.19.4: upstream appears to include fix (patch already present when attempting manual application)
https://github.com/gregkh/linux/commits … mu/iommu.c
https://github.com/gregkh/linux/commits … mu/iommu.c
https://github.com/torvalds/linux/commi … mu/iommu.c
Patch is from 27 Feb 2026 and afaict hasn't been picked up anywhere yet?
I am an Arch tester currently awaiting GitLab access to file this formally.
Ping back if you don't have an account tomorrow 7:00 UTC or after
@gromit, according to the OP they can't (unless you added their account)

Indeed I cannot, it was the first thing I tried. When trying to sign up I got a message to contact a support email address which I have done.

I was under the impression that the patch existed in 6.19.4 because when I tried to apply the patch to it when compiling from source it looked like the patch was there, but new to this so probably easily confused.

@cryptearth, noted. I have indeed tried to use the mailing list and got bounced back. I need to set up a mailing client that can deal with them. I thought it would be urgent given the fact that this causes boot failures, it got marked as such by another distro (admittedly with different procedures) and it has been signed off by several testers and might get pushed to core imminently, and it is about the kernel. Obviously I was misguided. Given that I attempted other channels and was not able to access them I resorted to the forums.

If you would be willing to also receive some pointers, an acknowledgement of what I was trying to achieve in addition to everything I did wrong would have been nice to see. This wasn't me trying to get my favourite app to work on Arch Linux.

Last edited by Xariann (Yesterday 17:29:06)

cryptearth · Yesterday 18:49:15

Xariann wrote:

@cryptearth, noted. I have indeed tried to use the mailing list and got bounced back. I need to set up a mailing client that can deal with them. I thought it would be urgent given the fact that this causes boot failures, it got marked as such by another distro (admittedly with different procedures) and it has been signed off by several testers and might get pushed to core imminently, and it is about the kernel. Obviously I was misguided. Given that I attempted other channels and was not able to access them I resorted to the forums.

well, yes, it is quite important - and thanks for bringing it up - but usually additions like "urgent", "important", "required fast" or similar are often abused by inexperienced users trying to get attention - usually for quite unimportant things OPs not even bothered to give one second the ask google about - and hence are often dismissed as spam
lucky for you this topic has at least are quite descriptive title so those who have to take a look at it did so anyway no matter the urgent "tag"
it's just a friendly hint: it's better to chose a good topic title rather than "spam" with stuff like "urgent" or "important" - a well chosen topic title will draw required attention way better - and enables users to get whether "do I have to bother to look into the topic to figure out I don't care?" or if it's something they can help with

as for mailing lists: usually you have to subscribe to a list upfront before you can post to it - so a bounce sounds like you tried to send to it without subscribing to it - this is normal and expected behaviour to prevent spam

seth · Yesterday 20:35:59

because when I tried to apply the patch to it

What source exactly and do you still have the output you ran into?

When trying to sign up I got a message to contact a support email address which I have done.

'key - idk whether gromit has picked up on this but otherwise

seth wrote:

Ping back if you don't have an account tomorrow 7:00 UTC or after

Arch Linux

#1 Yesterday 12:57:28

Kernel 6.19.5 boot regression with IOMMU enabled [urgent]

#2 Yesterday 14:05:13

Re: Kernel 6.19.5 boot regression with IOMMU enabled [urgent]

#3 Yesterday 14:57:40

Re: Kernel 6.19.5 boot regression with IOMMU enabled [urgent]

#4 Yesterday 15:02:24

Re: Kernel 6.19.5 boot regression with IOMMU enabled [urgent]

#5 Yesterday 17:27:23

Re: Kernel 6.19.5 boot regression with IOMMU enabled [urgent]

#6 Yesterday 18:49:15

Re: Kernel 6.19.5 boot regression with IOMMU enabled [urgent]

#7 Yesterday 20:35:59

Re: Kernel 6.19.5 boot regression with IOMMU enabled [urgent]

Board footer