Re: MP Build... FYI
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. > >> Andres, did this ever go by chance into the 62x series of builds >> (as opposed to being a separate kernel RPM? > >> If so, at which build did it go in? > > There's been a miscommunication: while the ChangeLog for 624 says > "* libertas wake on network data" (whatever that means), such a patch > was not in the build. The only difference between 623->624 was one > patch that modified the DCON, and the only difference between 624->625 > was another single DCON patch. Jim's description of each build is > correct. Sigh. Looks like the wrong kernels ended up the builds. The main differences between them are the wake-on-broadcast patch, and some additional delays in the dcon workaround code. Hopefully that shouldn't make a difference... > > The "wake on broadcast" patch went into a "mfgtest" kernel branch > so that it could be used independently by Quanta (since it is not > appropriate for a release). The 6xx builds use the "trial-3" > series of kernels, which did not see this patch. > > - Chris. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: MP Build... FYI
On Sun, 04 Nov 2007 10:55:05 -0500 Jim Gettys <[EMAIL PROTECTED]> wrote: > 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. It went into 624 and 625. The DCON power cycle thing is in all builds, but the proper register init path is only in 625. > > Andres, did this ever go by chance into the 62x series of builds (as > opposed to being a separate kernel RPM? > > If so, at which build did it go in? > > My understanding of the situation is: > 623 - last fully tested MP build > 624 - first attempt at DCON power cycle hammer code, > missing a case. > 625 - most recent build, only intended for manufacturing test > and burn-in, with working DCON power cycle hammer > code. > > - Jim > > > > On Sun, 2007-11-04 at 02:27 -0500, Mary Lou Jepsen wrote: > > thanks arnold. > > - Mary Lou > > > > On Sun, 2007-11-04 at 14:40 +0800, [EMAIL PROTECTED] wrote: > > > Actually, I had asked our test engineer in CSMC to prepare 625 > > > for the factory suspend/resume test tomorrow. They are doing this > > > right now. It means we should have both 624 and 625 test image > > > to be ready tomorrow. We can make decision which image we want > > > to use in the factory suspend/resume test after we confirm the > > > test result of the 4 machines that were failed with DCON problem > > > before. > > > > > > > > > Best Regards, > > > Arnold Kao > > > Quanta Computer Inc. > > > Tel : 886-3-327-2345 EXT:18958 > > > Fax : 886-3-328-9780 > > > > > > > > > -Original Message- > > > From: Richard Smith [mailto:[EMAIL PROTECTED] On Behalf Of > > > Richard 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. > > > > 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 confirm this. If Quanta sees this > > > > problem AT ALL in the production > > > > testing, there will be pressure to halt until further > > > > hardware/software fixes are found. > > > > > > I'm getting a slightly different story. I was trying to meet > > > with people yesterday to discuss the whole mfg testing procedure > > > so I knew what was going on and what I would need to do to get > > > the new kernel into the Run-In image. > > > > > > Arnold tells me that he thinks its too late to get the DCON > > > workaround kernel into the Run-In image. He suggestion was that > > > if we see a DCON problem that we pull the machine out of the > > > rack, update the kernel and then re-add it back into the testing. > > > > > ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
RE: MP Build... FYI
Actually, I had asked our test engineer in CSMC to prepare 625 for the factory suspend/resume test tomorrow. They are doing this right now. It means we should have both 624 and 625 test image to be ready tomorrow. We can make decision which image we want to use in the factory suspend/resume test after we confirm the test result of the 4 machines that were failed with DCON problem before. Best Regards, Arnold Kao Quanta Computer Inc. Tel : 886-3-327-2345 EXT:18958 Fax : 886-3-328-9780 -Original Message- From: Richard Smith [mailto:[EMAIL PROTECTED] On Behalf Of Richard 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. > 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 confirm this. If Quanta sees this problem AT ALL > in the production > testing, there will be pressure to halt until further hardware/software > fixes are found. I'm getting a slightly different story. I was trying to meet with people yesterday to discuss the whole mfg testing procedure so I knew what was going on and what I would need to do to get the new kernel into the Run-In image. Arnold tells me that he thinks its too late to get the DCON workaround kernel into the Run-In image. He suggestion was that if we see a DCON problem that we pull the machine out of the rack, update the kernel and then re-add it back into the testing. -- Richard Smith <[EMAIL PROTECTED]> One Laptop Per Child ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: MP Build... FYI
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 opposed to being a separate kernel RPM? > If so, at which build did it go in? There's been a miscommunication: while the ChangeLog for 624 says "* libertas wake on network data" (whatever that means), such a patch was not in the build. The only difference between 623->624 was one patch that modified the DCON, and the only difference between 624->625 was another single DCON patch. Jim's description of each build is correct. The "wake on broadcast" patch went into a "mfgtest" kernel branch so that it could be used independently by Quanta (since it is not appropriate for a release). The 6xx builds use the "trial-3" series of kernels, which did not see this patch. - Chris. -- Chris Ball <[EMAIL PROTECTED]> ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
RE: MP Build... FYI
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 opposed to being a separate kernel RPM? If so, at which build did it go in? My understanding of the situation is: 623 - last fully tested MP build 624 - first attempt at DCON power cycle hammer code, missing a case. 625 - most recent build, only intended for manufacturing test and burn-in, with working DCON power cycle hammer code. - Jim On Sun, 2007-11-04 at 02:27 -0500, Mary Lou Jepsen wrote: > thanks arnold. > - Mary Lou > > On Sun, 2007-11-04 at 14:40 +0800, [EMAIL PROTECTED] wrote: > > Actually, I had asked our test engineer in CSMC to prepare 625 for the > > factory suspend/resume test tomorrow. They are doing this right now. It > > means we should have both 624 and 625 test image to be ready tomorrow. We > > can make decision which image we want to use in the factory suspend/resume > > test after we confirm the test result of the 4 machines that were failed > > with DCON problem before. > > > > > > Best Regards, > > Arnold Kao > > Quanta Computer Inc. > > Tel : 886-3-327-2345 EXT:18958 > > Fax : 886-3-328-9780 > > > > > > -Original Message- > > From: Richard Smith [mailto:[EMAIL PROTECTED] On Behalf Of Richard 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. > > > 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 confirm this. If Quanta sees this problem AT ALL > > > in the production > > > testing, there will be pressure to halt until further hardware/software > > > fixes are found. > > > > I'm getting a slightly different story. I was trying to meet with > > people yesterday to discuss the whole mfg testing procedure so I knew > > what was going on and what I would need to do to get the new kernel into > > the Run-In image. > > > > Arnold tells me that he thinks its too late to get the DCON workaround > > kernel into the Run-In image. He suggestion was that if we see a DCON > > problem that we pull the machine out of the rack, update the kernel and > > then re-add it back into the testing. > > > -- Jim Gettys One Laptop Per Child ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: MP Build... FYI
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 On Sun, 2007-11-04 at 09:49 -0400, Walter Bender wrote: > 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 with the DCON bug, given > the lack of aggressive suspend/resume in the 624 build, is minimal. > > (4) We believe that the kernel patch in 625 is adequate to address the > DCON bug. This is being tested now. > > Until we reach conclusion re 625, we should be using 624 for MP. > > If 625 does indeed fix the DCON bug, then we should roll over to it, > if and only if we are able to find adequate testing resources. The > changes will be incorporated into Update.1 regardless. > > If 625 does not fix the DCON bug, we need to consider alternatives. > > Agreed? > > -walter ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: MP Build... FYI
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 with the DCON bug, given the lack of aggressive suspend/resume in the 624 build, is minimal. (4) We believe that the kernel patch in 625 is adequate to address the DCON bug. This is being tested now. Until we reach conclusion re 625, we should be using 624 for MP. If 625 does indeed fix the DCON bug, then we should roll over to it, if and only if we are able to find adequate testing resources. The changes will be incorporated into Update.1 regardless. If 625 does not fix the DCON bug, we need to consider alternatives. Agreed? -walter ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: MP Build... FYI
We are also testing the first 1500 units for on rapid cycle suspend/resume. If the 625 build fixes this - it would be excellent to get the most data we can on our best solution. However, richard pointed out a back up - we can take the units that fail the 24 hour test and put 625 on them and then run them for another 24 hours. I'm about to meet with richard, matt, gary and arnold now. - mary lou On Sun, 2007-11-04 at 01:04 -0400, John Watlington wrote: > 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 (where we only support sleep, > not automatic suspend) that it will be an extremely rare complaint > (roughly one tenth of the machines will show the problem once > every 5-20K resumes --- that's a lot of button pushes!). When the > display is powered down automatically for power conservation, > the code path should reinitialize the DCON correctly. > > It is a low severity bug, the user hits any key and the problem > clears up. > RMA requests for machines showing this problem can be answered with a > request that they upgrade their software. > > John > > On Nov 4, 2007, at 12:32 AM, Richard A. Smith wrote: > > > Jim Gettys 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, > because this addresses a suspected bug, the failure to > initialize the > DCON registers when power is re-applied to DCON. Build 625 is in > testing by Quanta right now. > > > > I just spoke with Arnold about the current 624/625 testing status. > > > > 624 testing was completed by Quanta and is ready to go. They were not > > able to start testing 625 because there was no signed image. > > > > Current plan is for 624 to go onto the machines. > > > > _If_ we claim that 625 are the new bits and sign them for use on MP > > machines then Quanta can start testing 625 on Monday morning. > > > > They _might_ be able to complete the testing in time for MP but Arnold > > says it will involve a lot of work from the .tw testing team. > > > > Gary and I will be headed to CSMC at 8pm Changshu time to look a the > > results of the > 24 hour DCON test. I'll report back the results and > > then the team can make the call on going with 624 or trying to push > > for > > 625. > > > > -- > > Richard Smith <[EMAIL PROTECTED]> > > One Laptop Per Child > > ___ > > Devel mailing list > > Devel@lists.laptop.org > > http://lists.laptop.org/listinfo/devel > ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
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 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 confirm this. If Quanta sees this problem AT ALL > in the production > testing, there will be pressure to halt until further hardware/software > fixes are found. I'm getting a slightly different story. I was trying to meet with people yesterday to discuss the whole mfg testing procedure so I knew what was going on and what I would need to do to get the new kernel into the Run-In image. Arnold tells me that he thinks its too late to get the DCON workaround kernel into the Run-In image. He suggestion was that if we see a DCON problem that we pull the machine out of the rack, update the kernel and then re-add it back into the testing. -- Richard Smith <[EMAIL PROTECTED]> One Laptop Per Child ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: MP Build... FYI
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 confirm this. If Quanta sees this problem AT ALL in the production testing, there will be pressure to halt until further hardware/ software fixes are found. But no, there is not need to rush testing to ship with fixed bits right away. These machines will be upgraded before anybody sees the problem in the field. John On Nov 4, 2007, at 1:08 AM, Kim Quirk wrote: > 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 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 (where we only support sleep, > not automatic suspend) that it will be an extremely rare complaint > (roughly one tenth of the machines will show the problem once > every 5-20K resumes --- that's a lot of button pushes!). When the > display is powered down automatically for power conservation, > the code path should reinitialize the DCON correctly. > > It is a low severity bug, the user hits any key and the problem > clears up. > RMA requests for machines showing this problem can be answered with a > request that they upgrade their software. > > John > > On Nov 4, 2007, at 12:32 AM, Richard A. Smith wrote: > > > Jim Gettys 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, > because this addresses a suspected bug, the failure to > initialize the > DCON registers when power is re-applied to DCON. Build 625 is in > testing by Quanta right now. > > > > I just spoke with Arnold about the current 624/625 testing status. > > > > 624 testing was completed by Quanta and is ready to go. They > were not > > able to start testing 625 because there was no signed image. > > > > Current plan is for 624 to go onto the machines. > > > > _If_ we claim that 625 are the new bits and sign them for use on MP > > machines then Quanta can start testing 625 on Monday morning. > > > > They _might_ be able to complete the testing in time for MP but > Arnold > > says it will involve a lot of work from the .tw testing team. > > > > Gary and I will be headed to CSMC at 8pm Changshu time to look a the > > results of the > 24 hour DCON test. I'll report back the results > and > > then the team can make the call on going with 624 or trying to push > > for > > 625. > > > > -- > > Richard Smith < [EMAIL PROTECTED]> > > One Laptop Per Child > > ___ > > Devel mailing list > > Devel@lists.laptop.org > > http://lists.laptop.org/listinfo/devel > > ___ > Devel mailing list > Devel@lists.laptop.org > http://lists.laptop.org/listinfo/devel > ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: MP Build... FYI
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 rare complaint > (roughly one tenth of the machines will show the problem once > every 5-20K resumes --- that's a lot of button pushes!). I would say this makes 624 the obviously correct choice at this stage. -- Ivan Krstić <[EMAIL PROTECTED]> | http://radian.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: MP Build... FYI
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 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 (where we only support sleep, > not automatic suspend) that it will be an extremely rare complaint > (roughly one tenth of the machines will show the problem once > every 5-20K resumes --- that's a lot of button pushes!). When the > display is powered down automatically for power conservation, > the code path should reinitialize the DCON correctly. > > It is a low severity bug, the user hits any key and the problem > clears up. > RMA requests for machines showing this problem can be answered with a > request that they upgrade their software. > > John > > On Nov 4, 2007, at 12:32 AM, Richard A. Smith wrote: > > > Jim Gettys 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, > because this addresses a suspected bug, the failure to > initialize the > DCON registers when power is re-applied to DCON. Build 625 is in > testing by Quanta right now. > > > > I just spoke with Arnold about the current 624/625 testing status. > > > > 624 testing was completed by Quanta and is ready to go. They were not > > able to start testing 625 because there was no signed image. > > > > Current plan is for 624 to go onto the machines. > > > > _If_ we claim that 625 are the new bits and sign them for use on MP > > machines then Quanta can start testing 625 on Monday morning. > > > > They _might_ be able to complete the testing in time for MP but Arnold > > says it will involve a lot of work from the .tw testing team. > > > > Gary and I will be headed to CSMC at 8pm Changshu time to look a the > > results of the > 24 hour DCON test. I'll report back the results and > > then the team can make the call on going with 624 or trying to push > > for > > 625. > > > > -- > > Richard Smith <[EMAIL PROTECTED]> > > One Laptop Per Child > > ___ > > Devel mailing list > > Devel@lists.laptop.org > > http://lists.laptop.org/listinfo/devel > > ___ > Devel mailing list > Devel@lists.laptop.org > http://lists.laptop.org/listinfo/devel > ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: MP Build... FYI
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 (where we only support sleep, not automatic suspend) that it will be an extremely rare complaint (roughly one tenth of the machines will show the problem once every 5-20K resumes --- that's a lot of button pushes!). When the display is powered down automatically for power conservation, the code path should reinitialize the DCON correctly. It is a low severity bug, the user hits any key and the problem clears up. RMA requests for machines showing this problem can be answered with a request that they upgrade their software. John On Nov 4, 2007, at 12:32 AM, Richard A. Smith wrote: > Jim Gettys 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, because this addresses a suspected bug, the failure to initialize the DCON registers when power is re-applied to DCON. Build 625 is in testing by Quanta right now. > > I just spoke with Arnold about the current 624/625 testing status. > > 624 testing was completed by Quanta and is ready to go. They were not > able to start testing 625 because there was no signed image. > > Current plan is for 624 to go onto the machines. > > _If_ we claim that 625 are the new bits and sign them for use on MP > machines then Quanta can start testing 625 on Monday morning. > > They _might_ be able to complete the testing in time for MP but Arnold > says it will involve a lot of work from the .tw testing team. > > Gary and I will be headed to CSMC at 8pm Changshu time to look a the > results of the > 24 hour DCON test. I'll report back the results and > then the team can make the call on going with 624 or trying to push > for > 625. > > -- > Richard Smith <[EMAIL PROTECTED]> > One Laptop Per Child > ___ > Devel mailing list > Devel@lists.laptop.org > http://lists.laptop.org/listinfo/devel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: MP Build... FYI
Jim Gettys 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, >>> because this addresses a suspected bug, the failure to initialize the >>> DCON registers when power is re-applied to DCON. Build 625 is in >>> testing by Quanta right now. I just spoke with Arnold about the current 624/625 testing status. 624 testing was completed by Quanta and is ready to go. They were not able to start testing 625 because there was no signed image. Current plan is for 624 to go onto the machines. _If_ we claim that 625 are the new bits and sign them for use on MP machines then Quanta can start testing 625 on Monday morning. They _might_ be able to complete the testing in time for MP but Arnold says it will involve a lot of work from the .tw testing team. Gary and I will be headed to CSMC at 8pm Changshu time to look a the results of the > 24 hour DCON test. I'll report back the results and then the team can make the call on going with 624 or trying to push for 625. -- Richard Smith <[EMAIL PROTECTED]> One Laptop Per Child ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: MP Build... FYI
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 *not* get into the build. - Jim On Sat, 2007-11-03 at 21:07 -0400, Andres Salomon wrote: > 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, > > because this addresses a suspected bug, the failure to initialize the > > DCON registers when power is re-applied to DCON. Build 625 is in > > testing by Quanta right now. > > > > Please let me know immediately if this is an issue. > > > > - Mary Lou > > I don't believe 625 has been well tested yet; as far as I know, > it hasn't even gone through http://wiki.laptop.org/go/1_Hour_Smoke_Test > yet (if I'm wrong, please correct me). > > Once it has been signed by cscott, has been through a smoke test, and > Richard reports back about whether the DCON workaround succeeded on his > tests last night, I'll feel comfortable with 625 on MP machines. > ___ > Devel mailing list > Devel@lists.laptop.org > http://lists.laptop.org/listinfo/devel -- Jim Gettys One Laptop Per Child ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: MP Build... FYI
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 may be testing the wrong software right now. - Mary Lou On Sat, 2007-11-03 at 21:07 -0400, Andres Salomon wrote: > 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, > > because this addresses a suspected bug, the failure to initialize the > > DCON registers when power is re-applied to DCON. Build 625 is in > > testing by Quanta right now. > > > > Please let me know immediately if this is an issue. > > > > - Mary Lou > > I don't believe 625 has been well tested yet; as far as I know, > it hasn't even gone through http://wiki.laptop.org/go/1_Hour_Smoke_Test > yet (if I'm wrong, please correct me). > > Once it has been signed by cscott, has been through a smoke test, and > on his > tests last night, ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: MP Build... FYI
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, > because this addresses a suspected bug, the failure to initialize the > DCON registers when power is re-applied to DCON. Build 625 is in > testing by Quanta right now. > > Please let me know immediately if this is an issue. > > - Mary Lou I don't believe 625 has been well tested yet; as far as I know, it hasn't even gone through http://wiki.laptop.org/go/1_Hour_Smoke_Test yet (if I'm wrong, please correct me). Once it has been signed by cscott, has been through a smoke test, and Richard reports back about whether the DCON workaround succeeded on his tests last night, I'll feel comfortable with 625 on MP machines. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
MP Build... FYI
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, because this addresses a suspected bug, the failure to initialize the DCON registers when power is re-applied to DCON. Build 625 is in testing by Quanta right now. Please let me know immediately if this is an issue. - Mary Lou ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
