On Thursday, June 26, 2014 at 11:26:09 AM, Juergen Borleis wrote: > Hi Marek, > > On Thursday 26 June 2014 11:17:12 Marek Vasut wrote: > > On Thursday, June 26, 2014 at 09:32:30 AM, Juergen Borleis wrote: > > > On Thursday 26 June 2014 05:43:19 Fabio Estevam wrote: > > > > [...] > > > > > > > Below is the log with linux-next kernel and earlyprintk enabled: > > > Does it also hang when you disable "earlyprintk"? A few weeks ago we > > > had a similar issue with i.MX6/PCI and "earlyprintk" (at the end it > > > was caused by a clock change for the UART when changing from the early > > > to the regular console). > > > > How can the UART clock have impact on the PCIe please ? > > Not to the PCIe hardware, it just hanged the kernel when the PCIe driver > came up (due to some of its messages it tries to output at this moment). Another hint, can a blocking msleep() hang the driver ? The driver probes in fs_initcall stage, I'm not sure if it cannot hit some kind of a problem when using the msleep() ? It's unlikely though ... Best regards, Marek Vasut -- To unsubscribe from this list: send the line "unsubscribe linux-pci" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
