Hey Nicolas, Over the last few days I've been playing with recent kernels on a BeagleBoard xM. So far I've gotten Linus' v2.6.37 kernel booting, as well as the android-2.6.37 git tree booting as well. However, when I try to boot the latest linaro 2.6.37 git tree, I just get:
Starting kernel ...
Uncompressing Linux... done, booting the kernel.
And nothing else. I've tried enabling early printk, but still nothing.
I'm working on bisecting down what broke since 2.6.37, but if you have any hints, I'd appreciate it!
thanks -john
On Fri, 2011-01-21 at 00:36 -0800, john stultz wrote:
Hey Nicolas, Over the last few days I've been playing with recent kernels on a BeagleBoard xM. So far I've gotten Linus' v2.6.37 kernel booting, as well as the android-2.6.37 git tree booting as well. However, when I try to boot the latest linaro 2.6.37 git tree, I just get:
Starting kernel ...
Uncompressing Linux... done, booting the kernel.
And nothing else. I've tried enabling early printk, but still nothing.
I'm working on bisecting down what broke since 2.6.37, but if you have any hints, I'd appreciate it!
Just a small update before I head to bed: I bisected it down and it looks like 24251d487c726042855144a1b00aec54df1ca8cf (sched_clock: allow init_sched_clock() to be called early) is the culprit. I'll have to take a look at it tomorrow to see whats going on. Reverting it against the linaro-2.6.37 head does resolve the issue.
thanks -john
I suppose attached patch from Paul should fix this issue.
regards Vishwa
On Fri, Jan 21, 2011 at 2:41 PM, john stultz johnstul@us.ibm.com wrote:
On Fri, 2011-01-21 at 00:36 -0800, john stultz wrote:
Hey Nicolas, Over the last few days I've been playing with recent kernels on a BeagleBoard xM. So far I've gotten Linus' v2.6.37 kernel booting, as well as the android-2.6.37 git tree booting as well. However, when I try to boot the latest linaro 2.6.37 git tree, I just get:
Starting kernel ...
Uncompressing Linux... done, booting the kernel.
And nothing else. I've tried enabling early printk, but still nothing.
I'm working on bisecting down what broke since 2.6.37, but if you have any hints, I'd appreciate it!
Just a small update before I head to bed: I bisected it down and it looks like 24251d487c726042855144a1b00aec54df1ca8cf (sched_clock: allow init_sched_clock() to be called early) is the culprit. I'll have to take a look at it tomorrow to see whats going on. Reverting it against the linaro-2.6.37 head does resolve the issue.
thanks -john
linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
On Fri, 21 Jan 2011, john stultz wrote:
On Fri, 2011-01-21 at 00:36 -0800, john stultz wrote:
Hey Nicolas, Over the last few days I've been playing with recent kernels on a BeagleBoard xM. So far I've gotten Linus' v2.6.37 kernel booting, as well as the android-2.6.37 git tree booting as well. However, when I try to boot the latest linaro 2.6.37 git tree, I just get:
Starting kernel ...
Uncompressing Linux... done, booting the kernel.
And nothing else. I've tried enabling early printk, but still nothing.
I'm working on bisecting down what broke since 2.6.37, but if you have any hints, I'd appreciate it!
Just a small update before I head to bed: I bisected it down and it looks like 24251d487c726042855144a1b00aec54df1ca8cf (sched_clock: allow init_sched_clock() to be called early) is the culprit. I'll have to take a look at it tomorrow to see whats going on. Reverting it against the linaro-2.6.37 head does resolve the issue.
OK, I think I know what's going on then. Will have a look.
Nicolas
On Fri, 21 Jan 2011, Nicolas Pitre wrote:
On Fri, 21 Jan 2011, john stultz wrote:
On Fri, 2011-01-21 at 00:36 -0800, john stultz wrote:
Hey Nicolas, Over the last few days I've been playing with recent kernels on a BeagleBoard xM. So far I've gotten Linus' v2.6.37 kernel booting, as well as the android-2.6.37 git tree booting as well. However, when I try to boot the latest linaro 2.6.37 git tree, I just get:
Starting kernel ...
Uncompressing Linux... done, booting the kernel.
And nothing else. I've tried enabling early printk, but still nothing.
I'm working on bisecting down what broke since 2.6.37, but if you have any hints, I'd appreciate it!
Just a small update before I head to bed: I bisected it down and it looks like 24251d487c726042855144a1b00aec54df1ca8cf (sched_clock: allow init_sched_clock() to be called early) is the culprit. I'll have to take a look at it tomorrow to see whats going on. Reverting it against the linaro-2.6.37 head does resolve the issue.
OK, I think I know what's going on then. Will have a look.
Should be fixed now, along with a couple other fixes from the upstream OMAP tree.
Nicolas
-
john stultz -
Nicolas Pitre -
Vishwanath Sripathy