Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 24 Aug 2015 15:20:26 -0500
From:      Mark Felder <feld@FreeBSD.org>
To:        Konstantin Belousov <kostikbel@gmail.com>
Cc:        freebsd-current@freebsd.org
Subject:   Re: pkg with an ssh repo crashes CURRENT
Message-ID:  <1440447626.1845381.364831585.23530DD6@webmail.messagingengine.com>
In-Reply-To: <20150820221852.GX2072@kib.kiev.ua>
References:  <1440014993.2793501.360634953.2FF3B076@webmail.messagingengine.com> <1440021176.3252738.360727753.7FEDAB82@webmail.messagingengine.com> <20150820115041.GU2072@kib.kiev.ua> <1440102370.941813.361650057.269DD227@webmail.messagingengine.com> <20150820221852.GX2072@kib.kiev.ua>

next in thread | previous in thread | raw e-mail | index | archive | help


On Thu, Aug 20, 2015, at 17:18, Konstantin Belousov wrote:
> On Thu, Aug 20, 2015 at 03:26:10PM -0500, Mark Felder wrote:
> > 
> > I've recreated this in a bhyve VM with the latest CURRENT snapshot,
> > r286893. You can grab the whole /var/crash dump at
> > https://feld.me/freebsd/crash.tar.gz
> vmcore is useless without matching kernel.debug.
> 
> > 
> > I've pasted the ps output below, but it's also included in the info.0
> > file.
> And this is not very useful without the preceeding panic message and
> other
> bits from the panic handler.
> 
> I guess the process 666 was current when the panic occured ?
> Basically, what I want is to see the p_reaper value for the process
> with the pid 667.  Even just p_reaper->p_pid is enough.
> 

Do you need me to recreate the issue and provide you a matching vmcore
and kernel.debug as well as full scrollback before the panic message and
ddb output (bt, ps, etc) ?



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1440447626.1845381.364831585.23530DD6>