Skip to contentSkip to conversation

fails to boot since commit 6430a5987f8bb9a7c5187b343956aa8ef404d571

sh7785lcr proto Raúl Porcel 3 participants 4 messages Jun 13, 2010 – Jun 22, 2010 SuperH

lore
Share & tools
lore

Raúl Porcel

author
#0 lore raw

Hello list,

I tried some weeks to upgrade the sh7785lcr prototype board using 32bits to the latest released kernel(2.6.34.something). I've also tried with latest git.

However it fails to boot:

<snip>
U-Boot 1.3.3-00319-gcd0b0dc-dirty (Sep 9 2008 - 17:12:09)

CPU: SH4A
BOARD: Renesas Technology Corp. R0P7785LC0011RL
DRAM:  128MB
FLASH: 64MB
PCI: SH7780 PCI host bridge found.
PCI:   Bus Dev VenId DevId Class Int
        00  00  10ec  8169  0200  00
        00  01  1095  3512  0180  00
In:    serial
Out:   serial
Err:   serial
Net:   RTL8169#0

=> run boot32
## Starting application at 0xA3F80000 ...

U-Boot 2009.06-rc2-05736-gf40f6db-dirty (May 26 2009 - 14:43:40)

CPU: SH4
BOARD: Renesas Technology Corp. R0P7785LC0011RL
DRAM:  384MB
FLASH: 64MB
PCI: SH7780 PCI host bridge found.
PCI:   Bus Dev VenId DevId Class Int
        00  00  10ec  8169  0200  00
        00  01  1095  3512  0180  00
In:    serial
Out:   serial
Err:   serial
Net:   RTL8169#0
Hit any key to stop autoboot:  0

Using RTL8169#0 device
TFTP from server 192.168.0.3; our IP address is 192.168.0.12 Filename 'uImage.32bit'.
Load address: 0x89000000
Loading: #################################################################

         #################################################################
         ########################################################
done
Bytes transferred = 2726217 (299949 hex)
## Booting kernel from Legacy Image at 89000000 ...
   Image Name:   Linux-2.6.35-rc2-00750-g9973e38
   Image Type:   SuperH Linux Kernel Image (gzip compressed)
   Data Size:    2726153 Bytes =  2.6 MB

Load Address: 88001000
Entry Point: 88002000
Verifying Checksum ... OK
? Uncompressing Kernel Image ... OK

<It reboots here>

U-Boot 1.3.3-00319-gcd0b0dc-dirty (Sep 9 2008 - 17:12:09)

CPU: SH4A
BOARD: Renesas Technology Corp. R0P7785LC0011RL
</snip>

I've bisected it and found this commit the culprit:
http://git.kernel.org/?p=linux/kernel/git/lethal/sh-2.6.git;a=commit;hd30a5987f8bb9a7c5187b343956aa8ef404d571

Using a commit before this one, it boots, and applying this patch to that commit, fails.

Reverting this commit on current git, still doesn't boot.

Needless to say, 29bit mode still works...

Talking with mfleming on #linux-sh(he did the commit, he suggested me the following:
<snip>
<mfleming> when the board resets can you read the value of address 0xff00000c from uboot and see if it contains 0x80000000 ? <armin76> mfleming:
http://dev.gentoo.org/~armin76/sh/sh7785lcr.32bitproto.config
<mfleming> (that's the TLB exception register)
<armin76> notice that the only change between defconfig and this one is the proto thing and the mem address and size
<armin76> mfleming: ok, let me check...
<armin76> when it resets you mean when i use the latest git kernel and starts over, right? :)
<mfleming> yes, or when you use the kernel that head my commit as HEAD. do they both reset?
<mfleming> s/head/has/
<armin76> yes
<armin76> both do the same
<mfleming> either one is fine then
<mfleming> but if you use mine it'll be easier to debug <mfleming> my commit, i mean
<armin76> sure, lets see...
<armin76> mfleming: md 0xff00000c
<armin76> ff00000c: 80000000 2c000000 00000000 00000000 .......,........
<mfleming> wait, are you still at the uboot prompt? <mfleming> what's in 0xff000020 ?
<armin76> yes
<armin76> md 0xff000020
<armin76> ff000020: 00000000 00000140 00000000 00000000 ....@...........
<mfleming> aha!
<mfleming> multipl TLB hit exception
<mfleming> err, multiple
</snip>

My kconfig is at
http://dev.gentoo.org/~armin76/sh/sh7785lcr.32bitproto.config

Thanks

author
#1 lore raw
Quoted 6 lines · Raúl Porcel

Hello list,

I tried some weeks to upgrade the sh7785lcr prototype board using 32bits to the latest released kernel(2.6.34.something). I've also tried with latest git.

<snip>

By Matt Fleming's request i've tested latest git again, and turns out that if i run the 'pmb' command on the 32bit uboot, the kernel boots.

So i believe this is 'fixed'.

#2 lore raw
In reply to Raúl Porcel

Hi,

2010/6/18 Raúl Porcel <[email protected]>:

Quoted 7 lines · Raúl Porcel
Quoted 6 lines

Hello list,

I tried some weeks to upgrade the sh7785lcr prototype board using 32bits to the latest released kernel(2.6.34.something). I've also tried with latest git.

Quoted 6 lines

<snip>

By Matt Fleming's request i've tested latest git again, and turns out that if i run the 'pmb' command on the 32bit uboot, the kernel boots.

So i believe this is 'fixed'.

Yes, This is correct.
If you want to boot 32bit kernel, you need run pmb command.

Best regards,
Nobuhiro

Signature · 3 lines
Nobuhiro Iwamatsu
   iwamatsu at {nigauri.org / debian.org}
   GPG ID: 40AD1FA6
#3 lore raw
In reply to Raúl Porcel
Quoted 10 lines · Nobuhiro Iwamatsu

2010/6/18 Ra?l Porcel <[email protected]>:

Quoted 9 lines · Ra?l Porcel
Quoted 6 lines

Hello list,

I tried some weeks to upgrade the sh7785lcr prototype board using 32bits to the latest released kernel(2.6.34.something). I've also tried with latest git.

<snip>

Quoted 8 lines
Quoted 4 lines

By Matt Fleming's request i've tested latest git again, and turns out that if i run the 'pmb' command on the 32bit uboot, the kernel boots.

So i believe this is 'fixed'.

Yes, This is correct.
If you want to boot 32bit kernel, you need run pmb command.

This has always been the case though, so I'm confused as to what you think changed between the older and current kernels?