Date: Wed, 31 Mar 2010 18:50:12 GMT From: Nathaniel W Filardo <nwf@cs.jhu.edu> To: freebsd-sparc64@FreeBSD.org Subject: Re: kern/145211: Memory modified after free Message-ID: <201003311850.o2VIoCE4014962@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR sparc64/145211; it has been noted by GNATS. From: Nathaniel W Filardo <nwf@cs.jhu.edu> To: bug-followup@freebsd.org Cc: Subject: Re: kern/145211: Memory modified after free Date: Wed, 31 Mar 2010 14:49:40 -0400 --vDpvzslK0qRw06MN Content-Type: text/plain; charset=us-ascii Content-Disposition: inline It occurs to me to add that at least the second crash was correlated with a burst of traffic on bge2, which usually sits idle. FWIW, bge0 and bge3 are typically busy, and bge1 is not connected. Is it possible that this is a bge bug? I'll be recreating the busy-bge2 scenario to test other things anyway and will report should it trigger a panic again. While I'm recovering from filing an underinformative bug report, I'll note that the machine is a Sun Fire V210 (with 2G of RAM and 2 1GHz CPUs). Anything else that would help? --nwf; --vDpvzslK0qRw06MN Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkuzmUQACgkQTeQabvr9Tc/LkgCcCsjzML2Y64L3dFCpBLt8Wrhz AjMAoIbbsLVLuxqQOAzHnoPcfv2/h72A =tU8H -----END PGP SIGNATURE----- --vDpvzslK0qRw06MN--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201003311850.o2VIoCE4014962>