Date: Wed, 13 Nov 2019 09:10:06 +0100 From: Hans Petter Selasky <hps@selasky.org> To: sgk@troutmask.apl.washington.edu Cc: Mark Johnston <markj@freebsd.org>, freebsd-current@freebsd.org, freebsd-x11@freebsd.org Subject: Re: unkillable process consuming 100% cpu Message-ID: <1de2773b-3f54-472b-65a1-0f1c297aab60@selasky.org> In-Reply-To: <20191113003001.GA94074@troutmask.apl.washington.edu> References: <20191107202919.GA4565@troutmask.apl.washington.edu> <20191107203223.GF16978@raichu> <20191108220935.GA856@troutmask.apl.washington.edu> <6a4e5993-623a-ebaa-8180-e11c7d48e706@selasky.org> <20191112173136.GA69344@troutmask.apl.washington.edu> <0961307a-8b14-8240-0466-6bb4edf52788@selasky.org> <20191113003001.GA94074@troutmask.apl.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1de2773b-3f54-472b-65a1-0f1c297aab60>