Problem booting P2020DS with SDK 1.4 images.

martindubé — Mon, 04 Nov 2013 17:34:20 GMT

Hi,

I'm using the QorIQ sdk 1.4 and successfully created the 'fsl-image-minimal' files. However, when I try to use them on a P2020DS, I get what looks like a hang when the kernel is booting. I've also tried nfs file system and I get the exact same problem. I tried SDK 1.3 and it also hang after "RPC: Registered tcp NFSv4.1 backchannel transport module", but I don't get the rcu_sched info messages however.

Here is the boot log:

=> setenv bootargs root=/dev/ram rw console=$consoledev,$baudrate

=> tftp $ramdiskaddr $ramdiskfile;tftp $loadaddr $bootfile;tftp $fdtaddr $fdtfile;bootm $loadaddr $ramdiskaddr $fdtaddr

Speed: 1000, full duplex

Using eTSEC1 device

TFTP from server 192.168.0.94; our IP address is 192.168.0.241

Filename 'fsl-image-minimal-p2020ds.ext2.gz.u-boot'.

Load address: 0x2000000

Loading: #################################################################

#################################################################

#########################################

done

Bytes transferred = 3458233 (34c4b9 hex)

Speed: 1000, full duplex

Using eTSEC1 device

TFTP from server 192.168.0.94; our IP address is 192.168.0.241

Filename 'uImage-p2020ds.bin'.

Load address: 0x4000000

Loading: #################################################################

#################################################################

############

done

Bytes transferred = 3986006 (3cd256 hex)

Speed: 1000, full duplex

Using eTSEC1 device

TFTP from server 192.168.0.94; our IP address is 192.168.0.241

Filename 'uImage-p2020ds.dtb'.

Load address: 0xc00000

Loading: ##

done

Bytes transferred = 26234 (667a hex)

WARNING: adjusting available memory to 30000000

## Booting kernel from Legacy Image at 04000000 ...

Image Name: Linux-3.8.13-rt9-QorIQ-SDK-V1.4

Image Type: PowerPC Linux Kernel Image (gzip compressed)

Data Size: 3985942 Bytes = 3.8 MiB

Load Address: 00000000

Entry Point: 00000000

Verifying Checksum ... OK

## Loading init Ramdisk from Legacy Image at 02000000 ...

Image Name: fsl-image-minimal-p2020ds-201311

Image Type: PowerPC Linux RAMDisk Image (gzip compressed)

Data Size: 3458169 Bytes = 3.3 MiB

Load Address: 00000000

Entry Point: 00000000

Verifying Checksum ... OK

## Flattened Device Tree blob at 00c00000

Booting using the fdt blob at 0xc00000

Uncompressing Kernel Image ... OK

Loading Ramdisk to 2fcb3000, end 2ffff479 ... OK

Loading Device Tree to 00ff6000, end 00fff679 ... OK

Using P2020 DS machine description

Memory CAM mapping: 256/256/256 Mb, residual: 1280Mb

Linux version 3.8.13-rt9-QorIQ-SDK-V1.4 (freescale@freescale-sdk) (gcc version 4.7.2 (GCC) ) #1 SMP Thu Oct 31 21:43:28 CST 2013

Found initrd at 0xefcb3000:0xeffff479

CPU maps initialized for 1 thread per core

bootconsole [udbg0] enabled

setup_arch: bootmem

mpc85xx_ds_setup_arch()

MPC85xx DS board from Freescale Semiconductor

arch: exit

Zone ranges:

DMA [mem 0x00000000-0x2fffffff]

Normal empty

HighMem [mem 0x30000000-0x7fffffff]

Movable zone start for each node

Early memory node ranges

node 0: [mem 0x00000000-0x7fffffff]

MMU: Allocated 1088 bytes of context maps for 255 contexts

PERCPU: Embedded 7 pages/cpu @c2006000 s6432 r8192 d14048 u32768

Built 1 zonelists in Zone order, mobility grouping on. Total pages: 520192

Kernel command line: root=/dev/ram rw console=ttyS0,115200

PID hash table entries: 4096 (order: 2, 16384 bytes)

Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)

Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)

Memory: 2001052k/2097152k available (7724k kernel code, 96100k reserved, 300k data, 1325k bss, 268k init)

Kernel virtual memory layout:

* 0xfff5f000..0xfffff000 : fixmap

* 0xffc00000..0xffe00000 : highmem PTEs

* 0xffbfd000..0xffc00000 : early ioremap

* 0xf1000000..0xffbfd000 : vmalloc & ioremap

SLUB: Genslabs=15, HWalign=32, Order=0-3, MinObjects=0, CPUs=2, Nodes=1

Hierarchical RCU implementation.

RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=2.

NR_IRQS:512 nr_irqs:512 16

mpic: Setting up MPIC " OpenPIC " version 1.2 at ffe40000, max 2 CPUs

