10:12 <warpme> guys: in dmesg i'm getting "probe of ffbd0000.ethernet returned -517 after 28 usecs". Is -517 means missing one/more of clocks?

10:13 <mansr> 517 is EPROBEDEFER

10:18 <warpme> indeed this (and many other modules are deferred; i see "platform ffbd0000.ethernet: deferred probe pending"). I'm trying to find why. I added initcall_debug to kernel cmd and got this -517 info. but can't find clue what missings are causing deferred load (in fact module is deferred for endless time=not loaded at all)

11:18 <apritzel> warpme: do you get to a prompt? Can you check /sys/kernel/debug/devices_deferred to see if the device is still in there?

11:19 <apritzel> sometimes that file gives more info

11:20 <warpme> apritzel : unfortunately no :-( Both: USB and Eth support is in deferred modules....

11:21 <warpme> but i can add this to init scriptes

11:21 <warpme> let me try

11:24 <apritzel> warpme: carefully look in dmesg for error messages from drivers

11:24 <DarkNeutrino> Also enable log level 7 and enable debug

11:25 <DarkNeutrino> Could help to tell you why its doing that

12:29 <wens> apritzel: your mfd patch got rejected :|

12:29 <apritzel> yeah, I just saw

12:29 <apritzel> it's look pretty nasty to split this up, though

12:30 <apritzel> checking whether I can abuse a member of struct mfd_cell to mark that it's optional

12:32 <apritzel> or even add a flag to that struct

12:34 <warpme> DarkNeutrino : when you are saying "enable debug" - do you mean specific kernel config or kernel cmd.line?

12:38 <DarkNeutrino> CONFIG_DEBUG_KERNEL

12:38 <DarkNeutrino> Enable this and then you can enable debug for that specific driver if such feature exists

12:39 <DarkNeutrino> If not. I use the lovely method of spam it with debug prints hehe