public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
* [U-Boot] Kernel hang when replace older uboot with uboot master V2
@ 2019-02-19  9:30 rosysong at rosinson.com
  2019-02-19  9:37 ` Lukasz Majewski
  0 siblings, 1 reply; 6+ messages in thread
From: rosysong at rosinson.com @ 2019-02-19  9:30 UTC (permalink / raw)
  To: u-boot

Hi all, 
    And When I turn off the log, its bootlog like this:

U-Boot 2019.01-00079-g3420a6fc6e-dirty (Feb 19 2019 - 17:19:16 +0800)

Qualcomm Atheros QCA9561 ver 1 rev 0
Model: AP152 Reference Board
DRAM:  128 MiB
Loading Environment from SPI Flash... SF: Detected w25q128bv with page size 256 Bytes, erase size 4 KiB, total 16 MiB, mapped at 9f000000
*** Warning - bad CRC, using default environment

In:    uart at 18020000
Out:   uart at 18020000
Err:   uart at 18020000
Net:   
Warning: eth at 0x19000000 (eth0) using random MAC address - 56:87:3c:61:9b:50
eth0: eth at 0x19000000
Hit any key to stop autoboot:  0 
ap152 # bootm 0x1f060000
## Booting kernel from Legacy Image at 1f060000 ...
   Image Name:   MIPS OpenWrt Linux-4.14.101
   Image Type:   MIPS Linux Kernel Image (lzma compressed)
   Data Size:    1615030 Bytes = 1.5 MiB
   Load Address: 80060000
   Entry Point:  80060000
   Verifying Checksum ... OK
   Uncompressing Kernel Image ... OK
[    0.000000] Linux version 4.14.101 (xxx at xxx-PC) (gcc version 7.4.0 (OpenWrt GCC 7.4.0 r8997-488af51f81)) #0 Mon Feb 18 15:11:32 2019
[    0.000000] bootconsole [early0] enabled
[    0.000000] CPU0 revision is: 00019750 (MIPS 74Kc)
[    0.000000] MIPS: machine is ROSINSON WR818
[    0.000000] SoC: Qualcomm Atheros QCA956X ver 1 rev 0
[    0.000000] Determined physical RAM map:
[    0.000000]  memory: 08000000 @ 00000000 (usable)
[    0.000000] Initrd not found or empty - disabling initrd
[    0.000000] Primary instruction cache 64kB, VIPT, 4-way, linesize 32 bytes.
[    0.000000] Primary data cache 32kB, 4-way, VIPT, cache aliases, linesize 32 bytes
[    0.000000] Zone ranges:
[    0.000000]   Normal   [mem 0x0000000000000000-0x0000000007ffffff]
[    0.000000] Movable zone start for each node
[    0.000000] Early memory node ranges
[    0.000000]   node   0: [mem 0x0000000000000000-0x0000000007ffffff]
[    0.000000] Initmem setup node 0 [mem 0x0000000000000000-0x0000000007ffffff]
[    0.000000] random: get_random_bytes called from start_kernel+0x8c/0x474 with crng_init=0
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 32512
[    0.000000] Kernel command line: console=ttyS0,115200n8 rootfstype=squashfs,jffs2
[    0.000000] PID hash table entries: 512 (order: -1, 2048 bytes)
[    0.000000] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
[    0.000000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
[    0.000000] Writing ErrCtl register=00000000
[    0.000000] Readback ErrCtl register=00000000
[    0.000000] Memory: 123184K/131072K available (3777K kernel code, 150K rwdata, 912K rodata, 1232K init, 204K bss, 7888K reserved, 0K cma-reserved)
[    0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[    0.000000] NR_IRQS: 51
[    0.000000] CPU clock: 775.000 MHz
[    0.000000] clocksource: MIPS: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 4932285024 ns
[    0.000007] sched_clock: 32 bits at 387MHz, resolution 2ns, wraps every 5541893118ns
[    0.008841] Calibrating delay loop... 385.84 BogoMIPS (lpj=1929216)
[    0.075897] pid_max: default: 32768 minimum: 301
[    0.081292] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.088805] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.100195] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[    0.111385] futex hash table entries: 256 (order: -1, 3072 bytes)
[    0.118370] pinctrl core: initialized pinctrl subsystem
[    0.125117] NET: Registered protocol family 16
[    0.152720] clocksource: Switched to clocksource MIPS
[    0.159331] NET: Registered protocol family 2
[    0.164932] TCP established hash table entries: 1024 (order: 0, 4096 bytes)
[    0.172894] TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
[    0.180116] TCP: Hash tables configured (established 1024 bind 1024)
[    0.187461] UDP hash table entries: 256 (order: 0, 4096 bytes)
[    0.194136] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[    0.201461] NET: Registered protocol family 1
[    0.209168] Crashlog allocated RAM at address 0x3f00000
[    0.216385] workingset: timestamp_bits=30 max_order=15 bucket_order=0
[    0.227688] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    0.234346] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
[    0.253234] io scheduler noop registered
[    0.257682] io scheduler deadline registered (default)
[    0.263810] ar7200-usb-phy usb-phy: phy reset is missing
[    0.271331] pinctrl-single 1804002c.pinmux: 544 pins at pa b804002c size 68
[    0.280201] Serial: 8250/16550 driver, 1 ports, IRQ sharing disabled
[    0.288040] console [ttyS0] disabled
[    0.292122] 18020000.uart: ttyS0 at MMIO 0x18020000 (irq = 8, base_baud = 1562500) is a 16550A
[    0.301943] console [ttyS0] enabled
[    0.301943] console [ttyS0] enabled
[    0.309500] bootconsole [early0] disabled
[    0.309500] bootconsole [early0] disabled
[    0.332542] m25p80 spi0.0: w25q128 (16384 Kbytes)
[    0.337492] 5 fixed-partitions partitions found on MTD device spi0.0
[    0.344060] Creating 5 MTD partitions on "spi0.0":
[    0.349014] 0x000000000000-0x000000040000 : "u-boot"
[    0.354834] 0x000000040000-0x000000050000 : "u-boot-env"
[    0.360944] 0x000000050000-0x000000060000 : "factory"
[    0.366831] 0x000000060000-0x000000fe0000 : "firmware"
[    0.374973] 2 uimage-fw partitions found on MTD device firmware
[    0.381090] Creating 2 MTD partitions on "firmware":
[    0.386258] 0x000000000000-0x000000190000 : "kernel"
[    0.392027] 0x000000190000-0x000000f80000 : "rootfs"
[    0.397783] mtd: device 5 (rootfs) set to be root filesystem
[    0.403703] 1 squashfs-split partitions found on MTD device rootfs
[    0.410095] 0x000000440000-0x000000f80000 : "rootfs_data"
[    0.416295] 0x000000ff0000-0x000001000000 : "art"
[    0.422691] libphy: Fixed MDIO Bus: probed
[    0.763078] libphy: ag71xx_mdio: probed
[    0.770036] switch0: Atheros AR8337 rev. 2 switch registered on mdio-bus.0
[    1.424526] ag71xx 19000000.eth: invalid MAC address, using random address
[    1.763882] ag71xx 19000000.eth: connected to PHY at mdio-bus.0:00 [uid=004dd036, driver=Atheros AR8216/AR8236/AR8316]
[    1.775479] eth0: Atheros AG71xx at 0xb9000000, irq 4, mode:SGMII
[    1.783515] NET: Registered protocol family 10
[    1.791439] Segment Routing with IPv6
[    1.795358] NET: Registered protocol family 17
[    1.799984] 8021q: 802.1Q VLAN Support v1.8
[    1.810014] VFS: Mounted root (squashfs filesystem) readonly on device 31:5.
[    1.824049] Freeing unused kernel memory: 1232K
[    1.828729] This architecture does not have kernel memory protection.

^ permalink raw reply	[flat|nested] 6+ messages in thread

* [U-Boot] Kernel hang when replace older uboot with uboot master V2
  2019-02-19  9:30 [U-Boot] Kernel hang when replace older uboot with uboot master V2 rosysong at rosinson.com
@ 2019-02-19  9:37 ` Lukasz Majewski
  2019-02-19  9:45   ` rosysong at rosinson.com
  2019-02-19  9:48   ` rosysong at rosinson.com
  0 siblings, 2 replies; 6+ messages in thread