mpic: ISU size: 256, shift: 8, mask: ff

mpic: Initializing for 256 sources

i8259 legacy interrupt controller initialized

clocksource: timebase mult[d555e12] shift[24] registered

Console: colour dummy device 80x25

pid_max: default: 32768 minimum: 301

Mount-cache hash table entries: 512

mpic: requesting IPIs...

Brought up 2 CPUs

devtmpfs: initialized

NET: Registered protocol family 16

Found FSL PCI host bridge at 0x00000000ffe08000. Firmware bus number: 0->0

PCI host bridge /pcie@ffe08000 ranges:

MEM 0x0000000080000000..0x000000009fffffff -> 0x0000000080000000

IO 0x00000000ffc00000..0x00000000ffc0ffff -> 0x0000000000000000

/pcie@ffe08000: PCICSRBAR @ 0xfff00000

Found FSL PCI host bridge at 0x00000000ffe09000. Firmware bus number: 0->2

PCI host bridge /pcie@ffe09000 (primary) ranges:

MEM 0x00000000a0000000..0x00000000bfffffff -> 0x00000000a0000000

IO 0x00000000ffc10000..0x00000000ffc1ffff -> 0x0000000000000000

/pcie@ffe09000: PCICSRBAR @ 0xfff00000

Found FSL PCI host bridge at 0x00000000ffe0a000. Firmware bus number: 0->0

PCI host bridge /pcie@ffe0a000 ranges:

MEM 0x00000000c0000000..0x00000000dfffffff -> 0x00000000c0000000

IO 0x00000000ffc20000..0x00000000ffc2ffff -> 0x0000000000000000

/pcie@ffe0a000: PCICSRBAR @ 0xfff00000

PCI: Probing PCI hardware

fsl-pci ffe08000.pcie: PCI host bridge to bus 0000:00

pci_bus 0000:00: root bus resource [io 0xfffe0000-0xfffeffff] (bus address [0x0000-0xffff])

pci_bus 0000:00: root bus resource [mem 0x80000000-0x9fffffff]

pci_bus 0000:00: root bus resource [bus 00-ff]

