Re: head -r339076 based powerpc64 context: fatal kernel trap [ during /usr/tests/Kyuafile's sys/netipsec/tunnel/aes_cbc_128_hmac_sha1:v4 ]

2018-10-17 Thread Mark Millard
[Booting a debug kernel reported a lock order
reversal that might be relevant. The problem
repeated again: seems to always fail in my
context. The backtrace is like the prior
one, but for the debug kernel build being used
this time.]

On 2018-Oct-17, at 6:29 PM, Mark Millard  wrote:

> [I got another data storage interrupt failure, again
> during kyaua showing:
> 
> sys/netipsec/tunnel/aes_cbc_128_hmac_sha1:v4  ->
> 
> but the backtrace looks different. See below.]
> 
> On 2018-Oct-17, at 4:58 PM, Mark Millard  wrote:
> 
>> On a powerpc64 with builworld buildkernel built via
>> devel/powerpc64-xtoolchain-gcc for head -r339076
>> (some source adjustments), and a system-cc-is-clang
>> I attempted a:
>> 
>> # kyua test -k /usr/tests/Kyuafile
>> 
>> It got to:
>> 
>> sys/netinet/reuseport_lb:basic_ipv4  ->  failed: 
>> /usr/src/tests/sys/netinet/reuseport_lb.c:165: bind() failed: Address 
>> already in use  [0.014s]
>> sys/netinet/reuseport_lb:basic_ipv6  ->  failed: 
>> /usr/src/tests/sys/netinet/reuseport_lb.c:221: bind() failed: Address 
>> already in use  [0.014s]
>> sys/netipsec/tunnel/aes_cbc_128_hmac_sha1:v4  ->  
>> 
>> and then the system crashed. I am re-running to
>> see what happens.
>> 
>> The context has a non-debug kernel (but with
>> symbols).
>> 
>> Hand transcribed from a picture . . .
>> 
>> fatal kernel trap:
>> 
>> exception   = 0x300 (data storage interrupt)
>> virtual address = 0xbfba8530
>> dsisr   = 0x4200
>> srr0= 0x72b054
>> srr1= 0x90009032
>> current msr = 0x90009032
>> lr  = 0x69948c
>> curthread   = 0xc00036f7f000
>> pid = 12798, comm = ifconfig
>> 
>> [ thread pid 12798 tid 100312 ]
>> Stopped at lock_init+0x78 stw r9,0x8(r3)
>> db:0:kdb.enter.default> bt
>> Tracing pid 12798 tid 100312 td 0xc00036f7f000
>> 0xe0004646e330: at 0xe0004646e36c
>> 0xe0004646e360: at epair_modevent+0xf0
>> 0xe0004646e410: at module_register_init+0xe8
>> 0xe0004646e4a0: at linker_laod_module+0x6f8
> 
> Should have been: linker_load_module
> 
>> 0xe0004646e580: at kern_kldload+0x150
>> 0xe0004646e5e0: at sys_kldload+0xb80
>> 0xe0004646e630: at trap+0xef4
>> 0xe0004646e790: at powerpc_interrupt+0x12c
>> 0xe0004646e820: user sc trap by 0x81017fcf8
>> srr1 = 0x9000f032
>> r1   = 0x3fffcfe0
>> cr   = 0x28022482
>> xer  = 0x2000
>> ctr  = 0x81017fcf0
>> r2   = 0x810336300
>> 
>> 
>> # uname -apKU
>> FreeBSD FBSDG5L 12.0-ALPHA8 FreeBSD 12.0-ALPHA8 #4 r339076M: Mon Oct 15 
>> 13:19:35 PDT 2018 
>> markmi@FBSDG5L:/usr/obj/powerpc64vtsc_xtoolchain-gcc/powerpc.powerpc64/usr/src/powerpc.powerpc64/sys/GENERIC64vtsc-NODBG
>>   powerpc powerpc64 1200084 1200084
>> 
>> ports was at -r480180.
>> 
> 
> Again failed during:
> 
> sys/netinet/reuseport_lb:basic_ipv4  ->  failed: 
> /usr/src/tests/sys/netinet/reuseport_lb.c:165: bind() failed: Address already 
> in use  [0.013s]
> sys/netinet/reuseport_lb:basic_ipv6  ->  failed: 
> /usr/src/tests/sys/netinet/reuseport_lb.c:221: bind() failed: Address already 
> in use  [0.013s]
> sys/netipsec/tunnel/aes_cbc_128_hmac_sha1:v4  ->  
> 
> 
> The backtrace this time shows (hand transcribed):
> 
> fatal kernel trap:
> 
> exception   = 0x300 (data storage interrupt)
> virtual address = 0xc0008cab6530
> dsisr   = 0x4200
> srr0= 0xe00046e5b228
> srr1= 0x90009032
> current msr = 0x90009032
> lr  = 0xe00046e5b220
> curthread   = 0xcd48e000
> pid = 9666, comm = jail
> 
> [ thread pid 9666 tid 100185 ]
> Stopped at vnet_epair_init+0x78: stdx r3,r29,r30
> db:0:kdb.enter.default> bt
> Tracing pid 9666 tid 100185 td 0xcd48e000
> 0xe000470a1240: at vnet_sysinit+0x64
> 0xe000470a1270: at vnet_alloc+0xfc
> 0xe000470a12d0: at kern_jail_set+0x1e30
> 0xe000470a15e0: at sys_jail_set+08c
> 0xe000470a1630: at trap+0xef4
> 0xe000470a1790: at powerpc_interrupt+0x12c
> 0xe000470a1820: user sc trap by 0x81016a888
> srr1 = 0x9000f032
> r1   = 0x3fffd090
> cr   = 0x28002482
> xer  = 0x2000
> ctr  = 0x81016a880
> r2   = 0x810322300
> 
> I got a core.txt.0 this time. it reported:
> 
> . . .
> epair3a: Ethernet address: 02:60:27:70:4b:0a
> epair3b: Ethernet address: 02:60:27:70:4b:0b
> epair3a: link state changed to UP
> epair3b: link state changed to UP
> 
> fatal kernel trap:
> 
>   exception   = 0x300 (data storage interrupt)
>   virtual address = 0xc0008cab6530
>   dsisr   = 0x4200
>   srr0= 0xe00046e5b228 (0xe00046e5b228)
>   srr1= 0x90009032
>   current msr = 0x90009032
>   lr  = 0xe00046e5b220 (0xe00046e5b220)
>   curthread   = 0xcd48e000
>  pid = 9666, comm = jail
> 
> 

epair3a: Ethernet address: 02:60:27:70:4b:0a
epair3b: Ethernet address: 02:60:27:70:4b:0b
epair3a: link state 

Re: head -r339076 based powerpc64 context: fatal kernel trap [ during /usr/tests/Kyuafile's sys/netipsec/tunnel/aes_cbc_128_hmac_sha1:v4 ]

2018-10-17 Thread Mark Millard
[I got another data storage interrupt failure, again
during kyaua showing:

sys/netipsec/tunnel/aes_cbc_128_hmac_sha1:v4  ->

but the backtrace looks different. See below.]

On 2018-Oct-17, at 4:58 PM, Mark Millard  wrote:

> On a powerpc64 with builworld buildkernel built via
> devel/powerpc64-xtoolchain-gcc for head -r339076
> (some source adjustments), and a system-cc-is-clang
> I attempted a:
> 
> # kyua test -k /usr/tests/Kyuafile
> 
> It got to:
> 
> sys/netinet/reuseport_lb:basic_ipv4  ->  failed: 
> /usr/src/tests/sys/netinet/reuseport_lb.c:165: bind() failed: Address already 
> in use  [0.014s]
> sys/netinet/reuseport_lb:basic_ipv6  ->  failed: 
> /usr/src/tests/sys/netinet/reuseport_lb.c:221: bind() failed: Address already 
> in use  [0.014s]
> sys/netipsec/tunnel/aes_cbc_128_hmac_sha1:v4  ->  
> 
> and then the system crashed. I am re-running to
> see what happens.
> 
> The context has a non-debug kernel (but with
> symbols).
> 
> Hand transcribed from a picture . . .
> 
> fatal kernel trap:
> 
> exception   = 0x300 (data storage interrupt)
> virtual address = 0xbfba8530
> dsisr   = 0x4200
> srr0= 0x72b054
> srr1= 0x90009032
> current msr = 0x90009032
> lr  = 0x69948c
> curthread   = 0xc00036f7f000
> pid = 12798, comm = ifconfig
> 
> [ thread pid 12798 tid 100312 ]
> Stopped at lock_init+0x78 stw r9,0x8(r3)
> db:0:kdb.enter.default> bt
> Tracing pid 12798 tid 100312 td 0xc00036f7f000
> 0xe0004646e330: at 0xe0004646e36c
> 0xe0004646e360: at epair_modevent+0xf0
> 0xe0004646e410: at module_register_init+0xe8
> 0xe0004646e4a0: at linker_laod_module+0x6f8

Should have been: linker_load_module

> 0xe0004646e580: at kern_kldload+0x150
> 0xe0004646e5e0: at sys_kldload+0xb80
> 0xe0004646e630: at trap+0xef4
> 0xe0004646e790: at powerpc_interrupt+0x12c
> 0xe0004646e820: user sc trap by 0x81017fcf8
> srr1 = 0x9000f032
> r1   = 0x3fffcfe0
> cr   = 0x28022482
> xer  = 0x2000
> ctr  = 0x81017fcf0
> r2   = 0x810336300
> 
> 
> # uname -apKU
> FreeBSD FBSDG5L 12.0-ALPHA8 FreeBSD 12.0-ALPHA8 #4 r339076M: Mon Oct 15 
> 13:19:35 PDT 2018 
> markmi@FBSDG5L:/usr/obj/powerpc64vtsc_xtoolchain-gcc/powerpc.powerpc64/usr/src/powerpc.powerpc64/sys/GENERIC64vtsc-NODBG
>   powerpc powerpc64 1200084 1200084
> 
> ports was at -r480180.
> 

Again failed during:

sys/netinet/reuseport_lb:basic_ipv4  ->  failed: 
/usr/src/tests/sys/netinet/reuseport_lb.c:165: bind() failed: Address already 
in use  [0.013s]
sys/netinet/reuseport_lb:basic_ipv6  ->  failed: 
/usr/src/tests/sys/netinet/reuseport_lb.c:221: bind() failed: Address already 
in use  [0.013s]
sys/netipsec/tunnel/aes_cbc_128_hmac_sha1:v4  ->  


The backtrace this time shows (hand transcribed):

fatal kernel trap:

exception   = 0x300 (data storage interrupt)
virtual address = 0xc0008cab6530
dsisr   = 0x4200
srr0= 0xe00046e5b228
srr1= 0x90009032
current msr = 0x90009032
lr  = 0xe00046e5b220
curthread   = 0xcd48e000
pid = 9666, comm = jail

[ thread pid 9666 tid 100185 ]
Stopped at vnet_epair_init+0x78: stdx r3,r29,r30
db:0:kdb.enter.default> bt
Tracing pid 9666 tid 100185 td 0xcd48e000
0xe000470a1240: at vnet_sysinit+0x64
0xe000470a1270: at vnet_alloc+0xfc
0xe000470a12d0: at kern_jail_set+0x1e30
0xe000470a15e0: at sys_jail_set+08c
0xe000470a1630: at trap+0xef4
0xe000470a1790: at powerpc_interrupt+0x12c
0xe000470a1820: user sc trap by 0x81016a888
srr1 = 0x9000f032
r1   = 0x3fffd090
cr   = 0x28002482
xer  = 0x2000
ctr  = 0x81016a880
r2   = 0x810322300

I got a core.txt.0 this time. it reported:

. . .
epair3a: Ethernet address: 02:60:27:70:4b:0a
epair3b: Ethernet address: 02:60:27:70:4b:0b
epair3a: link state changed to UP
epair3b: link state changed to UP

fatal kernel trap:

   exception   = 0x300 (data storage interrupt)
   virtual address = 0xc0008cab6530
   dsisr   = 0x4200
   srr0= 0xe00046e5b228 (0xe00046e5b228)
   srr1= 0x90009032
   current msr = 0x90009032
   lr  = 0xe00046e5b220 (0xe00046e5b220)
   curthread   = 0xcd48e000
  pid = 9666, comm = jail



===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)

___
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"