Bug 4979

Summary: [beagleobard xM] Some internal error message in dmesg when boot up
Product: [Build System, Metadata & Runtime] BSPs Reporter: Ning Zhang <ning.zhang>
Component: bsps-meta-yoctoAssignee: Simarpreet Singh <simar>
Status: RESOLVED DUPLICATE QA Contact:
Severity: normal    
Priority: Medium CC: ke.zou, yi.zhao
Version: 1.5   
Target Milestone: 1.5   
Hardware: Beagleboard   
OS: arm   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: Don't know
Attachments:
Description Flags
messages.test log file none

Description Ning Zhang 2013-08-05 07:45:00 UTC
Created attachment 1408 [details]
messages.test log file

poky: master:9de0ad47462c13ac4a2d73e12e92be6c1b4e0415

steps:
1. download autobuilder.yoctoproject.org/pub/nightly/20130731-1 beagleboard image and use it to boot up a beagleboard xm target.
2. input dmesg| grep error.  It shows below info:
dmesg | grep error
Internal error: Oops: 817 [#1] ARM

3. check /var/log/messages.test, here has some detail error info:

Aug  2 09:00:23 beagleboard user.alert kernel: Unable to handle kernel paging request at virtual address ffffffff
Aug  2 09:00:23 beagleboard user.alert kernel: pgd = de78c000
Aug  2 09:00:23 beagleboard user.alert kernel: [ffffffff] *pgd=9f2fe821, *pte=00000000, *ppte=00000000
Aug  2 09:00:23 beagleboard user.emerg kernel: Internal error: Oops: 817 [#1] ARM


4. the kernel info is:
root@beagleboard:/var/log# uname -a
Linux beagleboard 3.4.52-yocto-standard #1 Fri Jul 19 12:17:46 GMT 2013 armv7l GNU/Linux

5. when i use 20130625-2 image to retest this, it doesn't have this error. here is the log:
beagleboard login: root
root@beagleboard:~# dmesg | grep error
usbhs_omap usbhs_omap: xclk60mhsp1_ck set parentfailed error:-22
usbhs_omap usbhs_omap: xclk60mhsp2_ck set parentfailed error:-22
root@beagleboard:~# uname -a
Linux beagleboard 3.4.36-yocto-standard #1 Mon Jun 24 22:29:28 UTC 2013 armv7l GNU/Linux

6. This issue could be reproduce almost every time. /var/log/messages.test attached.
Comment 1 Simarpreet Singh 2013-08-06 02:29:27 UTC
For #5 as you mentioned, there was a patch upstream that fixed it. It was addressed in Bug 3936: https://bugzilla.yoctoproject.org/show_bug.cgi?id=3936.

Here's a link to the upstream patch: https://lkml.org/lkml/2013/1/16/297 This was supposedly merged in. I'll track the commit down tomorrow.

I'll look into steps #1,#2,#3 tomorrow as well.
Comment 2 Simarpreet Singh 2013-08-16 15:16:55 UTC
Marking as duplicate of Bug 3936.

*** This bug has been marked as a duplicate of bug 3936 ***
Comment 3 Simarpreet Singh 2013-08-16 15:26:20 UTC
Closing this issue as it has been fixed from an upstream patch in commit a8c4e9e1118f0a12e3a9524d8d597487d7e3476d on master branch.