> In message <Pine.LNX.3.96.1021230212600.8353B-100000@gatekeeper.tmr.com> you wr
> ite:
> > On Sun, 29 Dec 2002, Rusty Russell wrote:
> >
> > > In message <Pine.LNX.4.44.0212281758230.839-100000@linux-dev> you write:
> > > > Hello all,
> > > > I received the following warnings while a 'make modules_install'. It
> > > > looks like there are a few more locking changes that need to be made. :)
> > >
> > > This is SMP, right? Those warnings are perfectly correct (yes, those
> > > files need updating).
> >
> > Any guess when you'll get them fixed?
>
> I've discovered an interesting (but kinda obvious) phenomenon. If you
> destabilize some part of the kernel, it becomes the natural suspect
> for problems.
>
> The corollary is, I'm getting more reports on kernel "module" bugs
> which are not actually my fault at all (and some, like erroneous
> __init sections, which the new module code just shows up).
>
> This is one: these drivers are actually broken. They give warnings on
> compile, they won't link when compiled in, and they won't insert as
> modules.
>
> Hope that clarifies,
If they didn't work in 2.5.47, before the module change, then clearly they
are broken on their own. If they worked until then, and especially if they
work built-in still, I would certainly suspect that the problem is related
to the module change.
-- bill davidsen <davidsen@tmr.com> CTO, TMR Associates, Inc Doing interesting things with little computers since 1979.- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/