Re: drm panic after new world
- Reply: Steve Kargl : "Re: drm panic after new world"
- Reply: Bjoern A. Zeeb: "Re: drm panic after new world"
- In reply to: Steve Kargl : "drm panic after new world"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Thu, 29 May 2025 21:37:08 UTC
On Thu, May 29, 2025 at 01:06:22PM -0700, Steve Kargl wrote:
> __curthread () at /usr/src/sys/amd64/include/pcpu_aux.h:57
> 57 __asm("movq %%gs:%c1,%0" : "=r" (td)
> (kgdb) #0 __curthread () at /usr/src/sys/amd64/include/pcpu_aux.h:57
> td = <optimized out>
(snip)
> #5 0xffffffff805c8718 in pfs_add_node (
> parent=parent@entry=0xfffff80003955400, pn=pn@entry=0xfffff803557e0900)
> at /usr/src/sys/fs/pseudofs/pseudofs.c:123
> iter = <optimized out>
This is hitting a KASSERT under the INVARIANTS option.
> #6 0xffffffff805c8bd2 in pfs_create_file (parent=0xfffff80003955400,
> name=name@entry=0xffffffff82b293f4 "radeon_ring_gfx",
> fill=0xffffffff82bf70f0 <debugfs_fill>,
> attr=0xffffffff82bf72f0 <debugfs_attr>, vis=vis@entry=0x0,
> destroy=0xffffffff82bf7310 <debugfs_destroy>, flags=33)
> at /usr/src/sys/fs/pseudofs/pseudofs.c:266
> pn = 0xfffff803557e0900
> #7 0xffffffff82bf70b8 in debugfs_create_file (
> name=0xffffffff82b293f4 "radeon_ring_gfx", mode=292,
> parent=0xfffff8000398e400, data=0xfffffe012354dd30,
> fops=0xffffffff82b55918 <radeon_debugfs_ring_info_fops>)
> at /usr/src/sys/compat/lindebugfs/lindebugfs.c:209
> dm = 0xfffff80003990580
> dnode = 0xfffff80003990580
> pnode = <unavailable>
> flags = <optimized out>
> _size = <optimized out>
> _malloc_item = <optimized out>
> #8 0xffffffff82ad0084 in radeon_ring_init () from /boot/modules/radeonkms.ko
> No symbol table info available.
How does one get kernel debugging symbols into radeonkms.ko?
--
Steve