12.0-ALPHA6 dumps with 'Fatal double fault'
Michael Tuexen
tuexen at freebsd.org
Thu Sep 20 17:27:44 UTC 2018
> On 20. Sep 2018, at 19:11, Michael Schmiedgen <schmiedgen at gmx.net> wrote:
>
> Hi Michael,
>
> many thanks for your help.
>
>
> On 20.09.2018 18:15, Michael Tuexen wrote:
>>> On 20. Sep 2018, at 17:12, Michael Schmiedgen <schmiedgen at gmx.net> wrote:
>>>
>>>
>>>> Can you elaborate which port was triggering the fault and which platform you are using?
>>>> I would like to reproduce the issue and fix it.
>>>
>>> Port is devel/apr1 and platform is amd64.
>> Works fine on my side. It would be helpful if you could build a kernel with
>> debug symbols, reproduce the problem and provide a stack strace.
>
> Unfortunately I cannot. It is a production machine without debug that does not
> like to run on 11.1 OR 11.2 for some strange reason [1]. And I really do not
I'm not referring to 11.1 or 11.2. Just the kernel you use with debug symbols.
> want to run it on 11.0 anymore. Perhaps it is some crappy hardware from our
> hoster, I don't know. Anyway, after minimal-updating SVN to very-latest and
> removing SCTP it behaves just fine under load.
Removing SCTP means removing it from the kernel or disabling it in the port?
>
>
>> Since you said that it crashed multiple times makes me wonder if this problem
>> is related to SCTP in particular or if there is some other generic issue...
>
> The mentioned commit [2] lies exactly in my SVN update delta. So this could
> be the reason, too(?)
>
> Sadly I am to busy right now to investigate further, sorry.
OK. If you have some spare time, enable SCTP again and see if the problem
is related to it...
Best regards
Michael
>
> Thanks again,
> Michael
>
>
>
> [1]
> https://lists.freebsd.org/pipermail/freebsd-current/2014-October/052900.html
> https://lists.freebsd.org/pipermail/freebsd-stable/2014-December/081192.html
>
> [2]
> https://lists.freebsd.org/pipermail/freebsd-current/2018-September/071283.html
More information about the freebsd-current
mailing list