Booting mx31 on linux-next-20120517

Booting mx31 on linux-next-20120517

[Fabio Estevam]

Hi Sascha,

Are you able to boot any mx31 system on linux-next-20120517?

Just wanted to check with you first before start debugging this issue.

Regards,

Fabio Estevam

Booting mx31 on linux-next-20120517

[Fabio Estevam]

On Fri, May 18, 2012 at 12:48 AM, Fabio Estevam <festevam@gmail.com> wrote:
> Hi Sascha,
>
> Are you able to boot any mx31 system on linux-next-20120517?
>
> Just wanted to check with you first before start debugging this issue.

Adding earlyprintk shows me the following:

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
Booting Linux on physical CPU 0
Linux version 3.4.0-rc7-next-20120517 (fabio at fabio-Latitude-E6410)
(gcc version 4.4.4 (4.4.4_09.06.2010) ) #701 SMP Fri May 18 00:58:51
BRT 2012
CPU: ARMv6-compatible processor [4107b364] revision 4 (ARMv6TEJ), cr=00c5387d
CPU: PIPT / VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
Machine: Freescale MX31PDK (3DS)
bootconsole [earlycon0] enabled
cma: CMA: reserved 16 MiB at 86800000
Memory policy: ECC disabled, Data cache writeback
PERCPU: Embedded 7 pages/cpu @80759000 s5440 r8192 d15040 u32768
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 30464
Kernel command line: console=ttymxc0,115200 root=/dev/nfs ip=dhcp
nfsroot=192.168.1.105:/tftpboot/ltib earlyprintk
PID hash table entries: 512 (order: -1, 2048 bytes)
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 120MB = 120MB total
Memory: 98808k/98808k available, 32264k reserved, 0K highmem
Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
    vmalloc : 0x88800000 - 0xff000000   (1896 MB)
    lowmem  : 0x80000000 - 0x88000000   ( 128 MB)
    modules : 0x7f000000 - 0x80000000   (  16 MB)
      .text : 0x80008000 - 0x8055f000   (5468 kB)
      .init : 0x8055f000 - 0x805a7540   ( 290 kB)
      .data : 0x805a8000 - 0x805ff958   ( 351 kB)
       .bss : 0x805ff97c - 0x8065537c   ( 343 kB)
