Re: instability in -current ?

[Nick Hudson <nick.hudson%gmx.co.uk@localhost>]

On 09/12/2019 21:11, Michael Cheponis wrote:
> I am still seeing instability in 9.99.20.
>
> What I do is cvs checkout src ; ./build.sh -j 9 ; then I install the
> resulting kernel and do it all over again, by first deleting /usr/src/
> This takes a day or two, so I get these sort-of 48-hour snapshots.
>
>
> Trying to build most recently yielded:
>
> *Dec  9 11:00:03 S syslogd[190]: restart
> Dec  9 13:35:22 S syslogd[228]: restart
> Dec  9 13:35:22 S /netbsd: [ 55977.4574372] panic: kernel diagnostic
> assertion "!cpu_intr_p()" failed: file
> "/c/usr/src/sys/uvm/pmap/pmap_tlb.c", line 979
> Dec  9 13:35:22 S /netbsd: [ 55977.4574372] cpu0: Begin traceback...
> Dec  9 13:35:22 S /netbsd: [ 55977.4574372] 0x9de71a44: netbsd:vpanic+0x16c
> Dec  9 13:35:22 S /netbsd: [ 55977.4574372] Bad frame pointer: 0x80acbb3c
> Dec  9 13:35:22 S /netbsd: [ 55977.4574372] cpu0: End traceback...
> Dec  9 13:35:22 S /netbsd:
> Dec  9 13:35:22 S /netbsd: [ 55977.4574372] dump to dev 92,1 not possible
> Dec  9 13:35:22 S /netbsd: [ 55977.4574372] rebooting...*

Can you get it to drop into ddb and get things like "ps /l"? Maybe we
can get some more hints from ddb

Thanks,
Nick