[U-Boot] RK3399 boards (rockpi4 and rockpro64) kernel SError using upstream U-boot

Qu Wenruo quwenruo.btrfs at gmx.com
Sat Nov 9 06:38:10 UTC 2019


Hi,

Although recent U-boot upstream has merged the rk3399 ram patchset to
initial DDR4 properly, but strangely I can still trigger SError for
RockPi4 and RockPro64 boards using upstream U-boot with upstream kernel
(v5.4-rc). The dmesg is attached at the end.

This is pretty easy to trigger if using "memtester 3584M" (both boards
are 4G RAM variants).
The strange part is, if using the vendor uboot (like Armbian does), then
the kernel SError just goes away, so it looks like a bug in Uboot.

The U-boot I built follows the README.rockchip, using the SD card and
boot option 1 (miniloader + Uboot + rkbin).
The script build script (arch PKGBUILD) can be found here:

https://github.com/adam900710/PKGBUILDs/blob/rockpi4/alarm/uboot-rockpi4/PKGBUILD

Any clue for the problem?

Thanks,
Qu


Dmesg:

[16515.304212] SError Interrupt on CPU4, code 0xbf000000 -- SError
[16515.304214] CPU: 4 PID: 312266 Comm: xz Tainted: G             L
5.4.0-rc4-1-ARCH #1
[16515.304214] Hardware name: Pine64 RockPro64 (DT)
[16515.304215] pstate: 20000005 (nzCv daif -PAN -UAO)
[16515.304216] pc : __arch_copy_from_user+0x1e4/0x240
[16515.304217] lr : copyin+0x64/0x78
[16515.304217] sp : ffff800018a6ba60
[16515.304218] x29: ffff800018a6ba60 x28: 0000000000000000
[16515.304220] x27: ffff800018a6bbb0 x26: 0000000000001000
[16515.304222] x25: 0000000000000000 x24: 0000000000001000
[16515.304224] x23: ffff800018a6bd50 x22: ffff000009c01000
[16515.304225] x21: ffff800018a6bd40 x20: 0000000000001000
[16515.304227] x19: 0000000000000000 x18: 0000000000000000
[16515.304228] x17: 0000000000000000 x16: 0000000000000000
[16515.304230] x15: 0000000000000000 x14: 4f7d52dec520356f
[16515.304231] x13: a9de684a303f24f9 x12: 834588c331acaa6b
[16515.304233] x11: f7ff400b020fdd35 x10: 50b30156ca1b1f55
[16515.304234] x9 : 151da96d9c26e661 x8 : 4d11af6b86f45b1e
[16515.304236] x7 : 5da170ed6e6fbe74 x6 : ffff000009c00240
[16515.304238] x5 : ffff000009c01000 x4 : 0000000000000000
[16515.304239] x3 : 0000aaaac54c2290 x2 : 0000000000000d80
[16515.304241] x1 : 0000aaaac54c2500 x0 : ffff000009c00000
[16515.304243] Kernel panic - not syncing: Asynchronous SError Interrupt
[16515.304244] CPU: 4 PID: 312266 Comm: xz Tainted: G             L
5.4.0-rc4-1-ARCH #1
[16515.304245] Hardware name: Pine64 RockPro64 (DT)
[16515.304245] Call trace:
[16515.304246]  dump_backtrace+0x0/0x178
[16515.304246]  show_stack+0x24/0x30
[16515.304247]  dump_stack+0xa8/0xd0
[16515.304248]  panic+0x148/0x320
[16515.304248]  __stack_chk_fail+0x0/0x28
[16515.304249]  arm64_serror_panic+0x84/0x90
[16515.304249]  do_serror+0x7c/0x120
[16515.304250]  el1_error+0x84/0xf8
[16515.304251]  __arch_copy_from_user+0x1e4/0x240
[16515.304251]  iov_iter_copy_from_user_atomic+0xe8/0x388
[16515.304252]  iomap_write_actor+0xd0/0x190
[16515.304253]  iomap_apply+0xcc/0x150
[16515.304253]  iomap_file_buffered_write+0x78/0xa8
[16515.304254]  xfs_file_buffered_aio_write+0xd8/0x340
[16515.304255]  xfs_file_write_iter+0xd4/0xe8
[16515.304255]  new_sync_write+0x114/0x198
[16515.304256]  __vfs_write+0x74/0x90
[16515.304257]  vfs_write+0xbc/0x1c8
[16515.304257]  ksys_write+0x74/0xf8
[16515.304258]  __arm64_sys_write+0x24/0x30
[16515.304258]  el0_svc_handler+0xa4/0x188
[16515.304259]  el0_svc+0x8/0xc
[16515.304273] SMP: stopping secondary CPUs
[16515.304274] Kernel Offset: disabled
[16515.304274] CPU features: 0x0002,20006008
[16515.304275] Memory Limit: none

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20191109/1ff96530/attachment.sig>


More information about the U-Boot mailing list