From: Lukasz Majewski @ 2019-02-19  9:37 UTC (permalink / raw)
  To: u-boot

On Tue, 19 Feb 2019 17:30:57 +0800
"rosysong at rosinson.com" <rosysong@rosinson.com> wrote:

> Hi all, 
>     And When I turn off the log, its bootlog like this:
> 
> U-Boot 2019.01-00079-g3420a6fc6e-dirty (Feb 19 2019 - 17:19:16 +0800)
> 
> Qualcomm Atheros QCA9561 ver 1 rev 0
> Model: AP152 Reference Board
> DRAM:  128 MiB
> Loading Environment from SPI Flash... SF: Detected w25q128bv with
> page size 256 Bytes, erase size 4 KiB, total 16 MiB, mapped at
> 9f000000 *** Warning - bad CRC, using default environment

Here is the culprit - the on-board (tuned, setup) envs are not
accessible (or read in a wrong way).

Apparently the default envs doesn't have proper root=... setup.

Please check the env related entries in Kconfig.


Best regards,

Lukasz Majewski

--

DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-59 Fax: (+49)-8142-66989-80 Email: lukma at denx.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20190219/51e4e19c/attachment.sig>

^ permalink raw reply	[flat|nested] 6+ messages in thread

* [U-Boot] Kernel hang when replace older uboot with uboot master V2
  2019-02-19  9:37 ` Lukasz Majewski
@ 2019-02-19  9:45   ` rosysong at rosinson.com
  2019-02-19 10:49     ` Lukasz Majewski
  2019-02-19  9:48   ` rosysong at rosinson.com
  1 sibling, 1 reply; 6+ messages in thread
