* mx6q boot on linux-next 20130703
@ 2013-07-03 23:52 Fabio Estevam
2013-07-04 4:08 ` Fabio Estevam
2013-07-04 6:39 ` Huang Shijie
0 siblings, 2 replies; 6+ messages in thread
From: Fabio Estevam @ 2013-07-03 23:52 UTC (permalink / raw)
To: linux-arm-kernel
Hi,
I am running linux-next 20130703 on a mx6q board, and seeing a strange
behaviour.
Only if I enable DEBUG_LL + earlyprintk and disable
CONFIG_SERIAL_FSL_LPUART (serial driver for the FSL Vybrid SoC), I am
able to boot the kernel until the prompt.
Does anyone have any suggestion?
Regards,
Fabio Estevam
^ permalink raw reply [flat|nested] 6+ messages in thread
* mx6q boot on linux-next 20130703
2013-07-03 23:52 mx6q boot on linux-next 20130703 Fabio Estevam
@ 2013-07-04 4:08 ` Fabio Estevam
2013-07-04 6:41 ` Shawn Guo
2013-07-04 6:39 ` Huang Shijie
1 sibling, 1 reply; 6+ messages in thread
From: Fabio Estevam @ 2013-07-04 4:08 UTC (permalink / raw)
To: linux-arm-kernel
On Wed, Jul 3, 2013 at 8:52 PM, Fabio Estevam <festevam@gmail.com> wrote:
> Hi,
>
> I am running linux-next 20130703 on a mx6q board, and seeing a strange
> behaviour.
>
> Only if I enable DEBUG_LL + earlyprintk and disable
> CONFIG_SERIAL_FSL_LPUART (serial driver for the FSL Vybrid SoC), I am
> able to boot the kernel until the prompt.
>
> Does anyone have any suggestion?
Ok, I managed to boot the default imx_v6_v7_defconfig on my mx6q board if I do:
--- a/drivers/tty/serial/imx.c
+++ b/drivers/tty/serial/imx.c
@@ -1652,7 +1652,7 @@ static void __exit imx_serial_exit(void)
uart_unregister_driver(&imx_reg);
}
-module_init(imx_serial_init);
+arch_initcall(imx_serial_init);
module_exit(imx_serial_exit);
MODULE_AUTHOR("Sascha Hauer");
Is this the correct approach?
^ permalink raw reply [flat|nested] 6+ messages in thread* mx6q boot on linux-next 20130703
2013-07-04 4:08 ` Fabio Estevam
@ 2013-07-04 6:41 ` Shawn Guo
2013-07-08 22:36 ` Fabio Estevam
0 siblings, 1 reply; 6+ messages in thread
From: Shawn Guo @ 2013-07-04 6:41 UTC (permalink / raw)
To: linux-arm-kernel
On Thu, Jul 04, 2013 at 01:08:13AM -0300, Fabio Estevam wrote:
> On Wed, Jul 3, 2013 at 8:52 PM, Fabio Estevam <festevam@gmail.com> wrote:
> > Hi,
> >
> > I am running linux-next 20130703 on a mx6q board, and seeing a strange
> > behaviour.
> >
> > Only if I enable DEBUG_LL + earlyprintk and disable
Yes, I see the issue here too, and turning on earlyprintk can remove the
issue.
> > CONFIG_SERIAL_FSL_LPUART (serial driver for the FSL Vybrid SoC), I am
This is irrelevant according to my test.
> > able to boot the kernel until the prompt.
> >
> > Does anyone have any suggestion?
>
I do not get time to track it down. But it does not seems to be an imx
specific problem.
> Ok, I managed to boot the default imx_v6_v7_defconfig on my mx6q board if I do:
>
> --- a/drivers/tty/serial/imx.c
> +++ b/drivers/tty/serial/imx.c
> @@ -1652,7 +1652,7 @@ static void __exit imx_serial_exit(void)
> uart_unregister_driver(&imx_reg);
> }
>
> -module_init(imx_serial_init);
> +arch_initcall(imx_serial_init);
> module_exit(imx_serial_exit);
>
> MODULE_AUTHOR("Sascha Hauer");
>
> Is this the correct approach?
Without knowing the root cause of the problem, we can not tell.
Shawn
^ permalink raw reply [flat|nested] 6+ messages in thread* mx6q boot on linux-next 20130703
2013-07-04 6:41 ` Shawn Guo
@ 2013-07-08 22:36 ` Fabio Estevam
0 siblings, 0 replies; 6+ messages in thread
From: Fabio Estevam @ 2013-07-08 22:36 UTC (permalink / raw)
To: linux-arm-kernel
On Thu, Jul 4, 2013 at 3:41 AM, Shawn Guo <shawn.guo@linaro.org> wrote:
> On Thu, Jul 04, 2013 at 01:08:13AM -0300, Fabio Estevam wrote:
>> On Wed, Jul 3, 2013 at 8:52 PM, Fabio Estevam <festevam@gmail.com> wrote:
>> > Hi,
>> >
>> > I am running linux-next 20130703 on a mx6q board, and seeing a strange
>> > behaviour.
>> >
>> > Only if I enable DEBUG_LL + earlyprintk and disable
>
> Yes, I see the issue here too, and turning on earlyprintk can remove the
> issue.
linux-next 20130708 does not have this issue anymore.
^ permalink raw reply [flat|nested] 6+ messages in thread
* mx6q boot on linux-next 20130703
2013-07-03 23:52 mx6q boot on linux-next 20130703 Fabio Estevam
2013-07-04 4:08 ` Fabio Estevam
@ 2013-07-04 6:39 ` Huang Shijie
2013-07-04 12:07 ` Fabio Estevam
1 sibling, 1 reply; 6+ messages in thread
From: Huang Shijie @ 2013-07-04 6:39 UTC (permalink / raw)
To: linux-arm-kernel
? 2013?07?04? 07:52, Fabio Estevam ??:
> Hi,
>
> I am running linux-next 20130703 on a mx6q board, and seeing a strange
> behaviour.
>
> Only if I enable DEBUG_LL + earlyprintk and disable
> CONFIG_SERIAL_FSL_LPUART (serial driver for the FSL Vybrid SoC), I am
> able to boot the kernel until the prompt.
>
> Does anyone have any suggestion?
I tested the linux-next-0625, the boot is ok.
I think this issue is caused by the common code, not the imx code.
thanks
Huang Shijie
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2013-07-08 22:36 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-07-03 23:52 mx6q boot on linux-next 20130703 Fabio Estevam
2013-07-04 4:08 ` Fabio Estevam
2013-07-04 6:41 ` Shawn Guo
2013-07-08 22:36 ` Fabio Estevam
2013-07-04 6:39 ` Huang Shijie
2013-07-04 12:07 ` Fabio Estevam
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.