RE: 12.0-ALPHA6 dumps with 'Fatal double fault'

2018-09-21 Thread Cy Schubert
Yes, I was thinking that myself.

---
Sent using a tiny phone keyboard.
Apologies for any typos and autocorrect.
Also, this old phone only supports top post. Apologies.

Cy Schubert
 or 
The need of the many outweighs the greed of the few.
---

-Original Message-
From: Michael Tuexen
Sent: 20/09/2018 07:41
To: Michael Schmiedgen
Cc: freebsd-current@FreeBSD.org
Subject: Re: 12.0-ALPHA6 dumps with 'Fatal double fault'

> On 20. Sep 2018, at 14:18, Michael Schmiedgen  wrote:
> 
> Hi List,
> 
> if compiling ports and configure script checks for SCTP with
> 
> 'checking whether SCTP is supported...'
> 
> 12.0-ALPHA6 dumps core with message:
> 
> Fatal double fault
> rip 0x80b96297 rsp 0xfe00be241bb0 rbp 0xfe00be245490
> rax 0x1 rdx 0x3 rbx 0x7fffd198
> rcx 0x80b9620b rsi 0xf8029eeb0368 rdi 0x4
> r8 0xf801c925c580 r9 0xfe00be2456d4 r10 0x4
> r11 0xfe00be245b80 r12 0x7fffd190 r13 0
> r14 0x1 r15 0x7fffd1a8 rflags 0x10293
> cs 0x20 ss 0x28 ds 0x3b es 0x3b fs 0x13 gs 0x1b
> fsbase 0x8002318d0 gsbase 0x81648a00 kgsbase 0
> cpuid = 0; apic id = 00
> panic: double fault
> cpuid = 0
> 
> I can provide crash dumps if desired, but without debug information.
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.

Best regards
Michael
> 
> Thanks,
>  Michael
> ___
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


Re: 12.0-ALPHA6 dumps with 'Fatal double fault'

2018-09-20 Thread Michael Schmiedgen




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.


I know, this was only some background information.



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?


From the kernel. I commented out 'options SCTP' and recompiled.



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...


Yes, if time and point in time permits, because that's a production server
and I can only mess around with it late night.


Michael
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


Re: 12.0-ALPHA6 dumps with 'Fatal double fault'

2018-09-20 Thread Michael Tuexen
> On 20. Sep 2018, at 19:11, Michael Schmiedgen  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  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

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


Re: 12.0-ALPHA6 dumps with 'Fatal double fault'

2018-09-20 Thread Michael Schmiedgen

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  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
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.



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.

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
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


Re: 12.0-ALPHA6 dumps with 'Fatal double fault'

2018-09-20 Thread Michael Tuexen
> On 20. Sep 2018, at 17:12, Michael Schmiedgen  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.

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...

Best regards
Michael
> 
> CPU: Intel(R) Xeon(R) CPU E31245 @ 3.30GHz (3300.10-MHz K8-class CPU)
>  Origin="GenuineIntel"  Id=0x206a7  Family=0x6  Model=0x2a  Stepping=7
>  
> Features=0xbfebfbff
> Features2=0x1fbae3ff
>  AMD Features=0x28100800
>  AMD Features2=0x1
>  XSAVE Features=0x1
>  VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID
>  TSC: P-state invariant, performance statistics
> 
> It crashed multiple times randomly under heavy load when compiling ports. But 
> I
> observed a crash two times exactly in the same place: configure script SCTP 
> test
> in devel/apr1.
> 
> Thanks,
>  Michael

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


Re: 12.0-ALPHA6 dumps with 'Fatal double fault'

2018-09-20 Thread Michael Schmiedgen




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.

CPU: Intel(R) Xeon(R) CPU E31245 @ 3.30GHz (3300.10-MHz K8-class CPU)
  Origin="GenuineIntel"  Id=0x206a7  Family=0x6  Model=0x2a  Stepping=7
  
Features=0xbfebfbff
Features2=0x1fbae3ff
  AMD Features=0x28100800
  AMD Features2=0x1
  XSAVE Features=0x1
  VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID
  TSC: P-state invariant, performance statistics

It crashed multiple times randomly under heavy load when compiling ports. But I
observed a crash two times exactly in the same place: configure script SCTP test
in devel/apr1.

Thanks,
  Michael
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


Re: 12.0-ALPHA6 dumps with 'Fatal double fault'

2018-09-20 Thread Michael Tuexen
> On 20. Sep 2018, at 14:18, Michael Schmiedgen  wrote:
> 
> Hi List,
> 
> if compiling ports and configure script checks for SCTP with
> 
> 'checking whether SCTP is supported...'
> 
> 12.0-ALPHA6 dumps core with message:
> 
> Fatal double fault
> rip 0x80b96297 rsp 0xfe00be241bb0 rbp 0xfe00be245490
> rax 0x1 rdx 0x3 rbx 0x7fffd198
> rcx 0x80b9620b rsi 0xf8029eeb0368 rdi 0x4
> r8 0xf801c925c580 r9 0xfe00be2456d4 r10 0x4
> r11 0xfe00be245b80 r12 0x7fffd190 r13 0
> r14 0x1 r15 0x7fffd1a8 rflags 0x10293
> cs 0x20 ss 0x28 ds 0x3b es 0x3b fs 0x13 gs 0x1b
> fsbase 0x8002318d0 gsbase 0x81648a00 kgsbase 0
> cpuid = 0; apic id = 00
> panic: double fault
> cpuid = 0
> 
> I can provide crash dumps if desired, but without debug information.
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.

Best regards
Michael
> 
> Thanks,
>  Michael
> ___
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


Re: 12.0-ALPHA6 dumps with 'Fatal double fault'

2018-09-20 Thread Michael Schmiedgen

I removed SCTP from kernel and updated from r338797 to r338827
and the problem seems to be gone.

Michael



On 20.09.2018 14:18, Michael Schmiedgen wrote:

Hi List,

if compiling ports and configure script checks for SCTP with

'checking whether SCTP is supported...'

12.0-ALPHA6 dumps core with message:

Fatal double fault
rip 0x80b96297 rsp 0xfe00be241bb0 rbp 0xfe00be245490
rax 0x1 rdx 0x3 rbx 0x7fffd198
rcx 0x80b9620b rsi 0xf8029eeb0368 rdi 0x4
r8 0xf801c925c580 r9 0xfe00be2456d4 r10 0x4
r11 0xfe00be245b80 r12 0x7fffd190 r13 0
r14 0x1 r15 0x7fffd1a8 rflags 0x10293
cs 0x20 ss 0x28 ds 0x3b es 0x3b fs 0x13 gs 0x1b
fsbase 0x8002318d0 gsbase 0x81648a00 kgsbase 0
cpuid = 0; apic id = 00
panic: double fault
cpuid = 0

I can provide crash dumps if desired, but without debug information.

Thanks,
   Michael



___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"