11.0-CURRENT panic at (allegedly) a dpms signal (monitor off), in drm2

2013-12-17 Thread Markiyan Kushnir
14:00:~$ uname -a FreeBSD mkushnir.mooo.com 11.0-CURRENT FreeBSD 11.0-CURRENT #1 r259227: Thu Dec 12 10:17:56 EET 2013 r...@mkushnir.mooo.com:/usr/obj/usr/src/sys/MAREK amd64 Left my desktop (new Xorg, newcons, radeonkms) for a couple of minutes and found it rebooted after a panic. Never seen

Re: 11.0-CURRENT panic at (allegedly) a dpms signal (monitor off), in drm2

2013-12-17 Thread Markiyan Kushnir
/var/log/messages (cut out everything before approx an hour before the panic) and Xorg log of the panicked session: https://drive.google.com/file/d/0B9Q-zpUXxqCnX3IzY3BHMGRSVkk/edit?usp=sharing https://drive.google.com/file/d/0B9Q-zpUXxqCna3pfTVl2dWZraTg/edit?usp=sharing -- Markiyan.

Re: 11.0-CURRENT panic at (allegedly) a dpms signal (monitor off), in drm2

2013-12-17 Thread Jean-Sébastien Pédron
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

Re: 11.0-CURRENT panic at (allegedly) a dpms signal (monitor off), in drm2

2013-12-17 Thread Markiyan Kushnir
2013/12/17 Jean-Sébastien Pédron jean-sebastien.ped...@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