public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Martin Knoblauch <knobi@knobisoft.de>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
	linux-kernel@vger.kernel.org, efault@gmx.de,
	tigran aivazian <tigran@aivazian.fsnet.co.uk>
Subject: Re: Analyzed/Solved: Booting 2.6.30-rc2-git7 very slow
Date: Tue, 28 Apr 2009 18:28:37 -0700	[thread overview]
Message-ID: <20090428182837.62c51f26.akpm@linux-foundation.org> (raw)
In-Reply-To: <409142.83316.qm@web32605.mail.mud.yahoo.com>

On Fri, 24 Apr 2009 05:45:19 -0700 (PDT) Martin Knoblauch <knobi@knobisoft.de> wrote:

> 
> 
>  OK, I just found the reason for both intel-ucode and tg3 failures. Apparently between 2.6.28 and 2.6.29 the mount of sysfs has subtely changed from:
> 
> /sys /sys sysfs rw 0 0
> 
> to:
> 
> none /sys sysfs rw,relatime 0 0

I assume that you're referring to the contents of /proc/mounts?

>  The "none" breaks the RHEL-4 provided hotplug script "firmware.agent" when it tries to parse the mount point for "/sys". As a result, the firmware loading is never properly finished and the driver(s) just timeout on the value  in /sys/class/firmware/timeout. Bingo. Simple fix in user-pace possible - cool down Martin :-)
> 
> Questions remains: was this intentional? It breaks existing userspace and should therefore be considered a regression - right? On the other hand, it will never be a problem for RHEL-4/5 kernels, unless the change in 2.6.29 gets backported. Any ideas?

afaik that was unintentional and was probably a mistake.

I wonder how we did that.

  reply	other threads:[~2009-04-29  1:32 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 [this message]
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
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=20090428182837.62c51f26.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=efault@gmx.de \
    --cc=knobi@knobisoft.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@sisk.pl \
    --cc=tigran@aivazian.fsnet.co.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