Ed Greshko writes:
On 09/10/16 20:15, Sam Varshavchik wrote:
Can't get any more broken than a segfault at startup :-)
Looking at the carnage in /var/log/messages, it broke so bad that even
systemd-coredump
choked on itself, and failed to do whatever it wanted to do. Impressive.
Booted back to 4.6.7 to get things going again. Don't really have much to
add to bug
1374917, besides the sorry state of affairs from /var/log/messages.
chroot might have something to do with it. I'm running named-chroot.service
FWIW, I'm also running named-chroot.service and
[egreshko@meimei ~]$ uname -r 4.7.2-201.fc24.x86_64
But unable to reproduce your issue.
All-righty, this must be something about this particular named-chroot configuration…