From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760690AbZE0GX2 (ORCPT ); Wed, 27 May 2009 02:23:28 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1757348AbZE0GXU (ORCPT ); Wed, 27 May 2009 02:23:20 -0400 Received: from smtp1.linux-foundation.org ([140.211.169.13]:41803 "EHLO smtp1.linux-foundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752895AbZE0GXT (ORCPT ); Wed, 27 May 2009 02:23:19 -0400 Date: Tue, 26 May 2009 23:22:39 -0700 From: Andrew Morton To: Martin Knoblauch Cc: Al Viro , Mike Galbraith , "Rafael J. Wysocki" , linux-kernel@vger.kernel.org, tigran aivazian Subject: Re: Analyzed/Solved: Booting 2.6.30-rc2-git7 very slow Message-Id: <20090526232239.acf0f080.akpm@linux-foundation.org> In-Reply-To: <926930.45651.qm@web32602.mail.mud.yahoo.com> References: <409142.83316.qm@web32605.mail.mud.yahoo.com> <20090428182837.62c51f26.akpm@linux-foundation.org> <1240977096.5478.3.camel@marge.simson.net> <20090429011755.c141c599.akpm@linux-foundation.org> <20090429120827.GI8633@ZenIV.linux.org.uk> <884894.99151.qm@web32602.mail.mud.yahoo.com> <20090429174154.GK8633@ZenIV.linux.org.uk> <225539.25847.qm@web32607.mail.mud.yahoo.com> <20090429181041.GM8633@ZenIV.linux.org.uk> <926930.45651.qm@web32602.mail.mud.yahoo.com> X-Mailer: Sylpheed 2.4.8 (GTK+ 2.12.5; x86_64-redhat-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 30 Apr 2009 02:12:00 -0700 (PDT) Martin Knoblauch wrote: > > ----- Original Message ---- > > > From: Al Viro > > To: Martin Knoblauch > > Cc: Andrew Morton ; Mike Galbraith ; Rafael J. Wysocki ; linux-kernel@vger.kernel.org; tigran aivazian > > Sent: Wednesday, April 29, 2009 8:10:41 PM > > Subject: Re: Analyzed/Solved: Booting 2.6.30-rc2-git7 very slow > > > > On Wed, Apr 29, 2009 at 10:51:35AM -0700, Martin Knoblauch wrote: > > > 2.6.30-rc3-git2: > > > > > > rootfs / rootfs rw 0 0 > > > /proc /proc proc rw,relatime 0 0 > > > none /sys sysfs rw,relatime 0 0 > > > none /dev tmpfs rw,relatime,mode=755 0 0 > > > /dev/root / ext3 rw,relatime,errors=continue,data=writeback 0 0 > > > none /dev tmpfs rw,relatime,mode=755 0 0 > > > /proc /proc proc rw,relatime 0 0 > > > /proc/bus/usb /proc/bus/usb usbfs rw,relatime 0 0 > > > /sys /sys sysfs rw,relatime 0 0 > > > none /dev/pts devpts rw,relatime,gid=5,mode=620 0 0 > > > /dev/cciss/c0d0p1 /boot ext3 rw,relatime,errors=continue,data=writeback 0 0 > > > none /dev/shm tmpfs rw,relatime 0 0 > > > /dev/cciss/c0d0p4 /scratch ext2 rw,noatime,errors=continue 0 0 > > > none /proc/sys/fs/binfmt_misc binfmt_misc rw,relatime 0 0 > > > sunrpc /var/lib/nfs/rpc_pipefs rpc_pipefs rw,relatime 0 0 > > > > Cute... I wonder how that second mount(2) managed to succeed. Could you > > check what explicit mounting of sysfs on that point *again* does? > Hi Al, > > by now I know a bit more. Starting with 2.6.29, the > > none /sys sysfs rw 0 0 > > line is already in /proc/mounts when entering userspace. So I guess it comes out of my initrd. Again, what changed? > afacit this didn't get understood, let alone fixed? I see that you had a PCI-related issue which changed boot timing a lot, but that isn't the bug - it simply exposed the bug by changing timing?