From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <gentoo-user+bounces-145557-garchives=archives.gentoo.org@lists.gentoo.org> Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id AD53C198005 for <garchives@archives.gentoo.org>; Mon, 25 Feb 2013 21:33:24 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 45EE8E07D7; Mon, 25 Feb 2013 21:32:59 +0000 (UTC) Received: from mail.muc.de (colin.muc.de [193.149.48.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id A9BECE07C8 for <gentoo-user@lists.gentoo.org>; Mon, 25 Feb 2013 21:32:57 +0000 (UTC) Received: (qmail 86393 invoked by uid 3782); 25 Feb 2013 21:32:50 -0000 Received: from acm.muc.de (pD951B3BF.dip.t-dialin.net [217.81.179.191]) by colin.muc.de (tmda-ofmipd) with ESMTP; Mon, 25 Feb 2013 22:32:48 +0100 Received: (qmail 16098 invoked by uid 1000); 25 Feb 2013 21:32:19 -0000 Date: Mon, 25 Feb 2013 21:32:19 +0000 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Kernel 3.7.9: Lots of devices are root root rw-------. Message-ID: <20130225213219.GB15821@acm.acm> References: <20130223171841.GA3178@acm.acm> <5129D2E3.5020206@gmail.com> <20130224110201.GA2212@acm.acm> <512A3AF3.4010601@gmail.com> <20130224214022.GA2967@acm.acm> <512AA6AB.7020306@gmail.com> Precedence: bulk List-Post: <mailto:gentoo-user@lists.gentoo.org> List-Help: <mailto:gentoo-user+help@lists.gentoo.org> List-Unsubscribe: <mailto:gentoo-user+unsubscribe@lists.gentoo.org> List-Subscribe: <mailto:gentoo-user+subscribe@lists.gentoo.org> List-Id: Gentoo Linux mail <gentoo-user.gentoo.org> X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <512AA6AB.7020306@gmail.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-Delivery-Agent: TMDA/1.1.12 (Macallan) From: Alan Mackenzie <acm@muc.de> X-Primary-Address: acm@muc.de X-Archives-Salt: 93cb4489-5823-40cd-ad89-307634c0e38f X-Archives-Hash: 816c72d98c530e451038fe9b9fa5eae4 Hi, Alan. On Mon, Feb 25, 2013 at 01:47:55AM +0200, Alan McKinnon wrote: > On 24/02/2013 23:40, Alan Mackenzie wrote: > > On Sun, Feb 24, 2013 at 06:08:19PM +0200, Alan McKinnon wrote: > >> On 24/02/2013 13:02, Alan Mackenzie wrote: > >>> On Sun, Feb 24, 2013 at 10:44:19AM +0200, Alan McKinnon wrote: > >>>> On 23/02/2013 19:18, Alan Mackenzie wrote: > >>>>> Hi, Gentoo! > >>>>> Just built the new kernel 3.7.9 last night, and it's one of these > >>>>> "nothing works" situations. > >>> Sorry, I was exaggerating here. I can work normally as long as I don't > >>> try to use a peripheral, such as printer, audio, or scanner. My network > >>> connection is working OK. > >>>>> It seems the problems are with the device files, whose ownership is set > >>>>> to "root root" (rather than, e.g., "root audio") and whose permissions > >>>>> are set to crw------- (rather than the expected crw-rw----). > >>>>> I'm still running udev-171-r10. This might well make a difference. > >>>>> Needless to say, everything works under kernel 3.6.11. It would be nice > >>>>> if there were some mistake in my kernel config. > >>>>> Could somebody help me get this fixed, please. > > [ .... ] > >> I suppose your next step is to examine udev's logs where it creates the > >> various devices. > > And I promised myself some months ago I would _never_ spend time on udev > > innards. ;-( > > So, I set the debugging options inside /etc/conf.d/udev, which causes > > /run/udev/udev.log to be created. > > On the failing 3.7.9, /run/udev/udev.log terminates abruptly with an > > error message, with the entire file, 55 lines, looking like this: > > 1361736665.547175 [1761] parse_file: reading '/lib/udev/rules.d/10-dm.rules' as rules file > > 1361736665.547289 [1761] parse_file: reading '/run/udev/rules.d/10-root-link.rules' as rules file > > [ ..... ] > > 1361736665.553901 [1761] parse_file: reading '/lib/udev/rules.d/95-upower-wup.rules' as rules file > > 1361736665.553924 [1761] parse_file: reading '/lib/udev/rules.d/97-bluetooth-hid2hci.rules' as rules file > > 1361736665.553971 [1761] udev_rules_new: rules use 108624 bytes tokens (9052 * 12 bytes), 31856 bytes buffer > > 1361736665.553977 [1761] udev_rules_new: temporary index used 48860 bytes (2443 * 20 bytes) > > 1361736665.554010 [1761] main: error creating epoll fd: Function not implemented > > I hope "epoll fd", whatever that may be, is something critically > > important to justify just stopping udev. But it can't be that important > > if kernel 3.6.11 doesn't emit such an event. It looks like the kernel's > > event interface has changed. > > It seems that the contents of /dev, such as they were, were created > > directly by the kernel when devtmpfs was mounted. Normally they would be > > modified into something usable by udev. > > Maybe I should just bite the bullet and go through the pain of updating > > my udev to version 197-r8. :-( > Sounds logical to me, I'd conclude the same. > Perhaps you should report your findings to b.g.o just in case the > DEPENDS and config options between kernel and udev need to be tweaked in > the ebuilds (I'd hate to see many users have to go through the same as > yourself) I did that this morning (European time). I suspect I'll get an answer along the lines of "what do you expect if you use old versions?". > Got it on the pain you feel, I avoid looking into udev like it was the > plague. Some days I wonder if going back to MAKEDEV wouldn't be far > simpler in Gentoo land..... MAKEDEV?? I spent some time this afternoon making sure I knew how to chroot effectively, using my old "mdev system" as a rescue system. Probably updating udev will just go OK for me. I'll wait until I here back from the Gentoo guys on my bug report. Thanks for the help in sorting this out. > -- > Alan McKinnon > alan.mckinnon@gmail.com -- Alan Mackenzie (Nuremberg, Germany).