SLUB: Genslabs=11, HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Hierarchical RCU implementation.
NR_IRQS:436
MXC IRQ initialized
CPU identified as i.MX31, silicon rev 2.0
sched_clock: 32 bits at 66MHz, resolution 15ns, wraps every 64585ms
Console: colour dummy device 80x30
Calibrating delay loop... 531.66 BogoMIPS (lpj=2658304)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
CPU0: thread -1, cpu 0, socket -1, mpidr 4107b364
Setting up static identity map for 0x8042d550 - 0x8042d5c0
Brought up 1 CPUs
SMP: Total of 1 processors activated (531.66 BogoMIPS).
devtmpfs: initialized
initlevel:0=early, 4 registered initcalls
initlevel:1=core, 23 registered initcalls
pinctrl core: initialized pinctrl subsystem
dummy:
NET: Registered protocol family 16
initlevel:2=postcore, 14 registered initcalls
DMA: preallocated 256 KiB pool for atomic coherent allocations
initlevel:3=arch, 8 registered initcalls
L210 cache controller enabled
l2x0: 8 ways, CACHE_ID 0x41000040, AUX_CTRL 0x00030024, Cache size: 131072 B
gpiochip_add: registered GPIOs 0 to 31 on device: imx31-gpio.0
gpiochip_add: registered GPIOs 32 to 63 on device: imx31-gpio.1
gpiochip_add: registered GPIOs 64 to 95 on device: imx31-gpio.2
3-Stack Debug board detected, rev = 0x0200
initlevel:4=subsys, 36 registered initcalls
bio: create slab <bio-0> at 0
fixed-dummy:
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
Linux video capture interface: v2.00
initlevel:5=fs, 16 registered initcalls
Switching to clocksource mxc_timer1
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 4096 (order: 3, 32768 bytes)
TCP bind hash table entries: 4096 (order: 3, 32768 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
TCP: reno registered
UDP hash table entries: 128 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 128 (order: 0, 4096 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
initlevel:6=device, 248 registered initcalls
VFS: Disk quotas dquot_6.5.2
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
NFS: Registering the id_resolver key type
Key type id_resolver registered
fuse init (API version 7.19)
msgmni has been set to 224
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
mx3_sdc_fb mx3_sdc_fb: registered, using mode Epson-VGA
Console: switching to colour frame buffer device 60x40
imx-sdma imx31-sdma: initialized
Serial: IMX driver
brd: module loaded
loop: module loaded
smsc911x: Driver version 2008-10-21
smsc911x-mdio: probed
smsc911x smsc911x: eth0: attached PHY driver [Generic PHY]
(mii_bus:phy_addr=smsc911x-fffffff:01, irq=-1)
smsc911x smsc911x: eth0: MAC Address: 00:04:9f:00:94:e3
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
mousedev: PS/2 mouse device common for all mice
i2c /dev entries driver
lirc_dev: IR Remote Control driver registered, major 253
IR NEC protocol handler initialized
IR RC5(x) protocol handler initialized
IR RC6 protocol handler initialized
IR JVC protocol handler initialized
IR Sony protocol handler initialized
IR RC5 (streamzap) protocol handler initialized
IR SANYO protocol handler initialized
IR MCE Keyboard/mouse protocol handler initialized
IR LIRC bridge handler initialized
soc-camera-pdrv soc-camera-pdrv.0: Probing soc-camera-pdrv.0
soc-camera-pdrv soc-camera-pdrv.0: Failed to get supply 'cmos_vcore': -517
dmaengine_get: failed to get dma1chan0: (-22)
dmaengine_get: failed to get dma1chan1: (-22)
dmaengine_get: failed to get dma1chan2: (-22)
dmaengine_get: failed to get dma1chan3: (-22)
dmaengine_get: failed to get dma1chan4: (-22)
dmaengine_get: failed to get dma1chan5: (-22)
dmaengine_get: failed to get dma1chan6: (-22)
dmaengine_get: failed to get dma1chan7: (-22)
dmaengine_get: failed to get dma1chan8: (-22)
dmaengine_get: failed to get dma1chan9: (-22)
dmaengine_get: failed to get dma1chan10: (-22)
dmaengine_get: failed to get dma1chan11: (-22)
dmaengine_get: failed to get dma1chan12: (-22)
dmaengine_get: failed to get dma1chan13: (-22)
dmaengine_get: failed to get dma1chan14: (-22)
dmaengine_get: failed to get dma1chan15: (-22)
dmaengine_get: failed to get dma1chan16: (-22)
dmaengine_get: failed to get dma1chan17: (-22)
dmaengine_get: failed to get dma1chan18: (-22)
dmaengine_get: failed to get dma1chan19: (-22)
dmaengine_get: failed to get dma1chan20: (-22)
dmaengine_get: failed to get dma1chan21: (-22)
dmaengine_get: failed to get dma1chan22: (-22)
dmaengine_get: failed to get dma1chan23: (-22)
dmaengine_get: failed to get dma1chan24: (-22)
dmaengine_get: failed to get dma1chan25: (-22)
dmaengine_get: failed to get dma1chan26: (-22)
dmaengine_get: failed to get dma1chan27: (-22)
dmaengine_get: failed to get dma1chan28: (-22)
dmaengine_get: failed to get dma1chan29: (-22)
dmaengine_get: failed to get dma1chan30: (-22)
imx2-wdt imx2-wdt.0: IMX2+ Watchdog Timer enabled. timeout=60s (nowayout=0)
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pltfm: SDHCI platform and OF driver helper
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
TCP: cubic registered
NET: Registered protocol family 10
sit: IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
Key type dns_resolver registered
initlevel:7=late, 20 registered initcalls
VFP support v0.3: implementor 41 architecture 1 part 20 variant b rev 2
turn off boot console earlycon

How can we prevent the "turn off boot console earlycon" to happen?

Thanks,

Fabio Estevam

Booting mx31 on linux-next-20120517

[Uwe Kleine-König]

On Fri, May 18, 2012 at 01:07:07AM -0300, Fabio Estevam wrote:
> initlevel:7=late, 20 registered initcalls
> VFP support v0.3: implementor 41 architecture 1 part 20 variant b rev 2
> turn off boot console earlycon
> 
> How can we prevent the "turn off boot console earlycon" to happen?
pass

	keep_bootcon

as kernel parameter.

Best regards
Uwe

-- 
Pengutronix e.K.                           | Uwe Kleine-K?nig            |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

Booting mx31 on linux-next-20120517

[Dirk Behme]

On 18.05.2012 08:00, Uwe Kleine-K?nig wrote:
> On Fri, May 18, 2012 at 01:07:07AM -0300, Fabio Estevam wrote:
>> initlevel:7=late, 20 registered initcalls
>> VFP support v0.3: implementor 41 architecture 1 part 20 variant b rev 2
>> turn off boot console earlycon
>>
>> How can we prevent the "turn off boot console earlycon" to happen?
> pass
>
> 	keep_bootcon
>
> as kernel parameter.

And you might want to check if console=ttymxc0 is correct. At least 
some days back while I had a similar issue on i.MX6 it was just a 
wrong console given at the command line.

The boot log you sent has

Serial: IMX driver

but unfortunately doesn't tell us which UART port is used (if there 
are several at all like with i.MX6).

Best regards

Dirk

Booting mx31 on linux-next-20120517

[Sascha Hauer]

On Fri, May 18, 2012 at 01:07:07AM -0300, Fabio Estevam wrote:
> On Fri, May 18, 2012 at 12:48 AM, Fabio Estevam <festevam@gmail.com> wrote:
> > Hi Sascha,
> >
> > Are you able to boot any mx31 system on linux-next-20120517?
> >
> > Just wanted to check with you first before start debugging this issue.
> 
> Adding earlyprintk shows me the following:

Looks familiar. Check the pinctrl support. The i.MX UART driver (and
also the FEC driver) do a devm_pinctrl_get_select_default which does
not seem to be complete. Either the pinctrl dummy providers did not make
it to -next yet or they are simply not activated.


Sascha

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

Booting mx31 on linux-next-20120517

[Philippe Rétornaz]

Le vendredi 18 mai 2012 00:48:35 Fabio Estevam a ?crit :
> Hi Sascha,
> 
> Are you able to boot any mx31 system on linux-next-20120517?

I'm not able to boot it, it does hang/crash in the device initcall:
(...)
[    0.274656] initlevel:6=device, 135 registered initcalls
[    0.286256] msgmni has been set to 227
[    0.289522] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 
252)
[    0.289548] io scheduler noop registered
[    0.289570] io scheduler cfq registered (default)
[    0.413953] mx3_sdc_fb mx3_sdc_fb: registered, using mode Epson-VGA
[    0.544110] Console: switching to colour frame buffer device 60x40
[    0.555321] imx-sdma imx31-sdma: loaded firmware 1.0
[    0.588970] imx-sdma imx31-sdma: initialized
[    0.590912] Serial: IMX driver
[    0.591139] imx21-uart.0: ttymxc0 at MMIO 0x43f90000 (irq = 45) is a IMX
[    1.260201] console [ttymxc0] enabled
[    1.278640] spi_imx imx31-cspi.1: master is unqueued, this is deprecated

