linux-kernel - Re: [Bug #13178] Booting very slow

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 20 May 2009 03:14:36 -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

 ------------------------------------------------------
Martin Knoblauch
email: k n o b i AT knobisoft DOT de
www:   http://www.knobisoft.de

----- 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 10:58:24 AM
> Subject: Re: [Bug #13178] Booting very slow
> 
> On Tue, May 19, 2009 at 09:22, Martin Knoblauch wrote:
> >> >  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.
> 
> I wouldn't be surprised if we are just "too fast" again now with the
> async stuff, for another piece of rather fragile userspace bootup
> logic, making some wrong assumptions. Are you compiling-in the modules
> for the root disk and the root filesystem?
> 
> Cheers,
> Kay

 timing may actually be the answer. I finally manged to bisect the thing and the first bad commit is this one:

|commit 1120f8b8169fb2cb51219d326892d963e762edb6
|Author: Stephen Hemminger <shemminger@...tta.com>
|Date:   Thu Dec 18 09:17:16 2008 -0800
|
|    PCI: handle long delays in VPD access
|
|    Accessing the VPD area can take a long time.  The existing
|    VPD access code fails consistently on my hardware. There are comments
|
|    Change the access routines to:
|      * use a mutex rather than spinning with IRQ's disabled and lock held
|      * have a much longer timeout
|      * call cond_resched while spinning
|
|    Signed-off-by: Stephen Hemminger <shemminger@...tta.com>
|    Reviewed-by: Matthew Wilcox <willy@...ux.intel.com>
|    Signed-off-by: Jesse Barnes <jbarnes@...tuousgeek.org>

  And no, the "cciss", "ext3" and "jbd" are modules in my intrd image.

 I will continue the discussion under the original topic.

Cheers
--
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/