Date: Thu, 10 Jan 2013 16:48:18 +0100 From: "O. Hartmann" <ohartman@zedat.fu-berlin.de> To: Gleb Smirnoff <glebius@FreeBSD.org> Cc: freebsd-current@FreeBSD.org Subject: Re: loopback interface broken on current Message-ID: <50EEE2C2.8050404@zedat.fu-berlin.de> In-Reply-To: <20130109085907.GJ66284@glebius.int.ru> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --]
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>
> H> The symptoms in my case are:
> H>
> H> Booting the box is all right until it comes to the start of nfsuserd.
> 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 interrupt
> H> them, there are other services which will not start.
> H>
> H> Trying to login as root on the console fails - I never get a password
> H> tag after having issued the root login name. Since this machine is bound
> H> to a local and remote OpenLDAP backend, I'm used to have an emergency
> H> local user which usually works - but this time, neither root nor this
> H> user can login!
> H>
> 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 inet6
> H> linklocal address, some nd6 options, but sometimes even IPv6 assignments
> H> do not show up.
> H>
> 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 kernel
> H> module. While the kernel and module (*.ko) get installed properly, the
> H> recompilation of the VirtualBox port gets stuck when the system unfolds
> H> the source tarball. Hitting Ctrl-T say "sbwait" for the process. Other
> 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>
> H> The funny thing is, that after several reboots, the box gets up as normal.
> H>
> H> I revealed this issue approx. two weeks ago when out of the sudden the
> H> amd automounter stopped working and the NFSv4 network drives didn't
> H> attach properly and made the whole box being stuck.
> H>
> H> Sorry for the more superficial description of the problem ...
> H>
> H> Has the problem been identified? Is there a solution? Since it affects
> 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 server
> 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.
>
> This looks unrelated to the problem discussed, because r245218 is
> later than r244989 which backed out my change.
>
> Can you do a binary search to identify which revision broke things?
>
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=0x020000 card=0x844e1043 chip=0x15038086
rev=0x05 hdr=0x00
vendor = 'Intel Corporation'
device = '82579V Gigabit Network Connection'
class = network
subclass = 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
[-- Attachment #2 --]
-----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-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?50EEE2C2.8050404>