[opensuse-factory] Radeon crashes?
I've been seeing a lot of the following messages since the 4.16 series kernel
(and other software updates, of course). I wonder if anyone can say what is
going on, or has experienced this.
It's not a constant; in fact, the current 4.16.3-1-default has been up for two
days before it produced the below log. When it happens, it may happen once or
several times in a row, and the display shows a delay in updating, when
opening a new window for example, or simply paging text. It then straightens
out and behaves normally.
Apr 29 22:51:56 sgt.decathlon.org kernel: radeon 0000:00:01.0: swiotlb buffer
is full (sz: 2097152 bytes)
Apr 29 22:51:56 sgt.decathlon.org kernel: radeon 0000:00:01.0: swiotlb:
coherent allocation failed, size=2097152
Apr 29 22:51:56 sgt.decathlon.org kernel: CPU: 0 PID: 1634 Comm: X Not tainted
4.16.3-1-default #1 openSUSE Tumbleweed (unreleased)
Apr 29 22:51:56 sgt.decathlon.org kernel: Hardware name: Hewlett-Packard HP
2000 Notebook PC/3577, BIOS F.43 12/13/2011
Apr 29 22:51:56 sgt.decathlon.org kernel: Call Trace:
Apr 29 22:51:56 sgt.decathlon.org kernel: dump_stack+0x85/0xc5
Apr 29 22:51:56 sgt.decathlon.org kernel: swiotlb_alloc_coherent+0x1b6/0x1d0
Apr 29 22:51:56 sgt.decathlon.org kernel: ttm_dma_pool_get_pages+0x1ed/0x5b0
[ttm]
Apr 29 22:51:56 sgt.decathlon.org kernel: ttm_dma_populate+0x25e/0x350 [ttm]
Apr 29 22:51:56 sgt.decathlon.org kernel: ttm_tt_bind+0x2c/0x60 [ttm]
Apr 29 22:51:56 sgt.decathlon.org kernel: ttm_bo_handle_move_mem+0x577/0x5b0
[ttm]
Apr 29 22:51:56 sgt.decathlon.org kernel: ttm_bo_validate+0x100/0x110 [ttm]
Apr 29 22:51:56 sgt.decathlon.org kernel: ? drm_vma_offset_add+0x41/0x60
[drm]
Apr 29 22:51:56 sgt.decathlon.org kernel: ? drm_mm_remove_node+0x2fe/0x350
[drm]
Apr 29 22:51:56 sgt.decathlon.org kernel: ttm_bo_init_reserved+0x382/0x430
[ttm]
Apr 29 22:51:56 sgt.decathlon.org kernel: ttm_bo_init+0x52/0xc0 [ttm]
Apr 29 22:51:56 sgt.decathlon.org kernel: ? radeon_update_memory_usage.isra.
4+0x50/0x50 [radeon]
Apr 29 22:51:56 sgt.decathlon.org kernel: radeon_bo_create+0x180/0x240
[radeon]
Apr 29 22:51:56 sgt.decathlon.org kernel: ? radeon_update_memory_usage.isra.
4+0x50/0x50 [radeon]
Apr 29 22:51:56 sgt.decathlon.org kernel: radeon_gem_object_create+0x93/0x180
[radeon]
Apr 29 22:51:56 sgt.decathlon.org kernel: ? radeon_gem_pwrite_ioctl+0x30/0x30
[radeon]
Apr 29 22:51:56 sgt.decathlon.org kernel: radeon_gem_create_ioctl+0x56/0xf0
[radeon]
Apr 29 22:51:56 sgt.decathlon.org kernel: ? radeon_gem_pwrite_ioctl+0x30/0x30
[radeon]
Apr 29 22:51:56 sgt.decathlon.org kernel: drm_ioctl_kernel+0x5b/0xb0 [drm]
Apr 29 22:51:56 sgt.decathlon.org kernel: drm_ioctl+0x2ad/0x350 [drm]
Apr 29 22:51:56 sgt.decathlon.org kernel: ? radeon_gem_pwrite_ioctl+0x30/0x30
[radeon]
Apr 29 22:51:56 sgt.decathlon.org kernel: ? __do_fault+0x20/0xb0
Apr 29 22:51:56 sgt.decathlon.org kernel: ? handle_pte_fault+0x609/0xde0
Apr 29 22:51:56 sgt.decathlon.org kernel: radeon_drm_ioctl+0x49/0x80 [radeon]
Apr 29 22:51:56 sgt.decathlon.org kernel: do_vfs_ioctl+0x90/0x5f0
Apr 29 22:51:56 sgt.decathlon.org kernel: ? handle_mm_fault+0x101/0x250
Apr 29 22:51:56 sgt.decathlon.org kernel: ? __fget+0x6e/0xb0
Apr 29 22:51:56 sgt.decathlon.org kernel: SyS_ioctl+0x74/0x80
Apr 29 22:51:56 sgt.decathlon.org kernel: do_syscall_64+0x76/0x140
Apr 29 22:51:56 sgt.decathlon.org kernel: entry_SYSCALL_64_after_hwframe
+0x42/0xb7
Apr 29 22:51:56 sgt.decathlon.org kernel: RIP: 0033:0x7fc040002967
Apr 29 22:51:56 sgt.decathlon.org kernel: RSP: 002b:00007ffea060cf78 EFLAGS:
00003246 ORIG_RAX: 0000000000000010
Apr 29 22:51:56 sgt.decathlon.org kernel: RAX: ffffffffffffffda RBX:
0000000000000002 RCX: 00007fc040002967
Apr 29 22:51:56 sgt.decathlon.org kernel: RDX: 00007ffea060cff0 RSI:
00000000c020645d RDI: 000000000000001a
Apr 29 22:51:56 sgt.decathlon.org kernel: RBP: 00007ffea060cff0 R08:
0000000000000002 R09: 0000000000000000
Apr 29 22:51:56 sgt.decathlon.org kernel: R10: 0000000000000000 R11:
0000000000003246 R12: 00000000c020645d
Apr 29 22:51:56 sgt.decathlon.org kernel: R13: 000000000000001a R14:
00005572fc0c6d20 R15: 0000000000000002
--
Tom Hardy
Tom Hardy composed on 2018-04-29 23:09 (UTC-0500):
I've been seeing a lot of the following messages since the 4.16 series kernel (and other software updates, of course). I wonder if anyone can say what is going on, or has experienced this.
Have you tried the default Xorg video driver (modesetting, integral to the server; removing the AMD/ATI drivers is the simplest way to enable)? Which gfxchip? lspci -nnk | grep -A4 VGA inxi -G -c0 -- "Wisdom is supreme; therefore get wisdom. Whatever else you get, get wisdom." Proverbs 4:7 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Monday, 30 April 2018 00:03:23 CDT Felix Miata wrote:
Have you tried the default Xorg video driver (modesetting, integral to the server; removing the AMD/ATI drivers is the simplest way to enable)?
I haven't done anything yet, and I am not sure I know how. Are you saying the easiest way is to remove some packages? I'll have to figure out which ones. Or use modesetting? By way of a kernel parameter at boot? It's a laptop with the AMD E450 APU.
lspci -nnk | grep -A4 VGA
00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ ATI] Wrestler [Radeon HD 6320] [1002:9806] Subsystem: Hewlett-Packard Company Device [103c:3577] Kernel driver in use: radeon Kernel modules: radeon 00:11.0 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/ SB8x0/SB9x0 SATA Controller [AHCI mode] [1002:4391]
inxi -G -c0
Graphics: Card: Advanced Micro Devices [AMD/ATI] Wrestler [Radeon HD 6320]
Display Server: X.Org 1.19.6 drivers: ati,radeon (unloaded:
modesetting,fbdev,vesa)
Resolution: 1366x768@59.99hz
OpenGL: renderer: AMD PALM (DRM 2.50.0 / 4.16.3-1-default, LLVM
6.0.0) version: 3.3 Mesa 18.0.1
--
Tom Hardy
I think it is the same with this one
https://bugs.freedesktop.org/show_bug.cgi?id=104082 which is open for
long time. Was fixed but re-appeared.
On Mon, Apr 30, 2018 at 8:59 AM, Tom Hardy
On Monday, 30 April 2018 00:03:23 CDT Felix Miata wrote:
Have you tried the default Xorg video driver (modesetting, integral to the server; removing the AMD/ATI drivers is the simplest way to enable)?
I haven't done anything yet, and I am not sure I know how. Are you saying the easiest way is to remove some packages? I'll have to figure out which ones. Or use modesetting? By way of a kernel parameter at boot?
It's a laptop with the AMD E450 APU.
lspci -nnk | grep -A4 VGA
00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ ATI] Wrestler [Radeon HD 6320] [1002:9806] Subsystem: Hewlett-Packard Company Device [103c:3577] Kernel driver in use: radeon Kernel modules: radeon 00:11.0 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/ SB8x0/SB9x0 SATA Controller [AHCI mode] [1002:4391]
inxi -G -c0
Graphics: Card: Advanced Micro Devices [AMD/ATI] Wrestler [Radeon HD 6320] Display Server: X.Org 1.19.6 drivers: ati,radeon (unloaded: modesetting,fbdev,vesa) Resolution: 1366x768@59.99hz OpenGL: renderer: AMD PALM (DRM 2.50.0 / 4.16.3-1-default, LLVM 6.0.0) version: 3.3 Mesa 18.0.1
-- Tom Hardy
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Tom Hardy composed on 2018-04-30 00:59 (UTC-0500):
Felix Miata wrote:
Have you tried the default Xorg video driver (modesetting, integral to the server; removing the AMD/ATI drivers is the simplest way to enable)?
I haven't done anything yet, and I am not sure I know how. Are you saying the easiest way is to remove some packages? I'll have to figure out which ones. Or use modesetting? By way of a kernel parameter at boot?
Remove xf86-video-ati and modesetting should automatically be used, as your inxi output indicates in use radeon, which xf86-video-ati provides. The other possibility would have been xf86-video-amdgpu. All this will do is give an opportunity to test if an alternative driver makes the crashing stop. I'm not suggesting the driver in use is the actual problem, only that it might be. Does the crashing stop if you boot a 4.15 kernel, or do you no longer have one to try? I have 4.15.13-2.4 if you want to try. I normally don't let .0 or .1 kernels install on mine.
It's a laptop with the AMD E450 APU.
lspci -nnk | grep -A4 VGA
00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ ATI] Wrestler [Radeon HD 6320] [1002:9806] Subsystem: Hewlett-Packard Company Device [103c:3577] Kernel driver in use: radeon Kernel modules: radeon 00:11.0 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/ SB8x0/SB9x0 SATA Controller [AHCI mode] [1002:4391]
inxi -G -c0
Graphics: Card: Advanced Micro Devices [AMD/ATI] Wrestler [Radeon HD 6320] Display Server: X.Org 1.19.6 drivers: ati,radeon (unloaded: modesetting,fbdev,vesa) Resolution: 1366x768@59.99hz OpenGL: renderer: AMD PALM (DRM 2.50.0 / 4.16.3-1-default, LLVM 6.0.0) version: 3.3 Mesa 18.0.1-- "Wisdom is supreme; therefore get wisdom. Whatever else you get, get wisdom." Proverbs 4:7 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Monday, 30 April 2018 02:31:06 CDT Felix Miata wrote:
Remove xf86-video-ati and modesetting should automatically be used, as your inxi output indicates in use radeon, which xf86-video-ati provides. The other possibility would have been xf86-video-amdgpu.
Both are installed on my system. Is there any chance that amdgpu would be
used if ati is removed? Would that be a problem?
For kernels, I have the last two in the 4.16 series, and I have kernel-
default-4.13.3-1.1.x86_64. (Which was present when I added "oldest" to
multiversion kernel.)
I'll plan to reboot later today, with latest kernel and one or more drivers
removed, and then run several days to see if anything happens.
--
Tom Hardy
On Monday, 30 April 2018 02:31:06 CDT Felix Miata wrote:
Remove xf86-video-ati and modesetting should automatically be used,...
Modesetting is in effect, and no crashing so far, but memory has yet to be
exercised.
I notice a couple of differences:
o Hardware cursor? (It is not affected by progs such as redshift.)
o Session Restore on startup has been unreliable for some time, so that I
restart some progs that should have restored, adjust their size, position, and
desktop, etc. Well, the latest session restored many copies of some of those
programs, (konsole, ksysguard) and restored one that failed to restore in the
previous session (Atril Document Viewer). It didn't put them in the right
place, though.
--
Tom Hardy
On Monday, 30 April 2018 02:31:06 CDT Felix Miata wrote:
Remove xf86-video-ati and modesetting should automatically be used, as your inxi output indicates in use radeon, which xf86-video-ati provides. The other possibility would have been xf86-video-amdgpu.
All this will do is give an opportunity to test if an alternative driver makes the crashing stop. I'm not suggesting the driver in use is the actual problem, only that it might be. Does the crashing stop if you boot a 4.15 kernel, or do you no longer have one to try? I have 4.15.13-2.4 if you want to try. I normally don't let .0 or .1 kernels install on mine.
So, it's back. I ran for two days without problems, and then decided to
increase memory pressure by opening a big fat program, josm, using it for a
bit, going through a suspend/resume, and got the log shown below.
What's next? I don't recall a problem with 4.15 kernels, but I could be wrong
about that.
sgt:~ # inxi -G -c0
Graphics: Card: Advanced Micro Devices [AMD/ATI] Wrestler [Radeon HD 6320]
Display Server: X.Org 1.19.6 drivers: modesetting (unloaded:
fbdev,vesa) Resolution: 1366x768@59.99hz
OpenGL: renderer: AMD PALM (DRM 2.50.0 / 4.16.3-1-default, LLVM
6.0.0) version: 3.3 Mesa 18.0.1
sgt:~ # lspci -nnk | grep -A4 VGA
00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/
ATI] Wrestler [Radeon HD 6320] [1002:9806]
Subsystem: Hewlett-Packard Company Device [103c:3577]
Kernel driver in use: radeon
Kernel modules: radeon
00:11.0 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/
SB8x0/SB9x0 SATA Controller [AHCI mode] [1002:4391]
May 02 21:57:42 sgt.decathlon.org ksmserver[1900]: UnmapNotify: 79691818
May 02 21:57:42 sgt.decathlon.org ksmserver[1900]: UnmapNotify: 79691818
May 02 21:57:42 sgt.decathlon.org ksmserver[1900]: CreateNotify: 79691833
May 02 21:57:44 sgt.decathlon.org ksmserver[1900]: Grab Released
May 02 21:57:45 sgt.decathlon.org kernel: radeon 0000:00:01.0: swiotlb buffer
is full (sz: 2097152 bytes)
May 02 21:57:45 sgt.decathlon.org kernel: radeon 0000:00:01.0: swiotlb:
coherent allocation failed, size=2097152
May 02 21:57:45 sgt.decathlon.org kernel: CPU: 0 PID: 1669 Comm: X Not tainted
4.16.3-1-default #1 openSUSE Tumbleweed (unreleased)
May 02 21:57:45 sgt.decathlon.org kernel: Hardware name: Hewlett-Packard HP
2000 Notebook PC/3577, BIOS F.43 12/13/2011
May 02 21:57:45 sgt.decathlon.org kernel: Call Trace:
May 02 21:57:45 sgt.decathlon.org kernel: dump_stack+0x85/0xc5
May 02 21:57:45 sgt.decathlon.org kernel: swiotlb_alloc_coherent+0x1b6/0x1d0
May 02 21:57:45 sgt.decathlon.org kernel: ttm_dma_pool_get_pages+0x1ed/0x5b0
[ttm]
May 02 21:57:45 sgt.decathlon.org kernel: ttm_dma_populate+0x25e/0x350 [ttm]
May 02 21:57:45 sgt.decathlon.org kernel: ttm_tt_bind+0x2c/0x60 [ttm]
May 02 21:57:45 sgt.decathlon.org kernel: ttm_bo_handle_move_mem+0x577/0x5b0
[ttm]
May 02 21:57:45 sgt.decathlon.org kernel: ttm_bo_validate+0x100/0x110 [ttm]
May 02 21:57:45 sgt.decathlon.org kernel: ? drm_vma_offset_add+0x41/0x60
[drm]
May 02 21:57:45 sgt.decathlon.org kernel: ? drm_irq_uninstall+0x5e/0x160
[drm]
May 02 21:57:45 sgt.decathlon.org kernel: ttm_bo_init_reserved+0x382/0x430
[ttm]
May 02 21:57:45 sgt.decathlon.org kernel: ttm_bo_init+0x52/0xc0 [ttm]
May 02 21:57:45 sgt.decathlon.org kernel: ? radeon_update_memory_usage.isra.
4+0x50/0x50 [radeon]
May 02 21:57:45 sgt.decathlon.org kernel: radeon_bo_create+0x180/0x240
[radeon]
May 02 21:57:45 sgt.decathlon.org kernel: ? radeon_update_memory_usage.isra.
4+0x50/0x50 [radeon]
May 02 21:57:45 sgt.decathlon.org kernel: radeon_gem_object_create+0x93/0x180
[radeon]
May 02 21:57:45 sgt.decathlon.org kernel: ? radeon_gem_pwrite_ioctl+0x30/0x30
[radeon]
May 02 21:57:45 sgt.decathlon.org kernel: radeon_gem_create_ioctl+0x56/0xf0
[radeon]
May 02 21:57:45 sgt.decathlon.org kernel: ? unix_stream_recvmsg+0x43/0x50
May 02 21:57:45 sgt.decathlon.org kernel: ? radeon_gem_pwrite_ioctl+0x30/0x30
[radeon]
May 02 21:57:45 sgt.decathlon.org kernel: drm_ioctl_kernel+0x5b/0xb0 [drm]
May 02 21:57:45 sgt.decathlon.org kernel: drm_ioctl+0x2ad/0x350 [drm]
May 02 21:57:45 sgt.decathlon.org kernel: ? radeon_gem_pwrite_ioctl+0x30/0x30
[radeon]
May 02 21:57:45 sgt.decathlon.org kernel: ? timerqueue_add+0x52/0x80
May 02 21:57:45 sgt.decathlon.org kernel: radeon_drm_ioctl+0x49/0x80 [radeon]
May 02 21:57:45 sgt.decathlon.org kernel: do_vfs_ioctl+0x90/0x5f0
May 02 21:57:45 sgt.decathlon.org kernel: ? __sys_recvmsg+0x5d/0x70
May 02 21:57:45 sgt.decathlon.org kernel: ? __fget+0x6e/0xb0
May 02 21:57:45 sgt.decathlon.org kernel: SyS_ioctl+0x74/0x80
May 02 21:57:45 sgt.decathlon.org kernel: do_syscall_64+0x76/0x140
May 02 21:57:45 sgt.decathlon.org kernel: entry_SYSCALL_64_after_hwframe
+0x42/0xb7
May 02 21:57:45 sgt.decathlon.org kernel: RIP: 0033:0x7fb4e0e4f967
May 02 21:57:45 sgt.decathlon.org kernel: RSP: 002b:00007ffc633fde38 EFLAGS:
00003246 ORIG_RAX: 0000000000000010
May 02 21:57:45 sgt.decathlon.org kernel: RAX: ffffffffffffffda RBX:
0000000000000002 RCX: 00007fb4e0e4f967
May 02 21:57:45 sgt.decathlon.org kernel: RDX: 00007ffc633fdeb0 RSI:
00000000c020645d RDI: 000000000000001a
May 02 21:57:45 sgt.decathlon.org kernel: RBP: 00007ffc633fdeb0 R08:
0000000000000002 R09: 0000000000000000
May 02 21:57:45 sgt.decathlon.org kernel: R10: 0000000000000000 R11:
0000000000003246 R12: 00000000c020645d
May 02 21:57:45 sgt.decathlon.org kernel: R13: 000000000000001a R14:
000055c481cb9770 R15: 0000000000000002
--
Tom Hardy
Tom Hardy composed on 2018-05-02 22:15 (UTC-0500):
So, it's back. I ran for two days without problems, and then decided to increase memory pressure by opening a big fat program, josm, using it for a bit, going through a suspend/resume, and got the log shown below.
What's next? I don't recall a problem with 4.15 kernels, but I could be wrong about that.
Dunno what to suggest other than an interior cleaning, making sure all fans are working, or running memtest overnight. I'm not going to install josm. I've yet to see any Java app with usable UI. What else do you use besides web browsers?
sgt:~ # inxi -G -c0 Graphics: Card: Advanced Micro Devices [AMD/ATI] Wrestler [Radeon HD 6320] Display Server: X.Org 1.19.6 drivers: modesetting (unloaded: fbdev,vesa) Resolution: 1366x768@59.99hz OpenGL: renderer: AMD PALM (DRM 2.50.0 / 4.16.3-1-default, LLVM 6.0.0) version: 3.3 Mesa 18.0.1
sgt:~ # lspci -nnk | grep -A4 VGA 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ ATI] Wrestler [Radeon HD 6320] [1002:9806] Subsystem: Hewlett-Packard Company Device [103c:3577] Kernel driver in use: radeon Kernel modules: radeon
I have this 32-bit desktop PC with 2G RAM, fairly close to your GPU running ATM: grep RETT /etc/os-release PRETTY_NAME="openSUSE Tumbleweed" uname -a Linux gx28c 4.16.4-1-default #1 SMP Tue Apr 24 08:49:53 UTC 2018 (2ebc2ec) i686 i686 i386 GNU/Linux inxi -G -c0 Graphics: Card: Advanced Micro Devices [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] Display Server: X.Org 1.19.6 drivers: modesetting (unloaded: fbdev,vesa) Resolution: 1920x1200@59.95hz OpenGL: renderer: AMD CAICOS (DRM 2.50.0 / 4.16.4-1-default, LLVM 6.0.0) version: 3.3 Mesa 18.0.1 lspci -nnk | grep -A3 VGA 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] [1002:6779] Subsystem: Dell Radeon HD 6450 [1028:2120] Kernel driver in use: radeon Kernel modules: radeon -- "Wisdom is supreme; therefore get wisdom. Whatever else you get, get wisdom." Proverbs 4:7 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Thursday, 3 May 2018 00:47:53 CDT Felix Miata wrote:
Dunno what to suggest other than an interior cleaning, making sure all fans are working, or running memtest overnight.
I'm not going to install josm. I've yet to see any Java app with usable UI.
The point of JOSM was to use and shuffle memory until a 2MiB allocation couldn't be made a la https://bugs.freedesktop.org/show_bug.cgi?id=104082 . It seems someone was interested. Takashi Iwai maybe?
What else do you use besides web browsers?
Just for the heck of it: https://i.redd.it/ln2a00i6x5yz.png is a typical
screenshot. JOSM, if running, would be on the "Map" desktop. I've got a
couple of servers running in the background, also.
--
Tom Hardy
Tom Hardy composed on 2018-05-03 01:38 (UTC-0500):
Felix Miata wrote:
Dunno what to suggest other than an interior cleaning, making sure all fans are working, or running memtest overnight.
I'm not going to install josm. I've yet to see any Java app with usable UI.
The point of JOSM was to use and shuffle memory until a 2MiB allocation couldn't be made a la https://bugs.freedesktop.org/show_bug.cgi?id=104082 . It seems someone was interested. Takashi Iwai maybe?
What else do you use besides web browsers?
Just for the heck of it: https://i.redd.it/ln2a00i6x5yz.png is a typical screenshot. JOSM, if running, would be on the "Map" desktop. I've got a couple of servers running in the background, also.
I've forgotten when I first started my HD6450 PC. I think it was Monday, but maybe Tuesday. When I woke up after the first night it was locked up solid, and after the power off reset I failed to discover what might have happened. In the days following it's been fine running 3 Fedoras, 42.3 and TW. Current uptime running TW is 1.5 days and has both Firefox 17 and Youtube fullscreen on 59 running. Soon I must shut it down to free up the station for work on another PC. -- "Wisdom is supreme; therefore get wisdom. Whatever else you get, get wisdom." Proverbs 4:7 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Mon, 30 Apr 2018 06:09:48 +0200, Tom Hardy wrote:
I've been seeing a lot of the following messages since the 4.16 series kernel (and other software updates, of course). I wonder if anyone can say what is going on, or has experienced this.
It's not a constant; in fact, the current 4.16.3-1-default has been up for two days before it produced the below log. When it happens, it may happen once or several times in a row, and the display shows a delay in updating, when opening a new window for example, or simply paging text. It then straightens out and behaves normally.
Apr 29 22:51:56 sgt.decathlon.org kernel: radeon 0000:00:01.0: swiotlb buffer is full (sz: 2097152 bytes) Apr 29 22:51:56 sgt.decathlon.org kernel: radeon 0000:00:01.0: swiotlb: coherent allocation failed, size=2097152
Hrm, I hoped that this sort of bug was addressed by the recent fixes in 4.16.y / stable branch. At least, amdgpu drivers seem working better, but radeon hits, too. Could you check the kernel in OBS home:tiwai:stable-dma32 repo? This might help reducing such allocation failures. thanks, Takashi -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (4)
-
Felix Miata -
Stratos Zolotas -
Takashi Iwai -
Tom Hardy