On 2019-09-25 17:51, Thomas Laus wrote:
> I was able to mount my zfs filesystem r+w and added the rc_debug="YES"
> to my rc.conf. The additional debug messages were written to the beadm
> boot environment /var/log/messages. Since the computer locked up, I was
> unable to read this log and email
On 2019-09-24 15:09, Ian Lepore wrote:
>
> On my system, a whole lotta stuff happens between ntpd and syscons (the
> thing that configures blanktime). Try setting rc_debug=YES in rc.conf,
> that should write more info to syslog about what's happening between
> ntpd and the lockup point.
>
Ian:
> Ian Lepore [i...@freebsd.org] wrote:
> >
> > On my system, a whole lotta stuff happens between ntpd and syscons (the
> > thing that configures blanktime). Try setting rc_debug=YES in rc.conf,
> > that should write more info to syslog about what's happening between
> > ntpd and the lockup
Ian Lepore [i...@freebsd.org] wrote:
>
> On my system, a whole lotta stuff happens between ntpd and syscons (the
> thing that configures blanktime). Try setting rc_debug=YES in rc.conf,
> that should write more info to syslog about what's happening between
> ntpd and the lockup point.
>
The
On Tue, 2019-09-24 at 14:32 -0400, Thomas Laus wrote:
> On 2019-09-24 11:58, Pete Wright wrote:
> >
> > darn, and they didn't give you any additional information in the
> > messages buffer, or generate a core file?
> >
>
> There were no messages in the syslog and no other log that showed
>
On 2019-09-24 11:58, Pete Wright wrote:
>
> darn, and they didn't give you any additional information in the
> messages buffer, or generate a core file?
>
There were no messages in the syslog and no other log that showed
anything after killing the console. On my working BEADM boot
environment,
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
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:
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
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.
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
14 matches
Mail list logo
