On 06/28/13 09:58, Stehle Vincent-B46079 wrote: > From: linux-next-owner@xxxxxxxxxxxxxxx [mailto:linux-next-owner@xxxxxxxxxxxxxxx] On Behalf Of Stephen Boyd > (..) >> Do you have debug_ll support to get some serial logs? > Hi, > > Thanks for your concern on the matter. You are right, there is debug_ll support for i.MX6. If I activate it for next-20130628 imx_v6_v7_defconfig, that only "buys" me one additional line, though: > > Uncompressing Linux... done, booting the kernel. Oh and also add earlyprintk to the command line and enable the earlyprintk config. It should buy you some more lines. > >> Also could you try booting with maxcpus=1 on the kernel commandline? > Good idea; it goes much further with this one (until it crashes in wm8962_probe(), which is as far as I go when I revert 064706514ec3fea740c2656e03c4f01f6a551ac4). Interesting. Thanks for the test. > >> And it would be useful to have the output of /proc/timer_list if you have it from a working device. > Sure; I pasted it below. Is this an SMP capable device? What devicetree blob are you using? > >> I believe you have a per-cpu TWD timer and a global imx-gpt? > I think you are right from what I see in /proc/interrupts. Well oddly I don't see any twd in the timer list but that may be because you're not running more than one CPU? It would be good to get the output when you run SMP if it has that support. -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation -- To unsubscribe from this list: send the line "unsubscribe linux-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
