vt [was: Re: [Bug 235564] INDEX.keymaps for vt contains "from-" keymaps but the files are missing]

[Chris]

On Tue, 10 Mar 2020 05:14:49 +1000 Andy Farkas andyf at andyit.com.au said

> On 2020-03-10 01:04, Konstantin Belousov wrote:
> > Take a look at r334530.
> 
> 
> "or the user really hates this feature and can't wait to turn it off"
> 
> 
> 
> Excellently explained by Bruce as usual:
> 
> 
> "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.
> 
> 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.  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).
> 
> The default colors are 8-15 starting at 15 (bright white on black)
> for CPU 0 and repeating every 8 CPUs.  This works best with 8 CPUs.
OK the colors are CPU/core bound. 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.
Annoying! IMHO. I guess I'll have to have a look at getting the
white/high-intensity-white behavior back.

A *massive* thanks for all the insight, Andy!

--Chris
> 
> 
> 
> RIP
> 
> 
> https://photos.app.goo.gl/YiVmFtWiK8Niy3Fw6
> 
> 
> -andyf
> 
> 
> _______________________________________________
> freebsd-stable at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe at freebsd.org"