<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
I have access to an E350M1. I will test these patches tonight and
report back with results.<br>
<br>
Thank you!<br>
-Marshall Buschman<br>
<br>
On 09/07/2011 02:53 AM, She, Kerry wrote:
<blockquote
cite="mid:F53A09371FB723428826B442A4B20A410758DCA9@sbjgexmb1.amd.com"
type="cite">
<pre wrap="">
</pre>
<blockquote type="cite">
<pre wrap="">-----Original Message-----
From: <a class="moz-txt-link-abbreviated" href="mailto:coreboot-bounces@coreboot.org">coreboot-bounces@coreboot.org</a> [<a class="moz-txt-link-freetext" href="mailto:coreboot">mailto:coreboot</a>-
<a class="moz-txt-link-abbreviated" href="mailto:bounces@coreboot.org">bounces@coreboot.org</a>] On Behalf Of <a class="moz-txt-link-abbreviated" href="mailto:perh52@runbox.com">perh52@runbox.com</a>
Sent: Friday, August 19, 2011 12:37 AM
To: coreboot
Subject: [coreboot] E350M1 does not POST
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">Hi,
</pre>
<blockquote type="cite">
<pre wrap="">Upon booting, I get this:
</pre>
</blockquote>
<pre wrap="">
[...]
you could try commit 0df0e14fb, that may or may not work, the
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">commit
</pre>
<blockquote type="cite">
<pre wrap="">after
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">that broke fusion boards completely, apparently.
Florian
</pre>
</blockquote>
<pre wrap="">Thank you! I can confirm that 0df0e14fb works properly.
-Marshall
</pre>
</blockquote>
<pre wrap="">
Frank,
It looks like we have a regression. Is there some dependency on the
other patches that have not yet been committed?
Marc
</pre>
</blockquote>
<pre wrap="">
Unfortunately git bisect is no help here because the commit which
</pre>
</blockquote>
<pre wrap="">caused
</pre>
<blockquote type="cite">
<pre wrap="">the regression was a huge one.
It's important that large patches are broken down into a set of small
comprehensible patches, each with an explanatory commit message.
<<quote from git-bisect-lk2009.html documentation>>
...
sometimes "interesting" changes of behavior in the software are
introduced in some commits.
In fact people are specially interested in commits that introduce a
"bad" behavior, called a bug or a regression. They are interested in
these commits because a commit (hopefully) contains a very small set
of source code changes. And it's much easier to understand and
properly fix a problem when you only need to check a very small set of
changes, than when you don't know where look in the first place.
So to help people find commits that introduce a "bad" behavior, the
"git bisect" set of commands was invented.
</pre>
</blockquote>
<pre wrap="">Hello, All
Since commit 84cbce2 cause E350M1 not POST,
Following patches should resolve this regression problem, please see the
attachment in detail.
I have test it on a Persimmon mainboard,
anybody can have a test on E350M1?
Thanks
--
Kerry sheh
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
</blockquote>
<br>
</body>
</html>