On Sun, Apr 05, 2015 at 05:57:08PM -0500, Alan Cox wrote: > ... > > A> Just curious, amd64 or i386? > > > > Panics on amd64...., while building a kernel for i386, if that matters :) > > > > Maybe. I didn't trip the assertion building amd64 kernels or world. > Maybe the difference is that the machine in question is still running a > world from before the last clang update. > ...
After enoountering the panic (twice), I built head/amd64 (starting from stable/10/amd64); that built & booted without incident. I then went back to head/i386 (different slice), ran "make clean", then completely re-built world & kernel (in single-user mode, since it was during the transition to multi-user mode that I encountered the panic), while running: FreeBSD 11.0-CURRENT FreeBSD 11.0-CURRENT #1561 r281106M/281106:1100067: Sun Apr 5 06:01:06 PDT 2015 r...@g1-254.catwhisker.org:/common/S4/obj/usr/src/sys/CANARY i386 On reboot, I was running: FreeBSD 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r281106M/281106:1100067: Sun Apr 5 11:54:52 PDT 2015 root@:/common/S4/obj/usr/src/sys/CANARY i386 which still exhibited the panic. When I noted that you had committed r28118, I hand-applied that, rebooted to that last head/i386 (in single-user mode), and rebuilt the kernel (only) -- with -DNOCLEAN. The result: FreeBSD g1-254.catwhisker.org 11.0-CURRENT FreeBSD 11.0-CURRENT #1561 r281106M/281106:1100067: Sun Apr 5 14:44:52 PDT 2015 root@:/common/S4/obj/usr/src/sys/CANARY i386 survived the transition to multi-user mode successfully (which promises to make tomorrow morning a bit less stressful for me). All of this is done on the same hardware -- merely different slices of the disk. The machine has 8GB RAM, but only a bit less than half of that would have been accessible to the i386 flavor (as I am not attempting to do PAE). Peace, david -- David H. Wolfskill da...@catwhisker.org Those who murder in the name of God or prophet are blasphemous cowards. See http://www.catwhisker.org/~david/publickey.gpg for my public key.
Description: PGP signature