From owner-freebsd-stable@freebsd.org Mon Sep 7 06:48:24 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8C66F9CC067 for ; Mon, 7 Sep 2015 06:48:24 +0000 (UTC) (envelope-from peter@wemm.org) Received: from smtp2.wemm.org (smtp2.wemm.org [IPv6:2001:470:67:39d::78]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp2.wemm.org", Issuer "StartCom Class 1 Primary Intermediate Server CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 75795970 for ; Mon, 7 Sep 2015 06:48:24 +0000 (UTC) (envelope-from peter@wemm.org) Received: from overcee.wemm.org (canning.wemm.org [192.203.228.65]) by smtp2.wemm.org (Postfix) with ESMTP id 08C701DE; Sun, 6 Sep 2015 23:48:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=wemm.org; s=m20140428; t=1441608504; bh=XR8/7qeeFqQK6ibP8knbK6nziIp/K7K/tgkU9JSG0dk=; h=From:To:Cc:Subject:Date:In-Reply-To:References; b=DG/acVqaUJhrs8DfFewONdve4KD7j8eSTbuZX7OmJi50JqzA1/eQxMCiLCTZbqm4t 53PloPP+4RTmlfXtI8RVtkrnqZBcfJtZr6ZmPF84aTJZJDUuPM+JwqV/y3klBsvWAV dmV7ilxgIxMOoVLDD6UCKBDmP6vnl484V89gHmkA= From: Peter Wemm To: freebsd-stable@freebsd.org, mexas@bris.ac.uk Cc: marcel@xcllnt.net, kostikbel@gmail.com Subject: Re: ia64 stable/10 r286316: hang at Entering /boot/kernel/kernel Date: Sun, 06 Sep 2015 23:48:18 -0700 Message-ID: <1939276.T7b5bOdInc@overcee.wemm.org> User-Agent: KMail/4.14.3 (FreeBSD/11.0-CURRENT; KDE/4.14.3; amd64; ; ) In-Reply-To: <201509031630.t83GUZPr056951@mech-as222.men.bris.ac.uk> References: <201509031630.t83GUZPr056951@mech-as222.men.bris.ac.uk> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1979146.WVtIZAD9S0"; micalg="pgp-sha256"; protocol="application/pgp-signature" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Sep 2015 06:48:24 -0000 --nextPart1979146.WVtIZAD9S0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="us-ascii" On Thursday, September 03, 2015 05:30:35 PM Anton Shterenlikht wrote: > >From marcel@xcllnt.net Thu Sep 3 17:20:42 2015 > > > >To be clear: with the limits and without my patch you > >can=3DE2=3D80=3D99t even boot right? >=20 > yes, this is right. >=20 > >> If I remove these, then I can boot. > >> > >>=3D20 > >> > >> If I try booting with -s, then I get to a hang at > > > >> "Entering /boot/kernel=3DE2=3D80=3D9D: > >Is this with or without limits? > >And is this with or without patch? >=20 > It seems the patch made no difference. > With the limits I cannot boot with or without the patch. > Without the limits I can boot with or without the patch. >=20 > >> /boot/kernel.old/kernel text=3D3D0x1110710 data=3D3D0xdfce8+0xa54f= 8 =3D > > > >syms=3D3D[0x8+0xc29e8+0x8+0xb78f6] > > > >> ?[37m?[44mBooting...?[m > >> Entering /boot/kernel.old/kernel at 0x9ffc000000010500... > >> *********************************************************** > >> * ROM Version : 04.29 > >> * ROM Date : 11/30/2007 > >> * BMC Version : 04.04 > > > >This is not a hang. This is a machine check. >=20 > After this line >=20 > Entering /boot/kernel.old/kernel at 0x9ffc000000010500... >=20 > The machine is not responding. I've left it for hours, > just to be sure. > The following line appears only after a power cycle. >=20 > >> Is it worth investigating what limit value will boot? > > > >I=3DE2=3D80=3D99m inclined to say that it=3DE2=3D80=3D99s best to re= move the limits > >altogether and just work with the default. If you need > >different default, add them to your kernel configuration. > >Set MAXTSIZ, DFLDSIZ, MAXDSIZ, DFLSSIZ and MAXSSIZ > >accordingly. > > > >Since you lower maxdsiz and maxssiz from 1G to 512M, > >you can safely leave them as is (unless you tend to have > >runaway processes :-) > > > >You increase maxssiz from 256M to 512M, which you > >probably want to keep doing to make sure you can run > >the same set of processes as you do now. > > > >At this point in time, the only fix I=3DE2=3D80=3D99m willing to mak= e > >is for the size of the array that holds relocations. If > >it made things better, I=3DE2=3D80=3D99ll commit it. If it didn=3DE2= =3D80=3D99t, =3D > >then > >I=3DE2=3D80=3D99m not going to commit it. >=20 > No, I don't think it made any difference. >=20 > >Anything more involved will take more time than I=3DE2=3D80=3D99m > >willing to put into ia64 at this time... >=20 > sure, no problem. >=20 > Anton This thread reminds me of what happened to eris.freebsd.org - removing = DDB=20 from=20the kernel solved it for us in the freebsd.org cluster. The same kernel binary booted on the old 2-cpu itanium machine, just n= ot on=20 the 8-core machine. =2D-=20 Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com; KI= 6FJV UTF-8: for when a ' or ... just won\342\200\231t do\342\200\246 --nextPart1979146.WVtIZAD9S0 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part. Content-Transfer-Encoding: 7Bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAABCAAGBQJV7TMyAAoJEDXWlwnsgJ4EzQUH/jqqCajSLn3n/JOlDeu7ByUr VY2LTKi83NwXH28qB86EoTStBeF5Ohlg9yqUju4RRfATVGGnXdSWShEZrCX/vtoQ Mk96206CiNXoLRz++jER3gtukrhvWjiZFqm2pyWi/9b+e1nxN/negsqUfA2O8BEa BELsbOpvHgW/TQa5i1pwK4fdJKWuDy8dgT2pZyFUM/Ce33/dFj1fwf8Hdm/f2cpH U51ZuwaiGMmPRl61Lr1iTUG2hIFJv7pUsv3CHdG3gHbqiI3grYlkYgy6WrxO26T/ yFmbyl+p6+/0CdfOqfDBsYgvuYH9o1g4M7PiLHfBVOkJjUOdc9MNM0aUE5Mt2pQ= =Frth -----END PGP SIGNATURE----- --nextPart1979146.WVtIZAD9S0--