[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100603150422.GA31604@oksana.dev.rtsoft.ru>
Date: Thu, 3 Jun 2010 19:04:22 +0400
From: Anton Vorontsov <cbouatmailru@...il.com>
To: Luming Yu <luming.yu@...il.com>
Cc: Jeff Garzik <jeff@...zik.org>, LKML <linux-kernel@...r.kernel.org>,
Michal Marek <mmarek@...e.cz>, Sam Ravnborg <sam@...nborg.org>
Subject: Re: 2.6.25-rc1 ahci regression
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@...il.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@...il.com
irc://irc.freenode.net/bd2
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists