AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:
CFG:
PT:0
S:andy.sharp@lsi.com
RQ:
SSV:mhbs.lsil.com
NSV:
SSH:
R:<Brian.Stark@lsi.com>
MAID:2
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
RMID:#imap/LSI/INBOX	0	E1EC65251D4B3D46BBC0AAA3C0629222B281DA02@cosmail02.lsi.com
X-Sylpheed-End-Special-Headers: 1
Date: Thu, 4 Mar 2010 23:30:48 -0800
From: Andrew Sharp <andy.sharp@lsi.com>
To: "Stark, Brian" <Brian.Stark@lsi.com>
Subject: Re: PP BIOS Issues
Message-ID: <20100304233048.33ef8129@ripper.onstor.net>
In-Reply-To: <E1EC65251D4B3D46BBC0AAA3C0629222B281DA02@cosmail02.lsi.com>
References: <A11ADD3877B3C543B65BE8E196B7BDFFBB84D1F7@cosmail02.lsi.com>
	<20100304230003.69ca9061@ripper.onstor.net>
	<E1EC65251D4B3D46BBC0AAA3C0629222B281DA02@cosmail02.lsi.com>
Organization: LSI
X-Mailer: Sylpheed-Claws 2.6.0 (GTK+ 2.8.20; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

The part where they run around like a bunch of deaf people in a
completely dark room.

Somewhere, Rick Lund is spinning in his grave.  Oh wait, he's not dead
yet.


On Fri, 5 Mar 2010 00:17:35 -0700 "Stark, Brian" <Brian.Stark@lsi.com>
wrote:

> Which part?
> 
> 
> -----Original Message-----
> From: Andrew Sharp [mailto:andy.sharp@lsi.com] 
> Sent: Thursday, March 04, 2010 11:00 PM
> To: Stark, Brian
> Subject: Re: PP BIOS Issues
> 
> If I hadn't been reading these myself, I would have not believed it.
> 
> On Thu, 4 Mar 2010 21:54:01 -0700 "Padmanabhan, Seetharaman"
> <Seetharaman.Padmanabhan@lsi.com> wrote:
> 
> > Updates for 3/4/2010
> > 
> > From: Padmanabhan, Seetharaman
> > Sent: Thursday, March 04, 2010 8:52 PM
> > To: Brown, Bill E; Weber, Chris; Jameson.Chiang@quantatw.com; Busch,
> > Keith; Schwing, Aaron; Jayda.Lin@quantatw.com; Baum, Susan;
> > Rajappan, Jayaraj Cc: Stover, Jeremy; Matt.Yu@quantatw.com;
> > Rex.Hong@quantatw.com; Jolad, Amarnath; Venkatesha, Pradeep; Panda,
> > Siddharth; Parameswaran, Subramanian (Subbu); Sandwell, James; H N,
> > Bhuvaneshwar; Betty.Chang@quantatw.com; Eddie.Hsieh@quantatw.com;
> > Smith, Larry; Tammana, Dilip; Lecter.Yang@quantatw.com;
> > Luap.Chiang@quantatw.com; Finfrock, Randy; James-Lee@quantatw.com;
> > S.H.Wang@quantatw.com; Lee, Aaron Subject: PP BIOS Issues
> > 
> > Summary:
> > We have made some incremental progress on the BIOS issues but no
> > closure yet...  Quanta, AMI, Intel and LSI are working to collect
> > various data to isolate the problem further.
> > 
> > Action Items for today:
> > 
> > 1.       LSI US/CRB (ICT), AMI Osage 018 w/ IO APIC and MC enabled
> > 
> > a.       After removing PCIe NIC adapter from the system, CRB is
> > able to boot Xen successfully.  Chris will attempt to bring-up
> > RAIDApp tomorrow and verify CB3 operation.
> > 
> > 2.       LSI US/CRB (Mil), AMI Osage 018 w/ IO APIC and MC disabled
> > 
> > a.       After inserting CF Flash, CRB is able to boot Xen
> > successfully.  CB3 operation reports similar errors seen on PP
> > platform with 2A07f BIOS.
> > 
> > b.      Bill Brown (Intel) confirmed today that for CB3 operations
> > to succeed, IO APIC MUST be enabled.  This explains why 2A07f BIOS
> > does not react well for CB3 operations.
> > 
> > 3.       Intel US / PP, SKU 4 B0 Silicon, 2A07f BIOS
> > 
> > a.       Bill Brown (Intel) is able to successfully boot non Xen
> > Linux.  Planning to run CB3 diagnostic tool and share his results by
> > tomorrow.
> > 
> >                                                                            i.
> > If passes, problem we see might be applicable only to VT-d
> > environments
> > 
> > 1.       Note: Adam (Intel) has identified some issues DMAR table
> > update with AMI Osage 017 tree which might impact VT-d behavior.
> > However, this issue seems to have been fixed with AMI Osage 018
> > tree.
> > 
> >                                                                          ii.
> > If fails, Bill Brown will attempt to build AMI Osage 018 tree for PP
> > and repeat this experiment.
> > 
> > 4.       Quanta / CRB
> > 
> > a.       AMI Osage 017 source with IO APIC enabled and MC disabled
> > results in a post error code 0x0D.
> > 
> >                                                                            i.
> > AMI (Taiwan) unfortunately is not able to recreate the same failure
> > but has agreed to pass on the AMI compiled BIOS image to Quanta.
> > 
> >                                                                          ii.
> > Jameson is planning to load this new BIOS on his CRB and verify the
> > post error.
> > 
> > 5.       Quanta / PP
> > 
> > a.       Jameson to build AMI Osage 018 with IO APIC enabled and MC
> > disabled for PP and pass it on to LSI for parallel data collection.
> > Goal is to verify if CB3 operations will succeed running AMI BIOS as
> > is without any OEM change.
> > 
> > 
> > From: Brown, Bill E [mailto:bill.e.brown@intel.com]
> > Sent: Thursday, March 04, 2010 7:34 PM
> > To: Weber, Chris; Padmanabhan, Seetharaman;
> > Jameson.Chiang@quantatw.com; Busch, Keith; Schwing, Aaron;
> > Jayda.Lin@quantatw.com; Baum, Susan; Rajappan, Jayaraj Cc: Stover,
> > Jeremy; Matt.Yu@quantatw.com; Rex.Hong@quantatw.com; Jolad,
> > Amarnath; Venkatesha, Pradeep; Panda, Siddharth; Parameswaran,
> > Subramanian (Subbu); Sandwell, James; H N, Bhuvaneshwar;
> > Betty.Chang@quantatw.com; Eddie.Hsieh@quantatw.com; Smith, Larry;
> > Tammana, Dilip; Lecter.Yang@quantatw.com; Luap.Chiang@quantatw.com;
> > Finfrock, Randy; James-Lee@quantatw.com; S.H.Wang@quantatw.com; Lee,
> > Aaron; Brown, Bill E Subject: RE: BIOS 2A07f issues
> > 
> > Some data that may help Jameson to duplicate the problem with POST
> > hang at 96 on WC:
> > 
> > I have an Intel Pro/1000 PT Desktop Adapter network card (NIC).  I
> > tried it in the raptor slot (the slot on the left-hand side of WC)
> > on both my A3 board and the A6 board, and both of them booted to
> > the EFI shell without hanging.  For both test cases, nothing was
> > plugged into the IOPTOR slot (the slot near the front of WC), there
> > is a CF card plugged in, and I tested with
> > 0ABRB018-enIOAPIC-enME.ROM.
> > 
> > My take is that the hang at POST 96 may be dependant on the specific
> > NIC installed, or maybe the location (which slot, RAPTOR or IOPTOR).
> > 
> > Chris, which slot was your NIC plugged into?
> > 
> > regards,
> >    Bill
> > 
> > ________________________________
> > From: Weber, Chris [mailto:Chris.Weber@lsi.com]
> > Sent: Thursday, March 04, 2010 5:04 PM
> > To: Padmanabhan, Seetharaman; Brown, Bill E;
> > Jameson.Chiang@quantatw.com; Busch, Keith; Schwing, Aaron;
> > Jayda.Lin@quantatw.com; Baum, Susan; Rajappan, Jayaraj Cc: Stover,
> > Jeremy; Matt.Yu@quantatw.com; Rex.Hong@quantatw.com; Jolad,
> > Amarnath; Venkatesha, Pradeep; Panda, Siddharth; Parameswaran,
> > Subramanian (Subbu); Sandwell, James; H N, Bhuvaneshwar;
> > Betty.Chang@quantatw.com; Eddie.Hsieh@quantatw.com; Smith, Larry;
> > Tammana, Dilip; Lecter.Yang@quantatw.com; Luap.Chiang@quantatw.com;
> > Finfrock, Randy; James-Lee@quantatw.com; S.H.Wang@quantatw.com; Lee,
> > Aaron Subject: RE: BIOS 2A07f issues I was able to get a Wahweap
> > Canyon (A3 board w/B0 CPU) up and running today, so I should be able
> > to help out with that effort if needed.
> > 
> > I saw similar results with my system:
> > Osage 18 w/IOAPIC disabled  - Boots most of the time with add-in NIC
> > and Falcon SAS card (I did see BIOS hang at 96 once).  Xen boots
> > successfully w/VT-d enabled. Osage 18 w/IOAPIC enabled - BIOS hangs
> > at 96 if I have add-in NIC installed.  BIOS completes w/NIC removed
> > and Falcon SAS card installed.  Xen boots successfully w/VT-d
> > enabled.
> > 
> > I did not have time to try and get IO running, but I can try that
> > tomorrow if we think there's value in that.
> > 
> > --Chris
> > 
