From owner-freebsd-current@FreeBSD.ORG Thu Jan 10 15:48:35 2013 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id DB7C77BD; Thu, 10 Jan 2013 15:48:35 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) by mx1.freebsd.org (Postfix) with ESMTP id 8372063E; Thu, 10 Jan 2013 15:48:35 +0000 (UTC) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost1.zedat.fu-berlin.de (Exim 4.69) with esmtp (envelope-from ) id <1TtKMl-000Sdl-5B>; Thu, 10 Jan 2013 16:48:27 +0100 Received: from e178006081.adsl.alicedsl.de ([85.178.6.81] helo=thor.walstatt.dyndns.org) by inpost2.zedat.fu-berlin.de (Exim 4.69) with esmtpsa (envelope-from ) id <1TtKMl-0042CT-0d>; Thu, 10 Jan 2013 16:48:27 +0100 Message-ID: <50EEE2C2.8050404@zedat.fu-berlin.de> Date: Thu, 10 Jan 2013 16:48:18 +0100 From: "O. Hartmann" User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: Gleb Smirnoff Subject: Re: loopback interface broken on current References: <201301011040.r01Ae37A043153@pozo.com> <20130101194803.GB25661@glebius.int.ru> <201301012042.r01Kgq6E001548@pozo.com> <20130102201330.GC25661@glebius.int.ru> <201301022325.r02NPKEE076633@pozo.com> <89160.1357182550@pf2.ed.niigata-u.ac.jp> <201301030355.r033t4aI001542@pozo.com> <90299.1357212618@pf2.ed.niigata-u.ac.jp> <20130104094532.4a921e47@ernst.jennejohn.org> <50ED30B9.7040101@zedat.fu-berlin.de> <20130109085907.GJ66284@glebius.int.ru> In-Reply-To: <20130109085907.GJ66284@glebius.int.ru> X-Enigmail-Version: 1.4.6 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig27CE62C2833F3C0E9520B7A6" X-Originating-IP: 85.178.6.81 Cc: freebsd-current@FreeBSD.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Jan 2013 15:48:35 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig27CE62C2833F3C0E9520B7A6 Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: quoted-printable Am 01/09/13 09:59, schrieb Gleb Smirnoff: > On Wed, Jan 09, 2013 at 09:56:25AM +0100, Hartmann, O. wrote: > H> Same here. > H> The OS: FreeBSD 10.0-CURRENT/amd64 r245218. Since I have three boxes= > H> running approximately the same configurations (I share my configs > H> between lab and home), but different hardware, I'm confused. > H>=20 > H> The symptoms in my case are: > H>=20 > H> Booting the box is all right until it comes to the start of nfsuserd= =2E > H> Prior to that, ntp adjusts the clock properly with an external time > H> server - so this implies network connectivity. Start of nfsuserd is= > H> stuck forever. > H> Interrupting the start of nfsuserd restarts several other services, = but > H> winbindd and slapd (OpenLDAP) get stuck again. In case I also interr= upt > H> them, there are other services which will not start. > H>=20 > H> Trying to login as root on the console fails - I never get a passwor= d > H> tag after having issued the root login name. Since this machine is b= ound > H> to a local and remote OpenLDAP backend, I'm used to have an emergenc= y > H> local user which usually works - but this time, neither root nor thi= s > H> user can login! > H>=20 > H> Bringing up the box in SINGLEUSER allows me to login. Investigating = the > H> network interfaces with ifconfig reveals, that the loopback did not = get > H> assigned to any inet 127.0.0.1 address. Sometimes there is only inet= 6 > H> linklocal address, some nd6 options, but sometimes even IPv6 assignm= ents > H> do not show up. > H>=20 > H> In a desperate move I tried to recompile a kernel. In /etc/src.conf,= I > H> recompile also the kernel module for the most recent virtual-box ker= nel > H> module. While the kernel and module (*.ko) get installed properly, t= he > H> recompilation of the VirtualBox port gets stuck when the system unfo= lds > H> the source tarball. Hitting Ctrl-T say "sbwait" for the process. Oth= er > H> processes seem to have trouble getting a proper ownership or UID for= a > H> file - this is my naiv interpretation what I see at the surface. > H>=20 > H> The funny thing is, that after several reboots, the box gets up as n= ormal. > H>=20 > H> I revealed this issue approx. two weeks ago when out of the sudden t= he > H> amd automounter stopped working and the NFSv4 network drives didn't > H> attach properly and made the whole box being stuck. > H>=20 > H> Sorry for the more superficial description of the problem ... > H>=20 > H> Has the problem been identified? Is there a solution? Since it affec= ts > H> only my very modern hardware (i7-3930, 32GB RAM, ASUS P9X79 WS > H> mainboard), while a very same setup on older hardware (our local ser= ver > H> is Intel Q6600 with 8GB RAM and and oldish Intel P45-chipset based > H> mainboard), both systems do have Intel NICs, I'm a bit confused. >=20 > This looks unrelated to the problem discussed, because r245218 is > later than r244989 which backed out my change. >=20 > Can you do a binary search to identify which revision broke things? >=20 Sorry for the delay. Today I realized that the problems occured and described are due to the fact that I use jumbo frames (mtu 9100 or mtu 6150) on the em0-device (em0@pci0:0:25:0: class=3D0x020000 card=3D0x844e1043 chip=3D0x1503= 8086 rev=3D0x05 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D '82579V Gigabit Network Connection' class =3D network subclass =3D ethernet ). Using the default of mtu 1500 does not make the problem occur. My time constraints disallow to do further or deeper investigations - at least until the end of next week, I'm sorry. The problems arose around Christmas, it might be even earlier, since I didn't access the machine since 10th December. I have other boxes with Intel NICs - different chiptypes. They do not show this problem. Oliver --------------enig27CE62C2833F3C0E9520B7A6 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iQEcBAEBAgAGBQJQ7uLKAAoJEOgBcD7A/5N8+B0H/AyeT0dNahSyuCbp5OiEWTyH LfKccvosiplls/sIeqeV5Wp6GlF/2PqDHO7mhXM/c/i07dXZpGdUttYxZbfEmYV9 /8DcVhNEYpYCyzyo1a0xIrMv4niyl+sZhdyla0hGbr0jaPOlu9KLTsDQH0E0EvmB UfAlhuAeZA8VcCoc4H/q31DVU83OIy2sey9KvCThEObvN7M8deNSf3qlkvuVMNUZ kF9fNy4cKujPh7GeAebyvAid9n27vQH6L9y1PSC+aPmp0TUXU3vULY66uLIv5SUW KWzYyF7JzdDGy09TJjvtrgV6hhHvdkuYeGm4QvZvFTc7HEPAUDfwtI0NkthKBGc= =xAVw -----END PGP SIGNATURE----- --------------enig27CE62C2833F3C0E9520B7A6--