Pete Wright [p...@nomadlogic.org] wrote:
>
> I remember having similar issues a while ago when we were first hacking on
> drm, one thing to try is updating /boot/loader.conf with the following:
> debug.debugger_on_panic=0
> dev.drm.skip_ddb="1"
> dev.drm.drm_debug_persist="1"
>
> these are semi-do
On 9/23/19 2:32 PM, Thomas Laus wrote:
Poul-Henning Kamp [p...@phk.freebsd.dk] wrote:
In message <11db909b-57ee-b452-6a17-90ec2765c...@acm.org>, Thomas Laus writes:
Where do I go from here? The computer is an Intel i5 Skylake with
onboard graphics.
Based on personal experience:
1
Poul-Henning Kamp [p...@phk.freebsd.dk] wrote:
>
> In message <11db909b-57ee-b452-6a17-90ec2765c...@acm.org>, Thomas Laus writes:
>
> >Where do I go from here? The computer is an Intel i5 Skylake with
> >onboard graphics.
>
> Based on personal experience:
>
> 1. Deinstall drm ports
>
On Mon, Sep 23, 2019 at 11:51 PM Poul-Henning Kamp wrote:
>
>
> In message
>
> , Warner Losh writes:
>
> >We are working on making drm ports less problematic on upgrade...
>
> Yes, I know.
>
> But when you track current, it seems that it takes a port-reinstall
> to get on that wagon...
In message
, Warner Losh writes:
>We are working on making drm ports less problematic on upgrade...
Yes, I know.
But when you track current, it seems that it takes a port-reinstall
to get on that wagon...
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org
On Mon, Sep 23, 2019, 10:02 PM Poul-Henning Kamp wrote:
>
> In message <11db909b-57ee-b452-6a17-90ec2765c...@acm.org>, Thomas Laus
> writes:
>
> >Where do I go from here? The computer is an Intel i5 Skylake with
> >onboard graphics.
>
> Based on personal experience:
>
> 1. Deinstall drm
In message <11db909b-57ee-b452-6a17-90ec2765c...@acm.org>, Thomas Laus writes:
>Where do I go from here? The computer is an Intel i5 Skylake with
>onboard graphics.
Based on personal experience:
1. Deinstall drm ports
2. Remove all remaining drm related files under /boot
3. Reinstall
I updated my source today and when the computer was booted, the screen
turned black at the point that the drm related kernel modules would
normally load. Suspecting a drm issue, I commented out the rc.conf line
that loads those kernel modules. This did not fix my problem. My last
good kernel was
(Please send the followup to freebsd-testing@ and note Reply-To is set.)
FreeBSD CI Weekly Report 2019-09-22
===
Here is a summary of the FreeBSD Continuous Integration results for the period
from 2019-09-16 to 2019-09-22.
During this period, we have:
* 2048 buil
