Date: Mon, 17 Jul 2017 21:35:26 -0400 From: Michael Butler <imb@protected-networks.net> To: Warner Losh <imp@bsdimp.com> Cc: FreeBSD Current <current@freebsd.org> Subject: [ solved ] Re: Panic on boot after upgrade from r320827 -> r320869 Message-ID: <9b72c06f-8f48-dddf-9017-34488978fe59@protected-networks.net> In-Reply-To: <405f9924-5354-c6ba-0fc1-c4acf3eebcda@protected-networks.net> References: <20170710115109.GD1177@albert.catwhisker.org> <20170711121311.GI1177@albert.catwhisker.org> <CANCZdfqRMybt2yzr8GrZCKtvh7WSkeorKXJ%2Bt5wtDSSY75S8fg@mail.gmail.com> <b1b65804-9752-942c-dbfd-075a4c5d6317@protected-networks.net> <CANCZdfp09QLQRgENS73JqbH-UwkjXvUB2j21xNes0zyeWc02VA@mail.gmail.com> <954e8793-7e17-8ae4-8449-39c742e0d432@protected-networks.net> <adbeefe6-9539-4151-0cd3-ab57b8657885@protected-networks.net> <405f9924-5354-c6ba-0fc1-c4acf3eebcda@protected-networks.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 07/15/17 15:32, I wrote: > Something about SVN r320844 causes almost all KDE applications to fail > on a signal 6. > > I've recompiled KDE and other components obviously dependent on kernel > structures (e.g. everything dbus-related). I still get core-files with a > back-trace that looks like: [ .. ] > SVN r320843 works, r320844 doesn't :-( Apparently, the failing port was HALD. It couldn't accept the revised kernel structure, failed and caused a cascade of failures up the KDE process-chain, including DBUS. Sorry it took so long to find :-( Recompiling HALD fixed the problem, imb
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9b72c06f-8f48-dddf-9017-34488978fe59>