Build failed in Jenkins: FreeBSD_HEAD #304

See -- [...truncated 325077 lines...] [192.168.10.2] out: usr.bin/tr/legacy_test:main -> passed [0.091s] [192.168.10.2] out: usr.bin/join/legacy_test:main -> passed [0.033s] [192.168.10.2] out: usr.bi

Re: What builds go to snapshots?

On 2016-05-22 23:33, Sergey Manucharian wrote: > Is there any materialistic definition of those builds, which > become snapshots at [0]? > > - Sergey > > [0] ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/11.0/ > > ___ > freebsd-current@freebsd

What builds go to snapshots?

Is there any materialistic definition of those builds, which become snapshots at [0]? - Sergey [0] ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/11.0/ ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/free

Re: Interesting error during installworld

On Sun, May 22, 2016 at 04:02:43PM -0700, Conrad Meyer wrote: > FreeBSD has tail(1). Does HardenedBSD remove it? Or is /usr/bin > missing from your PATH? > I noticed this with a straight vanilla FreeBSD build/install, but have been busy with "other things" today. It appears to me that the

Re: Interesting error during installworld

FreeBSD has tail(1). Does HardenedBSD remove it? Or is /usr/bin missing from your PATH? On Sun, May 22, 2016 at 1:21 PM, Shawn Webb wrote: > Hey All, > > I’m getting this error when doing `make installworld` on recent builds of > HEAD. It seems that the error is non-critical as installworld do

Re: Interesting error during installworld

HardenedBSD has it and it’s in /usr/bin. The only utilities that aren’t compiled by default in HardenedBSD are freebsd-update and portsnap. Thanks, Shawn Webb Cofounder and Security Engineer HardenedBSD GPG Key ID: 0x6A84658F52456EEE GPG Key Fingerprint: 2ABA B6BD EF6A F486 BE89 3D9E

Re: pkg chroot issues?

On Sun, May 22, 2016 at 02:18:07PM -0700, Matthew Macy wrote: > > > > On Sun, 22 May 2016 13:43:13 -0700 Tim Kientzle > wrote > > > > > On May 22, 2016, at 1:28 PM, K. Macy wrote: > > > > > > > > > > > > On Sunday, May 22, 2016, Tim Kientzle wrote: > > > Crochet

Re: pkg chroot issues?

On Sun, 22 May 2016 13:43:13 -0700 Tim Kientzle wrote > > > On May 22, 2016, at 1:28 PM, K. Macy wrote: > > > > > > > > On Sunday, May 22, 2016, Tim Kientzle wrote: > > Crochet has some experimental hooks to install packages onto the system > > being built, but

Re: pkg chroot issues?

> On May 22, 2016, at 1:28 PM, K. Macy wrote: > > > > On Sunday, May 22, 2016, Tim Kientzle wrote: > Crochet has some experimental hooks to install packages onto the system being > built, but this seems to be hitting problems due to limitations in 'pkg -c'. > In particular, it seems that p

Re: pkg chroot issues?

On Sun, May 22, 2016 at 10:31:08PM +0200, b...@freebsd.org wrote: > On Sun, May 22, 2016 at 01:24:12PM -0700, Tim Kientzle wrote: > > Crochet has some experimental hooks to install packages onto the system > > being built, but this seems to be hitting problems due to limitations in > > 'pkg -c'.

Re: pkg chroot issues?

On Sun, May 22, 2016 at 01:24:12PM -0700, Tim Kientzle wrote: > Crochet has some experimental hooks to install packages onto the system being > built, but this seems to be hitting problems due to limitations in 'pkg -c'. > In particular, it seems that pkg performs the chroot before it does any

Re: pkg chroot issues?

On Sunday, May 22, 2016, Tim Kientzle wrote: > Crochet has some experimental hooks to install packages onto the system > being built, but this seems to be hitting problems due to limitations in > 'pkg -c'. In particular, it seems that pkg performs the chroot before it > does any network lookups.

pkg chroot issues?

Crochet has some experimental hooks to install packages onto the system being built, but this seems to be hitting problems due to limitations in 'pkg -c'. In particular, it seems that pkg performs the chroot before it does any network lookups. This is a problem if the chroot is not a complete

Interesting error during installworld

Hey All, I’m getting this error when doing `make installworld` on recent builds of HEAD. It seems that the error is non-critical as installworld doesn’t actually error out. I’m running HardenedBSD 11-CURRENT on amd64. sh: tail: not found make[4]: "/usr/src/share/mk/bsd.compiler.mk" line 151: wa

Re: ZFS on root, beadm, and the /boot symlink

On 05/22/16 21:11, Allan Jude wrote: > On 2016-05-22 14:41, Randy Westlund wrote: >> My system was installed from 10.1 or 10.2 with root on ZFS and geli, but >> now it tracks current. It is not an EFI system. I'm trying to get boot >> environments to work, but the /boot symlink is throwing me off

