[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090616122547.1323d2d4@jbarnes-g45>
Date: Tue, 16 Jun 2009 12:25:47 -0700
From: Jesse Barnes <jbarnes@...tuousgeek.org>
To: Martin Knoblauch <knobi@...bisoft.de>
Cc: Kay Sievers <kay.sievers@...y.org>,
Andrew Morton <akpm@...ux-foundation.org>, efault@....de,
viro@...iv.linux.org.uk, rjw@...k.pl, linux-kernel@...r.kernel.org,
shemminger@...tta.com, matthew@....cx, mike.miller@...com
Subject: Re: Analyzed/Solved/Bisected: Booting 2.6.30-rc2-git7 very slow
On Thu, 28 May 2009 02:14:46 -0700 (PDT)
Martin Knoblauch <knobi@...bisoft.de> wrote:
> > I expect the duplicate comes from a left-over mount in initramfs
> > which isn't a duplicate in the sense of a bug in vfs or mount or
> > anything. I guess, it is just still mounted in the initial kernel
> > rootfs, below the root from the disk. It could be that a umount
> > from initramfs did go wrong because of a changed timing.
> >
>
> This is what I suspect as well. I know for sure that the first
> sysfs-line in /proc/mounts
>
> | none /sys sysfs rw 0 0
>
> is already there (2.6.29-rc1 and up) when entering startup-skripts.
> It is supposed to be unmounted before, but something seems to prevent
> it. I have idea how to capture debug output from the initrd/init
> script :-(
What's the latest here Martin? It sounded like this was a userspace
issue, with something reading the VPD over and over? Or was it just a
longer timeout that caused a specific driver to slow everything down?
--
Jesse Barnes, Intel Open Source Technology Center
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists