Re: vt(4) chops off the leftmost three columns

> On Jan 12, 2017, at 18:13, Ed Maste wrote: > > On 12 January 2017 at 18:50, Alan Somers wrote: >> I've seen three separate machines where FreeBSD11's vt(4) driver chops >> off the leftmost three columns of the screen. Rendering simply starts >> at

Re: vt(4) chops off the leftmost three columns

On 12 January 2017 at 18:50, Alan Somers wrote: > I've seen three separate machines where FreeBSD11's vt(4) driver chops > off the leftmost three columns of the screen. Rendering simply starts > at the beginning of the fourth column. In all cases, setting > "kern.vty=sc"

Re: vt(4) chops off the leftmost three columns

Alan Somers wrote: I've seen three separate machines where FreeBSD11's vt(4) driver chops off the leftmost three columns of the screen. Rendering simply starts at the beginning of the fourth column. In all cases, setting "kern.vty=sc" corrects the problem. The three different systems are: 1)

TSC as timecounter makes system lag

Hi all, since 2 or 3 weeks ago, I noticed that my old Penryn-based Intel Pentium T4200 notebook lagged a lot. System time was running a lot slower, sometimes even looked like it freezed. Keystroke repeat rate was slow too. Since system time is slow, I tried to change timecounter from default TSC

vt(4) chops off the leftmost three columns

I've seen three separate machines where FreeBSD11's vt(4) driver chops off the leftmost three columns of the screen. Rendering simply starts at the beginning of the fourth column. In all cases, setting "kern.vty=sc" corrects the problem. The three different systems are: 1) Haswell CPU with

build world broken on r311461

Broken on camcontrol clang -O2 -pipe -DRESCUE -MD -MF.depend.camcontrol.o -MTcamcontrol.o -std=gn u99 -fstack-protector-strong -Wsystem-headers -Werror -Wall -Wno-format-y2k -W - Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -W return-type -Wcast-qual

Re: r311568 makes freerdp very slow

On Thursday, January 12, 2017 12:42:11 PM Shawn Webb wrote: > On Thu, Jan 12, 2017 at 06:05:08PM +0100, Jakob Alvermark wrote: > > Hi, > > > > r311568 Set MORETOCOME for AIO write requests on a socket. > > > > After this commit freerdp is very slow. > > > > Before the password prompt would

Re: r311568 makes freerdp very slow

On Thu, Jan 12, 2017 at 06:05:08PM +0100, Jakob Alvermark wrote: > Hi, > > r311568 Set MORETOCOME for AIO write requests on a socket. > > After this commit freerdp is very slow. > > Before the password prompt would appear immediately when connecting to a > server. Now it takes 5-10 seconds.

r311568 makes freerdp very slow

Hi, r311568 Set MORETOCOME for AIO write requests on a socket. After this commit freerdp is very slow. Before the password prompt would appear immediately when connecting to a server. Now it takes 5-10 seconds. After entering the password, another 5-10 seconds until I am connected. Once

Re: CURRENT: em0 NIC freezes under heavy I/O on net

On 01/11/17 01:27, O. Hartmann wrote: > Running recent CURRENT (FreeBSD 12.0-CURRENT #5 r311919: Wed Jan 11 08:24:28 > CET 2017 amd64), the system freezes when doing a rsync over automounted > (autofs) NFSv4 filesystem, mounted from another CURRENT server (same revision, > but with BCM NICs). >

r311977: kernel build failure when NANDFS in kernel

On r311977, buildkernel fails with the error shown below. Kernel ist customised and "options NANDFS" has been added as well as "device nand" - the error shown suggest that is has to do with NANDFS. [...] ===> cc/cc_cdg (all) --- nand_geom.o --- /usr/src/sys/dev/nand/nand_geom.c:419:2: error:

FreeBSD_HEAD_amd64_gcc - Build #1761 - Fixed

FreeBSD_HEAD_amd64_gcc - Build #1761 - Fixed: Build information: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_amd64_gcc/1761/ Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_amd64_gcc/1761/changes Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_amd64_gcc/1761/console