public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Donald Parsons <dparsons@brightdsl.net>
Cc: Harald Hoyer <harald.hoyer@gmail.com>,
	Bjorn Helgaas <bjorn.helgaas@hp.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: Linux 2.6.35
Date: Wed, 04 Aug 2010 16:15:11 -0400	[thread overview]
Message-ID: <4C59CA4F.4090003@garzik.org> (raw)
In-Reply-To: <1280802701.5836.10.camel@falcon.homelinux.org>

On 08/02/2010 10:31 PM, Donald Parsons wrote:
> Using your suggestion as to where the problem lies, I investigated
> more deeply and found:
>
> I've now got 2.6.35-rc6-git3 to boot (and almost certainly 2.6.35 final)
>
> Make oldconfig broke at the transition where boot began failed, ie,
> between 2.6.34-git4 and 2.6.34-git5.   Even though modules are the
> same, boot fails.  If I use gconfig and set CONFIG_SATA_AHCI=y
> instead of CONFIG_SATA_AHCI=m it works, except cannot select =y
> unless CONFIG_ATA changed from m to y.
>
> So at some point in past, make oldconfig had apparently changed
> CONFIG_SATA_AHCI from y to m and system still booted.  But between
> 2.6.34-git4 and 2.6.34-git5 the ability to boot was lost.
>
> So make oldconfig is not 100% trustworthy in this case.  I do not
> know if this is a problem that should be fixed.  Ask if you want
> any .config diffs.


The modules are not necessarily the same:  "libahci" was introduced in

	commit 365cfa1ed5a36f9bcb9f64c9f0f52155af2e9fef
	Author: Anton Vorontsov <avorontsov@ru.mvista.com>
	Date:   Sun Mar 28 00:22:14 2010 -0400

	    ahci: Move generic code into libahci

so there exists the possibility that the initramfs builder, or whatever 
is being used to load your ATA drivers, missed this dependency.  Modern 
initramfs builders should be able to figure out module dependencies, so 
this /shouldn't/ be an issue...  but it might be.

	Jeff




  parent reply	other threads:[~2010-08-04 20:15 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-02  2:31 Linux 2.6.35 Donald Parsons
2010-08-02  3:28 ` Randy Dunlap
2010-08-02  3:38 ` Bjorn Helgaas
2010-08-02  4:21   ` Donald Parsons
2010-08-02 13:48     ` Bjorn Helgaas
2010-08-02 15:59       ` Harald Hoyer
2010-08-02 22:09         ` Frédéric L. W. Meunier
2010-08-02 22:34           ` Frédéric L. W. Meunier
2010-08-02 18:38       ` Donald Parsons
2010-08-02 16:08     ` Harald Hoyer
2010-08-03  2:31       ` Donald Parsons
2010-08-03  4:42         ` Randy Dunlap
2010-08-03 10:24           ` Stefan Richter
2010-08-03 18:26             ` Donald Parsons
2010-08-03 16:26           ` Donald Parsons
2010-08-03 16:40             ` Randy Dunlap
2010-08-03 17:45               ` Donald Parsons
2010-08-03 18:35                 ` Randy Dunlap
2010-08-03 22:34                 ` Randy Dunlap
2010-08-04 20:15         ` Jeff Garzik [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-08-01 23:52 Linus Torvalds
2010-08-02  0:32 ` Stephen Rothwell
2010-08-02  8:14   ` Nick Piggin
2010-08-02  8:52     ` Stephen Rothwell
2010-08-02  2:33 ` Dave Chinner
2010-08-02  2:50   ` Linus Torvalds
2010-08-02  5:58     ` Dave Chinner
2010-08-02  7:55       ` Nick Piggin
2010-08-02  8:24         ` Christoph Hellwig
2010-08-02  8:46           ` KOSAKI Motohiro
2010-08-02  9:05           ` Christoph Hellwig
2010-08-02 10:07             ` Nick Piggin
2010-08-02  9:51           ` Nick Piggin
2010-08-03  8:18   ` Andi Kleen
2010-08-03  9:28     ` Nick Piggin
2010-08-03  9:49       ` Andi Kleen
2010-08-03 15:05       ` Henrique de Moraes Holschuh

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=4C59CA4F.4090003@garzik.org \
    --to=jeff@garzik.org \
    --cc=bjorn.helgaas@hp.com \
    --cc=dparsons@brightdsl.net \
    --cc=harald.hoyer@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /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