From owner-freebsd-x11@FreeBSD.ORG Thu Oct 31 16:35:50 2013 Return-Path: Delivered-To: freebsd-x11@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 7E4F1C88 for ; Thu, 31 Oct 2013 16:35:50 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-pd0-x232.google.com (mail-pd0-x232.google.com [IPv6:2607:f8b0:400e:c02::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 5A1DA2D89 for ; Thu, 31 Oct 2013 16:35:50 +0000 (UTC) Received: by mail-pd0-f178.google.com with SMTP id x10so2598673pdj.23 for ; Thu, 31 Oct 2013 09:35:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to:content-type; bh=SnSqpLP/1L6+6vVJdVgTeXsGApunA2t2STHxuHyycL8=; b=OxQ4boA4vr1hqeKpfbBfXxwrscxSsUPROpBGo1ebmiukIFGvYpfVY2gn5e0PTNLLOK S2qnGD5ZUvhs66nGjRW+TJ4lF9vTV8SYyQ1+StJmPM5lIQRksaFmo76ZqJIku1d1D1/W WfvLxflSBngMAHxK+AY+v3tupn7b3N3jRtsdfS1pURqiHCiRZex+A/elA+KHsfE1WFs7 69d1wZnR1LXEEBQa6wLJV9vFOpn9iJjH7yht47y31X+xTwPf2V/P7PfJCQWpjkPCRfNV a5eUCbqj3ds85aE2USoG4MRNgfcbddwomTw9rwXPuemsCmW/Lo/ZSw9DsuHvhJzisEga izmg== MIME-Version: 1.0 X-Received: by 10.68.224.38 with SMTP id qz6mr2800984pbc.156.1383237349941; Thu, 31 Oct 2013 09:35:49 -0700 (PDT) Sender: kob6558@gmail.com Received: by 10.67.23.101 with HTTP; Thu, 31 Oct 2013 09:35:49 -0700 (PDT) Date: Thu, 31 Oct 2013 09:35:49 -0700 X-Google-Sender-Auth: jZniqUN8KcP9J-Aj_duadW3z0uQ Message-ID: Subject: Odd Intel KMS behavior when attempting X restart From: Kevin Oberman To: "freebsd-x11@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Oct 2013 16:35:50 -0000 This may prove to be of no value, but it might tickle some ideas, so I am posting an almost data free problem. Sorry. Yesterday I made a small mistake and mounted a device (Kindle) in s directory gamin was monitoring so that I could not unmount it. I thought I would just logout of Gnome, ssh in from my phone, unmount the device, and "startx". Seemed reasonable and not different from other X11 restarts in the current syscons world. My enviroment: FreeBSD 9-stable r256657 on a Lenovo T520 Thinkpad without Optimus. Running WITH_NEW_XORG and WITH_KMS. I logged out of Gnome. Screen blanked, as usual. While I was busy elsewhere (logging into my system from my phone is a bit tedious), the screen suddenly flashes fo display a bunch of diagonal lines, mostly red with a few white pixels. Wha??? As soon as I pressed a key, the console appeared complete with my shell prompt! I was back to a functioning vty. As far as I know, this is simply not possible, but I it happened. I entered a few commands and everything seemed "normal", so I tried starting Gnome. No joy, The screen blanked, but I never got a cursor or anything else. Used my network connection to enter a shutdown and rebooted. Any idea how this could have happened? While I'm looking forward to newcons to get vtys working again, it looks like something timing out, probably screensaver, managed to trigger a reset of the graphics and get a functioning display. It's ALMOST like syscons could be made to work with Intel KMS. -- R. Kevin Oberman, Network Engineer E-mail: rkoberman@gmail.com