public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: jim owens <jowens@hp.com>
To: "Miller, Mike (OS Dev)" <Mike.Miller@hp.com>
Cc: Martin Knoblauch <knobi@knobisoft.de>,
	Matthew Wilcox <matthew@wil.cx>,
	Andrew Morton <akpm@linux-foundation.org>,
	Mike Galbraith <efault@gmx.de>,
	"viro@ZenIV.linux.org.uk" <viro@ZenIV.linux.org.uk>,
	"rjw@sisk.pl" <rjw@sisk.pl>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"tigran@aivazian.fsnet.co.uk" <tigran@aivazian.fsnet.co.uk>,
	Kay Sievers <kay.sievers@vrfy.org>,
	"shemminger@vyatta.com" <shemminger@vyatta.com>,
	Jesse Barnes <jbarnes@virtuousgeek.org>
Subject: Re: Analyzed/Solved/Bisected: Booting 2.6.30-rc2-git7 very slow
Date: Wed, 27 May 2009 16:12:50 -0400	[thread overview]
Message-ID: <4A1D9EC2.4090602@hp.com> (raw)
In-Reply-To: <0F5B06BAB751E047AB5C87D1F77A7788694630B931@GVW0547EXC.americas.hpqcorp.net>

Miller, Mike (OS Dev) wrote:
>>>  Finally, today I built the ccsii driver into the kernel. 
>> It was previously modularized and loaded from initrd. The 
>> second "sysfs" line went away. But does this make cciss 
>> guilty? It is now loaded about 2 seconds earlier in the boot 
>> sequence, which is a big change in timing I guess.
>>>  Enlighten me :-)
>> No idea what is going on, but since I saw your May 20 
>> message, I have been trying to wake up someone whose day job 
>> it should be to care about dl380s and smartarrays. :)
> 
> What? I know Martin has pinged me in the past, but I do not think it was about this issue. If there's multiple sysfs entries for cciss I can't explain that offhand. We do little to nothing for sysfs in the driver.
> Had something similiar happen recently where "/" changed to "!". Had do to with our nested directory structure, /dev/cciss/name vs /dev/name. But we did not make that change, either.

It was not you that I was trying to get to look at this...
but now that I have your attention :)

I did not think it pointed at cciss or the sysfs entry as
being the problem.  I was wondering more about platform probe
timing, the bios, and how each card firmware reacts given
what I thought the patch did.  I could be totally wrong about
that as I work at the filesystem level.

We have not seen the problem yet but we have different
proliants/smartarrays.

If you can try it on matching hardware, great, if not
then someone will eventually find a system to test it.

jim

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

Thread overview: 56+ 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
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 [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2009-05-20 11:01 Analyzed/Solved/Bisected: " Martin Knoblauch
2009-05-27 11:25 Martin Knoblauch
2009-05-27 20:31 ` Andrew Morton
2009-05-27 20:56   ` Kay Sievers
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

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=4A1D9EC2.4090602@hp.com \
    --to=jowens@hp.com \
    --cc=Mike.Miller@hp.com \
    --cc=akpm@linux-foundation.org \
    --cc=efault@gmx.de \
    --cc=jbarnes@virtuousgeek.org \
    --cc=kay.sievers@vrfy.org \
    --cc=knobi@knobisoft.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew@wil.cx \
    --cc=rjw@sisk.pl \
    --cc=shemminger@vyatta.com \
    --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