All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anton Vorontsov <cbouatmailru@gmail.com>
To: Luming Yu <luming.yu@gmail.com>
Cc: Jeff Garzik <jeff@garzik.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Michal Marek <mmarek@suse.cz>, Sam Ravnborg <sam@ravnborg.org>
Subject: Re: 2.6.25-rc1 ahci regression
Date: Thu, 3 Jun 2010 19:04:22 +0400	[thread overview]
Message-ID: <20100603150422.GA31604@oksana.dev.rtsoft.ru> (raw)
In-Reply-To: <AANLkTimRDNiN-rOl-V-WnRiVwXNaZ8sPPmj_TzsNLZmq@mail.gmail.com>

On Thu, Jun 03, 2010 at 10:13:57PM +0800, Luming Yu wrote:
> On Thu, Jun 3, 2010 at 9:50 PM, Anton Vorontsov <cbouatmailru@gmail.com> wrote:
> > On Thu, Jun 03, 2010 at 05:23:19PM +0400, Anton Vorontsov wrote:
> > [...]
> >> Oh. It seems I found it. It must be the module order loading
> >> thing.
> >>
> >> Can you try the patch down below?
> >
> > OTOH... libahci is a link-time dependency. And the order doesn't
> > matter here. So you should just have the libahci module in
> > the initrd (actually, mkinitrd or whatever you use should
> > have included this automatically).
> >
> 
> Neither ahci nor libachi is automatically included in initrd..

What commands you use to build the kernel and initrd?

> Manually added ahci and libachi into initrd seems to make the problem go away..
> Any idea why that could happen?

No idea off hand.

Cc'ing Kbuild folks. Question is: is there something wrong with
writing stuff like this:
obj-$(CONFIG_SATA_AHCI)         += ahci.o libahci.o
obj-$(CONFIG_SATA_AHCI_PLATFORM) += ahci_platform.o libahci.o
as in drivers/ata/Makefile?

It seem to link fine, .ko's are created. But for some reason
initrd doesn't include these modules for Luming...

Thanks,

-- 
Anton Vorontsov
email: cbouatmailru@gmail.com
irc://irc.freenode.net/bd2

  reply	other threads:[~2010-06-03 15:04 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-03  7:02 2.6.25-rc1 ahci regression Luming Yu
2010-06-03  7:13 ` Jeff Garzik
2010-06-03  7:28   ` Luming Yu
2010-06-03 15:54     ` Jeff Garzik
2010-06-03  7:54 ` Anton Vorontsov
     [not found]   ` <AANLkTil6k_4YwdvLai_VUlVjgz030ctu7djVGHu0qgd2@mail.gmail.com>
2010-06-03  8:41     ` Anton Vorontsov
2010-06-03  8:56       ` Luming Yu
2010-06-03  9:15         ` Anton Vorontsov
2010-06-03  9:18         ` Luming Yu
2010-06-03  9:39           ` Anton Vorontsov
2010-06-03 12:35             ` Luming Yu
2010-06-03 13:14               ` Anton Vorontsov
2010-06-03 13:23                 ` Anton Vorontsov
2010-06-03 13:50                   ` Anton Vorontsov
2010-06-03 14:13                     ` Luming Yu
2010-06-03 15:04                       ` Anton Vorontsov [this message]
2010-06-03 15:07                         ` Luming Yu
2010-06-03 15:45                         ` Américo Wang
2010-06-03 15:48                           ` Luming Yu
2010-06-04  4:58                             ` Américo Wang
2010-06-03 15:55                           ` Anton Vorontsov
2010-06-04  5:00                             ` Américo Wang
2010-06-03 13:38                 ` Luming Yu

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=20100603150422.GA31604@oksana.dev.rtsoft.ru \
    --to=cbouatmailru@gmail.com \
    --cc=jeff@garzik.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luming.yu@gmail.com \
    --cc=mmarek@suse.cz \
    --cc=sam@ravnborg.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.