[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <201505232208.38978@pali>
Date: Sat, 23 May 2015 22:08:38 +0200
From: Pali Rohár <pali.rohar@...il.com>
To: Dmitry Torokhov <dmitry.torokhov@...il.com>
Cc: Valdis Kletnieks <Valdis.Kletnieks@...edu>,
Darren Hart <dvhart@...radead.org>,
lkml <linux-kernel@...r.kernel.org>,
platform-driver-x86@...r.kernel.org
Subject: Re: dell_rbtn - kernel panic at boot...
On Saturday 23 May 2015 03:05:36 Pali Rohár wrote:
> On Saturday 23 May 2015 00:53:16 Dmitry Torokhov wrote:
> > On Thu, May 21, 2015 at 7:06 PM, Valdis Kletnieks
> >
> > <Valdis.Kletnieks@...edu> wrote:
> > > So after I made both config variables =y, the resulting kernel
> > > built, but died a glorious death at boot.
> >
> > I guess if both are built-in then, according to link order,
> > dell-laptop starts first, before dell-rbtn, and dies in
> > dell_rbtn_notifier_register() in call to
> > driver_for_each_device(&rbtn_driver.drv, ...) because rbtn_driver
> > has not been registered yet and thus half-initlalized.
> >
> > Thanks.
>
> pr_debug() messages could be useful... but no idea if we can get
> them.
>
> Is there any way to fix that dependency race condition? Could
> driver_attach() function call help?
Or what about using late_initcall() instead module_init() for driver
dell-laptop.ko? By default module_init() for static linked modules is
macro for device_initcall() which is called before late_initcall(),
right?
--
Pali Rohár
pali.rohar@...il.com
Download attachment "signature.asc " of type "application/pgp-signature" (199 bytes)
Powered by blists - more mailing lists