* CONFIG_EARLY_PRINTK on versatile broken in mainline
@ 2012-04-05 22:52 Grant Likely
2012-04-05 23:08 ` Fabio Estevam
0 siblings, 1 reply; 6+ messages in thread
From: Grant Likely @ 2012-04-05 22:52 UTC (permalink / raw)
To: linux-arm-kernel
Has anyone else had problems with CONFIG_EARLY_PRINTK on current
mainline? ARM versatile fails to boot on qemu when it is selected.
I've just started bisecting. v3.3 is okay, but current mainline is
broken. Output stops after dumping out the memblock regions, and
__log_buf stops at the same place.
/home/grant/hacking/qemu/arm-softmmu/qemu-system-arm -M versatilepb
-nographic -kernel
/home/grant/hacking/linux/.build/arm/arch/arm/boot/zImage -append
memblock=debug earlyprintk console=ttyAMA0 console=tty0 debug -dtb
/home/grant/hacking/linux/.build/arm/arch/arm/boot/versatile-pb.dtb
-initrd /home/grant/hacking/images/versatile.rootfs.ext2
Uncompressing Linux... done, booting the kernel.
Booting Linux on physical CPU 0
Linux version 3.4.0-rc1+ (grant at ponder) (gcc version 4.6.3
(Ubuntu/Linaro 4.6.3-1ubuntu3) ) #383 Thu Apr 5 15:50:47 PDT 2012
CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00093177
CPU: VIVT data cache, VIVT instruction cache
Machine: ARM-Versatile (Device Tree Support), model: ARM Versatile PB
bootconsole [earlycon0] enabled
memblock_reserve: [0x00000000008400-0x000000003995f8]
arm_memblock_init+0x4c/0x150
memblock_reserve: [0x00000000d00000-0x0000000122f000]
arm_memblock_init+0xcc/0x150
memblock_reserve: [0x00000000004000-0x00000000008000]
arm_memblock_init+0xf0/0x150
memblock_reserve: [0x0000000122f000-0x00000001235fd2]
arm_dt_memblock_reserve+0x30/0xb4
MEMBLOCK configuration:
memory size = 0x8000000 reserved size = 0x8cb1ca
memory.cnt = 0x1
memory[0x0] [0x00000000000000-0x00000007ffffff], 0x8000000 bytes
reserved.cnt = 0x3
reserved[0x0] [0x00000000004000-0x00000000007fff], 0x4000 bytes
reserved[0x1] [0x00000000008400-0x000000003995f7], 0x3911f8 bytes
reserved[0x2] [0x00000000d00000-0x00000001235fd1], 0x535fd2 bytes
Memory policy: ECC disabled, Data cache writeback
memblock_reserve: [0x00000007fff000-0x00000008000000]
memblock_alloc_base_nid+0x44/0x58
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
^ permalink raw reply [flat|nested] 6+ messages in thread
* CONFIG_EARLY_PRINTK on versatile broken in mainline
2012-04-05 22:52 CONFIG_EARLY_PRINTK on versatile broken in mainline Grant Likely
@ 2012-04-05 23:08 ` Fabio Estevam
2012-04-05 23:19 ` Grant Likely
0 siblings, 1 reply; 6+ messages in thread
From: Fabio Estevam @ 2012-04-05 23:08 UTC (permalink / raw)
To: linux-arm-kernel
On Thu, Apr 5, 2012 at 7:52 PM, Grant Likely <grant.likely@secretlab.ca> wrote:
> Has anyone else had problems with CONFIG_EARLY_PRINTK on current
> mainline? ?ARM versatile fails to boot on qemu when it is selected.
> I've just started bisecting. ?v3.3 is okay, but current mainline is
> broken. ?Output stops after dumping out the memblock regions, and
> __log_buf stops at the same place.
Please try this patch:
http://permalink.gmane.org/gmane.linux.ports.arm.kernel/158694
^ permalink raw reply [flat|nested] 6+ messages in thread
* CONFIG_EARLY_PRINTK on versatile broken in mainline
2012-04-05 23:08 ` Fabio Estevam
@ 2012-04-05 23:19 ` Grant Likely
2012-04-05 23:27 ` Grant Likely
0 siblings, 1 reply; 6+ messages in thread
From: Grant Likely @ 2012-04-05 23:19 UTC (permalink / raw)
To: linux-arm-kernel
On Thu, Apr 5, 2012 at 4:08 PM, Fabio Estevam <festevam@gmail.com> wrote:
> On Thu, Apr 5, 2012 at 7:52 PM, Grant Likely <grant.likely@secretlab.ca> wrote:
>> Has anyone else had problems with CONFIG_EARLY_PRINTK on current
>> mainline? ?ARM versatile fails to boot on qemu when it is selected.
>> I've just started bisecting. ?v3.3 is okay, but current mainline is
>> broken. ?Output stops after dumping out the memblock regions, and
>> __log_buf stops at the same place.
>
> Please try this patch:
> http://permalink.gmane.org/gmane.linux.ports.arm.kernel/158694
I've already had that fix applied. This is a different issue. The
kernel boots fine if CONFIG_EARLY_PRINTK isn't defined.
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
^ permalink raw reply [flat|nested] 6+ messages in thread
* CONFIG_EARLY_PRINTK on versatile broken in mainline
2012-04-05 23:19 ` Grant Likely
@ 2012-04-05 23:27 ` Grant Likely
2012-04-06 0:07 ` Grant Likely
0 siblings, 1 reply; 6+ messages in thread
From: Grant Likely @ 2012-04-05 23:27 UTC (permalink / raw)
To: linux-arm-kernel
On Thu, Apr 5, 2012 at 4:19 PM, Grant Likely <grant.likely@secretlab.ca> wrote:
> On Thu, Apr 5, 2012 at 4:08 PM, Fabio Estevam <festevam@gmail.com> wrote:
>> On Thu, Apr 5, 2012 at 7:52 PM, Grant Likely <grant.likely@secretlab.ca> wrote:
>>> Has anyone else had problems with CONFIG_EARLY_PRINTK on current
>>> mainline? ?ARM versatile fails to boot on qemu when it is selected.
>>> I've just started bisecting. ?v3.3 is okay, but current mainline is
>>> broken. ?Output stops after dumping out the memblock regions, and
>>> __log_buf stops at the same place.
>>
>> Please try this patch:
>> http://permalink.gmane.org/gmane.linux.ports.arm.kernel/158694
>
> I've already had that fix applied. ?This is a different issue. ?The
> kernel boots fine if CONFIG_EARLY_PRINTK isn't defined.
Update: I'm still investigating, but it bisects out to this commit:
commit 94e5a85b3be0ce109d26aa6812b2a02c518a0e4b
Author: Russell King <rmk+kernel@arm.linux.org.uk>
Date: Wed Jan 18 15:32:49 2012 +0000
ARM: earlier initialization of vectors page
^ permalink raw reply [flat|nested] 6+ messages in thread* CONFIG_EARLY_PRINTK on versatile broken in mainline
2012-04-05 23:27 ` Grant Likely
@ 2012-04-06 0:07 ` Grant Likely
2012-04-06 0:19 ` Nicolas Pitre
0 siblings, 1 reply; 6+ messages in thread
From: Grant Likely @ 2012-04-06 0:07 UTC (permalink / raw)
To: linux-arm-kernel
On Thu, Apr 5, 2012 at 4:27 PM, Grant Likely <grant.likely@secretlab.ca> wrote:
> On Thu, Apr 5, 2012 at 4:19 PM, Grant Likely <grant.likely@secretlab.ca> wrote:
>> On Thu, Apr 5, 2012 at 4:08 PM, Fabio Estevam <festevam@gmail.com> wrote:
>>> On Thu, Apr 5, 2012 at 7:52 PM, Grant Likely <grant.likely@secretlab.ca> wrote:
>>>> Has anyone else had problems with CONFIG_EARLY_PRINTK on current
>>>> mainline? ?ARM versatile fails to boot on qemu when it is selected.
>>>> I've just started bisecting. ?v3.3 is okay, but current mainline is
>>>> broken. ?Output stops after dumping out the memblock regions, and
>>>> __log_buf stops at the same place.
>>>
>>> Please try this patch:
>>> http://permalink.gmane.org/gmane.linux.ports.arm.kernel/158694
>>
>> I've already had that fix applied. ?This is a different issue. ?The
>> kernel boots fine if CONFIG_EARLY_PRINTK isn't defined.
>
> Update: I'm still investigating, but it bisects out to this commit:
>
> commit 94e5a85b3be0ce109d26aa6812b2a02c518a0e4b
> Author: Russell King <rmk+kernel@arm.linux.org.uk>
> Date: ? Wed Jan 18 15:32:49 2012 +0000
>
> ? ?ARM: earlier initialization of vectors page
The following patch makes it boot. Calling printch() to output a
character right after early_trap_init() seems to unblock whatever was
wedging the system. A delay or a printk with "" format string doesn't
have any effect, it seems it must be a character output. This may be
a problem in the simulator. I've not been able to run this on real
hardware.
g.
diff --git a/arch/arm/mm/mmu.c b/arch/arm/mm/mmu.c
index b86f893..a6dafb1 100644
--- a/arch/arm/mm/mmu.c
+++ b/arch/arm/mm/mmu.c
@@ -995,6 +995,7 @@ void __init arm_mm_memblock_reserve(void)
* called function. This means you can't use any function or debugging
* method which may touch any device, otherwise the kernel _will_ crash.
*/
+extern void printch(int);
static void __init devicemaps_init(struct machine_desc *mdesc)
{
struct map_desc map;
@@ -1007,6 +1008,7 @@ static void __init devicemaps_init(struct
machine_desc *mdesc)
vectors = early_alloc(PAGE_SIZE);
early_trap_init(vectors);
+ printch('c');
for (addr = VMALLOC_START; addr; addr += PMD_SIZE)
pmd_clear(pmd_off_k(addr));
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
^ permalink raw reply related [flat|nested] 6+ messages in thread* CONFIG_EARLY_PRINTK on versatile broken in mainline
2012-04-06 0:07 ` Grant Likely
@ 2012-04-06 0:19 ` Nicolas Pitre
0 siblings, 0 replies; 6+ messages in thread
From: Nicolas Pitre @ 2012-04-06 0:19 UTC (permalink / raw)
To: linux-arm-kernel
On Thu, 5 Apr 2012, Grant Likely wrote:
> On Thu, Apr 5, 2012 at 4:27 PM, Grant Likely <grant.likely@secretlab.ca> wrote:
> > On Thu, Apr 5, 2012 at 4:19 PM, Grant Likely <grant.likely@secretlab.ca> wrote:
> >> On Thu, Apr 5, 2012 at 4:08 PM, Fabio Estevam <festevam@gmail.com> wrote:
> >>> On Thu, Apr 5, 2012 at 7:52 PM, Grant Likely <grant.likely@secretlab.ca> wrote:
> >>>> Has anyone else had problems with CONFIG_EARLY_PRINTK on current
> >>>> mainline? ?ARM versatile fails to boot on qemu when it is selected.
> >>>> I've just started bisecting. ?v3.3 is okay, but current mainline is
> >>>> broken. ?Output stops after dumping out the memblock regions, and
> >>>> __log_buf stops at the same place.
> >>>
> >>> Please try this patch:
> >>> http://permalink.gmane.org/gmane.linux.ports.arm.kernel/158694
> >>
> >> I've already had that fix applied. ?This is a different issue. ?The
> >> kernel boots fine if CONFIG_EARLY_PRINTK isn't defined.
> >
> > Update: I'm still investigating, but it bisects out to this commit:
> >
> > commit 94e5a85b3be0ce109d26aa6812b2a02c518a0e4b
> > Author: Russell King <rmk+kernel@arm.linux.org.uk>
> > Date: ? Wed Jan 18 15:32:49 2012 +0000
> >
> > ? ?ARM: earlier initialization of vectors page
>
> The following patch makes it boot. Calling printch() to output a
> character right after early_trap_init() seems to unblock whatever was
> wedging the system. A delay or a printk with "" format string doesn't
> have any effect, it seems it must be a character output. This may be
> a problem in the simulator. I've not been able to run this on real
> hardware.
FWIW, I have no problem booting v3.4-rc1 for vexpress on the ARM A15
Fast Model, given the patch referenced above is applied.
Nicolas
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2012-04-06 0:19 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-04-05 22:52 CONFIG_EARLY_PRINTK on versatile broken in mainline Grant Likely
2012-04-05 23:08 ` Fabio Estevam
2012-04-05 23:19 ` Grant Likely
2012-04-05 23:27 ` Grant Likely
2012-04-06 0:07 ` Grant Likely
2012-04-06 0:19 ` Nicolas Pitre
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox