On Wed, Mar 11, 2020 at 03:34:38PM +0000, Artem S. Tashkinov wrote:
On 3/11/20 3:24 PM, Christoph Hellwig wrote:
pdev->dma_mask = parent->dma_mask ? *parent->dma_mask : 0;
This patch makes no difference.
The kernel panics with the same call trace which starts with:
This looks really strange and not dma mask related, but there must be
some odd interactions somewhere.
Can you call gdb on the vmlinux file for the 5.5.8-200.fc31 kernel
in the jpg and then do
l *(kmem_cache_alloc_trace+0x7e)
l *(acpi_processor_add+0x3a)
and send the output?