Bug 10261 - [Test Case 1059] Parselogs is failing giving error: amd_nb: Cannot enumerate AMD northbridges
Summary: [Test Case 1059] Parselogs is failing giving error: amd_nb: Cannot enumerate ...
Status: VERIFIED FIXED
Alias: None
Product: BSPs
Classification: Build System, Metadata & Runtime
Component: bsps-runtime (show other bugs)
Version: 2.2
Hardware: x86 x86
: Medium normal
Target Milestone: 2.2 M4
Assignee: California Sullivan
QA Contact: Jair Gonzalez
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2016-09-12 19:42 UTC by Jose Perez C
Modified: 2016-10-31 20:16 UTC (History)
7 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Don't know


Attachments
testimage log (12.05 KB, text/x-log)
2016-09-12 19:42 UTC, Jose Perez C
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jose Perez C 2016-09-12 19:42:43 UTC
Created attachment 3413 [details]
testimage log

STATUS: PASSED
BUILD: 2.2 M3: 2679a347c576f5411fbe802d2f6201c94036ecb2
ENVIRONMENT: genericx86 - on MMAX32bit
STEPS TO REPRODUCE: 

1- execute `bitbake core-image-sato-sdk -c testimage `
  
2 - After execution check:
 Parse dmesg log and all log files in /var/log for keywords like: "error" , "failed" , "cannot", "can't" etc.
Filter out the known and invalid errors or errors that appear in certain situations and need to be ignored.



EXPECTED OUTCOME: 
  
 No errors or fails should be present in logs

ACTUAL:

| Central error: [    0.336316] amd_nb: Cannot enumerate AMD northbridges
| ***********************
| [    0.335667] e820: reserve RAM buffer [mem 0x0008f000-0x0008ffff]
| [    0.335671] e820: reserve RAM buffer [mem 0x0009e000-0x0009ffff]
| [    0.335675] e820: reserve RAM buffer [mem 0x78abb000-0x7bffffff]
| [    0.335678] e820: reserve RAM buffer [mem 0x7a000000-0x7bffffff]
| [    0.335977] Bluetooth: Core ver 2.21
| [    0.336004] NET: Registered protocol family 31
| [    0.336015] Bluetooth: HCI device and connection manager initialized
| [    0.336030] Bluetooth: HCI socket layer initialized
| [    0.336042] Bluetooth: L2CAP socket layer initialized
| [    0.336063] Bluetooth: SCO socket layer initialized
| [    0.336316] amd_nb: Cannot enumerate AMD northbridges
| [    0.336357] clocksource: Switched to clocksource refined-jiffies
| [    0.357946] pnp: PnP ACPI init
| [    0.358179] pnp 00:00: Plug and Play ACPI device, IDs PNP0b00 (active)
| [    0.358340] system 00:01: [io  0x0680-0x069f] has been reserved
| [    0.358357] system 00:01: [io  0x0400-0x047f] has been reserved
| [    0.358371] system 00:01: [io  0x0500-0x05fe] has been reserved
| [    0.358389] system 00:01: Plug and Play ACPI device, IDs PNP0c02 (active)
| [    0.358641] pnp 00:02: Plug and Play ACPI device, IDs PNP0501 (active)
| [    0.359259] system 00:03: [mem 0xe0000000-0xefffffff] could not be reserved
| [    0.359278] system 00:03: [mem 0xfed01000-0xfed01fff] has been reserved
Comment 1 Benjamin Esquivel 2016-09-20 21:21:15 UTC
This error has been previously white-listed for qemux86[1]. Perhaps it is time to move it to a wider category.

Moving it to medium since it is a known and already white-listed error.

http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/lib/oeqa/runtime/parselogs.py#n65
Comment 3 Jair Gonzalez 2016-10-21 16:26:45 UTC
I tested on build 2.2 M4: 4b94b498e21aeba945fe7e72a6b7c4bb0314fb83 with environment genericx86 on MMAX32Bit and could not reproduce the issue. Moving it to VERIFIED.
Comment 4 Armin Kuster 2016-10-31 15:15:41 UTC
I am seeing this on Krogoth ( after updating the kernel). I applied the patch mentioned and it did not fix the issue. Are there any other pre-req patches I might be missing?
Comment 5 California Sullivan 2016-10-31 18:12:14 UTC
The patch only whitelists the error in testimage rather than making the error go away. The error is harmless, and the CONFIG_ option that causes it is necessary for genericx86(-64).
Comment 6 Armin Kuster 2016-10-31 18:31:05 UTC
(In reply to comment #5)
> The patch only whitelists the error in testimage rather than making the
> error go away. 

correct. testimage is still failing even after applying the patch. 

The error is harmless, and the CONFIG_ option that causes it
> is necessary for genericx86(-64).
Comment 7 California Sullivan 2016-10-31 19:17:23 UTC
On generic or qemu?

It looks like commit 26b0657b2 handles it for qemu.
Comment 8 Armin Kuster 2016-10-31 20:16:36 UTC
(In reply to comment #7)
> On generic or qemu?
> 
> It looks like commit 26b0657b2 handles it for qemu.

hah, there is one for each. that fix it. thanks