Recent -current cpucontrol panic: [cpuctl, 129]: cannot bind to target cpu 1

With microcode_update_enable="YES" in rc.conf: db:0:kdb.enter.panic> show pcpu cpuid= 1 dynamic pcpu = 0xfe02ac1fd300 curthread= 0xf8000ae75a00: pid 736 "cpucontrol" curpcb = 0xfe023754eb80 fpcurthread = none idlethread = 0xf800022b5000: tid 13 "idle: cpu1

Jenkins build is back to normal : FreeBSD_HEAD_sparc64 #79

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

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

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: 300

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

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" > > > configured, IPFW > > > active (I have IPFW

FreeBSD_HEAD_i386 - Build #3176 - Still Failing

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 summari

Build failed in Jenkins: FreeBSD_HEAD #302

See -- [...truncated 57442 lines...] --- all_subdir_gnu/usr.bin/binutils/libbinutils --- --- rename.o --- cc -O2 -pipe -DBFD_DEFAULT_TARGET_SIZE=64 -I. -I/builds/workspace/FreeBSD_HEAD/src/gnu/usr.bin/bin

Re: newcons splash screen

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 up

FreeBSD_HEAD_i386 - Build #3175 - Still Failing

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 summari

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

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 > > /usr/src > > as

Build failed in Jenkins: FreeBSD_HEAD #301

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 -I/b

Re: em(4) broken in HEAD?

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, May 20, 2016 at

FreeBSD_HEAD_i386 - Build #3174 - Still Failing

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 summari

Re: em(4) broken in HEAD?

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 as of the last d

AHCI/ADA regression?

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, 0xfb00-0xfb0f