Date: Tue, 6 Jan 2015 16:27:34 -0800 From: Adrian Chadd <adrian@freebsd.org> To: sthaug@nethelp.no Cc: Craig Rodrigues <rodrigc@freebsd.org>, FreeBSD Stable Mailing List <freebsd-stable@freebsd.org> Subject: Re: 10.1-STABLE/i386 GENERIC + VIMAGE: Panic when going multiuser Message-ID: <CAJ-VmomPK6y1sFOpSCca6oJxKMWsNdh494PUB%2BhzGGq_oSMxgQ@mail.gmail.com> In-Reply-To: <20150106.195509.71132582.sthaug@nethelp.no> References: <CAG=rPVcEidZUZmvCxiDzZg1c-A98yt_B=Jq0cPT-w2xmmevOgQ@mail.gmail.com> <20150105.232339.74735411.sthaug@nethelp.no> <CAG=rPVf=_Xe%2Bz_5RAGXPeX%2BWQbM_Z7pPhz7WFeGs0eEpZcDBTw@mail.gmail.com> <20150106.195509.71132582.sthaug@nethelp.no>
next in thread | previous in thread | raw e-mail | index | archive | help
On 6 January 2015 at 10:55, <sthaug@nethelp.no> wrote: >> > Unfortunately, there is *no* IPv6 config on the box (aside from what >> > might be done by default). rc.conf: >> > >> > hostname="verdi.nethelp.no" >> > keymap="norwegian.iso.kbd" >> > ifconfig_bge1="inet 10.0.0.2 netmask 255.255.255.252" >> > sshd_enable="YES" >> > dumpdev="AUTO" >> > ddb_enable="YES" >> > background_fsck="NO" >> > >> >> >> That config is minimal, so I don't see anything offhand which would trigger >> IPv6. >> But there could be something else running on the system that triggers it. >> >> Do you have *any* kernel modules which are installed on the system and not >> built as part of the buildworld/buildkernel process? For example, kernel >> modules >> installed via a port? > > No modules. > >> Lastly, since your crash is triggered by "sysctl -a" with VIMAGE and DDB >> added to a GENERIC kernel config in 10.1, >> can you see the last sysctl which is printed out before the panic occurs? > > I have done a bit more testing with sysctl. There are two specific > sysctls which trigger the panic: > > net.inet6.ip6.temppltime > net.inet6.ip6.tempvltime > > All the other sysctls are fine, no panic generated. > > What can I do to help debug this further? The box where this happens > isn't doing anything else useful at the moment, so can be crashed at > will :-) Crash it, get the coredump into kgdb and pull out more information about the variables involved. The kernel coredump output above is useful, but it'd be much more useful to debug with a corefile and kgdb. :) -adrian > > Steinar Haug, Nethelp consulting, sthaug@nethelp.no > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-VmomPK6y1sFOpSCca6oJxKMWsNdh494PUB%2BhzGGq_oSMxgQ>