Date: Mon, 1 Oct 2018 11:19:22 +0200 From: Mateusz Guzik <mjguzik@gmail.com> To: Konstantin Belousov <kostikbel@gmail.com> Cc: Yuri Pankov <yuripv@yuripv.net>, freebsd-current <freebsd-current@freebsd.org> Subject: Re: vmstat -m and netstat -m dumping core when run on vmcores Message-ID: <CAGudoHFaM3o_rCzj_u8m43Bro1JKyWL_3VdYgi9cUUvAZ680_g@mail.gmail.com> In-Reply-To: <20181001090031.GC5335@kib.kiev.ua> References: <a340dd41-9ab9-5330-39c8-d188616e0244@yuripv.net> <20181001090031.GC5335@kib.kiev.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
On 10/1/18, Konstantin Belousov <kostikbel@gmail.com> wrote: > On Mon, Oct 01, 2018 at 09:15:46AM +0300, Yuri Pankov wrote: >> Hi, >> >> I've noticed the following rebooting after a panic: >> >> pid 41246 (vmstat), uid 0: exited on signal 11 (core dumped) >> pid 47091 (netstat), uid 0: exited on signal 11 >> >> And indeed, trying to manually run those on the resulting vmcore makes >> them crash: >> >> # vmstat -m -M /var/crash/vmcore.0 >> Segmentation fault (core dumped) >> # netstat -m -M /var/crash/vmcore.0 >> Segmentation fault >> >> Backtrace is below: >> >> * thread #1, name = 'vmstat', stop reason = signal SIGSEGV >> * frame #0: 0x000000080026d19f >> libmemstat.so.3`memstat_kvm_malloc(list=0x00000008007c5000, >> kvm_handle=0x000000080070e000) at memstat_malloc.c:351 >> frame #1: 0x0000000000204b15 vmstat`main [inlined] domemstat_malloc >> at vmstat.c:1406 >> frame #2: 0x0000000000204af4 vmstat`main(argc=<unavailable>, >> argv=0x00007fffffffeb28) at vmstat.c:386 >> frame #3: 0x0000000000204095 vmstat`_start(ap=<unavailable>, >> cleanup=<unavailable>) at crt1.c:74 >> >> Wonder if it's just me or something is broken here? > > I think this is due to r338899. libmemstat needs an adjustments to handle > that. > Indeed, I'll take care of it. Thanks for the report. -- Mateusz Guzik <mjguzik gmail.com>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAGudoHFaM3o_rCzj_u8m43Bro1JKyWL_3VdYgi9cUUvAZ680_g>