Re: ZFS on root, beadm, and the /boot symlink

On Sun, May 22, 2016 at 03:11:52PM -0400, Allan Jude wrote: > It is not possible to use boot environments when you have a separate > bootpool. This is the motivation for my recent work to implement GELI in > boot2 and loader, to allow you to combine GELI encryption with ZFS boot > environments, whi

Note on CFT image

On Sun, 22 May 2016 11:27:28 -0700 Matthew Macy wrote > To improve the user experience I disabled debug logging by default. Before > reporting a non-fatal error with i915 load the drm2 module first, then: > sysctl dev.drm.drm_debug=-1 to enable full logging. Once you have don

Re: ZFS on root, beadm, and the /boot symlink

On 2016-05-22 14:41, Randy Westlund wrote: > My system was installed from 10.1 or 10.2 with root on ZFS and geli, but > now it tracks current. It is not an EFI system. I'm trying to get boot > environments to work, but the /boot symlink is throwing me off. > > I have two pools from the installer

ZFS on root, beadm, and the /boot symlink

My system was installed from 10.1 or 10.2 with root on ZFS and geli, but now it tracks current. It is not an EFI system. I'm trying to get boot environments to work, but the /boot symlink is throwing me off. I have two pools from the installer's layout; a small bootpool and zroot. The bootpool

Update on CFT error reporting

To improve the user experience I disabled debug logging by default. Before reporting a non-fatal error with i915 load the drm2 module first, then: sysctl dev.drm.drm_debug=-1 to enable full logging. Once you have done that you can then load i915. The "unimplemented" and "dodgy" warnings are exp

repeatable panic on pageout with 945GM

With KDE and compositing enabled, I randomly get the following: (kgdb) info stack #0 doadump (textdump=) at pcpu.h:221 #1 0x8064e98e in kern_reboot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:366 #2 0x8064eea1 in vpanic (fmt=, ap=) at /usr/src/sys/kern/kern_shutdown.c:759 #

4.6 DRM/i915 update CFT (Sandy Bridge?)/IvyBridge/Haswell/Broadwell/SkyLake/KabyLake supported

I'm happy to announce a call for testers for the 4.6 update of drm and i915. The driver has been successfully tested on IvyBridge, Haswell, Broadwell and Skylake. At least basic HW 3D acceleration should work, VGA and DP out are known to work. Video decode has only been tried once and that did not

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

On 22.05.2016 12:32, Konstantin Belousov wrote: > On Sun, May 22, 2016 at 12:19:32PM +0300, Andrey Chernov wrote: >> On 22.05.2016 10:14, Konstantin Belousov wrote: >>> On Sun, May 22, 2016 at 09:47:08AM +0300, Andrey Chernov wrote: With microcode_update_enable="YES" in rc.conf: db:0

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

On Sun, May 22, 2016 at 12:19:32PM +0300, Andrey Chernov wrote: > On 22.05.2016 10:14, Konstantin Belousov wrote: > > On Sun, May 22, 2016 at 09:47:08AM +0300, Andrey Chernov wrote: > >> With microcode_update_enable="YES" in rc.conf: > >> > >> db:0:kdb.enter.panic> show pcpu > >> cpuid= 1

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

On 22.05.2016 10:14, Konstantin Belousov wrote: > On Sun, May 22, 2016 at 09:47:08AM +0300, Andrey Chernov wrote: >> With microcode_update_enable="YES" in rc.conf: >> >> db:0:kdb.enter.panic> show pcpu >> cpuid= 1 >> dynamic pcpu = 0xfe02ac1fd300 >> curthread= 0xf8000ae75a00: p

Re: 4.6 DRM/i915 update CFT (Sandy Bridge?)/IvyBridge/Haswell/Broadwell/SkyLake/KabyLake supported

On Sun, May 22, 2016 at 12:26:49AM -0700, Matthew Macy wrote: > I'm happy to announce a call for testers for the 4.6 update of drm and > i915. The driver has been successfully tested on IvyBridge, Haswell, > Broadwell and Skylake. At least basic HW 3D acceleration should work, > VGA and DP out

4.6 DRM/i915 update CFT (Sandy Bridge?)/IvyBridge/Haswell/Broadwell/SkyLake/KabyLake supported

I'm happy to announce a call for testers for the 4.6 update of drm and i915. The driver has been successfully tested on IvyBridge, Haswell, Broadwell and Skylake. At least basic HW 3D acceleration should work, VGA and DP out are known to work. Video decode has only been tried once and that did

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

On Sun, May 22, 2016 at 09:47:08AM +0300, Andrey Chernov wrote: > 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