From owner-freebsd-current@FreeBSD.ORG  Wed Dec 18 06:44:48 2013
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 26AD2B9D
 for <freebsd-current@freebsd.org>; Wed, 18 Dec 2013 06:44:48 +0000 (UTC)
Received: from mail-wi0-x232.google.com (mail-wi0-x232.google.com
 [IPv6:2a00:1450:400c:c05::232])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id B32C51AC0
 for <freebsd-current@freebsd.org>; Wed, 18 Dec 2013 06:44:47 +0000 (UTC)
Received: by mail-wi0-f178.google.com with SMTP id bz8so147526wib.5
 for <freebsd-current@freebsd.org>; Tue, 17 Dec 2013 22:44:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :cc:content-type:content-transfer-encoding;
 bh=2Kg1FFTbJvZar/c1CV++tRAuPfWL6bQYk38I5opa57s=;
 b=X4gEOBa/cHkeEyKDawom4NdjP2I4WJx131uqN+CmSk4ZwU6Aow4KVpNsRWTfCw0Hig
 rJ6jpwFA/YyHnlfmP1YdqWLE4DfmGJ7NWpham+6rJGWddZTpCiL1tWd7FR2M9KSUZwBH
 iJnsk8UUOahtxHL/YG1CJ7zIRAXPGtEfK/37AG9fZRA4ptsmlUlWswOI8njuYJ3SyZFA
 DxCAF8H1gescyQwkmbHT475oNvKe+hTRZEWoX/PQQv0LxscG712uj35nIrpeG/NYU5OL
 wgcsIvectg9JP4yBHFfEHPW88w4c2Ma/3psWb819pxA8tvQmCVYHbOJ36uwn+c1pO9+N
 Homg==
MIME-Version: 1.0
X-Received: by 10.180.108.97 with SMTP id hj1mr6440353wib.59.1387349086156;
 Tue, 17 Dec 2013 22:44:46 -0800 (PST)
Received: by 10.227.226.12 with HTTP; Tue, 17 Dec 2013 22:44:46 -0800 (PST)
In-Reply-To: <52B0C720.4060505@dumbbell.fr>
References: <CACvtUJcdNKq_Q_6up274Sc6XHerO4rmwxD3_==gS=Rh-a-kR+Q@mail.gmail.com>
 <52B0C720.4060505@dumbbell.fr>
Date: Wed, 18 Dec 2013 08:44:46 +0200
Message-ID: <CACvtUJfvqwpOLHzD6cL6fW=nSiAdky8YPYsSD2LrM_7nrEN9Yw@mail.gmail.com>
Subject: Re: 11.0-CURRENT panic at (allegedly) a dpms signal (monitor off),
 in drm2
From: Markiyan Kushnir <markiyan.kushnir@gmail.com>
To: =?ISO-8859-1?Q?Jean=2DS=E9bastien_P=E9dron?=
 <jean-sebastien.pedron@dumbbell.fr>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: freebsd-current@freebsd.org
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://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: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Dec 2013 06:44:48 -0000

2013/12/17 Jean-S=E9bastien P=E9dron <jean-sebastien.pedron@dumbbell.fr>:
> On 17.12.2013 13:19, Markiyan Kushnir wrote:
>> Left my desktop (new Xorg, newcons, radeonkms) for a couple of minutes
>> and found it rebooted after a panic. Never seen this kind of panic
>> before.
>
> That's weird: the code leading to this panic in unreachable, because
> there's no way currently (that I know of) to change the power management
> method of the driver to "dynamic".
>
> Can you reproduce the problem?
>
> If it helps, you can force your monitor off using xset(1):
> xset dpms force off
>

No, I cannot reproduce it reliably. I've tried switching the monitor
off for a while using xset, no luck. I will let you know once I have
more info on it.

--
Markiyan.


> --
> Jean-S=E9bastien P=E9dron
>