pci 0000:00:00.0: ignoring class 0x0b2000 (doesn't match header type 01)

pci 0000:00:00.0: bridge configuration invalid ([bus 00-00]), reconfiguring

pci 0000:00:00.0: PCI bridge to [bus 01-ff]

fsl-pci ffe09000.pcie: PCI host bridge to bus 0001:02

pci_bus 0001:02: root bus resource [io 0x0000-0xffff]

pci_bus 0001:02: root bus resource [mem 0xa0000000-0xbfffffff]

pci_bus 0001:02: root bus resource [bus 02-ff]

pci 0001:02:00.0: ignoring class 0x0b2000 (doesn't match header type 01)

pci 0001:02:00.0: Primary bus is hard wired to 0

pci 0001:02:00.0: bridge configuration invalid ([bus 01-02]), reconfiguring

pci 0001:02:00.0: PCI bridge to [bus 03-ff]

pci 0001:03:00.0: bridge configuration invalid ([bus 02-02]), reconfiguring

pci 0001:04:1d.0: unsupported PM cap regs version (4)

pci 0001:03:00.0: PCI bridge to [bus 04-ff] (subtractive decode)

fsl-pci ffe0a000.pcie: PCI host bridge to bus 0002:05

pci_bus 0002:05: root bus resource [io 0x20000-0x2ffff] (bus address [0x0000-0xffff])

pci_bus 0002:05: root bus resource [mem 0xc0000000-0xdfffffff]

pci_bus 0002:05: root bus resource [bus 05-ff]

pci 0002:05:00.0: ignoring class 0x0b2000 (doesn't match header type 01)

pci 0002:05:00.0: bridge configuration invalid ([bus 00-00]), reconfiguring

pci 0002:05:00.0: PCI bridge to [bus 06-ff]

pci 0000:00:00.0: PCI bridge to [bus 01]

pci 0000:00:00.0: bridge window [io 0xfffe0000-0xfffeffff]

pci 0000:00:00.0: bridge window [mem 0x80000000-0x9fffffff]

pci 0001:03:00.0: PCI bridge to [bus 04]

pci 0001:03:00.0: bridge window [io 0x1000-0x1fff]

pci 0001:03:00.0: bridge window [mem 0xa0000000-0xa00fffff]

pci 0001:02:00.0: PCI bridge to [bus 03-04]

pci 0001:02:00.0: bridge window [io 0x0000-0xffff]

pci 0001:02:00.0: bridge window [mem 0xa0000000-0xbfffffff]

pci 0002:05:00.0: PCI bridge to [bus 06]

pci 0002:05:00.0: bridge window [io 0x20000-0x2ffff]

pci 0002:05:00.0: bridge window [mem 0xc0000000-0xdfffffff]

pci 0000:00:00.0: enabling device (0106 -> 0107)

pci 0001:02:00.0: enabling device (0106 -> 0107)

pci 0002:05:00.0: enabling device (0106 -> 0107)

fsl-l2ctlr ffe20000.l2-cache-controller: Entire L2 as cache, provide valid sram address and size

fsl-l2ctlr: probe of ffe20000.l2-cache-controller failed with error -22

bio: create slab <bio-0> at 0

Freescale Elo / Elo Plus DMA driver

fsl-elo-dma ffe0c300.dma: #0 (fsl,eloplus-dma-channel), irq 76

fsl-elo-dma ffe0c300.dma: #1 (fsl,eloplus-dma-channel), irq 77

fsl-elo-dma ffe0c300.dma: #2 (fsl,eloplus-dma-channel), irq 78

fsl-elo-dma ffe0c300.dma: #3 (fsl,eloplus-dma-channel), irq 79

fsl-elo-dma ffe21300.dma: #0 (fsl,eloplus-dma-channel), irq 21

fsl-elo-dma ffe21300.dma: #1 (fsl,eloplus-dma-channel), irq 22

fsl-elo-dma ffe21300.dma: #2 (fsl,eloplus-dma-channel), irq 23

fsl-elo-dma ffe21300.dma: #3 (fsl,eloplus-dma-channel), irq 24

vgaarb: loaded

SCSI subsystem initialized

usbcore: registered new interface driver usbfs

usbcore: registered new interface driver hub

usbcore: registered new device driver usb

pps_core: LinuxPPS API ver. 1 registered

PTP clock support registered

Advanced Linux Sound Architecture Driver Initialized.

Switching to clocksource timebase

NET: Registered protocol family 2

TCP established hash table entries: 8192 (order: 4, 65536 bytes)

TCP bind hash table entries: 8192 (order: 4, 65536 bytes)

TCP: Hash tables configured (established 8192 bind 8192)

TCP: reno registered

UDP hash table entries: 512 (order: 2, 16384 bytes)

UDP-Lite hash table entries: 512 (order: 2, 16384 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.

INFO: rcu_sched detected stalls on CPUs/tasks: { 1} (detected by 0, t=5253 jiffies, g=4294967018, c=4294967017, q=96)

Task dump for CPU 1:

swapper/0 R running 0 1 0 0x00000804

Call Trace:

[ef049c00] [c200f328] 0xc200f328 (unreliable)

INFO: rcu_sched detected stalls on CPUs/tasks: { 1} (detected by 0, t=21008 jiffies, g=4294967018, c=4294967017, q=96)

Task dump for CPU 1:

swapper/0 R running 0 1 0 0x00000804

Call Trace:

[ef049c00] [c200f328] 0xc200f328 (unreliable)

INFO: rcu_sched detected stalls on CPUs/tasks: { 1} (detected by 0, t=36763 jiffies, g=4294967018, c=4294967017, q=96)

Task dump for CPU 1:

swapper/0 R running 0 1 0 0x00000804

Call Trace:

[ef049c00] [c200f328] 0xc200f328 (unreliable)

Any advice/tip for me to look at?

Thank you,

Martin

Re: Problem booting P2020DS with SDK 1.4 images.

yipingwang — Tue, 05 Nov 2013 07:00:08 GMT

P2020DS was removed since QorIQ SDK 1.2 release, the latest official SDK release for P2020DS is SDK 1.0.3 which could be downloaded from Freescale Linux SDK for QorIQ Processors, v1.0 and related releases.

Re: Problem booting P2020DS with SDK 1.4 images.

martindubé — Tue, 05 Nov 2013 14:05:10 GMT

Hi,

Thank you for you prompt answer. So even if 'fsl-setup-poky' lists the p2020ds as a supported ppc machine, I must not assume that it is supported by the SDK?

I will give a try to the 1.0.3 SDK and the 1.2 SDK because I'd like to have to most recent (working) one.

Regards,

Martin

Re: Problem booting P2020DS with SDK 1.4 images.

martindubé — Wed, 06 Nov 2013 14:53:06 GMT

Thanks. I'm somewhat new to this and I didn't realize that P2020DS, P2020RDB and P2020 where 3 different things, so when I read "QorIQ Communications Processors Mid-Performance Tier: P2020, P2041/0, P3041" in SDK 1.4 release notes, I assumed that P2020DS was supported because P2020 is listed as supported.

I got it working with 1.0.3. Thank you again.

topic Problem booting P2020DS with SDK 1.4 images. in P-Series

Problem booting P2020DS with SDK 1.4 images.

Re: Problem booting P2020DS with SDK 1.4 images.

Re: Problem booting P2020DS with SDK 1.4 images.

Re: Problem booting P2020DS with SDK 1.4 images.

Re: Problem booting P2020DS with SDK 1.4 images.