drm-current-kmod-4.16.g20190424 hangs

[Johannes Lundberg]

Hi

Hmm, this is not good. The only thing I can think of is the dma changes
to base linuxkpi...

Can you share a dmesg output from boot to crash, or at least to after
driver is loaded?

Tycho, any ideas?


On 4/26/19 5:00 AM, Jakob Alvermark wrote:
> Hi,
>
>
> When I upgraded -current to r346730 drm-current-kmod-4.16.g20190323
> wouldn't load, "device_attach: drmn0 attach returned 19"
>
> So I upgraded drm-current-kmod to 4.16.g20190424.
>
> It loads fine, but shortly after starting Xorg the screen freezes.
>
> The only way out is pressing the power button, it shuts down cleanly.
>
> /var/log/messages shows this:
>
> kernel: [drm] GPU HANG: ecode 7:0:0x60ac6ee9, in Xorg [100385],
> reason: Hang on rcs0, action: reset
> kernel: drmn0: Resetting chip after gpu hang
> syslogd: last message repeated 1 times
> kernel: drmn0: i915_reset_device timed out, cancelling all in-flight
> rendering.
> kernel: .
>
> Tried once more, same thing happened:
>
> kernel: [drm] GPU HANG: ecode 7:0:0x86f2fffd, in Xorg [100491],
> reason: Hang on rcs0, action: reset
> kernel: drmn0: Resetting chip after gpu hang
> syslogd: last message repeated 1 times
> kernel: drmn0: i915_reset_device timed out, cancelling all in-flight
> rendering.
> kernel: .
>
> Reverting back to drm-current-kmod-4.16.g20190323 and -current to
> r346593 (yay boot environments!) it is stable.
>
> This is on a laptop with CPU: Intel(R) Pentium(R) CPU  N3540  @
> 2.16GHz (2166.72-MHz K8-class CPU)
> Baytrail graphics.
>
>
> Jakob
>
> _______________________________________________
> freebsd-x11 at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-x11
> To unsubscribe, send any mail to "freebsd-x11-unsubscribe at freebsd.org"