Re: Serious crashes on 9.99.93

2021-12-30 Thread pin 
‐‐‐ Original Message ‐‐‐

On Thursday, December 30th, 2021 at 11:21 AM, Yorick Hardy 
 wrote:

> Dear current-users,
>
> I tried to reproduce the problems that pin is seeing. I seldom got
>
> as far as the web browser, but did get the following backtraces:
>
> Crash version 9.99.42, image version 9.99.93.
>
> WARNING: versions differ, you may not be able to examine this image.
>
> System panicked: pr_phinpage_check: [i915_request] item 0x939b82a4f840 
> not part of pool
>
> Backtrace from time of crash is available.
>
> _KERNEL_OPT_GENFB_GLYPHCACHE() at 0
>
> _KERNEL_OPT_GENFB_GLYPHCACHE() at 0
>
> sys_reboot() at sys_reboot
>
> vpanic() at vpanic+0x160
>
> device_printf() at device_printf
>
> pool_cache_put_paddr() at pool_cache_put_paddr+0x14f
>
> linux_dma_resv_fini() at linux_dma_resv_fini+0x55
>
> __i915_gem_free_object_rcu() at __i915_gem_free_object_rcu+0x45
>
> gc_thread() at gc_thread+0x92
>
> Crash version 9.99.42, image version 9.99.93.
>
> WARNING: versions differ, you may not be able to examine this image.
>
> System panicked: trap
>
> Backtrace from time of crash is available.
>
> _KERNEL_OPT_GENFB_GLYPHCACHE() at 0
>
> ?() at bf014f2a
>
> sys_reboot() at sys_reboot
>
> vpanic() at vpanic+0x160
>
> device_printf() at device_printf
>
> startlwp() at startlwp
>
> calltrap() at calltrap+0x19
>
> ffs_sync() at ffs_sync+0x75
>
> VFS_SYNC() at VFS_SYNC+0x22
>
> sched_sync() at sched_sync+0x90
>
> Could the first backtrace be a clue? Changes were made in this area after the 
> 15th,
>
> which is when pin still had a stable kernel.


Taylor suggested off-list that my issues looked like faulty memory.
Initially, I found it hard to believe as the crash only took place when 
launching the web browser.
Also, I had no issues the day before while running 9.99.92 from the 15th of 
December.

Moreover, I did a few memory tests and they all passed. Did also check if there 
were any available
updates to my BIOS and performed an SSD test on my drive. All good.

Taylor still insisted on faulty memory and to compile a kernel with some 
non-default options enabled.

It was although easier to open the lid of my laptop and replace the 2x4Gb RAM 
chips with a 8Gb one
I had in a box.

Surprise, no crashes until now. I used the browser for about 15 min, so not 
that extensive.
I wish to keep this thread alive until I have had the time to test this further 
and because Yorick
still experiences crashes.

That said, it will be a few days until I can do this. I did a clean re-install 
and need to set-up
my system as I like. It means building rust and leftwm-git and it's new year 
soon.

Btw, Happy New Year to all of you and thanks for all the support.

Regards,
pin

Re: Serious crashes on 9.99.93

2021-12-30 Thread Yorick Hardy 
Dear current-users,

