* Re: currect MigoR seems doesn't work
2009-09-29 5:59 currect MigoR seems doesn't work Kuninori Morimoto
@ 2009-09-29 7:58 ` Magnus Damm
2009-09-29 9:26 ` Kuninori Morimoto
` (5 subsequent siblings)
6 siblings, 0 replies; 8+ messages in thread
From: Magnus Damm @ 2009-09-29 7:58 UTC (permalink / raw)
To: linux-sh
Hi Morimoto-san,
On Tue, Sep 29, 2009 at 2:59 PM, Kuninori Morimoto
<morimoto.kuninori@renesas.com> wrote:
>> sh3-linux-objdump -d vmlinux > asm
> zsh: abort sh3-linux-objdump -d vmlinux
Last time i checked objdump was broken with dsp instructions.
Disabling dsp support in the kernel should solve the issue short term.
cheers,
/ magnus
^ permalink raw reply [flat|nested] 8+ messages in thread* Re: currect MigoR seems doesn't work
2009-09-29 5:59 currect MigoR seems doesn't work Kuninori Morimoto
2009-09-29 7:58 ` Magnus Damm
@ 2009-09-29 9:26 ` Kuninori Morimoto
2009-09-30 2:20 ` Kuninori Morimoto
` (4 subsequent siblings)
6 siblings, 0 replies; 8+ messages in thread
From: Kuninori Morimoto @ 2009-09-29 9:26 UTC (permalink / raw)
To: linux-sh
Hi Magnus
Thank you for comment
> Last time i checked objdump was broken with dsp instructions.
> Disabling dsp support in the kernel should solve the issue short term.
OK. if I remove DSP from .config,
I can use objdump !!
But MigoR still doesn't work now.
I need debug for it...
Thank you again
Best regards
--
Kuninori Morimoto
^ permalink raw reply [flat|nested] 8+ messages in thread* Re: currect MigoR seems doesn't work
2009-09-29 5:59 currect MigoR seems doesn't work Kuninori Morimoto
2009-09-29 7:58 ` Magnus Damm
2009-09-29 9:26 ` Kuninori Morimoto
@ 2009-09-30 2:20 ` Kuninori Morimoto
2009-09-30 2:24 ` Paul Mundt
` (3 subsequent siblings)
6 siblings, 0 replies; 8+ messages in thread
From: Kuninori Morimoto @ 2009-09-30 2:20 UTC (permalink / raw)
To: linux-sh
Hi
> But MigoR still doesn't work now.
> I need debug for it...
I searched MigoR dead process.
But I'm not sure why.
start_kernel
setup_arch
setup_memory
setup_bootmem_allocator
for()
reserve_bootmem (when i=2 I think)
mark_bootmem
BUG() <= dead here and reboot MigoR
Best regards
--
Kuninori Morimoto
^ permalink raw reply [flat|nested] 8+ messages in thread* Re: currect MigoR seems doesn't work
2009-09-29 5:59 currect MigoR seems doesn't work Kuninori Morimoto
` (2 preceding siblings ...)
2009-09-30 2:20 ` Kuninori Morimoto
@ 2009-09-30 2:24 ` Paul Mundt
2009-09-30 2:46 ` Kuninori Morimoto
` (2 subsequent siblings)
6 siblings, 0 replies; 8+ messages in thread
From: Paul Mundt @ 2009-09-30 2:24 UTC (permalink / raw)
To: linux-sh
On Wed, Sep 30, 2009 at 11:20:31AM +0900, Kuninori Morimoto wrote:
> > But MigoR still doesn't work now.
> > I need debug for it...
>
> I searched MigoR dead process.
> But I'm not sure why.
>
> start_kernel
> setup_arch
> setup_memory
> setup_bootmem_allocator
> for()
> reserve_bootmem (when i=2 I think)
> mark_bootmem
> BUG() <= dead here and reboot MigoR
>
Do you have NUMA support enabled? It's possible the LMB changes impacted
that.
^ permalink raw reply [flat|nested] 8+ messages in thread* Re: currect MigoR seems doesn't work
2009-09-29 5:59 currect MigoR seems doesn't work Kuninori Morimoto
` (3 preceding siblings ...)
2009-09-30 2:24 ` Paul Mundt
@ 2009-09-30 2:46 ` Kuninori Morimoto
2009-09-30 2:47 ` Paul Mundt
2009-11-26 8:37 ` Kuninori Morimoto
6 siblings, 0 replies; 8+ messages in thread
From: Kuninori Morimoto @ 2009-09-30 2:46 UTC (permalink / raw)
To: linux-sh
Dear Paul
> Do you have NUMA support enabled? It's possible the LMB changes impacted
> that.
It start works if I remove NUMA support from .config
--------------
NG case
--------------
> grep NUMA .config
CONFIG_SYS_SUPPORTS_NUMA=y
CONFIG_NUMA=y
--------------
OK case
--------------
> grep NUMA .config
CONFIG_SYS_SUPPORTS_NUMA=y
# CONFIG_NUMA is not set
Best regards
--
Kuninori Morimoto
^ permalink raw reply [flat|nested] 8+ messages in thread* Re: currect MigoR seems doesn't work
2009-09-29 5:59 currect MigoR seems doesn't work Kuninori Morimoto
` (4 preceding siblings ...)
2009-09-30 2:46 ` Kuninori Morimoto
@ 2009-09-30 2:47 ` Paul Mundt
2009-11-26 8:37 ` Kuninori Morimoto
6 siblings, 0 replies; 8+ messages in thread
From: Paul Mundt @ 2009-09-30 2:47 UTC (permalink / raw)
To: linux-sh
On Wed, Sep 30, 2009 at 11:46:07AM +0900, Kuninori Morimoto wrote:
> > Do you have NUMA support enabled? It's possible the LMB changes impacted
> > that.
>
> It start works if I remove NUMA support from .config
>
Thanks for testing, I'll look in to fixing it up.
^ permalink raw reply [flat|nested] 8+ messages in thread* Re: currect MigoR seems doesn't work
2009-09-29 5:59 currect MigoR seems doesn't work Kuninori Morimoto
` (5 preceding siblings ...)
2009-09-30 2:47 ` Paul Mundt
@ 2009-11-26 8:37 ` Kuninori Morimoto
6 siblings, 0 replies; 8+ messages in thread
From: Kuninori Morimoto @ 2009-11-26 8:37 UTC (permalink / raw)
To: linux-sh
Dear Paul
[Cc Magnus]
> start_kernel
> setup_arch
> setup_memory
> setup_bootmem_allocator
> for()
> reserve_bootmem (when i=2 I think)
> mark_bootmem
> BUG() <= dead here and reboot MigoR
(snip)
> > It start works if I remove NUMA support from .config
> >
> Thanks for testing, I'll look in to fixing it up.
Now, I got same phenomenon on EcoVec
which is mass production board.
46/50 board are working,
but 4/50 are can not work if It is romImage.
But it works If I use net boot.
My .config doesn't have NUMA support now.
Do you have any doubtful point ?
Best regards
--
Kuninori Morimoto
^ permalink raw reply [flat|nested] 8+ messages in thread