On Sat, 12 Jun 2021 at 14:19, BERTRAND Joël <joel.bertr...@systella.fr> wrote: > > Michael van Elst a écrit : > > joel.bertr...@systella.fr (=?UTF-8?Q?BERTRAND_Jo=c3=abl?=) writes: > > > >>> If you have a version of the kernel with debug symbols, you could > >>> use addr2line to identify the instruction that caused the uvm_fault > >>> at address 0xffffffff802280cc. Without debug symbols it is not > >>> that easy. > > > >> I have this kind of kernel, but I cannot obtain more information. > > > > addr2line -e $yourdebugkernel 0xffffffff802280cc > > > > should retrieve some information. > > Nope... > > legendre:[/] > addr2line -e netbsd.gdb 0xffffffff802280cc > ??:? > legendre:[/] > > > > Not that this has any connection to your problem, but I'd nevertheless add my 5c about istgt - I have been serving zvols for perhaps one year now under -current without any problems.
-- ----