But I don't need to enable earlyprintk to get serial output.
BTW, this is not limited to mx31pdk_3ds, but it also do it on mx31moboard.

It looks like it's related to the mc13783 PMIC, because the board *poweroff* 
itself. 

Maybe it's a bug in the regmap work of the mc13783 ?

Regards,

Philippe

Booting mx31 on linux-next-20120517

[Fabio Estevam]

Hi Sascha,

On Fri, May 18, 2012 at 5:59 AM, Sascha Hauer <s.hauer@pengutronix.de> wrote:

> Looks familiar. Check the pinctrl support. The i.MX UART driver (and
> also the FEC driver) do a devm_pinctrl_get_select_default which does
> not seem to be complete. Either the pinctrl dummy providers did not make
> it to -next yet or they are simply not activated.

You are right. After applying this patch:
http://marc.info/?l=linux-arm-kernel&m=133753393231876&w=2

, I am able to see the console messages without having to add 'earlyprintk'.

Now my boot hangs in another point:

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
Booting Linux on physical CPU 0
Linux version 3.4.0-next-20120521+ (fabio at fabio-Latitude-E6410) (gcc
version 4.4.4 (4.4.4_09.06.2010) ) #713 SMP Mon May 21 10:03:41 BRT
2012
CPU: ARMv6-compatible processor [4107b364] revision 4 (ARMv6TEJ), cr=00c5387d
CPU: PIPT / VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
Machine: Freescale MX31PDK (3DS)
cma: CMA: reserved 16 MiB at 86800000
Memory policy: ECC disabled, Data cache writeback
PERCPU: Embedded 7 pages/cpu @80737000 s5440 r8192 d15040 u32768
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 30464
Kernel command line: console=ttymxc0,115200 root=/dev/nfs ip=dhcp
nfsroot=10.29.240.143:/tftpboot/ltib root=/dev/nfs ip=dhcp
nfsroot=10.29.240.143:/tftpboot/b
PID hash table entries: 512 (order: -1, 2048 bytes)
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 120MB = 120MB total
Memory: 98944k/98944k available, 32128k reserved, 0K highmem
Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
    vmalloc : 0x88800000 - 0xff000000   (1896 MB)
    lowmem  : 0x80000000 - 0x88000000   ( 128 MB)
    modules : 0x7f000000 - 0x80000000   (  16 MB)
      .text : 0x80008000 - 0x80543000   (5356 kB)
      .init : 0x80543000 - 0x8058a540   ( 286 kB)
      .data : 0x8058c000 - 0x805de4e0   ( 330 kB)
       .bss : 0x805de504 - 0x80633f3c   ( 343 kB)
