Re: bug: keep_bootcon and early printk together can lead to (invisible) kernel panic

2013-02-21 Thread Aaro Koskinen
On Thu, Feb 21, 2013 at 03:37:17PM +0100, Patrik, Kluba wrote: > I had a silent lockup on one of our embedded system under development. > It was not easy to track it down, so here's what I discovered, in case > somebody runs into similar trouble. > Using 'keep_bootcon' command line parameter, and

bug: keep_bootcon and early printk together can lead to (invisible) kernel panic

2013-02-21 Thread Patrik, Kluba
Hi! I had a silent lockup on one of our embedded system under development. It was not easy to track it down, so here's what I discovered, in case somebody runs into similar trouble. Using 'keep_bootcon' command line parameter, and enabling early printk can lead to a kernel panic. At least on

bug: keep_bootcon and early printk together can lead to (invisible) kernel panic

2013-02-21 Thread Patrik, Kluba
Hi! I had a silent lockup on one of our embedded system under development. It was not easy to track it down, so here's what I discovered, in case somebody runs into similar trouble. Using 'keep_bootcon' command line parameter, and enabling early printk can lead to a kernel panic. At least on

Re: bug: keep_bootcon and early printk together can lead to (invisible) kernel panic

2013-02-21 Thread Aaro Koskinen
On Thu, Feb 21, 2013 at 03:37:17PM +0100, Patrik, Kluba wrote: I had a silent lockup on one of our embedded system under development. It was not easy to track it down, so here's what I discovered, in case somebody runs into similar trouble. Using 'keep_bootcon' command line parameter, and