Re: DRM-current-kmod is still a problem at r353339

2019-10-23 Thread Clay Daniels Jr.
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,

Re: DRM-current-kmod is still a problem at r353339

2019-10-23 Thread Niclas Zeising
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

Re: DRM-current-kmod is still a problem at r353339

2019-10-23 Thread Clay Daniels Jr.
sorry, should be all 3 installed (drm-kmod, drm-current-kmod, & gpu-firmware-kmod) On Wed, Oct 23, 2019 at 2:50 PM Clay Daniels Jr. wrote: > r353709 > Looked promising, but failed: > > Loaded r353709 > make install drm-kmod, all 3 installed > (drm-devel-kmod, drm-current-kmod, &

Re: DRM-current-kmod is still a problem at r353339

2019-10-23 Thread Clay Daniels Jr.
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:

Re: > r353680: multiuser crash due to: m_getzone: Inavlid cluster size 0

2019-10-23 Thread Navdeep Parhar
This is 241403 in bugzilla. On Wed, Oct 23, 2019, 12:57 AM O. Hartmann wrote: > The last known good update of CURRENT on a Fujitsu Primergy RX2530-M5 > (only one > of two sockets equipted, 64 GB RAM) was October, 17th, 2019 before 15 > o'clock, > I suppose that was r353680 that time. Today's

Re: DRM-current-kmod is still a problem at r353339

2019-10-23 Thread Niclas Zeising
On 2019-10-21 10:13, Niclas Zeising wrote: On 2019-10-17 23:05, Mark Johnston wrote: On Thu, Oct 17, 2019 at 10:31:12PM +0200, Niclas Zeising wrote: On 2019-10-17 21:53, ma...@freebsd.org wrote: On Thu, Oct 17, 2019 at 03:03:51PM +0200, Niclas Zeising wrote: On 2019-10-16 18:57, Neel Chauhan

> r353680: multiuser crash due to: m_getzone: Inavlid cluster size 0

2019-10-23 Thread O. Hartmann
The last known good update of CURRENT on a Fujitsu Primergy RX2530-M5 (only one of two sockets equipted, 64 GB RAM) was October, 17th, 2019 before 15 o'clock, I suppose that was r353680 that time. Today's update to r353881 resulted in an immediate crash when the network (igb0-igb3, two built-in