Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #60441 > unrolled thread

Bug#892517: linux: swiotlb coherent allocation failed

Back to article view | Back to linux.debian.kernel

Contents

  Bug#892517: linux: swiotlb coherent allocation failed Michael Gilbert <mgilbert@debian.org> - 2018-03-10 02:50 +0100
    Bug#892517: linux: swiotlb coherent allocation failed Salvatore Bonaccorso <carnil@debian.org> - 2018-03-20 11:30 +0100
      Bug#892517: linux: swiotlb coherent allocation failed Michael Gilbert <mgilbert@debian.org> - 2018-03-25 08:00 +0200
        Bug#892517: linux: swiotlb coherent allocation failed Salvatore Bonaccorso <carnil@debian.org> - 2018-04-05 17:00 +0200
    Processed: Re: Bug#892517: linux: swiotlb coherent allocation failed "Debian Bug Tracking System" <owner@bugs.debian.org> - 2018-03-20 11:30 +0100
    Bug#892517: marked as done (linux: swiotlb coherent allocation  failed) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2018-04-05 17:00 +0200
    Bug#892517: linux: swiotlb coherent allocation failed Adriano Vilela Barbosa <adriano.vilela@cefala.org> - 2018-05-27 00:50 +0200
      Bug#892517: linux: swiotlb coherent allocation failed Michael Gilbert <mgilbert@debian.org> - 2018-05-27 03:10 +0200
        Bug#892517: linux: swiotlb coherent allocation failed Salvatore Bonaccorso <carnil@debian.org> - 2018-05-27 11:30 +0200
    Processed: Re: Bug#892517: linux: swiotlb coherent allocation failed "Debian Bug Tracking System" <owner@bugs.debian.org> - 2018-05-27 03:10 +0200
    Processed: Re: Bug#892517: linux: swiotlb coherent allocation failed "Debian Bug Tracking System" <owner@bugs.debian.org> - 2018-05-27 11:30 +0200
    Bug#892517: linux: swiotlb coherent allocation failed nfb <notfreebeer@disroot.org> - 2018-05-28 01:50 +0200
    Bug#892517: Info received (Bug#892517: linux: swiotlb coherent allocation failed) nfb <notfreebeer@disroot.org> - 2018-06-05 20:40 +0200

#60441 — Bug#892517: linux: swiotlb coherent allocation failed

package: src:linux
version: 4.15.4-1
severity: minor
forwarded: https://lkml.org/lkml/2017/12/18/1259

This is a message that shows up a lot in dmesg starting with linux
4.15.  See LKML discussion and Ubuntu bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749202

Best wishes,
Mike

[toc] | [next] | [standalone]

#60511

Control: tags -1 + moreinfo

Hi Mike,

On Fri, Mar 09, 2018 at 08:43:07PM -0500, Michael Gilbert wrote:
> package: src:linux
> version: 4.15.4-1
> severity: minor
> forwarded: https://lkml.org/lkml/2017/12/18/1259
> 
> This is a message that shows up a lot in dmesg starting with linux
> 4.15.  See LKML discussion and Ubuntu bug:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749202

This should be fixed with the 4.15.11-1 upload to unstable.

https://git.kernel.org/linux/d0bc0c2a31c95002d37c3cc511ffdcab851b3256

Can you confirm that before we would proceed to mark it as fixed with
4.15.11-1?

Regards,
Salvatore

[toc] | [prev] | [next] | [standalone]

#60552

On Tue, Mar 20, 2018 at 6:15 AM, Salvatore Bonaccorso wrote:
> Can you confirm that before we would proceed to mark it as fixed with
> 4.15.11-1?

I have not seen it since updating, so I think it can be considered fixed.

Best wishes,
Mike

[toc] | [prev] | [next] | [standalone]

#60632

Source: linux
Source-Version: 4.15.11-1

Hi Mike,

On Sun, Mar 25, 2018 at 01:54:38AM -0400, Michael Gilbert wrote:
> On Tue, Mar 20, 2018 at 6:15 AM, Salvatore Bonaccorso wrote:
> > Can you confirm that before we would proceed to mark it as fixed with
> > 4.15.11-1?
> 
> I have not seen it since updating, so I think it can be considered fixed.