From: rosysong at rosinson.com @ 2019-02-19  9:45 UTC (permalink / raw)
  To: u-boot

Thanks for your reply, but this firmware can find the rootfs itself, 

>[    0.337492] 5 fixed-partitions partitions found on MTD device spi0.0
>[    0.344060] Creating 5 MTD partitions on "spi0.0":
>[    0.349014] 0x000000000000-0x000000040000 : "u-boot"
>[    0.354834] 0x000000040000-0x000000050000 : "u-boot-env"
>[    0.360944] 0x000000050000-0x000000060000 : "factory"
>[    0.366831] 0x000000060000-0x000000fe0000 : "firmware"
>[    0.374973] 2 uimage-fw partitions found on MTD device firmware
>[    0.381090] Creating 2 MTD partitions on "firmware":
>[    0.386258] 0x000000000000-0x000000190000 : "kernel"
>[    0.392027] 0x000000190000-0x000000f80000 : "rootfs"
>[    0.397783] mtd: device 5 (rootfs) set to be root filesystem

^ permalink raw reply	[flat|nested] 6+ messages in thread

* [U-Boot] Kernel hang when replace older uboot with uboot master V2
  2019-02-19  9:37 ` Lukasz Majewski
  2019-02-19  9:45   ` rosysong at rosinson.com
@ 2019-02-19  9:48   ` rosysong at rosinson.com
  1 sibling, 0 replies; 6+ messages in thread
From: rosysong at rosinson.com @ 2019-02-19  9:48 UTC (permalink / raw)
  To: u-boot


And I also added "root=" option to default env, it doesn't work either.

> Hi all, 
>     And When I turn off the log, its bootlog like this:
>
> U-Boot 2019.01-00079-g3420a6fc6e-dirty (Feb 19 2019 - 17:19:16 +0800)
>
> Qualcomm Atheros QCA9561 ver 1 rev 0
> Model: AP152 Reference Board
> DRAM:  128 MiB
> Loading Environment from SPI Flash... SF: Detected w25q128bv with
> page size 256 Bytes, erase size 4 KiB, total 16 MiB, mapped at
> 9f000000 *** Warning - bad CRC, using default environment
 
Here is the culprit - the on-board (tuned, setup) envs are not
accessible (or read in a wrong way).
 
Apparently the default envs doesn't have proper root=... setup.
 
Please check the env related entries in Kconfig.
 
 
Best regards

^ permalink raw reply	[flat|nested] 6+ messages in thread

* [U-Boot] Kernel hang when replace older uboot with uboot master V2
  2019-02-19  9:45   ` rosysong at rosinson.com
