Comment 2 for bug 1958416
Revision history for this message
| Thadeu Lima de Souza Cascardo (cascardo) wrote | #2 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
This looks like to be caused by a full swiotlb. NVME will use DMA_ATTR_NO_WARN, which means there won't be any message about a full swiotlb. On 5.15, report_addr (in fact, its equivalent dev_WARN_ONCE) is not called in the case of swiotlb failure.
Also, comparing 5.4 and 5.15 on that instance, one is allocatiing 64MiB and the other, 1024MiB, which might explain why swiotlb gets full on 5.4.