A. Smith
Sent: Sunday, November 04, 2007 1:46 PM
To: John Watlington
Cc: Kim Quirk; Jim Gettys; Arnold Kao (高顯宗); Mary Lou Jepsen; devel; Andres
Salomon
Subject: Re: MP Build... FYI
John Watlington wrote:
Quanta wants assurance that the software workaround which was broken in
#4479 is fixed
: Kim Quirk; Jim Gettys; Arnold Kao (高顯宗); Mary Lou Jepsen;
devel; Andres Salomon Subject: Re: MP Build... FYI
John Watlington wrote:
Quanta wants assurance that the software workaround which was
broken in #4479 is fixed.
Richard's testing is necessary to confirm
On Sun, 04 Nov 2007 14:06:57 -0500
Chris Ball [EMAIL PROTECTED] wrote:
Hi,
I'm still confused/concerned In particular, I have memories
of a change for manufacturing test to cause the systems to wake
up on multi-cast, to enable the mass suspend/resume testing of
units.
To summarize:
(1) We have consensus from both OLPC and Quanta that we do NOT put
bits on any MP machines that have not gone through our testing
regimes. This means that 625 will NOT go on any machines until we have
tested it.
(2) We have tested 624.
(3) OLPC believes that the risk associated
We are putting on three builds tomorrow
MP quanta standard test build
MP suspend/resume 24 hour test
MP ship build (need to de-activate, after allowing activation for
above).
also 624 and 625 wake up on a network ping - and not 623 - which may be
the best candidate for MP ship build.
- Mary Lou
Sent: Sunday, November 04, 2007 1:46 PM
To: John Watlington
Cc: Kim Quirk; Jim Gettys; Arnold Kao (高顯宗); Mary Lou Jepsen; devel; Andres
Salomon
Subject: Re: MP Build... FYI
John Watlington wrote:
Quanta wants assurance that the software workaround which was broken in
#4479
Hi,
I'm still confused/concerned In particular, I have memories of
a change for manufacturing test to cause the systems to wake up on
multi-cast, to enable the mass suspend/resume testing of units.
Andres, did this ever go by chance into the 62x series of builds
(as
On Sat, 03 Nov 2007 17:36:00 -0400
Mary Lou Jepsen [EMAIL PROTECTED] wrote:
Ship.1 are the bits Quanta is currently putting on machines in
the
factory. It is Build 624; Firmware Q2D03.
We are putting build 625 on mass production machines starting Monday,
Once Richard reports back about whether the DCON workaround
succeeded
We need to know before that so that we can make a decision with the DCON
initialization results - tonight china time at 8PM when we see the
results - quanta needs to do testing.
We may NOT be able to build tomorrow - they
I've never done a smoke test before. (and that smoke test is for the
more recent builds, rather than trial3/MP).
Other than having some trouble around activity and library installation,
625 checked out fine.
Upgrading from 623-625 indicated just changes in the kernel, so random
other stuff did
There shouldn't be any problems if 624 is used for MP.
The testing process is there for a reason, and should be strictly
followed.
The DCON bug that 625 fixes (#4479) will only show up on a small
number of machines, and it's frequency is low enough in normal
operation of our current software
John,
It sounds like you recommend that Quanta put 624 on the laptops at the end
of mfg test.
Is that true?
If so, I would support that decision as well; and we don't need to go
through the release testing for 625.
Regards,
Kim
On 11/4/07, John Watlington [EMAIL PROTECTED] wrote:
There
On Nov 4, 2007, at 1:04 AM, John Watlington wrote:
The DCON bug that 625 fixes (#4479) will only show up on a small
number of machines, and it's frequency is low enough in normal
operation of our current software (where we only support sleep,
not automatic suspend) that it will be an extremely
Quanta wants assurance that the software workaround which was broken
in #4479 is fixed.
Richard's testing is necessary to confirm this. It is also
essential that the kernel fix
which is theoretically the only difference between 624 and 625 be
part of the production
test code to further
14 matches
Mail list logo