On 2021-12-28, pin wrote:
> ‐‐‐ Original Message ‐‐‐
> 
> Unfortunately, I had to wipe my disk due to a corrupted file system.
> I did a fresh install using the 9.99.93 image from today 28-Dec-2021 08:57
> 
> The same crash happened the first time I launched the web browser.
> This time I got a stack backtrace, as follows:
> 
> 
> pin@mybox # pwd
> /var/crash
> pin@mybox # ls -l
> total 797032
> -rw---  1 root  wheel  2 Dec 28 20:41 bounds
> -rw---  1 root  wheel  5 Dec 28 00:19 minfree
> -rw---  1 root  wheel2332254 Dec 28 20:41 netbsd.0
> -rw---  1 root  wheel  405485080 Dec 28 20:41 netbsd.0.core
> pin@mybox # gdb --eval-command="file /netbsd.gdb"
> GNU gdb (GDB) 11.0.50.20200914-git
> Copyright (C) 2020 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later 
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.
> Type "show copying" and "show warranty" for details.
> This GDB was configured as "x86_64--netbsd".
> Type "show configuration" for configuration details.
> For bug reporting instructions, please see:
> .
> Find the GDB manual and other documentation resources online at:
> .
> 
> For help, type "help".
> Type "apropos word" to search for commands related to "word".
> Reading symbols from /netbsd.gdb...
> (gdb) target kvm netbsd.0.core
> 0x802261f5 in cpu_reboot (howto=howto@entry=260, 
> bootstr=bootstr@entry=0x0) at /usr/src/sys/arch/amd64/amd64/machdep.c:720
> 720 /usr/src/sys/arch/amd64/amd64/machdep.c: No such file or directory.
> (gdb) bt
> #0  0x802261f5 in cpu_reboot (howto=howto@entry=260, 
> bootstr=bootstr@entry=0x0) at /usr/src/sys/arch/amd64/amd64/machdep.c:720
> #1  0x80dbcd54 in kern_reboot (howto=howto@entry=260, 
> bootstr=bootstr@entry=0x0) at /usr/src/sys/kern/kern_reboot.c:73
> #2  0x80dffcf2 in vpanic (fmt=fmt@entry=0x81390370 "trap", 
> ap=ap@entry=0x8580b77ebab8) at /usr/src/sys/kern/subr_prf.c:290
> #3  0x80dffdb7 in panic (fmt=fmt@entry=0x81390370 "trap") at 
> /usr/src/sys/kern/subr_prf.c:209
> #4  0x80229017 in trap (frame=0x8580b77ebc00) at 
> /usr/src/sys/arch/amd64/amd64/trap.c:326
> #5  0x802210e3 in alltraps ()
> #6  0xff404040ff404040 in ?? ()
> #7  0x0019 in ?? ()
> #8  0x80f752dea000 in ?? ()
> #9  0x in ?? ()
> (gdb)
> 
> 
> 
> This did not happen before on 9.99.92 up to the 15th of December.
> Hope that this is useful.
> 
> Best Regards

I tried to reproduce the problems that pin is seeing. I seldom got
as far as the web browser, but did get the following backtraces:

  Crash version 9.99.42, image version 9.99.93.
  WARNING: versions differ, you may not be able to examine this image.
  System panicked: pr_phinpage_check: [i915_request] item 0x939b82a4f840 
not part of pool
  Backtrace from time of crash is available.
  _KERNEL_OPT_GENFB_GLYPHCACHE() at 0
  _KERNEL_OPT_GENFB_GLYPHCACHE() at 0
  sys_reboot() at sys_reboot
  vpanic() at vpanic+0x160
  device_printf() at device_printf
  pool_cache_put_paddr() at pool_cache_put_paddr+0x14f
  linux_dma_resv_fini() at linux_dma_resv_fini+0x55
  __i915_gem_free_object_rcu() at __i915_gem_free_object_rcu+0x45
  gc_thread() at gc_thread+0x92

  Crash version 9.99.42, image version 9.99.93.
  WARNING: versions differ, you may not be able to examine this image.
  System panicked: trap
  Backtrace from time of crash is available.
  _KERNEL_OPT_GENFB_GLYPHCACHE() at 0
  ?() at bf014f2a
  sys_reboot() at sys_reboot
  vpanic() at vpanic+0x160
  device_printf() at device_printf
  startlwp() at startlwp
  calltrap() at calltrap+0x19
  ffs_sync() at ffs_sync+0x75
  VFS_SYNC() at VFS_SYNC+0x22
  sched_sync() at sched_sync+0x90

Could the first backtrace be a clue? Changes were made in this area after the 
15th,
which is when pin still had a stable kernel.

-- 
Kind regards,

Yorick Hardy

Re: Serious crashes on 9.99.93

2021-12-28 Thread pin 
‐‐‐ Original Message ‐‐‐

Unfortunately, I had to wipe my disk due to a corrupted file system.
I did a fresh install using the 9.99.93 image from today 28-Dec-2021 08:57

The same crash happened the first time I launched the web browser.
This time I got a stack backtrace, as follows:


