[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <783496.86803.qm@web32608.mail.mud.yahoo.com>
Date: Tue, 19 May 2009 00:22:33 -0700 (PDT)
From: Martin Knoblauch <spamtrap@...bisoft.de>
To: Kay Sievers <kay.sievers@...y.org>
Cc: "Rafael J. Wysocki" <rjw@...k.pl>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Kernel Testers List <kernel-testers@...r.kernel.org>
Subject: Re: [Bug #13178] Booting very slow
----- Original Message ----
> From: Kay Sievers <kay.sievers@...y.org>
> To: Martin Knoblauch <spamtrap@...bisoft.de>
> Cc: Rafael J. Wysocki <rjw@...k.pl>; Linux Kernel Mailing List <linux-kernel@...r.kernel.org>; Kernel Testers List <kernel-testers@...r.kernel.org>
> Sent: Tuesday, May 19, 2009 2:26:04 AM
> Subject: Re: [Bug #13178] Booting very slow
>
> On Mon, May 18, 2009 at 10:15, Martin Knoblauch wrote:
>
> >> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13178
> >> Subject : Booting very slow
> >> Submitter : Martin Knoblauch
> >> Date : 2009-04-24 12:45 (23 days old)
> >> References : http://marc.info/?l=linux-kernel&m=124057716231773&w=4
> >
> > The issue is still open. It turns out that starting with 2.6.29-rc1
> /proc/mounts already has a "sysfs" line when entering the startup scripts from
> initrd. This breaks the RHEL4 firmware hotplug script.
>
> Is that possibly a missing/failing "umount /sys" _in_ initramfs, which
> leaves the sysfs entry in /proc/mounts behind, which then shows up as
> a duplicate when running in the real rootfs?
>
could be. Remains the question, why it never showed up before 2.6.29. I compared my initrd images for 2.6.28 and 2.6.29-rc1, and they only differ in the module-binaries.
Cheers
Martin
--
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