From owner-freebsd-stable@FreeBSD.ORG Tue Sep 30 06:27:11 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 37F61522 for ; Tue, 30 Sep 2014 06:27:11 +0000 (UTC) Received: from asp.reflexion.net (outbound-242.asp.reflexion.net [69.84.129.242]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C87BE252 for ; Tue, 30 Sep 2014 06:27:09 +0000 (UTC) Received: (qmail 1178 invoked from network); 30 Sep 2014 06:27:08 -0000 Received: from unknown (HELO mail-cs-04.app.dca.reflexion.local) (10.81.19.4) by 0 (rfx-qmail) with SMTP; 30 Sep 2014 06:27:08 -0000 Received: by mail-cs-04.app.dca.reflexion.local (Reflexion email security v7.30.7) with SMTP; Tue, 30 Sep 2014 02:27:08 -0400 (EDT) Received: (qmail 3591 invoked from network); 30 Sep 2014 06:27:08 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (DHE-RSA-AES256-SHA encrypted) SMTP; 30 Sep 2014 06:27:08 -0000 X-No-Relay: not in my network Received: from [192.168.1.8] (c-98-246-178-138.hsd1.or.comcast.net [98.246.178.138]) by iron2.pdx.net (Postfix) with ESMTPSA id 062221C402B for ; Mon, 29 Sep 2014 23:27:00 -0700 (PDT) From: Mark Millard Subject: vt does not resume properly after zzz [related powerpc64/GENERIC64 report?] Message-Id: <525EFCD4-ED16-4A73-A971-B32300B0AAC4@dsl-only.net> Date: Mon, 29 Sep 2014 23:27:03 -0700 To: freebsd-stable@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) X-Mailer: Apple Mail (2.1878.6) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Sep 2014 06:27:11 -0000 On Mon, Sep 29, 2014 at 1:20 PM, wrote: > Hi all, > > I have configured vt by adding `kern.vty=3Dvt' to /boot/loader.conf. > > After suspending the system using zzz and resuming, I can only see = black > screen. The system seem to be running, but the display is off. I was > able to reproduce it on two different computers running 10.1-BETA2 and > 10.1-BETA3. > > Is there a simple way to fix it? Should I report it to Bugzilla? > > Thank you for help! > > Marek > = https://lists.freebsd.org/pipermail/freebsd-ppc/2014-September/007204.html= (from Sept. 13) may be related to this report. It was titled: > For newer XOrg/drivers powerpc64/GENERIC64 for NVIDIA no longer crash = but Option-Fn gets nearly black text on black background Its details were then (some [...] notes added)... > I've updated to ports r368074 which updated Xorg, the drivers, and = even gcc (to 4.8.3). I used portmaster -t -D -a. This was on both... >=20 > FreeBSD FBSDG4S0 10.1-PRERELEASE FreeBSD 10.1-PRERELEASE #0 r271215: = Sat Sep 6 23:56:15 PDT 2014 root at = FBSDG4S0:/usr/obj/usr/src/sys/GENERIC powerpc >=20 > FreeBSD FBSDG5S0 10.1-PRERELEASE FreeBSD 10.1-PRERELEASE #0 r271278: = Mon Sep 8 12:40:56 PDT 2014 root at = FBSDG5S0:/usr/obj/usr/src/sys/GENERIC64 powerpc >=20 > both being booted on Quad Core G5 PowerMacs with the GeForce 7800 GT's = to update and rebooted to test. (Both of these SSDs are builds for = WITH_DEBUG_FILES=3D and WITHOUT_CLANG=3D and WITH_DEBUG=3D in = /etc/make.conf.) >=20 > The powerpc/GENERIC worked find for Option-Fn use. >=20 > The powerpc64/GENERIC64 appeared to have the black screen issue. = [Prior versions had a crash that left the screen black and this wording = refers to that older context where the server was quitting and a core = was being left behind.] But... >=20 > ... I noticed something for powerpc64/GENERIC64 due to the lighting = being different than earlier [where I had assumed that the crash was = still present]: >=20 > Option-Fn is(!) displaying the VTn display but just extremely faintly: = instead of the text being a fairly bright white against a black = background for powerpc64/GENERIC64 the text is nearly the same black = color as the background. But it is slightly lighter and in properly set = up conditions I can read it. (It may be monitor dependent on if there is = enough of a difference to actually see it that well.) Option-F9 gets = back to xfce4's display just fine too. >=20 > The powerpc64/GENERIC64 Xorg crash is gone as of this update. [Again = referring to the older version's crash problem on PowerMacs.] >=20 > I've not tried other contexts yet. (Such as NVIDIA GeForce4 Ti 4600 on = a PowerMac G4.) >=20 >=20 > Side notes: >=20 > Because historically I've had lots of problems with gcc = (re)builds/updates on powerpc or powerpc64 otherwise, I have the = full-bootstrap option enabled for building lang/gcc. >=20 > The only reason [that I] use WITHOUT_CLANG=3D is because I get = failures otherwise when WITH_DEBUG_FILES=3D is enabled. Specifically: = ... /libclangsema.a(SemaAccess.o): Unknown relocation type ????? for = symbol *UND* powerpc/GENERIC was then and is now still syscons by default. = powerpc64/GENERIC64 for .../stable/10/sys/powerpc/conf/GENERIC64 = switched to vt as the default on Sept. 4 (r271111 MFC'd r265871). At the = time I had not noticed the changed status and so was incorrectly = thinking syscons throughout the note. =3D=3D=3D Mark Millard markmi at dsl-only.net