From owner-freebsd-current@freebsd.org  Thu May 31 07:29:09 2018
Return-Path: <owner-freebsd-current@freebsd.org>
Delivered-To: freebsd-current@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 49B58FC916C
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Thu, 31 May 2018 07:29:09 +0000 (UTC) (envelope-from hps@selasky.org)
Received: from mail.turbocat.net (turbocat.net [88.99.82.50])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id D643174C27;
 Thu, 31 May 2018 07:29:08 +0000 (UTC) (envelope-from hps@selasky.org)
Received: from hps2016.home.selasky.org (unknown [62.141.128.70])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (No client certificate requested)
 by mail.turbocat.net (Postfix) with ESMTPSA id E4CAB260338;
 Thu, 31 May 2018 09:29:05 +0200 (CEST)
Subject: Re: [RFC] Deprecation and removal of the drm2 driver
To: "O. Hartmann" <ohartmann@walstatt.org>
Cc: "Rodney W. Grimes" <freebsd-rwg@pdx.rh.CN85.dnsmgr.net>,
 Glen Barber <gjb@FreeBSD.org>, Philip Homburg <pch-fbsd-1@u-1.phicoh.com>,
 "K. Macy" <kmacy@FreeBSD.org>, "A. Wilcox" <AWilcox@wilcox-tech.com>,
 FreeBSD Current <freebsd-current@FreeBSD.org>, Ed Maste <emaste@freebsd.org>
References: <20180524160234.GD68014@FreeBSD.org>
 <201805241610.w4OGAAGY041280@pdx.rh.CN85.dnsmgr.net>
 <20180530235156.310870d0@thor.intern.walstatt.dynvpn.de>
From: Hans Petter Selasky <hps@selasky.org>
Message-ID: <24a94651-f516-485d-36f4-0937824ca3d7@selasky.org>
Date: Thu, 31 May 2018 09:28:52 +0200
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101
 Thunderbird/52.8.0
MIME-Version: 1.0
In-Reply-To: <20180530235156.310870d0@thor.intern.walstatt.dynvpn.de>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 31 May 2018 07:29:09 -0000

On 05/30/18 23:51, O. Hartmann wrote:
> Loading graphics/drm-stable-kmod as requested (via rc.conf.local) ends up in a trap
> 12/crash. Very nice for such an old hardware. graphics/drm-next-kmod does load without
> crashing the system - but the console is stuck in the clumsy 80x25 mode.
> 
> So why should I vote for non-working drivers to replace perfectly working ones?

Usually the crashes you get are low hanging fruit. Why not get the 
backtrace and resolve the crash? It should take less than 10 minutes.

--HPS