Jenkins build is back to normal : FreeBSD_HEAD_sparc64 #79

2016-05-21 Thread jenkins-admin
See ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Jenkins build is back to normal : FreeBSD_HEAD #303

2016-05-21 Thread jenkins-admin
See ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

FreeBSD_HEAD_i386 - Build #3177 - Fixed

2016-05-21 Thread jenkins-admin
FreeBSD_HEAD_i386 - Build #3177 - Fixed: Build information: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/3177/ Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/3177/changes Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/3177/console Change summaries:

Re: CURRENT: ipfw: problems with timeouts and worse network performance

2016-05-21 Thread O. Hartmann
Am Sat, 21 May 2016 12:28:42 +0200 "O. Hartmann" schrieb: > Am Fri, 20 May 2016 17:41:39 +0300 > "Andrey V. Elsukov" schrieb: > > > On 20.05.16 17:23, O. Hartmann wrote: > > > The problem is simpel to trigger: have firewall type "WORKSTATION"

FreeBSD_HEAD_i386 - Build #3176 - Still Failing

2016-05-21 Thread jenkins-admin
FreeBSD_HEAD_i386 - Build #3176 - Still Failing: Build information: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/3176/ Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/3176/changes Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/3176/console Change

Build failed in Jenkins: FreeBSD_HEAD #302

2016-05-21 Thread jenkins-admin
See -- [...truncated 57442 lines...] --- all_subdir_gnu/usr.bin/binutils/libbinutils --- --- rename.o --- cc -O2 -pipe -DBFD_DEFAULT_TARGET_SIZE=64 -I.

Re: newcons splash screen

2016-05-21 Thread Thomas Mueller
Is the newcons nonsupport for console screensaver related to the nonsupport for newcons splash screen? Situation is the same in NetBSD 7.0_RELEASE and STABLE, and current/head, no support for screensaver. DRMKMS is NetBSD's equivalent/counterpart of FreeBSD's newcons. Boot to console comes

FreeBSD_HEAD_i386 - Build #3175 - Still Failing

2016-05-21 Thread jenkins-admin
FreeBSD_HEAD_i386 - Build #3175 - Still Failing: Build information: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/3175/ Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/3175/changes Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/3175/console Change

Re: CURRENT: ipfw: problems with timeouts and worse network performance

2016-05-21 Thread O. Hartmann
Am Fri, 20 May 2016 17:41:39 +0300 "Andrey V. Elsukov" schrieb: > On 20.05.16 17:23, O. Hartmann wrote: > > The problem is simpel to trigger: have firewall type "WORKSTATION" > > configured, IPFW > > active (I have IPFW statically in-kernel-compiled, no modules so far). Have

Build failed in Jenkins: FreeBSD_HEAD #301

2016-05-21 Thread jenkins-admin
See -- [...truncated 56789 lines...] --- all_subdir_gnu/usr.bin/binutils/as --- --- sb.o --- cc -O2 -pipe -DBFD_DEFAULT_TARGET_SIZE=64 -I. -I/builds/workspace/FreeBSD_HEAD/src/gnu/usr.bin/binutils/as

Re: em(4) broken in HEAD?

2016-05-21 Thread Chagin Dmitry
On Sat, May 21, 2016 at 02:00:09AM -0700, K. Macy wrote: > Much to my chagrin, this too is my fault. Please apply the attached > patch if it hasn't yet been committed to -CURRENT. > thanks, it fixes em for me. > On Fri, May 20, 2016 at 11:28 PM, Joel Dahl wrote: > > On Fri,

FreeBSD_HEAD_i386 - Build #3174 - Still Failing

2016-05-21 Thread jenkins-admin
FreeBSD_HEAD_i386 - Build #3174 - Still Failing: Build information: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/3174/ Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/3174/changes Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/3174/console Change

Re: em(4) broken in HEAD?

2016-05-21 Thread K. Macy
Much to my chagrin, this too is my fault. Please apply the attached patch if it hasn't yet been committed to -CURRENT. On Fri, May 20, 2016 at 11:28 PM, Joel Dahl wrote: > On Fri, May 20, 2016 at 07:32:30PM -0700, K. Macy wrote: >> I'm seeing watchdog resets on em(4) in my VMWare

AHCI/ADA regression?

2016-05-21 Thread Gary Jennejohn
There appears to be a regression in AHCI/ADA behavior since r300207. Starting a test kernel at r300293 results in extremely long timeouts probing ahcich2 for non-existent multiplier ports. Here some kernel output: ahci0: port 0xff00-0xff07,0xfe00-0xfe03,0xfd00-0xfd07,0xfc00-0xfc03,

ATA? related trouble with r300299

2016-05-21 Thread Oleg V. Nauman
I have faced the issue with fresh CURRENT stopped to boot on my old desktop after update to r300299 Verbose boot shows the endless cycle of ata2: SATA reset: ports status=0x05 ata2: reset tp1 mask=03 ostat0=50 ostat1=50 ata2: stat0=0x50 err=0x01 lsb=0x00 msb=0x00 ata2: stat1=0x50 err=0x01

Re: em(4) broken in HEAD?

2016-05-21 Thread Joel Dahl
On Fri, May 20, 2016 at 07:32:30PM -0700, K. Macy wrote: > I'm seeing watchdog resets on em(4) in my VMWare as of the last day or two. > > > > > > > I don't use ipfw, aliases or anything other than stock networking. I > > was unable to copy a large image off the VM without getting an > > unending