pin@mybox # pwd
/var/crash
pin@mybox # ls -l
total 797032
-rw---  1 root  wheel  2 Dec 28 20:41 bounds
-rw---  1 root  wheel  5 Dec 28 00:19 minfree
-rw---  1 root  wheel2332254 Dec 28 20:41 netbsd.0
-rw---  1 root  wheel  405485080 Dec 28 20:41 netbsd.0.core
pin@mybox # gdb --eval-command="file /netbsd.gdb"
GNU gdb (GDB) 11.0.50.20200914-git
Copyright (C) 2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64--netbsd".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word".
Reading symbols from /netbsd.gdb...
(gdb) target kvm netbsd.0.core
0x802261f5 in cpu_reboot (howto=howto@entry=260, 
bootstr=bootstr@entry=0x0) at /usr/src/sys/arch/amd64/amd64/machdep.c:720
720 /usr/src/sys/arch/amd64/amd64/machdep.c: No such file or directory.
(gdb) bt
#0  0x802261f5 in cpu_reboot (howto=howto@entry=260, 
bootstr=bootstr@entry=0x0) at /usr/src/sys/arch/amd64/amd64/machdep.c:720
#1  0x80dbcd54 in kern_reboot (howto=howto@entry=260, 
bootstr=bootstr@entry=0x0) at /usr/src/sys/kern/kern_reboot.c:73
#2  0x80dffcf2 in vpanic (fmt=fmt@entry=0x81390370 "trap", 
ap=ap@entry=0x8580b77ebab8) at /usr/src/sys/kern/subr_prf.c:290
#3  0x80dffdb7 in panic (fmt=fmt@entry=0x81390370 "trap") at 
/usr/src/sys/kern/subr_prf.c:209
#4  0x80229017 in trap (frame=0x8580b77ebc00) at 
/usr/src/sys/arch/amd64/amd64/trap.c:326
#5  0x802210e3 in alltraps ()
#6  0xff404040ff404040 in ?? ()
#7  0x0019 in ?? ()
#8  0x80f752dea000 in ?? ()
#9  0x in ?? ()
(gdb)



This did not happen before on 9.99.92 up to the 15th of December.
Hope that this is useful.

Best Regards

Re: Serious crashes on 9.99.93

2021-12-28 Thread pin 


‐‐‐ Original Message ‐‐‐

On Tuesday, December 28th, 2021 at 17:31, Yorick Hardy  
wrote:

> Dear pin,
>
> On 2021-12-28, pin wrote:
>
> > Sent with ProtonMail Secure Email.
> >
> > ‐‐‐ Original Message ‐‐‐
> >
> > On Tuesday, December 28th, 2021 at 16:29, Yorick Hardy 
> > yorickha...@gmail.com wrote:
> >
> > > Dear pin,
> > >
> > > On 2021-12-27, pin wrote:
> > >
> > > > Hi all,
> > > >
> > > > I've upgraded my amd64 machine to NetBSD-9.99.93 yesterday and I'm 
> > > > experience serious crashes which were not happening on 9.99.92.
> > > >
> > > > dmesg, https://pastebin.com/8WJeUJDj
> > > >
> > > > Xorg-log, https://pastebin.com/xTAmUZPU
> > > >
> > > > The backtraces from the coredumps aren't really useful, 
> > > > https://pastebin.com/eaXYEC0Z
> > > >
> > > > I've managed to reproduce the crashes by launching lariza or badwolf 
> > > > web browsers.
> > > >
> > > > The system runs without issues if I don't use a web browser.
> > > >
> > > > Also, I've noticed the following while booting after a crash
> > > >
> > > > panic: kernel diagnostic assertion "solocked2(so, so2)" failed: file 
> > > > "/usr/src/sys/kern/uipc_usrreq.c", line 525
> > > >
> > > > Finally, unsure if related, console resolution doesn't scale after 
> > > > loading i915drmkms0, it used to in 9.99.92.
> > > >
> > > > Although, resolution after startx is correct.
> > > >
> > > > I've hosted the core-dumps in case,
> > > >
> > > > netbsd.2.core.gz, https://ufile.io/d00lfx4f
> > > >
> > > > netbsd.2.gz, https://ufile.io/4yvklq5w
> > > >
> > > > Thank you for any hints.
> > > >
> > > > Best,
> > > >
> > > > pin
> > > >
> > > > Sent with ProtonMail Secure Email.
> > >
> > > Somehow I managed to get a backtrace (it seems to be correct):
> > >
> > > Crash version 9.99.82, image version 9.99.93.
> > >
> > > WARNING: versions differ, you may not be able to examine this image.
> > >
> > > crash: _kvm_kvatop(0)
> > >
> > > Kernel compiled without options LOCKDEBUG.
> > >
> > > System panicked: kernel diagnostic assertion "solocked2(so, so2)" failed: 
> > > file "/usr/src/sys/kern/uipc_usrreq.c", line 525
> > >
> > > Backtrace from time of crash is available.
> > >
> > > crash> bt
> > >
> > > _KERNEL_OPT_GENFB_GLYPHCACHE() at 0
> > >
> > > _KERNEL_OPT_GENFB_GLYPHCACHE() at 0
> > >
> > > sys_reboot() at sys_reboot
> > >
> > > vpanic() at vpanic+0x160
> > >
> > > __x86_indirect_thunk_rax() at __x86_indirect_thunk_rax
> > >
> > > unp_send() at unp_send+0xa15
> > >
> > > sosend() at sosend+0x845
> > >
> > > soo_write() at soo_write+0x2f
> > >
> > > do_filewritev.part.0() at do_filewritev.part.0+0x25d
> > >
> > > syscall() at syscall+0x196
> > >
> > > --- syscall (number 121) ---
> > >
> > > syscall+0x196:
> > >
> > > crash>
> > >
> > > the last change I could find which might be relevant was in 
> > > sys/kern/sys_generic.c 1.133, but that
> > >
> > > was before 9.99.93, so I am not sure where to look.
> > >
> > > Kind regards,
> > >
> > > Yorick Hardy
> >
> > Thanks!
> >
> > Was this change made in 9.99.92 after the 15th of December?
> >
> > Until the above date this did not happen.
> >
> > Regards
>
> 11 September, so: long before! But thanks, I will continue to look
>
> for any changes after 15 December (I am sure someone more knowledgeable
>
> will find it, but I will have a go in the mean time).
>
> -
>
> Kind regards,
>
> Yorick Hardy

