Complementing what Arnd said, we got the dynamic ftrace to work. Just changed 4 things in the *menuconfig*. Before these were built as modules (this is the default I guess): CONFIG_USB=m CONFIG_SOUND=m CONFIG_SND=m CONFIG_SND_USB_AUDIO=m
Then got them built into the kernel: CONFIG_USB=y CONFIG_SOUND=y CONFIG_SND=y CONFIG_SND_USB_AUDIO=y And everything worked just fine. In my config when I also tried to build the *CONFIG_SND_PS3* into the kernel, the kernel did not boot (probably another bug !? :-). Cheers, Remis On Sat, Jan 31, 2009 at 11:25 AM, Arnd Bergmann <a...@arndb.de> wrote: > On Saturday 31 January 2009, Geoff Levand wrote: >> > >> > So I take it that the above showed that the code worked for some? >> >> In my trials it blows up on the first load_module() call, and for my >> config that was usbcore: > > I looked into it some more with Remis yesterday, and we got ftrace > working by building usbcore and alsa into the kernel. Incidentally, > usbcore is the largest module in this installation (~3MB), which > indicates that it is in some way either related to the size of the > module. > >> This ptr of 5f666f725f726573 seems bogus. I think this code is not >> working correctly: > > This is an ascii string "_for_res", probably part of > usb_lock_device_for_reset. We saw the same behaviour, but > a different string. > > Arnd <>< _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
