[DragonFlyBSD - Bug #2927] e2a21467e1 Updates to show "4.7" and other changes to major headers should be temporarily suspended

bugtracker-admin at leaf.dragonflybsd.org bugtracker-admin at leaf.dragonflybsd.org
Thu Jul 21 10:21:46 PDT 2016

Issue #2927 has been updated by dillon.

Hmm.  The 5d920ec commit fixed the issues on the three build machines we've tested on (4-core/8-thread pkgbox64, 16-core/32-thread 2xXeon box, and the 4-socket 48-core opteron box).  If you are still getting lockups I need your machine configuration to try to reproduce it.  cpu's cores/threads, amount of memory, configured swap if any, and filesystems being used (UFS?).

Also, are you running the build from a console or from X?  If from X, try running from a console and see if it still reproduces (that will tell us whether there's an X interaction or not).  And see if you can break into the debugger when it locks up and get a kernel dump.


Bug #2927: e2a21467e1 Updates to show "4.7" and other changes to major headers should be temporarily suspended

* Author: davshao
* Status: New
* Priority: Normal
* Assignee: 
* Category: 
* Target version: 
commit 5d920ec6b97613f06aba4a09bfb91413b1fd93c3 Fix excessive ipiq recursion (2)
does not correct the problem I have observed on at least two machines that

make -j7 buildworld

locks up the machine.  (When using make buildworld I move /usr/obj/usr to start the build from scratch.)  On one machine there seems to be a reproducible lock up at

sh /usr/src/tools/install.sh -o root -g wheel -m 555  lto1 /usr/obj/usr/src/ctools_x86_64_x86_64/usr/libexec/gcc50

Changes to major headers should be temporarily suspended until this problem is resolved, because I have observed that even

make quickworld

can fail to complete without lockup.  Someone using UFS as their filesystem may experience quite substantial filesystem corruption after a lockup.  By limiting changes to major headers, this gives the greatest chance of a successful make quickworld when this problem is finally resolved.

You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account

More information about the Bugs mailing list