Date: Sun, 3 Oct 2004 13:33:18 -0700 From: Kris Kennaway <kris@obsecurity.org> To: Sascha Schumann <sascha@schumann.cx> Cc: freebsd-current@freebsd.org Subject: Re: Conclusion of thread "Deadlocks with recent SMP current"? Message-ID: <20041003203318.GA26177@xor.obsecurity.org> In-Reply-To: <Pine.LNX.4.60.0410032156300.10247@lx> References: <Pine.LNX.4.60.0410022154210.1355@localhost> <Pine.LNX.4.60.0410022223070.1355@localhost> <20041002210024.GA55807@xor.obsecurity.org> <Pine.LNX.4.60.0410032156300.10247@lx>
next in thread | previous in thread | raw e-mail | index | archive | help
--k1lZvvs/B4yU6o8G Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Oct 03, 2004 at 10:10:21PM +0200, Sascha Schumann wrote: > Just to give an update on our progress. >=20 > db server: Was upgraded to RELENG_5 with conservative > settings (no CPUTYPE, kernel config basically GENERIC except > an increased MAXDSIZ). Worked ok until we put some load onto > it. Crashed hard after about an hour of doing some work. >=20 > www server: Booted cleanly into 5.3 kernel, but would not > boot anymore after the following installworld. Deadlocks > during boot with all tested kernels - even those from a 5.2 > install medium and the previously successfully running 5.2.1 > kernel. =20 > =20 > vga0: <bla> > adv1: Invalid baseport of <bla> specified. Nearest etc. > <deadlock> >=20 > Both machines are 4xP4 Xeons with 4GB of RAM. If anyone is > interested in details, let me know. Yes, you'll need to provide actual details if you want someone to try to fix your problems. Kris --k1lZvvs/B4yU6o8G Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBYGIOWry0BWjoQKURArmUAKDAZeaaNPPyaG4HwMaW8it78fH1DACfVHLt vUYs4Q7s/ALKTqFzfRHbjh8= =jhKr -----END PGP SIGNATURE----- --k1lZvvs/B4yU6o8G--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041003203318.GA26177>