Thank you!

I've managed to get out netbsd.gdb from the system, https://ufile.io/httct5ef

Re-installing now, got a corrupted fs.

Best Regards

Re: Serious crashes on 9.99.93

2021-12-28 Thread Yorick Hardy 
Dear pin,

On 2021-12-28, pin wrote:
> 
> 
> Sent with ProtonMail Secure Email.
> 
> ‐‐‐ Original Message ‐‐‐
> 
> On Tuesday, December 28th, 2021 at 16:29, Yorick Hardy 
>  wrote:
> 
> > Dear pin,
> >
> > On 2021-12-27, pin wrote:
> >
> > > Hi all,
> > >
> > > I've upgraded my amd64 machine to NetBSD-9.99.93 yesterday and I'm 
> > > experience serious crashes which were not happening on 9.99.92.
> > >
> > > dmesg, https://pastebin.com/8WJeUJDj
> > >
> > > Xorg-log, https://pastebin.com/xTAmUZPU
> > >
> > > The backtraces from the coredumps aren't really useful, 
> > > https://pastebin.com/eaXYEC0Z
> > >
> > > I've managed to reproduce the crashes by launching lariza or badwolf web 
> > > browsers.
> > >
> > > The system runs without issues if I don't use a web browser.
> > >
> > > Also, I've noticed the following while booting after a crash
> > >
> > > panic: kernel diagnostic assertion "solocked2(so, so2)" failed: file 
> > > "/usr/src/sys/kern/uipc_usrreq.c", line 525
> > >
> > > Finally, unsure if related, console resolution doesn't scale after 
> > > loading i915drmkms0, it used to in 9.99.92.
> > >
> > > Although, resolution after startx is correct.
> > >
> > > I've hosted the core-dumps in case,
> > >
> > > netbsd.2.core.gz, https://ufile.io/d00lfx4f
> > >
> > > netbsd.2.gz, https://ufile.io/4yvklq5w
> > >
> > > Thank you for any hints.
> > >
> > > Best,
> > >
> > > pin
> > >
> > > Sent with ProtonMail Secure Email.
> >
> > Somehow I managed to get a backtrace (it seems to be correct):
> >
> > Crash version 9.99.82, image version 9.99.93.
> >
> > WARNING: versions differ, you may not be able to examine this image.
> >
> > crash: _kvm_kvatop(0)
> >
> > Kernel compiled without options LOCKDEBUG.
> >
> > System panicked: kernel diagnostic assertion "solocked2(so, so2)" failed: 
> > file "/usr/src/sys/kern/uipc_usrreq.c", line 525
> >
> > Backtrace from time of crash is available.
> >
> > crash> bt
> >
> > _KERNEL_OPT_GENFB_GLYPHCACHE() at 0
> >
> > _KERNEL_OPT_GENFB_GLYPHCACHE() at 0
> >
> > sys_reboot() at sys_reboot
> >
> > vpanic() at vpanic+0x160
> >
> > __x86_indirect_thunk_rax() at __x86_indirect_thunk_rax
> >
> > unp_send() at unp_send+0xa15
> >
> > sosend() at sosend+0x845
> >
> > soo_write() at soo_write+0x2f
> >
> > do_filewritev.part.0() at do_filewritev.part.0+0x25d
> >
> > syscall() at syscall+0x196
> >
> > --- syscall (number 121) ---
> >
> > syscall+0x196:
> >
> > crash>
> >
> > the last change I could find which might be relevant was in 
> > sys/kern/sys_generic.c 1.133, but that
> >
> > was before 9.99.93, so I am not sure where to look.
> >
> > --
> >
> > Kind regards,
> >
> > Yorick Hardy
> 
> Thanks!
> 
> Was this change made in 9.99.92 after the 15th of December?
> 
> Until the above date this did not happen.
> 
> Regards

