On Thu, Oct 03, 2019 at 03:05:27PM +0200, Hans Petter Selasky wrote: > On 2019-10-03 14:59, Steve Kargl wrote: > > On Thu, Oct 03, 2019 at 09:17:32AM +0200, Hans Petter Selasky wrote: > >> On 2019-10-02 23:19, Steve Kargl wrote: > >>> troutmask.apl.washington.edu dumped core - see /var/crash/vmcore.7 > >>> > >>> Wed Oct 2 14:12:38 PDT 2019 > >>> > >> > >> This looks like a simple NULL pointer. > >> > >> Can you re-compile the drm ports module with debugging symbols and then > >> reproduce? > >> > > > > Yes. Is there a ports knob, ie., 'make -DEBUG' for the > > drm ports? Or, do I need to add CFLAGS+=-g to the Makefile? > > > > BTW, this is what I have installed > > > > drm-current-kmod-4.16.g20190927 DRM modules for the linuxkpi-based KMS > > drm-kmod-g20190710 Metaport of DRM modules > > gpu-firmware-kmod-g20190825 Firmware modules for the linuxkpi-based KMS > > If you leave the port debug knob for drm-current-kmod AS-IS, I think you > can get away with: > > make DEBUG_FLAGS="-g" > > Then re-load the vmcore file in GDB/KGDB from ports (!) and add the > symbol files for the modules loaded. Then get the backtrace using bt > command. > > BTW: Did you try drm-devel-kmod for 13-current? > No. I let drm-kmod select drm-current-kod. I can trying drm-devel-kmodr. I do have an older graphics card, which required the drm-legacy-kmod port until recently % pciconf -vl ... vendor = 'Advanced Micro Devices, Inc. [AMD/ATI]' device = 'Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM]' class = display subclass = VGA -- SteveReceived on Thu Oct 03 2019 - 11:14:31 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:22 UTC