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:
[ .
Warner Losh imp at bsdimp.com wrote on Sat Jul 15 23:22:22 UTC 2017 :
> On Sat, Jul 15, 2017 at 1:32 PM, Michael Butler protected-networks.net>
> wrote:
>
> > On 07/11/17 19:53, Michael Butler wrote:
> >
> . . .
> >
> > Something about SVN r320844 causes almost all KDE applications to fail on
>
On Sat, Jul 15, 2017 at 6:49 PM, Michael Butler
wrote:
> On 07/15/17 20:39, Mark Millard wrote:
>
>> FYI for Michael B.: the incomplete kernel rebuild problem has a fix:
>> -r320919 .
>> See the fix (to the building problem that was created in -r320220 ):
>>
>> https://lists.freebsd.org/pipermail
On 07/15/17 20:39, Mark Millard wrote:
FYI for Michael B.: the incomplete kernel rebuild problem has a fix: -r320919 .
See the fix (to the building problem that was created in -r320220 ):
https://lists.freebsd.org/pipermail/svn-src-head/2017-July/102622.html
If the KDE problem persists based on
On Sat, Jul 15, 2017 at 1:32 PM, Michael Butler
wrote:
> On 07/11/17 19:53, Michael Butler wrote:
>
>> On 07/11/17 13:13, I wrote:
>>
>>> Take sdhci out of the kernel and try again. If that works, it tells us
one
thing (need to troubleshoot sdhci stuff more). If not it tells us
ano
On 07/11/17 19:53, Michael Butler wrote:
On 07/11/17 13:13, I wrote:
Take sdhci out of the kernel and try again. If that works, it tells
us one
thing (need to troubleshoot sdhci stuff more). If not it tells us
another
(need to troubleshoot CAM more), do we get errors with the ATA_IDENTIFY
comm
On 7/11/17 10:13 AM, Bryan Drewery wrote:
> On 7/11/17 10:09 AM, Warner Losh wrote:
>> Plus we know we have at least one bug in meta-mode rebuilding since not
>> everything is being rebuilt that should be across this change.
>
> Yes I'm looking into that.
>
This was a bug with buildkernel with M
On 07/11/17 13:13, I wrote:
Take sdhci out of the kernel and try again. If that works, it tells us
one
thing (need to troubleshoot sdhci stuff more). If not it tells us another
(need to troubleshoot CAM more), do we get errors with the ATA_IDENTIFY
command? Does it try multiple times per AHCI po
On 7/11/17 1:09 PM, Warner Losh wrote:
On a machine with SDHCI, a clean rebuild (after "r -rf /usr/obj") refuses
to find /dev/ada0 :-(
Take sdhci out of the kernel and try again. If that works, it tells us one
thing (need to troubleshoot sdhci stuff more). If not it tells us another
(need to
On 7/11/17 10:09 AM, Warner Losh wrote:
> Plus we know we have at least one bug in meta-mode rebuilding since not
> everything is being rebuilt that should be across this change.
Yes I'm looking into that.
--
Regards,
Bryan Drewery
signature.asc
Description: OpenPGP digital signature
On Tue, Jul 11, 2017 at 10:47 AM, Michael Butler wrote:
> On 7/11/17 10:32 AM, Warner Losh wrote:
>
>> On Tue, Jul 11, 2017 at 6:13 AM, David Wolfskill
>> wrote:
>>
>>> I believe that each of the machines has an MMC slot, but I also believe
>>> that in each case, it is empty.
>>>
>>> Is there an
On 7/11/17 10:32 AM, Warner Losh wrote:
On Tue, Jul 11, 2017 at 6:13 AM, David Wolfskill
wrote:
I believe that each of the machines has an MMC slot, but I also believe
that in each case, it is empty.
Is there anything else I might be able to do to help resolve this?
Try building a kernel wi
On Tue, Jul 11, 2017 at 08:32:26AM -0600, Warner Losh wrote:
> ...
> > While O. Hartmann had written to indicate the he had identified r320844
> > as the culprit, and I had other reason to suspect it, I was a bit busy
> > at work yesterday, and unable to determine this for myself empirically.
> >
>
On Tue, Jul 11, 2017 at 6:13 AM, David Wolfskill
wrote:
> On Mon, Jul 10, 2017 at 04:51:09AM -0700, David Wolfskill wrote:
> > Pnic occurred prior to mounting file systems
>
> While O. Hartmann had written to indicate the he had identified r320844
> as the culprit, and I had other reason to s
On Mon, Jul 10, 2017 at 04:51:09AM -0700, David Wolfskill wrote:
> Pnic occurred prior to mounting file systems
While O. Hartmann had written to indicate the he had identified r320844
as the culprit, and I had other reason to suspect it, I was a bit busy
at work yesterday, and unable to determ
Am Mon, 10 Jul 2017 04:51:09 -0700
David Wolfskill schrieb:
> Pnic occurred prior to mounting file systems; I was able to boot
> from the r320827 (as "kernel.old") OK. I was not able to get a
> dump. Both the laptop and the build machine panicked, but the build
> machine's keyboard was unrespon
Pnic occurred prior to mounting file systems; I was able to boot
from the r320827 (as "kernel.old") OK. I was not able to get a
dump. Both the laptop and the build machine panicked, but the build
machine's keyboard was unresponsive and its serial console isn't
funtioning at the moment (because of
17 matches
Mail list logo