We rebuild 11.1-Stable at least every two weeks.? Our build on the 7th Feb is in use on our development boxes, however the rebuild on 22nd resulted in frequent crashes and our reverting to FreeBSD 11.1-STABLE? r329008.? Is anyone actually running a Stable that was built after 22nd Feb?? Could you please share the revision number? Because the churn in https://lists.freebsd.org/pipermail/svn-src-stable-11/2018-March/ is high we haven't been able to sight if a problem was identified and fixed; so we're really looking for a functioning stable that we can resume tracking. PS There was no information in the logs, and we have no instrumentation in the kernel to help. Sorry. -- Influence national support against IP address spoofing (pretending to be someone else), refer: http://www.bcp38.info/index.php/Main_Page
On Tue, Mar 20, 2018 at 12:05:33PM +1100, Dewayne Geraghty wrote:> We rebuild 11.1-Stable at least every two weeks.? Our build on the 7th > Feb is in use on our development boxes, however the rebuild on 22nd > resulted in frequent crashes and our reverting to FreeBSD 11.1-STABLE? > r329008.? Is anyone actually running a Stable that was built after 22nd > Feb?? Could you please share the revision number?These are lightly loaded, but the two "production" boxes at home run a stable/11 snapshot, built weekly. Details on the process may be found at <http://www.catwhisker.org/~david/FreeBSD/upgrade.html>; the page with historical information (including "uname" output for each snapshot run) is <http://www.catwhisker.org/~david/FreeBSD/history/>. (Each of the two machines runs from the same sources as listed for "albert".) (My laptop & build machine run a daily snapshot of stable/11, as well as building & smoke-testing a daily snapshot of head. The above-cited "weekly snapshot" is actually a "daily snapshot" that is sampled only weekly -- on Sunday morning.)> ...Peace, david -- David H. Wolfskill david at catwhisker.org An investigator who doesn't make a perp nervous isn't doing his job. See http://www.catwhisker.org/~david/publickey.gpg for my public key. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 618 bytes Desc: not available URL: <http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20180319/14fffcc8/attachment.sig>
On 19 March 2018 at 18:05, Dewayne Geraghty <dewayne.geraghty at heuristicsystems.com.au> wrote:> We rebuild 11.1-Stable at least every two weeks. Our build on the 7th > Feb is in use on our development boxes, however the rebuild on 22nd > resulted in frequent crashes and our reverting to FreeBSD 11.1-STABLE > r329008. Is anyone actually running a Stable that was built after 22nd > Feb? Could you please share the revision number? > > Because the churn in > https://lists.freebsd.org/pipermail/svn-src-stable-11/2018-March/ is > high we haven't been able to sight if a problem was identified and > fixed; so we're really looking for a functioning stable that we can > resume tracking.Hi, I can't help identify the problem and if it was fixed without any information. Can you at least let us know what kind of crashes are you seeing? Kernel panics?SIGBUS? Something else? It would be best if you could bisect to the revision causing you problems. Note that despite the name, STABLE is a development branch and users of the branch are expected to be able to provide some help tracking down issues. -- Eitan Adler
On 20/03/2018 01:05, Dewayne Geraghty wrote:> We rebuild 11.1-Stable at least every two weeks.? Our build on the 7th > Feb is in use on our development boxes, however the rebuild on 22nd > resulted in frequent crashes and our reverting to FreeBSD 11.1-STABLE > r329008.? Is anyone actually running a Stable that was built after 22nd > Feb?? Could you please share the revision number?r330769 works fine for me. I usually upgrade on a Monday, though am holding off this week as am waiting for r330745 to land in STABLE, but it works fine for me always.> Because the churn in > https://lists.freebsd.org/pipermail/svn-src-stable-11/2018-March/ is > high we haven't been able to sight if a problem was identified and > fixed; so we're really looking for a functioning stable that we can > resume tracking.I use this to eyeball whats gone into STABLE, its a daily read for me as I find keeping up with the mailing list tricky too. http://www.freshbsd.org/?branch=RELENG_11&project=freebsd& -pete.