Could You Help Me To Check The Log

tony_l_cai — Wed, 22 Jul 2015 11:45:24 GMT

Hi, all

Our customized board is porting the Android 5.0, and now is in Kernel,but it stopped here. and I maybe need some help, 3Q~

----------------imx6q_init_machine------------------

Use WDOG1 as reset source

syscon 20c8000.anatop: regmap [mem 0x020c8000-0x020c8fff] registered

vdd1p1: 800 <--> 1375 mV at 1100 mV

vdd3p0: 2625 <--> 3400 mV at 3000 mV

vdd2p5: 2000 <--> 2750 mV at 2400 mV

cpu: 725 <--> 1450 mV at 1150 mV

vddpu: 725 <--> 1450 mV

vddsoc: 725 <--> 1450 mV at 1175 mV

syscon 20e0000.iomuxc-gpr: regmap [mem 0x020e0000-0x020e0037] registered

syscon 21bc000.ocotp-ctrl: regmap [mem 0x021bc000-0x021bffff] registered

-------------------imx6q_init_machine---end---------

hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.

hw-breakpoint: maximum watchpoint size is 4 bytes.

imx6q-pinctrl 20e0000.iomuxc: initialized IMX pinctrl driver

bio: create slab <bio-0> at 0

mxs-dma 110000.dma-apbh: initialized

usb_otg_vbus: 5000 mV

usb_h1_vbus: 5000 mV

wm8962-supply: no parameters

mipi_dsi_pwr_on: no parameters

sensor-supply: 3300 mV

i2c-core: driver [max17135] using legacy suspend method

i2c-core: driver [max17135] using legacy resume method

SCSI subsystem initialized

usbcore: registered new interface driver usbfs

usbcore: registered new interface driver hub

usbcore: registered new device driver usb

i2c i2c-0: IMX I2C adapter registered

i2c i2c-1: IMX I2C adapter registered

i2c i2c-2: IMX I2C adapter registered

Linux video capture interface: v2.00

pps_core: LinuxPPS API ver. 1 registered

PTP clock support registered

imx-ipuv3 2400000.ipu: IPU DMFC NORMAL mode: 1(0~1), 5B(4,5), 5F(6,7)

imx-ipuv3 2800000.ipu: IPU DMFC NORMAL mode: 1(0~1), 5B(4,5), 5F(6,7)

mxc_mipi_csi2 21dc000.mipi_csi: i.MX MIPI CSI2 driver probed

mxc_mipi_csi2 21dc000.mipi_csi: i.MX MIPI CSI2 dphy version is 0x3130302a

MIPI CSI2 driver module loaded

Advanced Linux Sound Architecture Driver Initialized.

Bluetooth: Core ver 2.16

NET: Registered protocol family 31

Bluetooth: HCI device and connection manager initialized

Bluetooth: HCI socket layer initialized

Bluetooth: L2CAP socket layer initialized

Bluetooth: SCO socket layer initialized

pureg-dummy: no parameters

Switching to clocksource mxc_timer1

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.

Trying to unpack rootfs image as initramfs...

Freeing initrd memory: 8K (85000000 - 85002000)

hw perfevents: enabled with ARMv7 Cortex-A9 PMU driver, 7 counters available

imx6_busfreq busfreq.16: busfreq_probe: failed to get axi_alt_sel_clk

imx6_busfreq: probe of busfreq.16 failed with error -2

Bus freq driver module loaded

bt power gpio is:2

mxc_bt_rfkill driver success loaded

rfkill: BT RF going to : on

mxc_bt_rfkill_reset

mxc_ir consumer_ir.41: unable to request PWM.

platform consumer_ir.41: Driver mxc_ir requests probe deferral

console [pstore-1] enabled

ramoops: attached 0x100000@0x4bf00000, ecc: 0/0

mxc_ramoops device success loaded

futex hash table entries: 512 (order: 3, 32768 bytes)

audit: initializing netlink socket (disabled)

type=2000 audit(0.360:1): initialized

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

Key type id_legacy registered

NTFS driver 2.1.30 [Flags: R/W DEBUG].

fuse init (API version 7.22)

msgmni has been set to 1994

io scheduler noop registered

io scheduler deadline registered

io scheduler cfq registered (default)