11 September, so: long before! But thanks, I will continue to look
for any changes after 15 December (I am sure someone more knowledgeable
will find it, but I will have a go in the mean time).

-- 
Kind regards,

Yorick Hardy

Re: Serious crashes on 9.99.93

2021-12-28 Thread pin 



Sent with ProtonMail Secure Email.

‐‐‐ Original Message ‐‐‐

On Tuesday, December 28th, 2021 at 16:29, Yorick Hardy  
wrote:

> Dear pin,
>
> On 2021-12-27, pin wrote:
>
> > Hi all,
> >
> > I've upgraded my amd64 machine to NetBSD-9.99.93 yesterday and I'm 
> > experience serious crashes which were not happening on 9.99.92.
> >
> > dmesg, https://pastebin.com/8WJeUJDj
> >
> > Xorg-log, https://pastebin.com/xTAmUZPU
> >
> > The backtraces from the coredumps aren't really useful, 
> > https://pastebin.com/eaXYEC0Z
> >
> > I've managed to reproduce the crashes by launching lariza or badwolf web 
> > browsers.
> >
> > The system runs without issues if I don't use a web browser.
> >
> > Also, I've noticed the following while booting after a crash
> >
> > panic: kernel diagnostic assertion "solocked2(so, so2)" failed: file 
> > "/usr/src/sys/kern/uipc_usrreq.c", line 525
> >
> > Finally, unsure if related, console resolution doesn't scale after loading 
> > i915drmkms0, it used to in 9.99.92.
> >
> > Although, resolution after startx is correct.
> >
> > I've hosted the core-dumps in case,
> >
> > netbsd.2.core.gz, https://ufile.io/d00lfx4f
> >
> > netbsd.2.gz, https://ufile.io/4yvklq5w
> >
> > Thank you for any hints.
> >
> > Best,
> >
> > pin
> >
> > Sent with ProtonMail Secure Email.
>
> Somehow I managed to get a backtrace (it seems to be correct):
>
> Crash version 9.99.82, image version 9.99.93.
>
> WARNING: versions differ, you may not be able to examine this image.
>
> crash: _kvm_kvatop(0)
>
> Kernel compiled without options LOCKDEBUG.
>
> System panicked: kernel diagnostic assertion "solocked2(so, so2)" failed: 
> file "/usr/src/sys/kern/uipc_usrreq.c", line 525
>
> Backtrace from time of crash is available.
>
> crash> bt
>
> _KERNEL_OPT_GENFB_GLYPHCACHE() at 0
>
> _KERNEL_OPT_GENFB_GLYPHCACHE() at 0
>
> sys_reboot() at sys_reboot
>
> vpanic() at vpanic+0x160
>
> __x86_indirect_thunk_rax() at __x86_indirect_thunk_rax
>
> unp_send() at unp_send+0xa15
>
> sosend() at sosend+0x845
>
> soo_write() at soo_write+0x2f
>
> do_filewritev.part.0() at do_filewritev.part.0+0x25d
>
> syscall() at syscall+0x196
>
> --- syscall (number 121) ---
>
> syscall+0x196:
>
> crash>
>
> the last change I could find which might be relevant was in 
> sys/kern/sys_generic.c 1.133, but that
>
> was before 9.99.93, so I am not sure where to look.
>
> --
>
> Kind regards,
>
> Yorick Hardy

