From owner-freebsd-bugs@freebsd.org Tue Mar 10 17:43:48 2020 Return-Path: Delivered-To: freebsd-bugs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 5E5D526B4B2 for ; Tue, 10 Mar 2020 17:43:48 +0000 (UTC) (envelope-from portmaster@BSDforge.com) Received: from udns.ultimatedns.net (static-24-113-41-81.wavecable.com [24.113.41.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "ultimatedns.net", Issuer "Let's Encrypt Authority X3" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 48cMry6HBYz3KZX for ; Tue, 10 Mar 2020 17:43:46 +0000 (UTC) (envelope-from portmaster@BSDforge.com) Received: from udns.ultimatedns.net (localhost [IPv6:0:0:0:0:0:0:0:1]) by udns.ultimatedns.net (8.15.2/8.15.2) with ESMTPS id 02AHhIgR056714 (version=TLSv1.2 cipher=DHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Tue, 10 Mar 2020 10:43:31 -0700 (PDT) (envelope-from portmaster@BSDforge.com) X-Mailer: Cypht MIME-Version: 1.0 Cc: In-Reply-To: <8df70772-faee-bd07-612f-696e8a1d477c@andyit.com.au> From: Chris Reply-To: portmaster@BSDforge.com To: Andy Farkas Subject: Re: vt [was: Re: [Bug 235564] INDEX.keymaps for vt contains "from-" keymaps but the files are missing] Date: Tue, 10 Mar 2020 10:43:25 -0700 Message-Id: <943cc5c712026dafa3cf00ed5e437146@udns.ultimatedns.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 48cMry6HBYz3KZX X-Spamd-Bar: + Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of portmaster@BSDforge.com has no SPF policy when checking 24.113.41.81) smtp.mailfrom=portmaster@BSDforge.com X-Spamd-Result: default: False [1.09 / 15.00]; ARC_NA(0.00)[]; HAS_REPLYTO(0.00)[portmaster@BSDforge.com]; XM_UA_NO_VERSION(0.01)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; NEURAL_HAM_MEDIUM(-0.04)[-0.037,0]; IP_SCORE(-0.31)[ip: (-0.48), ipnet: 24.113.0.0/16(-0.24), asn: 11404(-0.76), country: US(-0.05)]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[BSDforge.com]; REPLYTO_ADDR_EQ_FROM(0.00)[]; AUTH_NA(1.00)[]; NEURAL_HAM_LONG(-0.97)[-0.975,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:11404, ipnet:24.113.0.0/16, country:US]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[]; URIBL_XBL(1.50)[goo.gl] X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Mar 2020 17:43:48 -0000 On Tue, 10 Mar 2020 05:14:49 +1000 Andy Farkas andyf@andyit=2Ecom=2Eau said > On 2020-03-10 01:04, Konstantin Belousov wrote: > > Take a look at r334530=2E >=20 >=20 > "or the user really hates this feature and can't wait to turn it off" >=20 >=20 >=20 > Excellently explained by Bruce as usual: >=20 >=20 > "Revision 314641 - (view) (download) (annotate) - [select for diffs] > Modified Sat Mar 4 06:19:12 2017 UTC (3 years ago) by bde > File length: 107771 byte(s) > Diff to previous 312910 > Colorize syscons kernel console output according to a table indexed > by the CPU number=2E >=20 > This was originally for debugging near-deadlock conditions where > multiple CPUs either deadlock or scramble each other's output trying > to report the problem, but I found it interesting and sometimes > useful for ordinary kernel messages=2E=C2=A0 Ordinary kernel messages > shouldn't be interleaved, but if they are then the colorization > makes them readable even if the interleaving is for every character > (provided the CPU printing each message doesn't change)=2E >=20 > The default colors are 8-15 starting at 15 (bright white on black) > for CPU 0 and repeating every 8 CPUs=2E=C2=A0 This works best with 8 CPUs=2E OK the colors are CPU/core bound=2E That explains why initiating the NIC starts on one color, then changes to a *different* color when reporting the status -- the job moved to a *different* CPU/core=2E Annoying! IMHO=2E I guess I'll have to have a look at getting the white/high-intensity-white behavior back=2E A *massive* thanks for all the insight, Andy! --Chris >=20 >=20 >=20 > RIP >=20 >=20 > https://photos=2Eapp=2Egoo=2Egl/YiVmFtWiK8Niy3Fw6 >=20 >=20 > -andyf >=20 >=20 > _______________________________________________ > freebsd-stable@freebsd=2Eorg mailing list > https://lists=2Efreebsd=2Eorg/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd=2Eorg"