imx-weim 21b8000.weim: WEIM driver registered.

mxc_mipi_dsi 21e0000.mipi: i.MX MIPI DSI driver probed

MIPI DSI driver module loaded

imx6q-pinctrl 20e0000.iomuxc: pin MX6Q_PAD_DISP0_DAT9 already requested by 20840 00.pwm; cannot claim for lcd.34

imx6q-pinctrl 20e0000.iomuxc: pin-101 (lcd.34) status -22

imx6q-pinctrl 20e0000.iomuxc: could not request pin 101 on device 20e0000.iomuxc

mxc_lcdif lcd.34: Error applying setting, reverse things back

imx6q-pinctrl 20e0000.iomuxc: pin MX6Q_PAD_DISP0_DAT9 already requested by 20840 00.pwm; cannot claim for lcd.34

imx6q-pinctrl 20e0000.iomuxc: pin-101 (lcd.34) status -22

imx6q-pinctrl 20e0000.iomuxc: could not request pin 101 on device 20e0000.iomuxc

mxc_lcdif lcd.34: Error applying setting, reverse things back

mxc_lcdif lcd.34: can't get/select pinctrl

mxc_lcdif: probe of lcd.34 failed with error -22

mxc_sdc_fb fb.30: registered mxc display driver ldb

imx-ipuv3 2800000.ipu: IPU DMFC DP HIGH RESOLUTION: 1(0,1), 5B(2~5), 5F(6,7)

imx-ipuv3 2800000.ipu: Unsupported burst size 1

mxc_sdc_fb fb.30: timeout when waiting for flip irq

Console: switching to colour frame buffer device 128x48

mxc_sdc_fb fb.30: timeout when waiting for flip irq

mxc_sdc_fb fb.31: Can't get fb option for mxcfb1!

mxc_sdc_fb fb.32: Can't get fb option for mxcfb2!

mxc_sdc_fb fb.33: Can't get fb option for mxcfb3!

imx-sdma 20ec000.sdma: no iram assigned, using external mem

imx-sdma 20ec000.sdma: loaded firmware 1.1

imx-sdma 20ec000.sdma: initialized

pfuze100-regulator 1-0008: unrecognized pfuze chip ID!

pfuze100-regulator: probe of 1-0008 failed with error -5

Serial: IMX driver

2020000.serial: ttymxc0 at MMIO 0x2020000 (irq = 58) is a IMX

console [ttymxc0] enabled

21ec000.serial: ttymxc2 at MMIO 0x21ec000 (irq = 60) is a IMX

21f4000.serial: ttymxc4 at MMIO 0x21f4000 (irq = 62) is a IMX

serial: Freescale lpuart driver

imx sema4 driver is registered.

[drm] Initialized drm 1.1.0 20060810

[drm] Initialized vivante 1.0.0 20120216 on minor 0

brd: module loaded

loop: module loaded

imx6q-pinctrl 20e0000.iomuxc: pin MX6Q_PAD_KEY_COL1 already requested by 21f4000 .serial; cannot claim for 2008000.ecspi

imx6q-pinctrl 20e0000.iomuxc: pin-128 (2008000.ecspi) status -22

imx6q-pinctrl 20e0000.iomuxc: could not request pin 128 on device 20e0000.iomuxc

spi_imx 2008000.ecspi: Error applying setting, reverse things back

m25p80 spi32766.0: found mr25h256, expected m25p32

m25p80 spi32766.0: mr25h256 (32 Kbytes)

spi_imx 2008000.ecspi: probed

tun: Universal TUN/TAP device driver, 1.6

CAN device driver interface

fec 2188000.ethernet (unregistered net_device): Invalid MAC address: 00:00:00:00 :00:00

fec 2188000.ethernet (unregistered net_device): Using random MAC address: b6:ca: ab:6e:5d:a2

libphy: fec_enet_mii_bus: probed

fec 2188000.ethernet eth0: registered PHC device 0

PPP generic driver version 2.4.2

PPP BSD Compression module registered

PPP Deflate Compression module registered

PPP MPPE Compression module registered

NET: Registered protocol family 24

usbcore: registered new interface driver asix

usbcore: registered new interface driver ax88179_178a

usbcore: registered new interface driver cdc_ether

usbcore: registered new interface driver net1080

