Date: Sat, 27 Jun 2020 15:23:29 -0700 From: Chris <bsd-lists@BSDforge.com> To: FreeBSD CURRENT <freebsd-current@freebsd.org> Cc: Michael Gmelin <freebsd@grem.de> Subject: Re: weird Ctrl-T debug messages Message-ID: <a1c18042cb1bc2c1a24ef14c4e74b502@udns.ultimatedns.net> In-Reply-To: <20200627115910.4fe32aa6@bsd64.grem.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 27 Jun 2020 11:59:10 +0200 Michael Gmelin freebsd@grem=2Ede said > On Sat, 27 Jun 2020 12:06:17 +0300 > Andriy Gapon <avg@FreeBSD=2Eorg> wrote: >=20 > > On 27/06/2020 10:44, Li-Wen Hsu wrote: > > > On Sat, Jun 27, 2020 at 3:04 PM Hartmann, O=2E > > > <ohartmann@walstatt=2Eorg> wrote: =20 > > >> > > >> Running poudriere on recent CURRENT with (recent) 12-STABLE and > > >> CURRENT jails reveals a weird behaviour recently when hitting > > >> Ctrl-T: =20 > > > =2E=2E=2E =20 > > >> Is this debug fallout from /bin/sh? =20 > > >=20 > > > It's because kern=2Etty_info_kstacks is on by default now: > > >=20 > > > https://svnweb=2Efreebsd=2Eorg/changeset/base/362141 =20 > >=20 > > May I suggest that the stack trace is printed procstat -kk style > > (single line) ? I think that the more compact output would be more > > convenient=2E >=20 > It's a cool feature and having it on by default on CURRENT certainly > helps to discover it, which is great=2E Thanks for implementing this! >=20 > I wouldn't enable it by default on RELEASE versions though, as CTRL-T > is a user interface to get status information (at least this is how I > use it personally, e=2Eg=2E, while running commands like dd[0], cp, mv, > poudriere etc=2E), not for getting debug output=2E >=20 > Getting debug information every time I want to get the status seems > like something that would make my user experience worse=2E I understand > that this can be disabled locally, but that's a bit like changing > the default syslog=2Econf to write messages of log level LOG_DEBUG > to /var/log/messages=2E >=20 > So, in the long run (before 13-RELEASE) I would prefer to disable it by > default again, but maybe alter the default sysctl=2Econf to contain: >=20 > # Uncomment this to show stack traces on SIGINFO (ctrl-t) > #kern=2Etty_info_kstacks=3D1 >=20 > Question: Speaking of discovering the feature, wouldn't it make sense > to document this tunable on the stack(9) and/or tty(4) man page(s)? >=20 > Just my 2 cents A huge +1 here=2E I think you captured it well, Michael=2E Thanks=2E --Chris >=20 > [0] Typical use case: >=20 > $ dd if=3D/dev/random of=3D/dev/da0 bs=3D1m > <presses CTRL-T> > load: 0=2E37 cmd: dd 32247 [running] 0=2E91r 0=2E00u 0=2E88s 8% 2672k > 149+0 records in > 149+0 records out > 156237824 bytes transferred in 0=2E922956 secs (169279818 bytes/sec) > <presses CTRL-T again> > load: 0=2E42 cmd: dd 32247 [running] 2=2E52r 0=2E00u 2=2E46s 21% 2676k > 398+0 records in > 398+0 records out > 417333248 bytes transferred in 2=2E528253 secs (165067835 bytes/sec) > =2E=2E=2E >=20 > --=20 > Michael Gmelin > _______________________________________________ > freebsd-current@freebsd=2Eorg mailing list > https://lists=2Efreebsd=2Eorg/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd=2Eorg= "
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a1c18042cb1bc2c1a24ef14c4e74b502>