search for: 491520

...ce 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] [<ffff0000083ad...

...ce 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] [<ffff0000083ad...

...> 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+0x194/0x1a0 > [...

...> 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+0x194/0x1a0 > [...

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 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 > >>> ... > >>> [...

...rk 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_pag...

...imits 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+0x194/0x1a0 [ 5.383226] [<ffff000008096bb8>...

...'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 > >>> ... > >>> [...

Hi, Does anyone have a simple UK Extensions.conf that uses SIP that I could have a look at? I'm trying to get a simple Asterisk system up and running and I can't get any calls incoming or outgoing and I don't know why. Would it be worth posting up my extensions.conf and sip.conf? Thanks Richard

...recv 32768 at 131072 data recv 32768 at 163840 data recv 32768 at 196608 data recv 32768 at 229376 data recv 32768 at 262144 data recv 32768 at 294912 data recv 32768 at 327680 data recv 32768 at 360448 data recv 32768 at 393216 data recv 32768 at 425984 data recv 32768 at 458752 data recv 32768 at 491520 data recv 32768 at 524288 data recv 32768 at 557056 data recv 32768 at 589824 data recv 32768 at 622592 data recv 32768 at 655360 data recv 32768 at 688128 data recv 32768 at 720896 data recv 32768 at 753664 data recv 32768 at 786432 data recv 32768 at 819200 data recv 32768 at 851968 data recv 327...

On 2018-08-22 11:32, John McCall wrote: > >> On Aug 22, 2018, at 4:38 AM, Bevin Hansson <bevin.hansson at ericsson.com> wrote: >> >> >> >> On 2018-08-22 05:56, John McCall via llvm-dev wrote: >>>> On Aug 21, 2018, at 6:20 PM, Leonard Chan <leonardchan at google.com> wrote: >>>> If we were to create a new type down the line, I

Hi, When do the sftp to remote server with file system full, sftp connection get "ID mismatch" and connection closed. Is it supposed to get the "sftp>" prompt back? I try with V3.7.1p2 and V3.8.1p1 and have the same result. Please help. rdsosl.sef_cdf-831# sftp -v edosuser at rdsosl Connecting to rdsosl... OpenSSH_3.8.1p1, OpenSSL 0.9.7d 17 Mar 2004 debug1: Reading

...recv 32768 at 131072 data recv 32768 at 163840 data recv 32768 at 196608 data recv 32768 at 229376 data recv 32768 at 262144 data recv 32768 at 294912 data recv 32768 at 327680 data recv 32768 at 360448 data recv 32768 at 393216 data recv 32768 at 425984 data recv 32768 at 458752 data recv 32768 at 491520 data recv 32768 at 524288 data recv 32768 at 557056 data recv 32768 at 589824 data recv 32768 at 622592 data recv 32768 at 655360 data recv 32768 at 688128 data recv 32768 at 720896 data recv 32768 at 753664 data recv 32768 at 786432 data recv 32768 at 819200 data recv 32768 at 851968 data recv 327...

...84, inode bitmap at 425985, inode table at 425986 32254 free blocks, 16384 free inodes, 0 used directories Group 14: block bitmap at 458752, inode bitmap at 458753, inode table at 458754 32254 free blocks, 16384 free inodes, 0 used directories Group 15: block bitmap at 491520, inode bitmap at 491521, inode table at 491522 32254 free blocks, 16384 free inodes, 0 used directories Group 16: block bitmap at 524288, inode bitmap at 524289, inode table at 524290 32254 free blocks, 16384 free inodes, 0 used directories Group 17: block bitmap at 55...

https://bugzilla.samba.org/show_bug.cgi?id=13317 Bug ID: 13317 Summary: rsync returns success when target filesystem is full Product: rsync Version: 3.1.2 Hardware: x64 OS: FreeBSD Status: NEW Severity: major Priority: P5 Component: core Assignee: wayned at samba.org