Bug 12131 - Kernel traceback when reboot beaglebone black
Summary: Kernel traceback when reboot beaglebone black
Status: VERIFIED FIXED
Alias: None
Product: BSPs
Classification: Build System, Metadata & Runtime
Component: bsps-meta-yocto (show other bugs)
Version: 2.4
Hardware: x86 Multiple
: Medium+ normal
Target Milestone: 2.5 M3
Assignee: Kevin Hao
QA Contact: Yi Zhao
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2017-09-27 08:20 UTC by Yi Zhao
Modified: 2018-03-22 23:17 UTC (History)
5 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: Regression (Used to work)
Verified:
Documentation change: No (bug/feature does not impact docs)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Yi Zhao 2017-09-27 08:20:54 UTC 
Image location: https://autobuilder.yocto.io/pub/releases/yocto-2.4.rc1/machines/beaglebone/

Git rev: master/592c3449697ce39bf07864fafd7f0a61ca230561

Steps:
1. Download core-image-sato-sdk wic image from the above link.
2. Deploy the wic image to micro SD card and boot the system
3. reboot the system

There are some kernel backtrace messages when reboot the system:
####################################
root@beaglebone:~# reboot
INIT: Sending processes the TERM signal
root@beaglebone:~# Stopping OpenBSD Secure Shell server: sshdstopped /usr/sbin/sshd (pid 536)
.
[ ok ]pping Avahi mDNS/DNS-SD Daemon: avahi-daemon
Stopping atd: OK
Stopping bluetooth: bluetoothd.
Stopping system message bus: dbus.
cpsw 4a100000.ethernet eth0: Link is Down
Stopping syslogd/klogd: stopped syslogd (pid 568)
stopped klogd (pid 571)
Division by zero in kernel.
CPU: 0 PID: 549 Comm: Xorg Not tainted 4.12.12-yocto-standard #1
Hardware name: Generic AM33XX (Flattened Device Tree)
[<c010f544>] (unwind_backtrace) from [<c010c35c>] (show_stack+0x20/0x24)
[<c010c35c>] (show_stack) from [<c04b4554>] (dump_stack+0x20/0x28)
[<c04b4554>] (dump_stack) from [<c010c1e8>] (__div0+0x20/0x28)
[<c010c1e8>] (__div0) from [<c04b326c>] (Ldiv0+0x8/0x10)
[<c04b326c>] (Ldiv0) from [<c05b3014>] (tilcdc_crtc_update_fb+0xb0/0x1c0)
[<c05b3014>] (tilcdc_crtc_update_fb) from [<c05b1eb8>] (tilcdc_plane_atomic_update+0x54/0x5c)
[<c05b1eb8>] (tilcdc_plane_atomic_update) from [<c0566b28>] (drm_atomic_helper_commit_planes+0x170/0x250)
[<c0566b28>] (drm_atomic_helper_commit_planes) from [<c05b5058>] (tilcdc_commit+0x50/0x7c)
[<c05b5058>] (tilcdc_commit) from [<c0583714>] (drm_atomic_commit+0x54/0x68)
[<c0583714>] (drm_atomic_commit) from [<c0567250>] (drm_atomic_helper_set_config+0x68/0x8c)
[<c0567250>] (drm_atomic_helper_set_config) from [<c0577aa0>] (__drm_mode_set_config_internal+0x4c/0xe0)
[<c0577aa0>] (__drm_mode_set_config_internal) from [<c057840c>] (drm_mode_setcrtc+0x3fc/0x494)
[<c057840c>] (drm_mode_setcrtc) from [<c0570e8c>] (drm_ioctl+0x324/0x3ac)
[<c0570e8c>] (drm_ioctl) from [<c027056c>] (vfs_ioctl+0x30/0x44)
[<c027056c>] (vfs_ioctl) from [<c0270750>] (do_vfs_ioctl+0x94/0x874)
[<c0270750>] (do_vfs_ioctl) from [<c0270f90>] (SyS_ioctl+0x60/0x7c)
[<c0270f90>] (SyS_ioctl) from [<c01079a0>] (ret_fast_syscall+0x0/0x3c)
done
Stopping tcf-agent: OK
#############################
Comment 1 Kevin Hao 2017-10-11 11:04:33 UTC 
I have sent a patch to Jyri Sarha (the maintainer of TI LCDC) and the patch is still in review.
Comment 2 Kevin Hao 2017-11-23 01:39:54 UTC 
The patch for this issue has been merged in the mainline and should propagate to the stable soon.
Comment 3 Yi Zhao 2018-01-11 00:57:37 UTC 
This issue still exists in 2.5 M1 RC3 build.
Comment 4 Kevin Hao 2018-01-18 10:25:39 UTC 
The patch has been merged into mainline three months ago, but the process to propagate to stable kernel is much slow than I expect. So I will submit this patch to the linux-yocto directly.
Comment 5 Yi Zhao 2018-03-22 23:17:30 UTC 
Verified with 2.5 M3 RC1.
Git rev: master/f49ee61422c867516db252054e993df29f775136