usbcore: registered new interface driver cdc_subset

usbcore: registered new interface driver zaurus

usbcore: registered new interface driver cdc_ncm

ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver

usbcore: registered new interface driver cdc_acm

cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters

usbcore: registered new interface driver usb-storage

usbcore: registered new interface driver usbserial

usbcore: registered new interface driver option

usbserial: USB Serial support registered for GSM modem (1-port)

ci_hdrc ci_hdrc.1: doesn't support gadget

ci_hdrc ci_hdrc.1: EHCI Host Controller

ci_hdrc ci_hdrc.1: new USB bus registered, assigned bus number 1

ci_hdrc ci_hdrc.1: USB 2.0 started, EHCI 1.00

usb usb1: New USB device found, idVendor=1d6b, idProduct=0002

usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1

usb usb1: Product: EHCI Host Controller

usb usb1: Manufacturer: Linux 3.10.53 ehci_hcd

usb usb1: SerialNumber: ci_hdrc.1

hub 1-0:1.0: USB hub found

hub 1-0:1.0: 1 port detected

mousedev: PS/2 mouse device common for all mice

usbcore: registered new interface driver xpad

usbcore: registered new interface driver usb_acecad

usbcore: registered new interface driver aiptek

usbcore: registered new interface driver gtco

usbcore: registered new interface driver hanwang

usbcore: registered new interface driver kbtab

usbcore: registered new interface driver wacom

elan-touch 2-0010: elan - Read Hello Packet Failed

elan-touch: probe of 2-0010 failed with error -22

egalax_ts 1-0004: Failed to read firmware version

egalax_ts: probe of 1-0004 failed with error -5

egalax_ts 2-0004: Failed to read firmware version

egalax_ts: probe of 2-0004 failed with error -5

input: max11801_ts as /devices/soc0/soc.1/2100000.aips-bus/21a4000.i2c/i2c-1/1-0048/input/input0

i2c-core: driver [isl29023] using legacy suspend method

i2c-core: driver [isl29023] using legacy resume method

snvs_rtc 20cc034.snvs-rtc-lp: rtc core: registered 20cc034.snvs-rtc-lp as rtc0

i2c /dev entries driver

mxc_v4l2_output v4l2_out.38: V4L2 device registered as video16

mxc_v4l2_output v4l2_out.38: V4L2 device registered as video17

usbcore: registered new interface driver uvcvideo

USB Video Class driver (1.1.1)

gspca_main: v2.14.0 registered

max11801_ts 1-0048: FIFO_RD_AUX_MSB read fails

mag3110 2-000e: check mag3110 chip ID

mag3110 2-000e: read chip ID 0xffffff92 is not equal to 0xc4!

mag3110: probe of 2-000e failed with error -22

mma8x5x 0-001c: read chip ID 0xffffff92 is not equal to 0x1a,0x2a,0x3a,0x4a,0x5a!

mma8x5x: probe of 0-001c failed with error -22

imx2-wdt 20bc000.wdog: IMX2+ Watchdog Timer enabled. timeout=60s (nowayout=0)

device-mapper: uevent: version 1.0.3

device-mapper: ioctl: 4.24.0-ioctl (2013-01-15) initialised: dm-devel@redhat.com

Bluetooth: Virtual HCI driver ver 1.3

Bluetooth: HCI UART driver ver 2.2

Bluetooth: HCIATH3K protocol initialized

usbcore: registered new interface driver btusb

cpuidle: using governor ladder

cpuidle: using governor menu

sdhci: Secure Digital Host Controller Interface driver

sdhci: Copyright(c) Pierre Ossman

sdhci-pltfm: SDHCI platform and OF driver helper

Re: Could You Help Me To Check The Log

igorpadykov — Sat, 25 Jul 2015 07:39:00 GMT

Hi tony

without hardware knowledge of that specific board I am afraid it is

problematic to analyze logs. However for porting new software it

may be recommended to start with minimal image then add drivers

one by one, checking their functionality with unit test (imx-test) package

http://repository.timesys.com/buildsources/i/imx-test/imx-test-3.10.53-1.1.0/

Best regards

igor

i.MX Processors中的主题 Could You Help Me To Check The Log

Could You Help Me To Check The Log

Re: Could You Help Me To Check The Log