Thanks for confirming!

Regards,
Salvatore

[toc] | [prev] | [next] | [standalone]

#60512 — Processed: Re: Bug#892517: linux: swiotlb coherent allocation failed

Processing control commands:

> tags -1 + moreinfo
Bug #892517 [src:linux] linux: swiotlb coherent allocation failed
Added tag(s) moreinfo.

-- 
892517: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892517
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]

#60633 — Bug#892517: marked as done (linux: swiotlb coherent allocation failed)

[Multipart message — attachments visible in raw view] — view raw

Your message dated Thu, 5 Apr 2018 16:53:51 +0200
with message-id <20180405145351.mixvq4wuvvccdoi4@lorien.valinor.li>
and subject line Re: Bug#892517: linux: swiotlb coherent allocation failed
has caused the Debian Bug report #892517,
regarding linux: swiotlb coherent allocation failed
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
892517: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892517
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]

#61097

On Thu, 5 Apr 2018 16:53:51 +0200 Salvatore Bonaccorso
<carnil@debian.org> wrote:
> Source: linux
> Source-Version: 4.15.11-1
>
> Hi Mike,
>
> On Sun, Mar 25, 2018 at 01:54:38AM -0400, Michael Gilbert wrote:
> > On Tue, Mar 20, 2018 at 6:15 AM, Salvatore Bonaccorso wrote:
> > > Can you confirm that before we would proceed to mark it as fixed with
> > > 4.15.11-1?
> >
> > I have not seen it since updating, so I think it can be considered fixed.
>
> Thanks for confirming!
>
> Regards,
> Salvatore
>
>

Hi,

I'm getting lots of these messages on kernel 4.16.5-1. I'm running
Debian testing.

[104390.065326] radeon 0000:01:00.0: swiotlb buffer is full (sz: 2097152 bytes)
[104390.065330] radeon 0000:01:00.0: swiotlb: coherent allocation
failed, size=2097152
[104390.065334] CPU: 1 PID: 583 Comm: Xorg Tainted: G           O
4.16.0-1-amd64 #1 Debian 4.16.5-1
[104390.065335] Hardware name: Sony Corporation VGN-NW130D/VAIO, BIOS
R0170Y4 05/22/2009
[104390.065337] Call Trace:
[104390.065348]  dump_stack+0x5c/0x85
[104390.065352]  swiotlb_alloc_coherent+0x19b/0x1b0
[104390.065364]  ttm_dma_pool_get_pages+0x235/0x620 [ttm]
[104390.065371]  ttm_dma_populate+0x25e/0x350 [ttm]
[104390.065376]  ttm_tt_bind+0x2c/0x60 [ttm]
[104390.065382]  ttm_bo_handle_move_mem+0x577/0x5b0 [ttm]
[104390.065388]  ttm_bo_validate+0x120/0x130 [ttm]
[104390.065422]  ? drm_mode_parse_command_line_for_connector+0x37e/0x410 [drm]
[104390.065427]  ttm_bo_init_reserved+0x386/0x430 [ttm]
[104390.065432]  ttm_bo_init+0x6b/0xe0 [ttm]
[104390.065488]  ? radeon_update_memory_usage.isra.3+0x50/0x50 [radeon]
[104390.065508]  radeon_bo_create+0x180/0x230 [radeon]
[104390.065528]  ? radeon_update_memory_usage.isra.3+0x50/0x50 [radeon]
[104390.065549]  radeon_gem_object_create+0xa7/0x1d0 [radeon]
[104390.065554]  ? import_iovec+0x37/0xd0
[104390.065575]  ? radeon_gem_pwrite_ioctl+0x30/0x30 [radeon]
[104390.065596]  radeon_gem_create_ioctl+0x66/0x100 [radeon]
[104390.065618]  ? radeon_gem_pwrite_ioctl+0x30/0x30 [radeon]
[104390.065631]  drm_ioctl_kernel+0x5b/0xb0 [drm]
[104390.065645]  drm_ioctl+0x2cb/0x380 [drm]
[104390.065667]  ? radeon_gem_pwrite_ioctl+0x30/0x30 [radeon]
[104390.065671]  ? ep_scan_ready_list.constprop.16+0x242/0x250
[104390.065674]  ? timerqueue_add+0x52/0x80
[104390.065691]  radeon_drm_ioctl+0x49/0x80 [radeon]
[104390.065695]  do_vfs_ioctl+0xa4/0x630
[104390.065699]  ? __sys_recvmsg+0x7d/0x90
[104390.065701]  SyS_ioctl+0x74/0x80
[104390.065705]  do_syscall_64+0x6c/0x130
[104390.065708]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2
[104390.065711] RIP: 0033:0x7f0c9b843f07
[104390.065712] RSP: 002b:00007fffd5d43ea8 EFLAGS: 00000246 ORIG_RAX:
0000000000000010
[104390.065715] RAX: ffffffffffffffda RBX: 0000555f44e1a6c0 RCX:
00007f0c9b843f07
[104390.065716] RDX: 00007fffd5d43f00 RSI: 00000000c020645d RDI:
0000000000000018
[104390.065718] RBP: 00007fffd5d43f00 R08: 0000000000000002 R09:
0000000000000000
[104390.065719] R10: 0000000000000005 R11: 0000000000000246 R12:
00000000c020645d
[104390.065720] R13: 0000000000000018 R14: 000000000037a000 R15:
0000000000000000

