Date: Sun, 23 Jan 2005 19:07:28 -0800 From: Kris Kennaway <kris@obsecurity.org> To: "Marcos Biscaysaqu - ThePacific.net" <marcos@ThePacific.Net> Cc: freebsd-current@freebsd.org Subject: Re: BSD 5.3 crashes, "ath0: [GIANT-LOCKED]" Message-ID: <20050124030728.GA95899@xor.obsecurity.org> In-Reply-To: <41F513D7.6040801@ThePacific.Net> References: <41F513D7.6040801@ThePacific.Net>
next in thread | previous in thread | raw e-mail | index | archive | help
--BXVAT5kNtrzKuDFl Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jan 24, 2005 at 03:27:19PM +0000, Marcos Biscaysaqu - ThePacific.ne= t wrote: > Hi there >=20 > Im upgrade more than 50 boxes BSD5.2.1 to BSD5.3, and I started to have= =20 > a lot of crashes, Im runing BSD from RAM. all the boxes been working=20 > perfect in 5.2.1 but now Im having a lot of problems. >=20 > Im have repited dmesgs of my networks card with [GIANT-LOCKED] option and= : > "WARNING: debug.mpsafenet forced to 0 as ipsec requires Giant" > "WARNING: MPSAFE network stack disabled, expect reduced performance" These aren't errors. ipsec isn't yet mpsafe, so you can't run the network stack without Giant (i.e. just like older releases). > please let me know if you need more info. Yes, we need details of the actual crashes. See the chapter on kernel debugging in the developers' handbook to find out how to obtain the necessary debugging information. Kris --BXVAT5kNtrzKuDFl Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFB9GZwWry0BWjoQKURAgwEAKC4ZkhmpaznYeR+UCLz0TfwlYMXtwCg1wvB 1msVPTYJQfF/BAPWslqTWIU= =jbRn -----END PGP SIGNATURE----- --BXVAT5kNtrzKuDFl--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050124030728.GA95899>