Re: unkillable process consuming 100% cpu

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  *(radeon_gem_busy_ioctl+0x30)
>>> 0xa12b0 is in radeon_gem_busy_ioctl (/usr/ports/graphics/drm-current-kmod/work/kms-drm-2d2852e/drivers/gpu/drm/radeon/radeon_gem.c:453).
>>> 448     /usr/ports/graphics/drm-current-kmod/work/kms-drm-2d2852e/drivers/gpu/drm/radeon/radeon_gem.c: No such file or directory.
>>> (gdb)
>>
>> Like expected.
>>
> 
> 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 system was doing during the lockups.  So far, I
> cannot ge the system lock-up.  Looks like your patch fixes (or at
> least helps).  Thanks for taking a look at the problem.
> 

Can you apply the kdb.diff on top and check dmesg for prints?

--HPS