Adriano

[toc] | [prev] | [next] | [standalone]

#61100

control: found -1 4.16.5-1
control: reopen -1

This is back for me as well.

Best wishes,
Mike

[toc] | [prev] | [next] | [standalone]

#61103

Control: tags -1 + moreinfo

Hi,

On Sat, May 26, 2018 at 09:00:34PM -0400, Michael Gilbert wrote:
> control: found -1 4.16.5-1
> control: reopen -1
> 
> This is back for me as well.

There were various commits which went in up to v4.16.9 upstream which
should adress the issues. There is a 4.16.12-1 upload pending for sid,
can you check if this will fix your issue?

Regards,
Salvatore

[toc] | [prev] | [next] | [standalone]

#61099 — Processed: Re: Bug#892517: linux: swiotlb coherent allocation failed

Processing control commands:

> found -1 4.16.5-1
Bug #892517 {Done: Salvatore Bonaccorso <carnil@debian.org>} [src:linux] linux: swiotlb coherent allocation failed
Marked as found in versions linux/4.16.5-1 and reopened.
> reopen -1
Bug #892517 [src:linux] linux: swiotlb coherent allocation failed
Bug 892517 is not marked as done; doing nothing.

-- 
892517: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892517
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]

#61104 — Processed: Re: Bug#892517: linux: swiotlb coherent allocation failed

Processing control commands:

> tags -1 + moreinfo
Bug #892517 [src:linux] linux: swiotlb coherent allocation failed
Added tag(s) moreinfo.

-- 
892517: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892517
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]

#61115

Hi,
this is happening to me too, with nouveau drivers, and it starts for
example with a huge file transfer over LAN.
Btw as i can read on lklm.org and some other places on the net, it
seems the proposed patch is just addressing log spamming and
suppressing all those dmesg lines, while in my case i can say that
this issue is affecting user interaction as well, since the graphics
interface is stuttering and looks very unresponsive while the problem
is in progress. It's not just a matter of logs noise.
For example my interface was really laggish few minutes ago, and i
tryed to kill a firefox instance running inside a Xephyr display which
i discovered not responding anymore. The error messages suddenly
stopped filling the logs, and the general user interaction came back
as fluid as it should normally be. So i don't know if it's just me,
but in my case there is an impact on the graphical performance.

Thank you.

-- 
free as in freedom, not free beer

[toc] | [prev] | [next] | [standalone]

#61158 — Bug#892517: Info received (Bug#892517: linux: swiotlb coherent allocation failed)

> There were various commits which went in up to v4.16.9 upstream which
> should adress the issues. There is a 4.16.12-1 upload pending for sid,
> can you check if this will fix your issue?

Hi,
just reporting back that after 4.16.12-1 arrived to testing few days
ago i booted the new version this morning, and the error still hasn't
shown up, with the same workload that was triggering it before. At
least for now... maybe fixed?
Thank you.

-- 
free as in freedom, not free beer

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web