Re: buildworld errors at outset on fresh svn checkout

2016-10-07 Thread Kevin Oberman
On Thu, Oct 6, 2016 at 10:16 PM, Scott Bennett wrote: > I'm running into a problem in updating my 10-STABLE system from > source. > A "make buildworld" quits immediately. I tried a fresh svn checkout for > base/stable/10 and then tried to run buildworld again, but got the

Your buildworld system is pulling userland libraries/headers

2016-10-07 Thread Nathan Lay
Hello once again FreeBSD-stable, While upgrading from FreeBSD 10-STABLE and later updating my FreeBSD 11-STABLE system, I noticed that your build system is pulling headers and libraries from the userland rather than the /usr/src tree. This can't possibly be intended. I kind of figured with recent

Re: 11.0-RELEASE Status Update

2016-10-07 Thread Marcelo Gondim
Em 06/10/2016 17:18, Glen Barber escreveu: As many of you are aware, 11.0-RELEASE needed to be rebuilt to address several issues that were discovered after the release was built. Extra caution is being taken in testing the rebuilt releases, so at present, the final release announcement is

Re: 11.0-RELEASE Status Update

2016-10-07 Thread Bruce A. Mah
If memory serves me right, Cassiano Peixoto wrote: > Looks we have some import issues to be fixed before 11-RELEASE. I have > another one that nobody cares: > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213257 > and > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212413 > > It's

11.0-RELEASE and mbuf-related trace

2016-10-07 Thread Slawa Olhovchenkov
Has anybody comment on this? During debug tcp-related freeze I am collect starnge mbuf-related freeze (this is like recursive lock to UMA Slabs keg) and trace: last pid: 49575; load averages: 2.00, 2.05, 3.75up 1+01:12:08 22:13:42 853 processes: 15 running, 769 sleeping, 35 waiting, 34

Re: 11.0-RELEASE Status Update

2016-10-07 Thread Glen Barber
On Fri, Oct 07, 2016 at 10:52:37AM +0200, Johan Hendriks wrote: > Op 06/10/2016 om 22:18 schreef Glen Barber: > > As many of you are aware, 11.0-RELEASE needed to be rebuilt to address > > several issues that were discovered after the release was built. Extra > > caution is being taken in testing

Re: 11.0-RELEASE Status Update

2016-10-07 Thread Glen Barber
On Fri, Oct 07, 2016 at 08:57:26AM -0700, jungle Boogie wrote: > On 6 October 2016 at 13:18, Glen Barber wrote: > > the final release announcement is planned for Monday, October 10. > > suggestion: > update the schedule > https://www.freebsd.org/releases/11.0R/schedule.html >

Re: 11.0-RELEASE Status Update

2016-10-07 Thread jungle Boogie
On 6 October 2016 at 13:18, Glen Barber wrote: > the final release announcement is planned for Monday, October 10. suggestion: update the schedule https://www.freebsd.org/releases/11.0R/schedule.html -- --- inum: 883510009027723 sip: jungleboo...@sip2sip.info

The best tool for automation marketing

2016-10-07 Thread iMarketing Center
___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: 11.0-RELEASE Status Update

2016-10-07 Thread Cassiano Peixoto
Looks we have some import issues to be fixed before 11-RELEASE. I have another one that nobody cares: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213257 and https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212413 It's affecting ALTQ users on both FreeBSD 11 and 10.3, the system just

Re: Reproducible panic - Going nowhere without my init!

2016-10-07 Thread Konstantin Belousov
On Fri, Oct 07, 2016 at 08:32:24AM +1000, Andy Farkas wrote: > With your latest patch applied, I ran through my procedure more > than a dozen times and no panics! > > Any explanation why sleep(STALL_TIMEOUT) as apposed to a > bunch of sleep(1)'s tickles the panic? What happened was sleep() got

Re: 11.0 stuck on high network load

2016-10-07 Thread Slawa Olhovchenkov
On Thu, Oct 06, 2016 at 09:28:06AM +0200, Julien Charbon wrote: > Thanks again to Slawa, for his numerous debug reports and always > questioning my explanations. His last question directly led to this > finding. He is testing a quick workaround patch to check if there is more. Thanks very

11.0-RELEASE Status Update

2016-10-07 Thread Alexander Shitov
Op 06/10/2016 om 22:18 schreef Glen Barber: > As many of you are aware, 11.0-RELEASE needed to be rebuilt to address > several issues that were discovered after the release was built. Extra > caution is being taken in testing the rebuilt releases, so at present, > the final release announcement is

O Presente que o seu filho merece está aqui!

2016-10-07 Thread Netself
Caso no esteja visualizando corretamente esta mensagem, acesse aqui.

Re: 11.0-RELEASE Status Update

2016-10-07 Thread Johan Hendriks
Op 06/10/2016 om 22:18 schreef Glen Barber: > As many of you are aware, 11.0-RELEASE needed to be rebuilt to address > several issues that were discovered after the release was built. Extra > caution is being taken in testing the rebuilt releases, so at present, > the final release announcement