Date: Wed, 18 Dec 2013 08:44:46 +0200 From: Markiyan Kushnir <markiyan.kushnir@gmail.com> To: =?ISO-8859-1?Q?Jean=2DS=E9bastien_P=E9dron?= <jean-sebastien.pedron@dumbbell.fr> Cc: freebsd-current@freebsd.org Subject: Re: 11.0-CURRENT panic at (allegedly) a dpms signal (monitor off), in drm2 Message-ID: <CACvtUJfvqwpOLHzD6cL6fW=nSiAdky8YPYsSD2LrM_7nrEN9Yw@mail.gmail.com> In-Reply-To: <52B0C720.4060505@dumbbell.fr> References: <CACvtUJcdNKq_Q_6up274Sc6XHerO4rmwxD3_==gS=Rh-a-kR%2BQ@mail.gmail.com> <52B0C720.4060505@dumbbell.fr>
next in thread | previous in thread | raw e-mail | index | archive | help
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 >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CACvtUJfvqwpOLHzD6cL6fW=nSiAdky8YPYsSD2LrM_7nrEN9Yw>