Project

General

Profile

Actions

Bug #6

closed
IC

channel test fails on a Samsung DDR3L 8G memory with IVB processor

Bug #6: channel test fails on a Samsung DDR3L 8G memory with IVB processor

Added by Iru Cai about 10 years ago. Updated over 9 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
11/20/2015
Due date:
% Done:

0%

Estimated time:
Affected versions:
Needs backport to:
Affected hardware:
Affected OS:

Description

I'm using coreboot with a lenovo T420 laptop. I build coreboot as follows:

  1. checkout to a commit
  2. apply these patches:
  1. build coreboot

I found the latest git code causes a channel test failure on Samsung 8G DDR3L M471B1G73DB0-YK0 with i7-3720QM(QS version) processor, it works fine if I do one of the following changes:

  1. use i5-2520M processor
  2. use a 1.5V DDR3 8G memory or a Samsung 4G DDR3L module M471B5173QH0-YK0

I did a git bisect and the first bad commit is 9f1fbb9a3002e8d74d53d7973bd1c7e3d4879238.


Files

ehci.log (2.79 KB) ehci.log log from EHCI debug port Iru Cai, 11/20/2015 04:06 AM
ehci_normal.log (79.3 KB) ehci_normal.log EHCI log after reverse patching that commit and use the Samsung 8G DDR3L Iru Cai, 11/21/2015 02:47 AM
config (16.2 KB) config my coreboot config Iru Cai, 11/21/2015 02:47 AM
faillog.tar.xz (26.2 KB) faillog.tar.xz verbose log on channel test fail Iru Cai, 11/23/2015 04:11 AM
normallog.tar.xz (23.1 KB) normallog.tar.xz verbose log on successful boots after a reverse patching Iru Cai, 11/23/2015 04:11 AM

AC Updated by Alexander Couzens about 10 years ago Actions #1

@Iru it would be nice ifyou could add your .config,
what's the last upstream commit?

Ping siro about this.

SR Updated by Stefan Reinauer about 10 years ago Actions #2

I did a git bisect and the first bad commit is 9f1fbb9a3002e8d74d53d7973bd1c7e3d4879238.

Did you verify if the problem goes away if you back out exactly this patch with a top of tree build?

Also, did you try running with mrc.bin instead of native ram init?

IC Updated by Iru Cai about 10 years ago Actions #3

Stefan Reinauer wrote:

I did a git bisect and the first bad commit is 9f1fbb9a3002e8d74d53d7973bd1c7e3d4879238.

Did you verify if the problem goes away if you back out exactly this patch with a top of tree build?

Yes, I reverse patch that commit and the laptop boots with that memory module.

Also, did you try running with mrc.bin instead of native ram init?

Well, I don't know other MRC(is that the FSP or ChromiumOS MRC) other than the coreboot MRC.

And I've add my config and a normal boot log after reverse patching that commit and use that Samsung 8G DDR3L.

IC Updated by Iru Cai about 10 years ago Actions #4

Alexander Couzens wrote:

@Iru it would be nice ifyou could add your .config,

I've just add my config.

what's the last upstream commit?

362dbea2c9674bb50ddf2da306f477e7ae091134

Ping siro about this.

PR Updated by Patrick Rudolph about 10 years ago Actions #5

Please provide a full raminit log of the failing memory initialization.

IC Updated by Iru Cai about 10 years ago Actions #6

Patrick Rudolph wrote:

Please provide a full raminit log of the failing memory initialization.

OK. I set up the verbose RAM init log debug option and do the test. And I get some logs about channel test failure, and successful boots after a reverse patchcing.

IC Updated by Iru Cai about 10 years ago Actions #7

I've done some more testing recently, and found some more details:

  1. No bugs if I use a i5-3340M
  2. I just tested with a hynix 8G DDR3L module HMT41GS6BFR8A-PB, the machine also failed to boot, reverting that patch also solved the problem.

PR Updated by Patrick Rudolph almost 10 years ago Actions #8

This issue is fixed on master as https://review.coreboot.org/#/c/11248/ have been reverted. An updated version is under review: https://review.coreboot.org/#/c/13714/. Please test if possible.

IC Updated by Iru Cai almost 10 years ago Actions #9

  • Status changed from New to Resolved

PR Updated by Patrick Rudolph over 9 years ago Actions #10

  • Status changed from Resolved to Closed
Actions

Also available in: PDF Atom