Date: Wed, 23 Oct 2019 18:32:11 -0500 From: "Clay Daniels Jr." <clay.daniels.jr@gmail.com> To: Niclas Zeising <zeising+freebsd@daemonic.se> Cc: FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: DRM-current-kmod is still a problem at r353339 Message-ID: <CAGLDxTXKRRj203yYRWj=bXPBfzN4KKw0pf_C3rWF=--zqvpKFA@mail.gmail.com> In-Reply-To: <10bd8073-84ae-3c23-e164-4e5991a2f93f@daemonic.se> References: <CAGudoHE755ig7KGuzq8uNY01K2Jcf-MKBjCp8kbpJAoiHdbQMA@mail.gmail.com> <99c89ca0-462c-f4c7-fa07-6f61e9d39d66@acm.org> <f2e7c4b4c236ee694f277d78479cb6ee@neelc.org> <CAGudoHGwmp=vNwOy2W22rjx_mQj1nkbdYzuLfayM7O0vn4keeA@mail.gmail.com> <bb951f83-6a50-48ce-8efa-b8fa92a9840e@yggdrasil.evilham.com> <CAGudoHGoikyZudFSxYjypF8EL24BPxBTPQjAnCKTe%2Bvg3DJiWQ@mail.gmail.com> <bb4f31fcb7f06059f1d9fe391b119661@neelc.org> <3bb2e410-51dd-bc3f-7660-41a4683551b3@daemonic.se> <20191017195347.GB6447@raichu> <53ff1ac5-c7e8-1b6c-bd43-481eaef61120@daemonic.se> <20191017210510.GC6447@raichu> <96d8f37a-179b-ecad-62d1-5a097d30c0ed@daemonic.se> <29e29759-18bc-6747-ab11-e15eea4ac738@daemonic.se> <CAGLDxTU9r0KUJS-Hxjr3Hu4-72cTXh5QrfM2s_tDhgSn-cc8Kw@mail.gmail.com> <10bd8073-84ae-3c23-e164-4e5991a2f93f@daemonic.se>
next in thread | previous in thread | raw e-mail | index | archive | help
Niclas, my last working install of 13.0 Current was r353072 of Oct 4th. The next week's r353427 of Oct 11th did not work and I reverted to r353072 for a week. Then r353709 of Oct 18th did not work, and when I tried to revert back to r353072 it does not work either. These were install from ports, not pkg install. I'm looking at the available Current amd64 snapshots and all I see are: r352778 (which worked), r353072 (worked), r353427 (did not work for me), & r353709 (did not work for me). I don't see a r353906? I would like to provide the full backtrace from the panic, as well as the output from kldstat -v, but the boot hangs at this point, and the first line of the panic I quoted above was a pen & paper transcription. Not sure how to get what you would like... I will also note that I saw that the gpu-firmware-kmod package has a date of 10-15-2019, but that may not have anything to do with this. Thanks, Niclas. I really like FreeBSD, and I'm working on a little FreeBSD project on efitools & secure boot, so I would like to get this working again. But actually the new snapshot will come out the day after tomorrow, so there's always hope. Clay On Wed, Oct 23, 2019 at 4:33 PM Niclas Zeising <zeising+freebsd@daemonic.se> wrote: > On 2019-10-23 21:50, Clay Daniels Jr. wrote: > > r353709 > > Looked promising, but failed: > > > > Loaded r353709 > > make install drm-kmod, all 3 installed > > (drm-devel-kmod, drm-current-kmod, & gpu-firmware-kmod) > > set /etc/rc.conf & /boot/loader.conf configs as usual > > rebooted and looked good, video tingling > > pkg install xorg > > rebooted and ran startx > > > > panic: vm_page_assert_xbusied: page 0xfffffe0005057500 not exclusive > busy @ > > /usr/src/sys/vm/vm_page.c > > > > System: Ryzen 7 3700X, MSI 570 series motherboard & video card > > Hi! > Did this used to work before the recent changes to current? Can you > please update past current r353906, which contains some fixes that was > posted earlier in this thread. > > Can you also provide the full backtrace from the panic, as well as the > output from kldstat -v. > > Thank you! > Regards > -- > Niclas >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAGLDxTXKRRj203yYRWj=bXPBfzN4KKw0pf_C3rWF=--zqvpKFA>