On Mon, Nov 11, 2019 at 01:22:09PM +0100, Hans Petter Selasky wrote:
> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_gpuvm.c
> b/drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_gpuvm.c
> index a6e0a16ae..0697d70f4 100644
> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_gpuvm.c
> +++
On Wed, Nov 13, 2019 at 04:22:19PM +0100, Hans Petter Selasky wrote:
> On 2019-11-13 15:52, Steve Kargl wrote:
> > at /usr/src/sys/amd64/amd64/trap.c:743
> > #7 0x808b0468 in trap (frame=0xfe00b460e0c0)
> > at /usr/src/sys/amd64/amd64/trap.c:407
> > #8
> > #9
On 2019-11-13 15:52, Steve Kargl wrote:
at /usr/src/sys/amd64/amd64/trap.c:743
#7 0x808b0468 in trap (frame=0xfe00b460e0c0)
at /usr/src/sys/amd64/amd64/trap.c:407
#8
#9 0x in ?? ()
#10 0x817d2c0f in radeon_ttm_tt_to_gtt (ttm=0xf80061eeb248)
On Wed, Nov 13, 2019 at 09:10:06AM +0100, Hans Petter Selasky wrote:
> On 2019-11-13 01:30, Steve Kargl wrote:
> >
> > I installed the 2nd seqlock.diff, rebuilt drm-current-kmod-4.16.g20191023,
> > rebooting, and have been pounding on the system with workloads that are
> > similar to what the
I wonder if anyone remembers devstat code enough to help me or, at least, to
sanity check my line of thinking.
I am looking at a crash that happened in devstat_selectdevs(num_selections=27,
numdevs=25). At the time of the crash there was some reconfiguration of logical
volumes on a RAID
On 2019-11-13 01:30, Steve Kargl wrote:
On Tue, Nov 12, 2019 at 06:48:22PM +0100, Hans Petter Selasky wrote:
On 2019-11-12 18:31, Steve Kargl wrote:
Can you open the radeonkms.ko in gdb83 from ports and type:
l *(radeon_gem_busy_ioctl+0x30)
% /boot/modules/radeonkms.ko
(gdb) l