Re: debug tip after earlycon is closed?

Hi. 2016-07-28 16:44 GMT+09:00 Arnd Bergmann : > > I think the problem is that you have three consoles: > > - the boot console that stays active until a real console comes up > - the framebuffer console that is initialized early and goes on to > disable the bootconsole > - the

Re: debug tip after earlycon is closed?

Hi. 2016-07-28 16:44 GMT+09:00 Arnd Bergmann : > > I think the problem is that you have three consoles: > > - the boot console that stays active until a real console comes up > - the framebuffer console that is initialized early and goes on to > disable the bootconsole > - the serial console

Re: debug tip after earlycon is closed?

On Thu, Jul 28, 2016 at 01:20:22PM +0100, Russell King - ARM Linux wrote: > To me, what this means is that the DT parsing of linux,stdout is > broken - while it may look nice from a design point of view, the > design is wrong and fails to take account of non-UART consoles in > the system. Note

Re: debug tip after earlycon is closed?

On Thu, Jul 28, 2016 at 01:20:22PM +0100, Russell King - ARM Linux wrote: > To me, what this means is that the DT parsing of linux,stdout is > broken - while it may look nice from a design point of view, the > design is wrong and fails to take account of non-UART consoles in > the system. Note

Re: debug tip after earlycon is closed?

On Thu, Jul 28, 2016 at 09:44:53AM +0200, Arnd Bergmann wrote: > I think the problem is that you have three consoles: > > - the boot console that stays active until a real console comes up > - the framebuffer console that is initialized early and goes on to > disable the bootconsole > - the

Re: debug tip after earlycon is closed?

On Thu, Jul 28, 2016 at 09:44:53AM +0200, Arnd Bergmann wrote: > I think the problem is that you have three consoles: > > - the boot console that stays active until a real console comes up > - the framebuffer console that is initialized early and goes on to > disable the bootconsole > - the

Re: debug tip after earlycon is closed?

On Thursday, July 28, 2016 11:08:13 AM CEST Masahiro Yamada wrote: > Hi Arnd, > > > 2016-07-27 16:32 GMT+09:00 Arnd Bergmann : > > On Wednesday, July 27, 2016 10:23:09 AM CEST Masahiro Yamada wrote: > >> [0.04] sched_clock: 56 bits at 50MHz, resolution 20ns, wraps > >>

Re: debug tip after earlycon is closed?

On Thursday, July 28, 2016 11:08:13 AM CEST Masahiro Yamada wrote: > Hi Arnd, > > > 2016-07-27 16:32 GMT+09:00 Arnd Bergmann : > > On Wednesday, July 27, 2016 10:23:09 AM CEST Masahiro Yamada wrote: > >> [0.04] sched_clock: 56 bits at 50MHz, resolution 20ns, wraps > >> every

Re: debug tip after earlycon is closed?

Hi Arnd, 2016-07-27 16:32 GMT+09:00 Arnd Bergmann : > On Wednesday, July 27, 2016 10:23:09 AM CEST Masahiro Yamada wrote: >> [0.04] sched_clock: 56 bits at 50MHz, resolution 20ns, wraps >> every 4398046511100ns >> [0.008254] Console: colour dummy device 80x25 >> [

Re: debug tip after earlycon is closed?

Hi Arnd, 2016-07-27 16:32 GMT+09:00 Arnd Bergmann : > On Wednesday, July 27, 2016 10:23:09 AM CEST Masahiro Yamada wrote: >> [0.04] sched_clock: 56 bits at 50MHz, resolution 20ns, wraps >> every 4398046511100ns >> [0.008254] Console: colour dummy device 80x25 >> [0.012700]

Re: debug tip after earlycon is closed?

On Wednesday, July 27, 2016 10:23:09 AM CEST Masahiro Yamada wrote: > [0.04] sched_clock: 56 bits at 50MHz, resolution 20ns, wraps > every 4398046511100ns > [0.008254] Console: colour dummy device 80x25 > [0.012700] console [tty0] enabled > [0.016110] bootconsole [uniphier0]

Re: debug tip after earlycon is closed?

On Wednesday, July 27, 2016 10:23:09 AM CEST Masahiro Yamada wrote: > [0.04] sched_clock: 56 bits at 50MHz, resolution 20ns, wraps > every 4398046511100ns > [0.008254] Console: colour dummy device 80x25 > [0.012700] console [tty0] enabled > [0.016110] bootconsole [uniphier0]

Re: debug tip after earlycon is closed?

Hi Sebastian, 2016-07-27 11:17 GMT+09:00 Sebastian Reichel : > Hi, > > On Wed, Jul 27, 2016 at 10:23:09AM +0900, Masahiro Yamada wrote: >> When the kernel fails to boot and its log console is silent, >> I use earlycon and I often find the cause of error with it. >> >> But, I

Re: debug tip after earlycon is closed?

Hi Sebastian, 2016-07-27 11:17 GMT+09:00 Sebastian Reichel : > Hi, > > On Wed, Jul 27, 2016 at 10:23:09AM +0900, Masahiro Yamada wrote: >> When the kernel fails to boot and its log console is silent, >> I use earlycon and I often find the cause of error with it. >> >> But, I have been wondering

Re: debug tip after earlycon is closed?

Hi, On Wed, Jul 27, 2016 at 10:23:09AM +0900, Masahiro Yamada wrote: > When the kernel fails to boot and its log console is silent, > I use earlycon and I often find the cause of error with it. > > But, I have been wondering if there is an easy-to-use > debug tip which is available after

Re: debug tip after earlycon is closed?

Hi, On Wed, Jul 27, 2016 at 10:23:09AM +0900, Masahiro Yamada wrote: > When the kernel fails to boot and its log console is silent, > I use earlycon and I often find the cause of error with it. > > But, I have been wondering if there is an easy-to-use > debug tip which is available after

debug tip after earlycon is closed?

Hi. When the kernel fails to boot and its log console is silent, I use earlycon and I often find the cause of error with it. But, I have been wondering if there is an easy-to-use debug tip which is available after earlycon is disabled. I noticed the current mainline would not boot on my

debug tip after earlycon is closed?

Hi. When the kernel fails to boot and its log console is silent, I use earlycon and I often find the cause of error with it. But, I have been wondering if there is an easy-to-use debug tip which is available after earlycon is disabled. I noticed the current mainline would not boot on my