Re: hal crash under 8.99.42

[Chavdar Ivanov <ci4ic4%gmail.com@localhost>]

Hi,

That was badly described. It is not just hal crash, it is NetBSD panic
when hal is starting. Obvious from the trace, but still.

On Thu, 30 May 2019 at 14:49, Chavdar Ivanov <ci4ic4%gmail.com@localhost> wrote:
>
> Hi,
>
>
> I got a repeatable crash of hal under 8.99.42; running ok under 8.99.41
> from the 27th of May. I have disabled hal for the moment. The dmesg of
> the panic looks as follows:
>
> ...
>
> [    34.627608] acpibat0: normal capacity on 'charge state'
> [    66.605334] fatal protection fault in supervisor mode
> [    66.605334] trap type 4 code 0 rip 0xffffffff8021dca5 cs 0x8 rflags
> 0x10002 cr2 0x72e1f68e8000 ilevel 0 rsp 0xffffd7013a8ccdc8
> [    66.605334] curlwp 0xffff8939f96be1c0 pid 0.38 lowest kstack
> 0xffffd7013a8c92c0
> [    66.605334] panic: trap
> [    66.605334] cpu4: Begin traceback...
> 737]] 7]  ]f]ff a  aaftfftataaatatlaaa llalp l rppp
> porrprrtoreotoctoteetetieccecotttctitio ooiofnnnona    uf
> fflfafaaatuuauullu llttlitt t ni   i niniis nn ns  sp
> suuesupupurppeevpreeervsvrrviovisirioiss ossmoro o omrr dm  omdodo
> 373] 77 ]m]]]
> dtrddteeaeer
>
>
> 3333 ]3333 p7777a ]]]]pt    y ttttprrrryeaap aappe4pp   4t ct
> oyytydoepppyd eeepe  0 e 444  0   rcc 4cioorp oid dcpe0eoe   x0d00f 0x
> fer fr ffiif0fpip fpf  rff00iff0xpfxfff8
> ffff0f0ff82fxff1ffff2dffff1cfffdfacff5aff88 58f00c 0f22s12f1 1dsd0d
> c0cxc028axa1 55d58r
>  cf  ccalcrss5saf    lg0c0asxxxs g8880s  0  xrrrx10fff80xlll
> 10aaar00gggf20sss 0 l  2c00a0r xxgxc211s1r 0000 000 x00700x2222xe1
> 710cffcc0rrr760222e8   3d 0000ccxx0r4777022150c 1ce d0f51xff5f7le82692
> 8av75eicef1el2lde00 dv0f0b1e02x00l7 8  0iiil0r0el0xves80vev p e ril 0sl
> 0px0ex 0v80x ef8 xlfrf sdsfrp07pfsx  fp801  x370axr08xsff1ffpf35ff
> faddf4f0cf73x8d70af7
> 7]]73]  ]7 d01 ]013c 813ua3f
> 77377 ]]7]]9  ]  c1a aru8e9flr7d4fwlcap7d8d pd7c[[  [[ [ 6 6 66   ..
> 666666666006...556.3630600335055335373733]33]33 33 377707]0x]]] xf  ff
> 8c0ffc
> 77]]  ]]ff    f881cu98
> 73]  ]7 39u]r 3r9 3l9lfwafw9p9u7p 5ar5 f0l370xwcd2fx1pc0ff8 0ff
> 3]7]77  ]] 0 ] f f80ppf9xici8dufd99 f0r3f.9l0f47.f4829 p0960 23l504
> cox01flwf49 oe0p8fsi0ftdpe98 i k920dts83.  t900k5a.s09c2pt k6al 7
> cdo50lk w1xo 0ef8w0.s0fext5sff6pktff i dfldtk7fo as0dw0tc17.e3ka03a
> c12t803kf  xa 2f4lk0f23sofx7c2ffwtc
> 3]77 3] ] f7 0 df]
> e a[s ct  ka 66 tk660sa.x.l66f 00cfp55kfr33f o33d0t337xe7]c] 1
> 7f3tf0iadfo9d37n470a409121f31c3aabua082l
> 33 7777]]7]  2 tcc 00a
>
> 7 ]i 0n 2scu0p
> [    66.605334] ervisor mode
> [    66.605334] trap type 4 code 0 rip 0xffffffff8021dca5 cs 0x8 rflags
> 0x10202 cr2 v0pxafnfifcf(d70)1 3actd 6b5a0 ilevel 0x8 rsp 0xffffd7013f2d3b28
> [    66.605334] curlwp 0xffff893d50aaba20 pid 162.1 lowest kstack
> 0xffffd7013f2d02c0
> [    66.605334] netbsd:vpanic+0x160
> [    66.605334] snprintf() at netbsd:snprintf
> [    66.605334] startlwp() at netbsd:startlwp
> [    66.605334] alltraps() at netbsd:alltraps+0xc3
> [    66.605334] DDB lost frame for netbsd:Xhandle_lapic_tlb+0x17, trying
> 0xffffd7013a8cce10
> [    66.605334] Xhandle_lapic_tlb() at netbsd:Xhandle_lapic_tlb+0x17
> [    66.605334] --- interrupt ---
> [    66.605334] 286:
> [    66.605334] cpu4: End traceback...
>
> [    66.605334] dumping to dev 168,15 (offset=8, size=4152523):
> [    66.605334] dump autoconfiguration error: ahcisata0 port 3: clearing
> WDCTL_RST failed for drive 0
> succeeded
>
>
> ....
>
>
> I don't seem to be able to get the core into gdb 8.3 either with target
> kvm or with target kcore. How does one do this now with this version of
> gdb?
>
>
>


-- 
----