Hi Thomas, Have you been able to find the issue from the logs? Best regards, Luís Mendes On Wed, Jan 9, 2019 at 2:38 PM Luís Mendes <luis.p.mendes@xxxxxxxxx> wrote: > > Hello Thomas, > > Replies in between. > > Best regards, > Luís > > > On Wed, Jan 9, 2019 at 8:15 AM Thomas Petazzoni > <thomas.petazzoni@xxxxxxxxxxx> wrote: > > > > Hello Luis, > > > > On Tue, 8 Jan 2019 23:22:05 +0000, Luís Mendes wrote: > > > > > > Sorry for the long delay, the Christmas/New Year vacation and some > > > > personal issues got in the way. > > > No problem, life has its priorities! and by the way: Happy new year! > > > > Thanks, you too! > > Thanks! > > > > > > > > > You will most likely have to increase CONFIG_LOG_BUF_SHIFT to avoid > > > > having dropped messages, as my additional debug messages are quite > > > > verbose. I'm using CONFIG_LOG_BUF_SHIFT=16. > > > The logs from the new kernel are not starting at 0.0 sec, as > > > CONFIG_LOG_BUF_SHIFT=16 wasn't large enough, but for the reverted > > > patch case I changed to CONFIG_LOG_BUF_SHIFT=17. > > > If you find relevant information can be missing tell me and I will > > > recompile the kernel with the patch > > > 1f08673eef1236f7d02d93fcf596bb8531ef0d12 applied and > > > CONFIG_LOG_BUF_SHIFT=17. I believe it won't be needed though, since > > > the pci logs are practically complete. > > > > Sadly, the kern_4.20_debug.log file is incomplete. I would like to at > > least see it starting from: > > > > Jan 8 22:57:51 picolo kernel: [ 6.792819] mvebu-pcie soc:pcie: MEM: [mem 0xd0000000-0xefffffff], IO: [io 0xffe00000-0xffefffff] > > > > (this line from the reverted log, but I'd like to see it in the non-reverted log as well) > > In attachment follows the requested complete log using CONFIG_LOG_BUF_SHIFT=17. > > > > > Thanks! > > > > Thomas > > -- > > Thomas Petazzoni, CTO, Bootlin > > Embedded Linux and Kernel engineering > > https://bootlin.com
