If I emerge udev it brokes my system. I get a lot of messages udevsend [xxxx]: main: error getting socket: Address family not supported by protocol. One moment there is five messages "runaway loop modprobe net-pf-1" and then again a lot of messages from udevsend. It's strange but thoose messages appears before /sbin/init proccess starts!! Don't understand how, as far as I know /sbin/init is the first progamm started during boot process. If I emerge -C udev everything becomes fine. What's the problem? Some notes: I loaded from initramfs disk. My make.conf is bellow CFLAGS="-Os -mtune=i686 -pipe -fomit-frame-pointer" CHOST="i386-pc-linux-gnu" CXXFLAGS="${CFLAGS}" ACCEPT_KEYWORDS="~x86" FEATURES="ccache buildpkg nodoc noinfo noman" USE="-* minimal unicode ncurses userlocales" VIDEO_CARDS="via" INSTALL_MASK="/usr/share/include/* /usr/share/i18n* /usr/share/locale* /usr/share/zoneinfo*" PORTDIR_OVERLAY="/usr/local/portage" (if I change ACCEPT_KEYWORDS to x86 nothing happens). My kernel is compiled with Unix Socket support builtin (CONFIG_UNIX=y) I use gentoo-sources-2.6.16-r7 with gentoo-headers-2.6.11-r5. devfs support is deprecated in this kernel so with broken udev I ve no way to manage my device nodes. Maybe it will be important, but I compile everything in chroot env. I run it by command "setarch i686 chroot /chroot" (my host system is x86_64). And In that chroot env. I compile some packages with "ROOT=/image_root" just to make a root of my minimalistic Gentoo, that will be writen on USB.
How did you compile the kernel? Manually or using genkernel? Attach (don't paste) kernel .config here. Also, which udev version? Also, emerge --info missing.
Created attachment 87246 [details] kernel config
How to reproduce the bug on my x86_64 machine 1) mkdir /chroot 2) unpack stage3-i586-2006.0.tar.bz2 into /chroot 3) mkdir /chroot/usr/portage and bind proc and /usr/portage into /chroot 4) setarch i686 chroot /chroot 5) edit make.conf and update system to achieve this: Portage 2.1_rc1-r4 (default-linux/x86/2006.0, gcc-3.4.6, glibc-2.4-r3, 2.6.16-gentoo-r7lab3 i686) ================================================================= System uname: 2.6.16-gentoo-r7lab3 i686 AMD Opteron(tm) Processor 248 Gentoo Base System version 1.12.0_pre19 dev-lang/python: 2.4.3-r1 dev-python/pycrypto: 2.0.1-r5 dev-util/ccache: [Not Present] dev-util/confcache: [Not Present] sys-apps/sandbox: 1.2.18.1 sys-devel/autoconf: 2.13, 2.59-r7 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2 sys-devel/binutils: 2.16.1-r2 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.11-r5 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CBUILD="i586-pc-linux-gnu" CFLAGS="-Os -march=i586 -pipe" CHOST="i586-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/eselect/compiler /etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-Os -march=i586 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig buildpkg ccache distlocks metadata-transfer nodoc noinfo noman sandbox sfperms strict" GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/linux/distributions/gentoo" LANG="ru_RU.utf8" LC_ALL="" PKGDIR="/usr/portage/packages" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude='/distfiles' --exclude='/local' --exclude='/packages'" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 ncurses nopie nossp nptl nptlonly unicode elibc_glibc kernel_linux userland_GNU" Unset: ASFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LDFLAGS, LINGUAS, MAKEOPTS, PORTAGE_RSYNC_EXTRA_OPTS, PORTDIR_OVERLAY 6) mkdir /newroot 7) ROOT=/newroot emerge -eak glibc udev sed gawk grep 8) make in /newroot/dev/ null, console and zeto devices 9) edit /newroot/etc/fstab 8) pack /newroot in initrd image (ex. cd /newroot && find . | cpio -H newc -o | gzip -9 > /tmp/image.igz) 9) load any kernel known to work well with udev with this initrd image and you will get a lot of errors during kernel loading process (udevsend errors) and them oom-killer will start. All that happens before start of /sbin/init
I've noticed that all messages about "error getting socket" are displayed before "NET:Registering protocol family 1" message appeared.
Yes, you need socket support to run udev. What is happening on your boot process? Networking should be enabled before you hit userspace init, which is where udev runs. Can you attach your full syslog output? Are you changing the way the gentoo boot process works?
(In reply to comment #5) > Yes, you need socket support to run udev. > > What is happening on your boot process? Networking should be enabled before > you hit userspace init, which is where udev runs. > > Can you attach your full syslog output? > > Are you changing the way the gentoo boot process works? > Just repeat my steps I've posted before and you will get same errors. errors appeared during kernel loading proccess, PRIOR to any userspace events (even prior to starting of /sbin/init). Sorry, but I can't give you any logs, because system refueses to start - after a lot of error messages from udevsend it start oom-killer.
You are creating your own initrd from scratch, please either use the one that genkernel creates, or none at all.
So, am marking this invalid.
