Date: Thu, 22 May 2014 21:59:57 -0400 From: Eric Benoit <eric@ecks.ca> To: freebsd-sparc64@freebsd.org Subject: Re: FreeBSD 10-STABLE/sparc64 panic Message-ID: <537EAB9D.9020304@ecks.ca> In-Reply-To: <AB5649B5-BBFB-4284-9CFF-4784D28A18F3@distal.com> References: <20140518083413.GK24043@gradx.cs.jhu.edu> <751F7778-95CE-40FC-857F-222FB37737C0@distal.com> <20140518235853.GM24043@gradx.cs.jhu.edu> <20140519145222.GN24043@gradx.cs.jhu.edu> <A092DFEB-D5CF-473E-88BD-81B005C26C57@distal.com> <20140519193529.GO24043@gradx.cs.jhu.edu> <20140519205047.GP24043@gradx.cs.jhu.edu> <CA75738D-066D-4EDC-9018-89936EE861C6@distal.com> <AB5649B5-BBFB-4284-9CFF-4784D28A18F3@distal.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2014-05-20 10:45, Chris Ross wrote: > Despite the first boot working successfully, I rebooted it > again this morning, after it had been running for quite a few hours, > and the panic occurred 6 times before the system came up to > multiuser successfully. Just out of curiosity, and this is also for anyone else following along, are you using IPv6 and have something like: ifconfig_bge0_ipv6="inet6 accept_rtadv" in your /etc/rc.conf? My inglorious workaround was to remove (comment out) this line. Every build from r263478 to the latest and greatest has come up consistently and without issue. Since I actually do use IPv6 and SLAAC, I just re-enable these from rc.local. It seems once the system is mostly booted, this issue is no longer an issue. Perhaps this is a clue towards a proper fix? Later
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?537EAB9D.9020304>