public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Galbraith <efault@gmx.de>
To: Martin Knoblauch <knobi@knobisoft.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	viro@ZenIV.linux.org.uk, rjw@sisk.pl,
	linux-kernel@vger.kernel.org, tigran@aivazian.fsnet.co.uk
Subject: Re: Analyzed/Solved: Booting 2.6.30-rc2-git7 very slow
Date: Wed, 06 May 2009 10:37:45 +0200	[thread overview]
Message-ID: <1241599065.18090.18.camel@marge.simson.net> (raw)
In-Reply-To: <957194.27869.qm@web32605.mail.mud.yahoo.com>

On Wed, 2009-05-06 at 00:55 -0700, Martin Knoblauch wrote:

>  just to bring this back to my problem :-)

Good idea :-)

>  Last week I reported that the "new" sysfs entry in /proc/mounts already comes out of initrd. Does this ring a bell?
> 
> http://lkml.indiana.edu/hypermail/linux/kernel/0904.3/03048.html

Nope, no bells.

The only thing I can suggest is that you try a bisection.

	-Mike


  reply	other threads:[~2009-05-06  8:37 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-24 12:45 Analyzed/Solved: Booting 2.6.30-rc2-git7 very slow 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  9:36       ` Martin Knoblauch
2009-04-29  9:45       ` Martin Knoblauch
2009-04-29 12:08       ` Al Viro
2009-04-29 14:18         ` Mike Galbraith
2009-04-29 14:34           ` Al Viro
2009-04-29 17:28             ` Martin Knoblauch
2009-04-29 19:11             ` 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 [this message]
2009-05-06 10:57                   ` Martin Knoblauch
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
2009-04-29 17:24         ` Analyzed/Solved: " Martin Knoblauch
2009-04-29 17:35           ` Valdis.Kletnieks
2009-04-29 17:43             ` Al Viro
2009-04-30 13:02               ` Olivier Galibert
2009-04-29 17:45             ` Martin Knoblauch
2009-04-29 17:41           ` Al Viro
2009-04-29 17:51             ` Martin Knoblauch
2009-04-29 18:10               ` Al Viro
2009-04-30  9:12                 ` Martin Knoblauch
2009-05-27  6:22                   ` Andrew Morton
2009-04-29  9:34   ` 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=1241599065.18090.18.camel@marge.simson.net \
    --to=efault@gmx.de \
    --cc=akpm@linux-foundation.org \
    --cc=knobi@knobisoft.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@sisk.pl \
    --cc=tigran@aivazian.fsnet.co.uk \
    --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