SLUB: Genslabs=11, HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Hierarchical RCU implementation.
NR_IRQS:436
MXC IRQ initialized
CPU identified as i.MX31, silicon rev 2.0
sched_clock: 32 bits at 66MHz, resolution 15ns, wraps every 64585ms
Console: colour dummy device 80x30
Calibrating delay loop... 531.66 BogoMIPS (lpj=2658304)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
CPU0: thread -1, cpu 0, socket -1, mpidr 4107b364
Setting up static identity map for 0x8041dab0 - 0x8041db20
Brought up 1 CPUs
SMP: Total of 1 processors activated (531.66 BogoMIPS).
devtmpfs: initialized
initlevel:0=early, 4 registered initcalls
initlevel:1=core, 23 registered initcalls
pinctrl core: initialized pinctrl subsystem
dummy:
NET: Registered protocol family 16
initlevel:2=postcore, 14 registered initcalls
DMA: preallocated 256 KiB pool for atomic coherent allocations
initlevel:3=arch, 8 registered initcalls
L210 cache controller enabled
l2x0: 8 ways, CACHE_ID 0x41000040, AUX_CTRL 0x00030024, Cache size: 131072 B
3-Stack Debug board detected, rev = 0x0200
initlevel:4=subsys, 36 registered initcalls
bio: create slab <bio-0> at 0
fixed-dummy:
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
Linux video capture interface: v2.00
initlevel:5=fs, 15 registered initcalls
Switching to clocksource mxc_timer1
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 4096 (order: 3, 32768 bytes)
TCP bind hash table entries: 4096 (order: 3, 32768 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
TCP: reno registered
UDP hash table entries: 128 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 128 (order: 0, 4096 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
initlevel:6=device, 250 registered initcalls
VFS: Disk quotas dquot_6.5.2
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
NFS: Registering the id_resolver key type
Key type id_resolver registered
fuse init (API version 7.19)
msgmni has been set to 225
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
mx3_sdc_fb mx3_sdc_fb: registered, using mode Epson-VGA
Console: switching to colour frame buffer device 60x40
imx-sdma imx31-sdma: initialized
Serial: IMX driver
imx21-uart.0: ttymxc0 at MMIO 0x43f90000 (irq = 45) is a IMX
console [ttymxc0] enabled
brd: module loaded
loop: module loaded
spi_imx imx31-cspi.1: master is unqueued, this is deprecated

,if I remove the spi driver then the boots complete.

I am debugging this now, but any suggestions are welcome.

Thanks,

Fabio Estevam

Booting mx31 on linux-next-20120517

[Philippe Rétornaz]

Le lundi 21 mai 2012 10:20:09 Fabio Estevam a ?crit :
> Hi Sascha,
> 
> On Fri, May 18, 2012 at 5:59 AM, Sascha Hauer <s.hauer@pengutronix.de> 
wrote:
> 
> ,if I remove the spi driver then the boots complete.
> 
> I am debugging this now, but any suggestions are welcome.

Try to disable the MC13783 Pmic. On mx31moboard I have the same hang and I can 
clearly see that the board switchoff itself. 
It looks like somebody is writing in the wrong register (regmap code?).

Regards,

Philippe

Booting mx31 on linux-next-20120517

[Fabio Estevam]

On Mon, May 21, 2012 at 10:33 AM, Philippe R?tornaz
<philippe.retornaz@epfl.ch> wrote:

> Try to disable the MC13783 Pmic. On mx31moboard I have the same hang and I can
> clearly see that the board switchoff itself.
> It looks like somebody is writing in the wrong register (regmap code?).

You are right. If I disable the mc13783 driver then the boots proceed.

I will take a look at the mc13783 driver. If you also spot anything
wrong there, please let us know.

Thanks,

Fabio Estevam

Booting mx31 on linux-next-20120517

[Shawn Guo]

On Mon, May 21, 2012 at 10:35:42AM -0300, Fabio Estevam wrote:
> On Mon, May 21, 2012 at 10:33 AM, Philippe R?tornaz
> <philippe.retornaz@epfl.ch> wrote:
> 
> > Try to disable the MC13783 Pmic. On mx31moboard I have the same hang and I can
> > clearly see that the board switchoff itself.
> > It looks like somebody is writing in the wrong register (regmap code?).
> 
> You are right. If I disable the mc13783 driver then the boots proceed.
> 
> I will take a look at the mc13783 driver. If you also spot anything
> wrong there, please let us know.
> 
My imx51 babbage stops booting for the same cause.  And I tracked it
down a little bit and it goes to regmap patch below. 

commit 91b5e741184ea9836cd7d7509e4f9b6eefa27df2
Author: Marc Reilly <marc@cpdesign.com.au>
Date:   Sun Apr 1 16:41:37 2012 +1000

    mfd: Use regmap for the mc13xxx-core register access

    This change converts the mc13xxx core to use regmap rather than direct
    spi r/w.
    The spidev member of mc13xxx struct becomes redundant and is removed.
    Extra debugging aids are added to mc13xxx_reg_rmw.
    Mutex init is moved to before regmap init.

Marc,

Have you tested the patch with spi access?  It seems not to me.

-- 
Regards,
Shawn

Booting mx31 on linux-next-20120517

[Fabio Estevam]

Shawn,

On Wed, May 23, 2012 at 12:49 PM, Shawn Guo <shawn.guo@linaro.org> wrote:

> My imx51 babbage stops booting for the same cause. ?And I tracked it
> down a little bit and it goes to regmap patch below.
>
> commit 91b5e741184ea9836cd7d7509e4f9b6eefa27df2
> Author: Marc Reilly <marc@cpdesign.com.au>
> Date: ? Sun Apr 1 16:41:37 2012 +1000
>
> ? ?mfd: Use regmap for the mc13xxx-core register access
>
> ? ?This change converts the mc13xxx core to use regmap rather than direct
> ? ?spi r/w.
> ? ?The spidev member of mc13xxx struct becomes redundant and is removed.
> ? ?Extra debugging aids are added to mc13xxx_reg_rmw.
> ? ?Mutex init is moved to before regmap init.
>
> Marc,
>
> Have you tested the patch with spi access? ?It seems not to me.

The original issue from this thread was solved by this patch:
http://www.spinics.net/lists/arm-kernel/msg176093.html

For the mc13xxx hang, I started another thread:
http://marc.info/?l=linux-kernel&m=133778717002997&w=2

Please check the details there and any help is appreciatted.

Marc told us that he has no hardware to test mc13xxx via SPI.

Regards,

Fabio Estevam