Date: Fri, 11 Jun 2021 09:56:18 +0200 From: Emmanuel Vadot <manu@bidouilliste.com> To: "Herbert J. Skuhra" <herbert@gojira.at> Cc: freebsd-arm@freebsd.org Subject: Re: Easily reproducible stable/13 kernel crash Message-ID: <20210611095618.5df5abbe6696671a8966af65@bidouilliste.com> In-Reply-To: <87v96kvo77.wl-herbert@gojira.at> References: <63c37775-f1f6-def7-1ca2-4ac0460c46e2@shrew.net> <87y2bhuehz.wl-herbert@gojira.at> <87wnr0vq79.wl-herbert@gojira.at> <20210611091916.9e3d5fa55303a68dbfb1f6d2@bidouilliste.com> <87v96kvo77.wl-herbert@gojira.at>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 11 Jun 2021 09:46:04 +0200 "Herbert J. Skuhra" <herbert@gojira.at> wrote: > On Fri, 11 Jun 2021 09:19:16 +0200, Emmanuel Vadot wrote: > > > Can't reproduce here (running a stable_13-n245022-7d588615865 freshly > > built) on sopine. > > You could try to find which tree of the sysctl causes this (sysctl > > hw ; sysctl vm etc ...) > > net.inet.tcp.lro > > The last displayed line is: > > net.inet.tcp.path_mtu_discovery: 1 > > -- > Herbert > So just doing sysctl net.inet.tcp.lro make the board panic ? -- Emmanuel Vadot <manu@bidouilliste.com> <manu@FreeBSD.org>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20210611095618.5df5abbe6696671a8966af65>