A head buildworld race visible in the ci.freebsd.org build history

2018-06-15 Thread Mark Millard
In watching ci.freebsd.org builds I've seen a notable number of one time failures, such as (example from powerpc64): --- all_subdir_lib/libufs --- ranlib -D libufs.a ranlib: fatal: Failed to open 'libufs.a' *** [libufs.a] Error code 70 where the next build works despite the change being

Re: swapping is completely broken in -CURRENT r334649?

2018-06-15 Thread Mark Linimon
On Fri, Jun 15, 2018 at 11:14:40AM +0200, Mikaël Urankar wrote: > Last time I tried (2 weeks ago) qemu-ppc64-static was broken, not sure the > situation has evolved since that. I've been told by more than one person that it works, but the 2? 3? times I've tried it it just hung. I have real

Re: Resume without drm driver results in black screen

2018-06-15 Thread John Baldwin
On 5/17/18 3:01 AM, Johannes Lundberg wrote: > Hi > > I revived this old bug > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213501 > > Considering this also affects all X users using scfb driver it's worth > investigating. It's just not doable. You need some sort of driver for the GPU

Re: kgdb crashing on a vmcore with dumptid = 0

2018-06-15 Thread John Baldwin
On 5/4/18 10:49 PM, Eitan Adler wrote: > gdb$ bt > #0 thr_kill () at thr_kill.S:3 > #1 0x0008035046b4 in __raise (s=0x6) at /usr/src/lib/libc/gen/raise.c:54 > #2 0x000803504629 in abort () at /usr/src/lib/libc/stdlib/abort.c:67 > #3 0x00c805c6 in dump_core () at utils.c:284 >

review of nfsd rc.d script patch

2018-06-15 Thread Rick Macklem
Hi, For the pNFS service MDS machine, the nfsd can't be started until all nfs mounts in /etc/fstab are done. I think that adding "mountcritremote" to the "# REQUIRE:" line is sufficient to do this? I don't think delaying the startup of the nfsd daemon until after any NFS mounts are done will do

Re: freebsd bhyve instance does not show kernel messages after boot screen

2018-06-15 Thread Rodney W. Grimes
> On 14/06/2018 23:26, David P. Discher wrote: > > Try in /boot/loader.conf of the VM : > > > > console=userboot > > > > or after beastie drop to loader OK promot ?and try : > > > > set console=userboot > > > > I think 11.x should fall back to userboot in?bhyve if vidconsole of > > comconsole

Re: swapping is completely broken in -CURRENT r334649?

2018-06-15 Thread Kevin Lo
On Fri, Jun 15, 2018 at 04:40:22AM -0400, Mark Johnston wrote: > > On Fri, Jun 15, 2018 at 01:10:25PM +0800, Kevin Lo wrote: > > On Tue, Jun 05, 2018 at 05:48:08PM -0400, Mark Johnston wrote: > > > > > > On Wed, Jun 06, 2018 at 12:22:08AM +0300, Lev Serebryakov wrote: > > > > On 05.06.2018

Re: freebsd bhyve instance does not show kernel messages after boot screen

2018-06-15 Thread tech-lists
On 14/06/2018 23:26, David P. Discher wrote: Try in /boot/loader.conf of the VM : console=userboot or after beastie drop to loader OK promot  and try : set console=userboot I think 11.x should fall back to userboot in bhyve if vidconsole of comconsole were set. (This is assuming non-EFI

Re: swapping is completely broken in -CURRENT r334649?

2018-06-15 Thread Kurt Jaeger
Hi! > > I just started it again, and after a while the qemu-ppc64-static > > was at approx. 23 GB memory and increasing, without much progress. > Last time I tried (2 weeks ago) qemu-ppc64-static was broken, not sure the > situation has evolved since that. Ok, thanks! Then it's not the same

Re: Help USB keyboard trouble

2018-06-15 Thread Hans Petter Selasky
On 06/15/18 08:45, Alex V. Petrov wrote: Hans Petter! What can you say about my problem? Hi, I didn't have time to look into this. --HPS ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To

Re: swapping is completely broken in -CURRENT r334649?

2018-06-15 Thread Mikaël Urankar
Le ven. 15 juin 2018 à 11:10, Kurt Jaeger a écrit : > Hi! > > > > > The change was committed as r334752. Are you seeing unexpected OOM > > > > kills on or after that revision? > > > > > > When I tried to run a qemu-based poudriere run yesterday on a r334918 > > > box, it killed a few processes

Re: swapping is completely broken in -CURRENT r334649?

2018-06-15 Thread Mark Johnston
On Fri, Jun 15, 2018 at 11:07:34AM +0200, Kurt Jaeger wrote: > Hi! > > > > > The change was committed as r334752. Are you seeing unexpected OOM > > > > kills on or after that revision? > > > > > > When I tried to run a qemu-based poudriere run yesterday on a r334918 > > > box, it killed a few

Re: swapping is completely broken in -CURRENT r334649?

2018-06-15 Thread Kurt Jaeger
Hi! > > > The change was committed as r334752. Are you seeing unexpected OOM > > > kills on or after that revision? > > > > When I tried to run a qemu-based poudriere run yesterday on a r334918 > > box, it killed a few processes outside of that run and did not > > work out. > > > > I'm unsure

Re: swapping is completely broken in -CURRENT r334649?

2018-06-15 Thread Mark Johnston
On Fri, Jun 15, 2018 at 10:48:08AM +0200, Kurt Jaeger wrote: > Hi! > > > The change was committed as r334752. Are you seeing unexpected OOM > > kills on or after that revision? > > When I tried to run a qemu-based poudriere run yesterday on a r334918 > box, it killed a few processes outside of

Re: swapping is completely broken in -CURRENT r334649?

2018-06-15 Thread Kurt Jaeger
Hi! > The change was committed as r334752. Are you seeing unexpected OOM > kills on or after that revision? When I tried to run a qemu-based poudriere run yesterday on a r334918 box, it killed a few processes outside of that run and did not work out. I'm unsure it was because of that problem

Re: swapping is completely broken in -CURRENT r334649?

2018-06-15 Thread Mark Johnston
On Fri, Jun 15, 2018 at 01:10:25PM +0800, Kevin Lo wrote: > On Tue, Jun 05, 2018 at 05:48:08PM -0400, Mark Johnston wrote: > > > > On Wed, Jun 06, 2018 at 12:22:08AM +0300, Lev Serebryakov wrote: > > > On 05.06.2018 19:17, Gary Jennejohn wrote: > > > > > > > > > > I complained about this also

Re: Help USB keyboard trouble

2018-06-15 Thread Alex V. Petrov
Hans Petter! What can you say about my problem? 09.05.2018 18:31, Alex V. Petrov пишет: > 09.05.2018 14:08, Hans Petter Selasky пишет: >> On 05/09/18 05:52, Alex V. Petrov wrote: >>> The new USB-keyboard "Qumo Dragon War Mechanicus K11" continues to print >>> "A" when connected, as if the "a" key