Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 3 Oct 2019 23:52:38 +0200
From:      Hans Petter Selasky <hps@selasky.org>
To:        sgk@troutmask.apl.washington.edu
Cc:        freebsd-current@freebsd.org, Johannes Lundberg <johalun0@gmail.com>
Subject:   Re: radeon panics kernels
Message-ID:  <5aa9c63c-98a2-b222-1b8b-64d33e47951b@selasky.org>
In-Reply-To: <20191003202643.GA61643@troutmask.apl.washington.edu>
References:  <20191002211946.GA1031@troutmask.apl.washington.edu> <c77bbac6-beb3-eb84-0609-670117f444c0@selasky.org> <20191003125920.GA4528@troutmask.apl.washington.edu> <a8621832-75e3-38fb-a766-5b9bc47c131d@selasky.org> <20191003202643.GA61643@troutmask.apl.washington.edu>

next in thread | previous in thread | raw e-mail | index | archive | help
On 2019-10-03 22:26, Steve Kargl wrote:
> On Thu, Oct 03, 2019 at 03:05:27PM +0200, Hans Petter Selasky wrote:
>>
>> 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?
>>
> 
> Took a bit of trial and error.  If I skip the panic
> and trap frames (#0 through #8). I find the backtrace
> that follows by sig.  If I move to frame #11, I see
> 
> (kgdb) frame 11
> #11 r100_mm_rreg_slow (rdev=0xfffff80135766a70, reg=<optimized out>)
>      at /usr/ports/graphics/drm-current-kmod/work/kms-drm-2d2852e/drivers/gpu/drm/radeon/r100.c:4114
> 4114            writel(reg, ((void __iomem *)rdev->rmmio) + RADEON_MM_INDEX);
> (kgdb) p rdev->rmmio
> $3 = (void *) 0x0
> 
> So, your guess of a NULL pointer seems correct.

Can you do:

set print pretty on
print *rdev

--HPS




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5aa9c63c-98a2-b222-1b8b-64d33e47951b>