Re: drm-kmod, drm-next-kmod, radeonkms.ko, suspend and resume

Ack! It's been too long (at least a decade) since I've looked at a dump.
Thanks!
(kgdb) bt
#0  sched_switch (td=0xfffff80008060600, newtd=0xfffff80004210000,
    flags=<value optimized out>) at /usr/src/sys/kern/sched_4bsd.c:1066
1066            SDT_PROBE0(sched, , , on__cpu);
(kgdb) bt
#0  sched_switch (td=0xfffff80008060600, newtd=0xfffff80004210000,
    flags=<value optimized out>) at /usr/src/sys/kern/sched_4bsd.c:1066
#1  0xffffffff80b045f6 in mi_switch (flags=<value optimized out>, newtd=0x0)
    at /usr/src/sys/kern/kern_synch.c:439
#2  0xffffffff80b4b8bc in sleepq_catch_signals (wchan=0xfffff80008416a80,
    pri=0) at /usr/src/sys/kern/subr_sleepqueue.c:510
#3  0xffffffff80b4b3ff in sleepq_wait_sig (wchan=<value optimized out>,
    pri=<value optimized out>) at /usr/src/sys/kern/subr_sleepqueue.c:701
#4  0xffffffff825cdc88 in linux_add_to_sleepqueue
(wchan=0xfffff80008416a80,
    task=0xfffff80008416a80, wmesg=<value optimized out>, timeout=0,
    state=<value optimized out>)
    at /usr/src/sys/compat/linuxkpi/common/src/linux_schedule.c:62
#5  0xffffffff825cdd7b in linux_schedule_timeout (timeout=0)
    at /usr/src/sys/compat/linuxkpi/common/src/linux_schedule.c:315
#6  0xffffffff8248769a in gen5_ring_put_irq (ring=0xfffffe000229f1f8)
    at /usr/src/sys/dev/drm2/i915/intel_ringbuffer.c:776
#7  0xffffffff825cad58 in linux_kthread_fn (arg=<value optimized out>)
    at /usr/src/sys/compat/linuxkpi/common/src/linux_kthread.c:156
#8  0xffffffff80abd983 in fork_exit (
    callout=0xffffffff825cad10 <linux_kthread_fn>, arg=0x0,
    frame=0xfffffe0232ef1ac0) at /usr/src/sys/kern/kern_fork.c:1072
#9  0xffffffff80f59c4e in fork_trampoline ()
    at /usr/src/sys/amd64/amd64/exception.S:975
#10 0x0000000000000000 in ?? ()
Current language:  auto; currently minimal

What other output can I provide?
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkoberman_at_gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683


On Sat, Oct 6, 2018 at 10:34 AM Warner Losh <imp_at_bsdimp.com> wrote:

>
>
> On Sat, Oct 6, 2018 at 10:22 AM Kevin Oberman <rkoberman_at_gmail.com> wrote:
>
>> Due to lack of space on /var, I am unable to get a dump. (I'll get that
>> fixed soon, but shuffling partitions take more time than I have right now.
>>
>
> You can run savecore after you boot the system and direct its output to
> another partition, eg 'savecore /home/crash' Unless you are doing a lot of
> swapping, this is usually perfectly fine...
>
>  Warner
>