mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kay Sievers <kay.sievers@vrfy.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Martin Knoblauch <knobi@knobisoft.de>,
	efault@gmx.de, viro@zeniv.linux.org.uk, rjw@sisk.pl,
	linux-kernel@vger.kernel.org, shemminger@vyatta.com,
	jbarnes@virtuousgeek.org, matthew@wil.cx, mike.miller@hp.com
Subject: Re: Analyzed/Solved/Bisected: Booting 2.6.30-rc2-git7 very slow
Date: Wed, 27 May 2009 22:56:45 +0200	[thread overview]
Message-ID: <ac3eb2510905271356n1b01f273jca1f7aa8fc65c78b@mail.gmail.com> (raw)
In-Reply-To: <20090527133125.c36381b5.akpm@linux-foundation.org>

On Wed, May 27, 2009 at 22:31, Andrew Morton <akpm@linux-foundation.org> wrote:
> On Wed, 27 May 2009 04:25:57 -0700 (PDT)
> Martin Knoblauch <knobi@knobisoft.de> wrote:
>
>>  FWIW, I compiled the CCISS driver into the kernel. This makes the second "/sys" line in /proc/mounts go away, dmesg attached. But does it prove anything? The initialization of the CCISS hardware now happens about 2 seconds earlier in the bootup sequence. Does this hint to a problem with CCISS, or just confirms that the whole issue is really timing dependent? Anyway, I add Mike to CC.
>>
>
> It seems that the PCI change caused timing changes which triggered a
> udev/sysfs/whatever problem, which manifests as the duplicated
> /proc/mounts entry to turn up.
>
> What we don't know (afaik) is why the kernel permitted two entries in
> /proc/mounts.  That might be a bug.
>
> It could be that if dual /proc/mounts problem gets fixed, everything
> works OK - by intent or by accident, the userspace startup scripts may
> then work acceptably.
>
> I think Al asked you a few questions around the behaviour of mount(8)
> and the mount syscall, so we could delve further into why /proc/mounts
> is getting mucked up.  Did you end up running those tests?

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.

Thanks,
Kay

  reply	other threads:[~2009-05-27 20:57 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-27 11:25 Martin Knoblauch
2009-05-27 20:31 ` Andrew Morton
2009-05-27 20:56   ` Kay Sievers [this message]
2009-05-28  9:14     ` Martin Knoblauch
2009-06-16 19:25       ` Jesse Barnes
2009-06-17  8:35         ` Martin Knoblauch
2009-06-20 16:37           ` jim owens
2009-06-20 16:58             ` Matthew Wilcox
2009-06-20 18:19               ` Kay Sievers
2009-06-20 18:26                 ` Matthew Wilcox
2009-06-20 18:36                   ` Kay Sievers
2009-06-20 19:06                     ` Matthew Wilcox
2009-06-20 21:17                       ` jim owens
2009-06-21 10:57                         ` Martin Knoblauch
2009-06-21 13:50                           ` jim owens
2009-06-21 10:54             ` Martin Knoblauch
  -- strict thread matches above, loose matches on Subject: below --
2009-05-20 11:01 Martin Knoblauch
2009-04-24 12:45 Analyzed/Solved: " Martin Knoblauch
2009-04-29  1:28 ` Andrew Morton
2009-04-29  3:51   ` Mike Galbraith
2009-04-29  8:17     ` Andrew Morton
2009-04-29 12:08       ` Al Viro
2009-04-29 14:18         ` Mike Galbraith
2009-05-05 22:49           ` Andrew Morton
2009-05-06  4:45             ` Mike Galbraith
2009-05-06  7:55               ` Martin Knoblauch
2009-05-06  8:37                 ` Mike Galbraith
2009-05-20 10:22                   ` Analyzed/Solved/Bisected: " Martin Knoblauch
2009-05-27  6:31                     ` Andrew Morton
2009-05-27  9:14                       ` Martin Knoblauch
2009-05-27 11:21                       ` Matthew Wilcox
2009-05-27 11:53                         ` Martin Knoblauch
2009-05-27 18:07                           ` jim owens
2009-05-27 18:18                             ` Miller, Mike (OS Dev)
2009-05-27 20:12                               ` jim owens
2009-05-27 21:18                                 ` Miller, Mike (OS Dev)
2009-05-28  8:59                               ` Martin Knoblauch
2009-05-28 19:01                                 ` Miller, Mike (OS Dev)
2009-05-28 20:48                                   ` Martin Knoblauch

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ac3eb2510905271356n1b01f273jca1f7aa8fc65c78b@mail.gmail.com \
    --to=kay.sievers@vrfy.org \
    --cc=akpm@linux-foundation.org \
    --cc=efault@gmx.de \
    --cc=jbarnes@virtuousgeek.org \
    --cc=knobi@knobisoft.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew@wil.cx \
    --cc=mike.miller@hp.com \
    --cc=rjw@sisk.pl \
    --cc=shemminger@vyatta.com \
    --cc=viro@zeniv.linux.org.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome