Date: Fri, 18 Oct 2019 21:44:49 +0900 (JST) From: Masachika ISHIZUKA <ish@amail.plala.or.jp> To: freebsd-current@freebsd.org Subject: Re: DRM-current-kmod is still a problem at r353339 Message-ID: <20191018.214449.616506450481592816.ish@amail.plala.or.jp> In-Reply-To: <25593555-6452-0933-d0fe-0459425cde55@delphij.net> References: <72d67f0a-aeef-1c06-2b12-9351a1f52060@anduin.net> <689d53378dcca22adb29aa23f03e8e1b@neelc.org> <25593555-6452-0933-d0fe-0459425cde55@delphij.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> Another (semi-fixed!) data point -- I can confirm that with if > (vm_page_sleep_if_busy(page, "linuxkpi")) > -> if (!vm_page_busy_acquire(page, VM_ALLOC_WAITFAIL)) change and > mjg@'s earlier patch at > https://people.freebsd.org/~mjg/pmap-fict-invl.diff (please commit it) , > the latest drm-v5.0 branch of drm-current-kmod worked just fine with > Intel HD Graphics P630 on Lenovo P51. Thank you very good information. As I was updated from r352923(1300048) to r353722M(1300053) with https://people.freebsd.org/~mjg/pmap-fict-invl.diff, it can good working with drm-current-kmod with i5-7500 desktop machine. Without https://people.freebsd.org/~mjg/pmap-fict-invl.diff patch, drm-current-kmod is loaded success fully, but when starting xorg, drm-current-kmod was paniced as follows. (The following syslog was on i7-4500U notebook machine on r352923.) kernel: WARNING !drm_modeset_is_locked(&crtc->mutex) failed at /usr/local/sys/modules/drm-current-kmod/drivers/gpu/drm/drm_atomic_helper.c:577 syslogd: last message repeated 2 times kernel: WARNING !drm_modeset_is_locked(&dev->mode_config.connection_mutex) failed at /usr/local/sys/modules/drm-current-kmod/drivers/gpu/drm/drm_atomic_helper.c:622 kernel: WARNING !drm_modeset_is_locked(&plane->mutex) failed at /usr/local/sys/modules/drm-current-kmod/drivers/gpu/drm/drm_atomic_helper.c:821 syslogd: last message repeated 8 times kernel: WARN_ON(!mutex_is_locked(&dev->struct_mutex)) kernel: WARN_ON(!mutex_is_locked(&fbc->lock))WARN_ON(!mutex_is_locked(&fbc->lock))WARN_ON(!mutex_is_locked(&fbc->lock)) kernel: panic: handle_workitem_remove: DIRCHG and worklist not empty. kernel: cpuid = 2 kernel: time = 1571387388 kernel: KDB: stack backtrace: kernel: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe0060c4e860 kernel: vpanic() at vpanic+0x19d/frame 0xfffffe0060c4e8b0 kernel: panic() at panic+0x43/frame 0xfffffe0060c4e910 kernel: handle_workitem_remove() at handle_workitem_remove+0x607/frame 0xfffffe0060c4e980 kernel: process_worklist_item() at process_worklist_item+0x270/frame 0xfffffe0060c4ea00 kernel: softdep_process_worklist() at softdep_process_worklist+0xb2/frame 0xfffffe0060c4ea40 kernel: softdep_flush() at softdep_flush+0xef/frame 0xfffffe0060c4ea70 kernel: fork_exit() at fork_exit+0x84/frame 0xfffffe0060c4eab0 kernel: fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe0060c4eab0 kernel: --- trap 0, rip = 0, rsp = 0, rbp = 0 --- kernel: Uptime: 11h21m3s kernel: Dumping 874 out of 8058 MB:..2%..11%..21%..32%..41%..52%..61%..72%..81%..92% -- Masachika ISHIZUKA
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20191018.214449.616506450481592816.ish>