Date: Fri, 12 Mar 2004 16:47:17 -0800 From: Kris Kennaway <kris@obsecurity.org> To: Marius Strobl <marius@alchemy.franken.de> Cc: Ken Smith <kensmith@freebsd.org> Subject: Re: cvs commit: src/sys/kern subr_smp.c Message-ID: <20040313004717.GA48129@xor.obsecurity.org> In-Reply-To: <20040313001320.G99120@newtrinity.zeist.de> References: <200403122035.i2CKZMdp076683@repoman.freebsd.org> <20040312215636.GC46054@xor.obsecurity.org> <20040313001320.G99120@newtrinity.zeist.de>
next in thread | previous in thread | raw e-mail | index | archive | help
--ew6BAiZeqk4r7MaW Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Mar 13, 2004 at 12:13:20AM +0100, Marius Strobl wrote: > On Fri, Mar 12, 2004 at 01:56:37PM -0800, Kris Kennaway wrote: > > On Fri, Mar 12, 2004 at 12:35:22PM -0800, Ken Smith wrote: > > > kensmith 2004/03/12 12:35:22 PST > > >=20 > > > FreeBSD src repository > > >=20 > > > Modified files: > > > sys/kern subr_smp.c=20 > > > Log: > > > This is a temporary fix to solve a regression issue on sparc64 that > > > is caused by the way sparc64 registers its CPUs. Nate will work on > > > a real fix shortly. > >=20 > > Is this likely to fix the panics at boot time I'm having on my Ultra 30? > >=20 >=20 > The cdevsw changes seem to have broken FreeBSD/sparc64 when using sc(4) > in a similar way they broke FreeBSD/alpha. That sounds about right..it panics really early in the boot sequence [1] at around the time syscons would be initialized. Kris [1] the dreaded "Fast Access Data MMU Miss" --ew6BAiZeqk4r7MaW Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAUloVWry0BWjoQKURAofpAJ4zmGGa26L3SwprB3ypGoBMxteRJwCgtitu xCGT5LiezYN87pS5+GmyIRM= =53nO -----END PGP SIGNATURE----- --ew6BAiZeqk4r7MaW--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040313004717.GA48129>