search for: 1c130000

...ngs. >>> >>> It used to work with 4.9, but since 9491ae4 ("mm: don't cap request size >>> based on read-ahead setting") unlocked read-ahead, we quickly run into >>> the limit of swiotlb and panic: >>> >>> [ 5.382359] virtio-mmio 1c130000.virtio_block: swiotlb buffer is full >>> (sz: 491520 bytes) >>> [ 5.382452] virtio-mmio 1c130000.virtio_block: DMA: Out of SW-IOMMU >>> space for 491520 bytes >>> [ 5.382531] Kernel panic - not syncing: DMA: Random memory could be >>> DMA written &...

...ngs. >>> >>> It used to work with 4.9, but since 9491ae4 ("mm: don't cap request size >>> based on read-ahead setting") unlocked read-ahead, we quickly run into >>> the limit of swiotlb and panic: >>> >>> [ 5.382359] virtio-mmio 1c130000.virtio_block: swiotlb buffer is full >>> (sz: 491520 bytes) >>> [ 5.382452] virtio-mmio 1c130000.virtio_block: DMA: Out of SW-IOMMU >>> space for 491520 bytes >>> [ 5.382531] Kernel panic - not syncing: DMA: Random memory could be >>> DMA written &...

...swiotlb, which > limits the number of mappings. > > It used to work with 4.9, but since 9491ae4 ("mm: don't cap request size > based on read-ahead setting") unlocked read-ahead, we quickly run into > the limit of swiotlb and panic: > > [ 5.382359] virtio-mmio 1c130000.virtio_block: swiotlb buffer is full > (sz: 491520 bytes) > [ 5.382452] virtio-mmio 1c130000.virtio_block: DMA: Out of SW-IOMMU > space for 491520 bytes > [ 5.382531] Kernel panic - not syncing: DMA: Random memory could be > DMA written > ... > [ 5.383148] [<ffff000...

...swiotlb, which > limits the number of mappings. > > It used to work with 4.9, but since 9491ae4 ("mm: don't cap request size > based on read-ahead setting") unlocked read-ahead, we quickly run into > the limit of swiotlb and panic: > > [ 5.382359] virtio-mmio 1c130000.virtio_block: swiotlb buffer is full > (sz: 491520 bytes) > [ 5.382452] virtio-mmio 1c130000.virtio_block: DMA: Out of SW-IOMMU > space for 491520 bytes > [ 5.382531] Kernel panic - not syncing: DMA: Random memory could be > DMA written > ... > [ 5.383148] [<ffff000...

Booting Linux on an ARM fastmodel containing an SMMU emulation results in an unexpected I/O page fault from the legacy virtio-blk PCI device: [ 1.211721] arm-smmu-v3 2b400000.smmu: event 0x10 received: [ 1.211800] arm-smmu-v3 2b400000.smmu: 0x00000000fffff010 [ 1.211880] arm-smmu-v3 2b400000.smmu: 0x0000020800000000 [ 1.211959] arm-smmu-v3 2b400000.smmu: 0x00000008fa081002 [

Booting Linux on an ARM fastmodel containing an SMMU emulation results in an unexpected I/O page fault from the legacy virtio-blk PCI device: [ 1.211721] arm-smmu-v3 2b400000.smmu: event 0x10 received: [ 1.211800] arm-smmu-v3 2b400000.smmu: 0x00000000fffff010 [ 1.211880] arm-smmu-v3 2b400000.smmu: 0x0000020800000000 [ 1.211959] arm-smmu-v3 2b400000.smmu: 0x00000008fa081002 [

...t;>> It used to work with 4.9, but since 9491ae4 ("mm: don't cap request size > >>> based on read-ahead setting") unlocked read-ahead, we quickly run into > >>> the limit of swiotlb and panic: > >>> > >>> [ 5.382359] virtio-mmio 1c130000.virtio_block: swiotlb buffer is full > >>> (sz: 491520 bytes) > >>> [ 5.382452] virtio-mmio 1c130000.virtio_block: DMA: Out of SW-IOMMU > >>> space for 491520 bytes > >>> [ 5.382531] Kernel panic - not syncing: DMA: Random memory could be > &...

...mits the number of mappings. >> >> It used to work with 4.9, but since 9491ae4 ("mm: don't cap request size >> based on read-ahead setting") unlocked read-ahead, we quickly run into >> the limit of swiotlb and panic: >> >> [ 5.382359] virtio-mmio 1c130000.virtio_block: swiotlb buffer is full >> (sz: 491520 bytes) >> [ 5.382452] virtio-mmio 1c130000.virtio_block: DMA: Out of SW-IOMMU >> space for 491520 bytes >> [ 5.382531] Kernel panic - not syncing: DMA: Random memory could be >> DMA written >> ... >>...

...the SMMU, the DMA ops fall back to swiotlb, which limits the number of mappings. It used to work with 4.9, but since 9491ae4 ("mm: don't cap request size based on read-ahead setting") unlocked read-ahead, we quickly run into the limit of swiotlb and panic: [ 5.382359] virtio-mmio 1c130000.virtio_block: swiotlb buffer is full (sz: 491520 bytes) [ 5.382452] virtio-mmio 1c130000.virtio_block: DMA: Out of SW-IOMMU space for 491520 bytes [ 5.382531] Kernel panic - not syncing: DMA: Random memory could be DMA written ... [ 5.383148] [<ffff0000083ad754>] swiotlb_map_page+0x1...

...t;>> It used to work with 4.9, but since 9491ae4 ("mm: don't cap request size > >>> based on read-ahead setting") unlocked read-ahead, we quickly run into > >>> the limit of swiotlb and panic: > >>> > >>> [ 5.382359] virtio-mmio 1c130000.virtio_block: swiotlb buffer is full > >>> (sz: 491520 bytes) > >>> [ 5.382452] virtio-mmio 1c130000.virtio_block: DMA: Out of SW-IOMMU > >>> space for 491520 bytes > >>> [ 5.382531] Kernel panic - not syncing: DMA: Random memory could be > &...