Peter,
Your test kernel doesn't output anything on the console, but under a hardware debugger I can confirm that it does start, and then panics. I think it's a dtb problem. I tried using the reference one from the 3.8 rpm for ES and with no dtb. With no dtb we fall over in paging_init as we don't know what the physical machine looks like. With a dtb I don't yet have the exact failure caught (out of time tonight) but I suspect it is still a busted dtb. We can build a local kernel with debug, earlyprintk, and I can poke the debugger more on Wed evening. I skimmed the config only briefly, generally need more time to look into this.
Jon.
Paul will ping you for a link to that scratch kernel and try to gather some data, then I will poke more later. Night.
I'll add early printk to another one and kick off a build so it will give us more info.
P On 27 Feb 2013 07:23, "Jonathan Masters" jcm@redhat.com wrote:
Paul will ping you for a link to that scratch kernel and try to gather some data, then I will poke more later. Night.
-- Sent from my iPad
On Feb 27, 2013, at 2:11, Jonathan Masters jcm@redhat.com wrote:
Peter,
Your test kernel doesn't output anything on the console, but under a
hardware debugger I can confirm that it does start, and then panics. I think it's a dtb problem. I tried using the reference one from the 3.8 rpm for ES and with no dtb. With no dtb we fall over in paging_init as we don't know what the physical machine looks like. With a dtb I don't yet have the exact failure caught (out of time tonight) but I suspect it is still a busted dtb. We can build a local kernel with debug, earlyprintk, and I can poke the debugger more on Wed evening. I skimmed the config only briefly, generally need more time to look into this.
Jon.
-- Sent from my iPad _______________________________________________ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
OK, thanks. Any luck on the high bank issue? On 27 Feb 2013 07:11, "Jonathan Masters" jcm@redhat.com wrote:
Peter,
Your test kernel doesn't output anything on the console, but under a hardware debugger I can confirm that it does start, and then panics. I think it's a dtb problem. I tried using the reference one from the 3.8 rpm for ES and with no dtb. With no dtb we fall over in paging_init as we don't know what the physical machine looks like. With a dtb I don't yet have the exact failure caught (out of time tonight) but I suspect it is still a busted dtb. We can build a local kernel with debug, earlyprintk, and I can poke the debugger more on Wed evening. I skimmed the config only briefly, generally need more time to look into this.
Jon.
-- Sent from my iPad