Thanks!

Was this change made in 9.99.92 after the 15th of December?

Until the above date this did not happen.

Regards

Re: Serious crashes on 9.99.93

2021-12-28 Thread Yorick Hardy 
Dear pin,

On 2021-12-27, pin wrote:
> Hi all,
> I've upgraded my amd64 machine to NetBSD-9.99.93 yesterday and I'm experience 
> serious crashes which were not happening on 9.99.92.
> dmesg, https://pastebin.com/8WJeUJDj
> Xorg-log, https://pastebin.com/xTAmUZPU
> 
> The backtraces from the coredumps aren't really useful, 
> https://pastebin.com/eaXYEC0Z
> 
> I've managed to reproduce the crashes by launching lariza or badwolf web 
> browsers.
> The system runs without issues if I don't use a web browser.
> Also, I've noticed the following while booting after a crash
> 
> panic: kernel diagnostic assertion "solocked2(so, so2)" failed: file 
> "/usr/src/sys/kern/uipc_usrreq.c", line 525
> 
> Finally, unsure if related, console resolution doesn't scale after loading 
> i915drmkms0, it used to in 9.99.92.
> Although, resolution after startx is correct.
> 
> I've hosted the core-dumps in case,
> netbsd.2.core.gz, https://ufile.io/d00lfx4f
> netbsd.2.gz, https://ufile.io/4yvklq5w
> 
> Thank you for any hints.
> Best,
> pin
> 
> Sent with ProtonMail Secure Email.

Somehow I managed to get a backtrace (it seems to be correct):

  Crash version 9.99.82, image version 9.99.93.
  WARNING: versions differ, you may not be able to examine this image.
  crash: _kvm_kvatop(0)
  Kernel compiled without options LOCKDEBUG.
  System panicked: kernel diagnostic assertion "solocked2(so, so2)" failed: 
file "/usr/src/sys/kern/uipc_usrreq.c", line 525
  Backtrace from time of crash is available.
  crash> bt
  _KERNEL_OPT_GENFB_GLYPHCACHE() at 0
  _KERNEL_OPT_GENFB_GLYPHCACHE() at 0
  sys_reboot() at sys_reboot
  vpanic() at vpanic+0x160
  __x86_indirect_thunk_rax() at __x86_indirect_thunk_rax
  unp_send() at unp_send+0xa15
  sosend() at sosend+0x845
  soo_write() at soo_write+0x2f
  do_filewritev.part.0() at do_filewritev.part.0+0x25d
  syscall() at syscall+0x196
  --- syscall (number 121) ---
  syscall+0x196:
  crash>

the last change I could find which might be relevant was in 
sys/kern/sys_generic.c 1.133, but that
was before 9.99.93, so I am not sure where to look.

-- 
Kind regards,

Yorick Hardy

Serious crashes on 9.99.93

2021-12-27 Thread pin 
Hi all,
I've upgraded my amd64 machine to NetBSD-9.99.93 yesterday and I'm experience 
serious crashes which were not happening on 9.99.92.
dmesg, https://pastebin.com/8WJeUJDj
Xorg-log, https://pastebin.com/xTAmUZPU

The backtraces from the coredumps aren't really useful, 
https://pastebin.com/eaXYEC0Z

I've managed to reproduce the crashes by launching lariza or badwolf web 
browsers.
The system runs without issues if I don't use a web browser.
Also, I've noticed the following while booting after a crash

panic: kernel diagnostic assertion "solocked2(so, so2)" failed: file 
"/usr/src/sys/kern/uipc_usrreq.c", line 525

Finally, unsure if related, console resolution doesn't scale after loading 
i915drmkms0, it used to in 9.99.92.
Although, resolution after startx is correct.

I've hosted the core-dumps in case,
netbsd.2.core.gz, https://ufile.io/d00lfx4f
netbsd.2.gz, https://ufile.io/4yvklq5w

Thank you for any hints.
Best,
pin

Sent with ProtonMail Secure Email.