I forgot to mention that if I took one of the cpus out, coreboot
wouldn't start at all. If I put that one back in and took the other
out, I got the same output as before.
-------- Original Message --------
Subject: Re: [coreboot] [Fwd: Re: arima hdama problem]
Date: Tue, 20 Oct 2009 09:35:13 -0600
From: Hugh Greenberg <[email protected]>
To: ron minnich <[email protected]>
CC: Myles Watson <[email protected]>, [email protected]
References: <[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
It didn't work after I took the cpu out. I got the same output. Is
there anything else I could try?
--
Hugh Greenberg
ron minnich wrote:
On Fri, Oct 16, 2009 at 3:52 PM, Myles Watson <[email protected]> wrote:
Sorry, nothing jumps out at me. Ron's suggestion to remove a processor and
see if you get farther will probably get you past this point.
The way I would do this test:
1. take out a CPU and see if it boots
2. Put the CPU in, but put a hack into the code to bypass AP startup.
The more data points we have, the better.
ron
--
Hugh Greenberg
Los Alamos National Laboratory, CCS-1
Email: [email protected]
Phone: (505) 665-6471
--
coreboot mailing list: [email protected]
http://www.coreboot.org/mailman/listinfo/coreboot
