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

Hi!

On 2019-10-24 01:32, Clay Daniels Jr. wrote:
> 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?

That is a specific revision of the source tree, not a snapshot.  A 
snapshot that is later than r353906 is enough.  It is also possible to 
update FreeBSD to arbitrary revisions by building the system from source.


> 
> 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...

Sometimes, it is enough to have a photo of the information.  It is not 
as convenient as having it in text form, but in a pinch, it will do.
However, I'd syggest that you either update your system by building it 
from source (you can find details here: 
https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/current-stable.html) 
or wait for a more recent snapshot, before trying again.

As a side note, please try to leave your reply below the message you are 
replying to, it makes the flow of the text more natural, as this way, 
you will read the e-mail in the order it was written.

Regards!
-- 
Niclas