@ 2019-02-19 10:49     ` Lukasz Majewski
  2019-02-20  2:16       ` rosysong at rosinson.com
  0 siblings, 1 reply; 6+ messages in thread
From: Lukasz Majewski @ 2019-02-19 10:49 UTC (permalink / raw)
  To: u-boot

On Tue, 19 Feb 2019 17:45:12 +0800
"rosysong at rosinson.com" <rosysong@rosinson.com> wrote:

> Thanks for your reply, but this firmware can find the rootfs itself, 
> 
> >[    0.337492] 5 fixed-partitions partitions found on MTD device
> >spi0.0 [    0.344060] Creating 5 MTD partitions on "spi0.0":
> >[    0.349014] 0x000000000000-0x000000040000 : "u-boot"
> >[    0.354834] 0x000000040000-0x000000050000 : "u-boot-env"
> >[    0.360944] 0x000000050000-0x000000060000 : "factory"
> >[    0.366831] 0x000000060000-0x000000fe0000 : "firmware"
> >[    0.374973] 2 uimage-fw partitions found on MTD device firmware
> >[    0.381090] Creating 2 MTD partitions on "firmware":
> >[    0.386258] 0x000000000000-0x000000190000 : "kernel"
> >[    0.392027] 0x000000190000-0x000000f80000 : "rootfs"
> >[    0.397783] mtd: device 5 (rootfs) set to be root filesystem  
> 

This is too late - as this is the MTD partition info provided from
kernel's DTB.

You need the root= information which is probably available on your
environment (not accessible by some reason from new u-boot).

BTW: What is the version of old u-boot ?


Best regards,

Lukasz Majewski

--

DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-59 Fax: (+49)-8142-66989-80 Email: lukma at denx.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20190219/7b8df9ee/attachment.sig>

^ permalink raw reply	[flat|nested] 6+ messages in thread

* [U-Boot] Kernel hang when replace older uboot with uboot master V2
  2019-02-19 10:49     ` Lukasz Majewski
@ 2019-02-20  2:16       ` rosysong at rosinson.com
  0 siblings, 0 replies; 6+ messages in thread
From: rosysong at rosinson.com @ 2019-02-20  2:16 UTC (permalink / raw)
  To: u-boot



My old u-boot is 1.1.4

On Tue, 19 Feb 2019 17:45:12 +0800
"rosysong at rosinson.com" <rosysong@rosinson.com> wrote:
 
> Thanks for your reply, but this firmware can find the rootfs itself, 
>
> >[    0.337492] 5 fixed-partitions partitions found on MTD device
> >spi0.0 [    0.344060] Creating 5 MTD partitions on "spi0.0":
> >[    0.349014] 0x000000000000-0x000000040000 : "u-boot"
> >[    0.354834] 0x000000040000-0x000000050000 : "u-boot-env"
> >[    0.360944] 0x000000050000-0x000000060000 : "factory"
> >[    0.366831] 0x000000060000-0x000000fe0000 : "firmware"
> >[    0.374973] 2 uimage-fw partitions found on MTD device firmware
> >[    0.381090] Creating 2 MTD partitions on "firmware":
> >[    0.386258] 0x000000000000-0x000000190000 : "kernel"
> >[    0.392027] 0x000000190000-0x000000f80000 : "rootfs"
> >[    0.397783] mtd: device 5 (rootfs) set to be root filesystem 
>
 
This is too late - as this is the MTD partition info provided from
kernel's DTB.
 
You need the root= information which is probably available on your
environment (not accessible by some reason from new u-boot).
 
BTW: What is the version of old u-boot ?
 
 
Best regards,
 
Lukasz Majewski
 
--
 
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-59 Fax: (+49)-8142-66989-80 Email: lukma at denx.de

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2019-02-20  2:16 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2019-02-19  9:30 [U-Boot] Kernel hang when replace older uboot with uboot master V2 rosysong at rosinson.com
2019-02-19  9:37 ` Lukasz Majewski
2019-02-19  9:45   ` rosysong at rosinson.com
2019-02-19 10:49     ` Lukasz Majewski
2019-02-20  2:16       ` rosysong at rosinson.com
2019-02-19  9:48   ` rosysong at rosinson.com

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox