Date: Wed, 1 Jul 2015 11:18:37 +0200 From: Fabian Keil <freebsd-listen@fabiankeil.de> To: freebsd-stable@freebsd.org Subject: Re: New FreeBSD snapshots available: stable/10 (20150625 r284813) Message-ID: <128bd010.19091599@fabiankeil.de> In-Reply-To: <56A9EB91-2F97-4096-99C8-26D3EFC13D2D@distal.com> References: <20150626174927.GA69720@FreeBSD.org> <559330CF.2050606@pix.net> <20150701001613.GH5423@FreeBSD.org> <55934CFB.7050407@pix.net> <56A9EB91-2F97-4096-99C8-26D3EFC13D2D@distal.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--Sig_/ipAlNPWjfH+llhPk9s0hg8W Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Chris Ross <cross+freebsd@distal.com> wrote: > Yeah, this is the same panic you, I, and others have been seeing on > sparc64's with bge's, or at least v240's (and one other IIRC) for many > many months. Thanks for grabbing a core! Does it make a difference if you boot with hw.bge.allow_asf=3D0? According to the man page it is known to "cause system lockup problems on a small number of systems". It's not obvious to me why it's enabled by default on FreeBSD and I disable it on all my systems. Fabian --Sig_/ipAlNPWjfH+llhPk9s0hg8W Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlWTsGoACgkQBYqIVf93VJ10TQCdG3xuhWRSpcV3SM3dIktEM9hj MSYAoJm+dwEQJgZ/ETMF4Pdy7/+5d59H =nN6P -----END PGP SIGNATURE----- --Sig_/ipAlNPWjfH+llhPk9s0hg8W--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?128bd010.19091599>