Date: Thu, 19 May 2016 19:04:12 +0200 From: "O. Hartmann" <ohartman@zedat.fu-berlin.de> To: freebsd-current@freebsd.org Subject: Re: boot broken on VMWare somewhere between r300069 and r300176 Message-ID: <20160519190412.68752f55.ohartman@zedat.fu-berlin.de> In-Reply-To: <f9929585-2f30-4140-e3b4-0c930efa8903@FreeBSD.org> References: <CAHM0Q_N8aGeHr-JdkA7FcsBcCr6up-cF1Z=e2brJLT2g01HTUA@mail.gmail.com> <be3b2d82-1592-3fca-e1a4-a5161b45ee53@passap.ru> <f9929585-2f30-4140-e3b4-0c930efa8903@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--Sig_/tqF2B3ff.N7VFw+EVav9kRw Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On Thu, 19 May 2016 14:04:59 +0300 Andriy Gapon <avg@FreeBSD.org> wrote: > On 19/05/2016 13:50, Boris Samorodov wrote: > > 19.05.16 09:28, K. Macy =D0=BF=D0=B8=D1=88=D0=B5=D1=82: =20 > >> I did an IFC on my drm-next-4.6 branch yesterday at r300069. I just > >> did an IFC to r300176 and boot will hang right ater printing out > >> "setting hostid: ". ^T just shows sh [piperd]. ddb just shows the > >> shell as hanging in piperead. Diffing between those two revisions I > >> don't see any obvious offenders so I'm hoping that individuals who > >> have committed in the last 24 hours will have some idea of their > >> changes having such an impact. =20 > >=20 > > For me (BIOS boot at DELL notebook) is broken after jump > > from r300062 to r300158. CapsLock works, but ^T shows nothing. > > Here is a photo (sorry for the quality): > > ftp://ftp.wart.ru/pub/misc/boot_broken.jpg > >=20 > > Boot with r300062 works fine. =20 >=20 > A wild guess (not really), try to revert r300113 >=20 We updated several systems of different ages and CPU generations (around 10) to 300158. Bare metal. The systems all failed to boot, they got stuck after the USB system has been probed (according to the kernel messages). Some boxes get stuck after the message of the generation of the UUID occured. Pushing the Powerbutton performs a clean shutdown, although - so te system seems still alive, but usually the power is turning off - this time, the box is stuck with the uptime message. On random reboots some of the boxes boot. But the desaster then starts. The network is highly unstable and flaky - while I can ping hosts or resolve their IP by a DNS, I can not login via ssh, the webservices of the webserver of the machines in question are inaccessible as well as their databases (PostgreSQL) as well as ssh. And it is more frustrating: I can't update or go back with svn (either /usr/bin/svn or /usr/local/bin/svn) within the sources to avoid this mess. In all cases, svn "times out". Accessing the web from clients with the broken CURRENT code also ends up in a wild guess game: sometimes the connection to services can be established, sometimes not and I see a timeout. With svn in /usr/src, on one box I could obtain a poor fragment of the code via "svn update -r 300005" (300005 was in my case the starting point when everything was up an running and working). In short words: reverting back to r300113 isn't possible on the most systems! This problem has been present immediately after 300158 has been introduced and build-world/build-kernel has been performed and the fact, that different hardware, including NICs, has been affected, does not narrow down the problem to a specific NIC, CPU type or hardware. And that leads me to the question whether the code injected into CURRENT gets tested - or not. If there would be a test, I guess the problem would have revealed itself immediately. I boot via UEFI as well as BIOS - the problem is with both. In such a case as described with a nonworking svn, how am I supposed to revert to the supposedly working revision r300113? Kind regards and thanks in advance for your suggestions, O. Hartmann=20 P.S. I'm using IPFW on all systems. Disabling IPFW (ipfw disable firewall) seems= to releafe the symptoms a bit - no matter whether custom scripts were used or the sett= ings from rc.conf. --Sig_/tqF2B3ff.N7VFw+EVav9kRw Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJXPfIMAAoJEOgBcD7A/5N86XgIAOHcWP0CP6ngd/STAddiIKsf 7obvXijy5b48lqjgAjqR6iTk/B/AMt8CLP4QvVJx4sJZC34ZXAZbyttts09ZmY4f c/xy/gcfRikzSEi70uuZJwLOguze0+YgViln/9G8xGfojUnIjg2FBimilzKcSC7y IMA+bS54DDT/Gi78aJzy0DwBefQrE5IOutFJHfAtoeOgzNEFGyDYaWhtrjU0oxbL IDt7KkbwG0AM8M9vyeWJbuJalKWorCWpQjWOqjXheMo+PYCSwgqm/D9bssTQ7w6u qbuTNBRxfr7NKK6V/wNqE2MQBn9v6ixZj17vEZHMw8+ge+NWa3M6gVqS8+sB2Kc= =oJon -----END PGP SIGNATURE----- --Sig_/tqF2B3ff.N7VFw+EVav9kRw--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160519190412.68752f55.ohartman>