Re: New joyride build 2506 - q2e19
Mitch, Do you know if trac 8451 is going to be fixed for the G1G1V2 image being delivered to quanta? I think it is a bad idea delivering a self test that is broken. Could have bad PR implications. Just my 2 cents and 20 odd years of SQA experience on a diverse range of products. /Robert H. On Oct 4, 2008, at 9:31 PM, Mitch Bradley wrote: [EMAIL PROTECTED] wrote: Another strange thing I see with q2e19 is that at 19% battery, according to the battery gauge, the battery indicatory lamp started flashing red and orange. That would be a function of the EC code. Richard, any thoughts? On Oct 4, 2008, at 7:23 PM, Mitch Bradley wrote: Is q2e19 going to be included in the 8.2 release? The reason I ask is that trac 8451, test-all crash after the touchpad test, found in q2e18 is very disconcerting. q2e19 is a quick-turn release (half-day turnaround from head's up to release) for a pre-build of a limited run of machines with a new keyboard controller. It has new and barely-tested EC code plus a barely-tested change to the keyboard driver. It might not survive the weekend before e20 is issued. The mouse test problem that you found is likely to be e19's demise. It's possible that the problem could affect the keyboard in some cases. I have determined that the mouse test problem is caused by some device - either the EC or the touchpad - returning a RESEND code instead of an ACK in response to the first IDENTIFY request. I have never seen that happen before. It doesn't happen all the time; a lot of the time it works. I'm working on a fix. ___ 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: New joyride build 2506 - q2e19
The G1G1V2 build is going to get Q2E18. Do you know of brokenness in its selftest? [EMAIL PROTECTED] wrote: Mitch, Do you know if trac 8451 is going to be fixed for the G1G1V2 image being delivered to quanta? I think it is a bad idea delivering a self test that is broken. Could have bad PR implications. Just my 2 cents and 20 odd years of SQA experience on a diverse range of products. /Robert H. On Oct 4, 2008, at 9:31 PM, Mitch Bradley wrote: [EMAIL PROTECTED] wrote: Another strange thing I see with q2e19 is that at 19% battery, according to the battery gauge, the battery indicatory lamp started flashing red and orange. That would be a function of the EC code. Richard, any thoughts? On Oct 4, 2008, at 7:23 PM, Mitch Bradley wrote: Is q2e19 going to be included in the 8.2 release? The reason I ask is that trac 8451, test-all crash after the touchpad test, found in q2e18 is very disconcerting. q2e19 is a quick-turn release (half-day turnaround from head's up to release) for a pre-build of a limited run of machines with a new keyboard controller. It has new and barely-tested EC code plus a barely-tested change to the keyboard driver. It might not survive the weekend before e20 is issued. The mouse test problem that you found is likely to be e19's demise. It's possible that the problem could affect the keyboard in some cases. I have determined that the mouse test problem is caused by some device - either the EC or the touchpad - returning a RESEND code instead of an ACK in response to the first IDENTIFY request. I have never seen that happen before. It doesn't happen all the time; a lot of the time it works. I'm working on a fix. ___ 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: New joyride build 2506 - q2e19
I'm sorry, I've been reading e19 where you say e18. e18 is what is going to manufacturing. It's unfortunate that the selftest is broken, but we don't have time to re-qualify a new release. [EMAIL PROTECTED] wrote: Mitch, Do you know if trac 8451 is going to be fixed for the G1G1V2 image being delivered to quanta? I think it is a bad idea delivering a self test that is broken. Could have bad PR implications. Just my 2 cents and 20 odd years of SQA experience on a diverse range of products. /Robert H. On Oct 4, 2008, at 9:31 PM, Mitch Bradley wrote: [EMAIL PROTECTED] wrote: Another strange thing I see with q2e19 is that at 19% battery, according to the battery gauge, the battery indicatory lamp started flashing red and orange. That would be a function of the EC code. Richard, any thoughts? On Oct 4, 2008, at 7:23 PM, Mitch Bradley wrote: Is q2e19 going to be included in the 8.2 release? The reason I ask is that trac 8451, test-all crash after the touchpad test, found in q2e18 is very disconcerting. q2e19 is a quick-turn release (half-day turnaround from head's up to release) for a pre-build of a limited run of machines with a new keyboard controller. It has new and barely-tested EC code plus a barely-tested change to the keyboard driver. It might not survive the weekend before e20 is issued. The mouse test problem that you found is likely to be e19's demise. It's possible that the problem could affect the keyboard in some cases. I have determined that the mouse test problem is caused by some device - either the EC or the touchpad - returning a RESEND code instead of an ACK in response to the first IDENTIFY request. I have never seen that happen before. It doesn't happen all the time; a lot of the time it works. I'm working on a fix. ___ 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: New joyride build 2506 - q2e19
Mitch Bradley wrote: [EMAIL PROTECTED] wrote: Another strange thing I see with q2e19 is that at 19% battery, according to the battery gauge, the battery indicatory lamp started flashing red and orange. That would be a function of the EC code. Richard, any thoughts? Yes. That is one of the 3 new EC features in this release. I had to leave for my weekend before I could do proper changelog docs on the wiki. Alternating red/yellow battery LED is the critical voltage level warning. It means that your battery voltage has dipped to where its crossed the 5.7V threshold. It means that you are into the very non-linear voltage discharge curve.If it reaches 5.35V the EC powers off the voltage regulators for the rest of the system. 5.7V is a bit of a guess on my part. I tried to make it close enough to the hard shutoff that its meaningful yet far enough out so that there's enough time to do something even on batteries where the curve rolloff is very steep. This should normally appear when the battery is less than 10%. The hard shutoff occurs somewhere in the 4%-7% zone. [1] It should not have occurred at 19%. So one of 2 things happened: 1) EC Code bug. 2) Your SOC % reading does not reflect the actual state of the battery. Item 2 can occur 2 ways: 1) It sat on the shelf or in an XO turned off for a long time (ie weeks) 2) You have the charge balance problem in your cells. olpc-pwr-log will tell you which of the above is at fault. My bet would be its an early warning sign of 2.2 which is good since thats exactly one of the things this is supposed to try and detect. To test: Run your battery down until the EC shuts you off remove battery. Power up the XO without the battery once booted run olpc-pwr-log in a VT or disable idle-suspend Insert the battery Charge until full Ctrl-C restart olpc-pwr-log After you see the first line of log output pull the power cable Let it run till the EC shuts you off. Then look at the 2nd log file (the discharge cycle). The very last columns of numbers should end up in the -2800 to -3100 range. If not then your battery is suspect. Send me the 2 log files regardless because I want to review them. There's also some info here: http://wiki.laptop.org/go/XO_LiFePO4_Recovery_Procedure But if you really are only off by 10-13% then it maybe hard to tell looking at the charging log as described in that procedure. The log analysis on the wiki is for the most common charge balance failure symptoms. [1] The SOC % reported up to the host is based on the typical raw capacity of the battery not the usable capacity which is why the numbers for fully charged and empty are weird. Scaling this % so that its a sane 0% - 100% is on my list of changes for 9.1 -- Richard Smith [EMAIL PROTECTED] One Laptop Per Child ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: New joyride build 2506 - q2e19
Is q2e19 going to be included in the 8.2 release? The reason I ask is that trac 8451, test-all crash after the touchpad test, found in q2e18 is very disconcerting. On Oct 3, 2008, at 7:22 PM, Build Announcer v2 wrote: http://xs-dev.laptop.org/~cscott/olpc/streams/joyride/build2506 Changes in build 2506 from build: 2504 Size delta: -0.13M -bootfw q2e18-1.olpc2.unsigned +bootfw q2e19-1.olpc2.unsigned --- Changes for bootfw q2e19-1.olpc2.unsigned from q2e18-1.olpc2.unsigned --- + trac 8451 - Fixed test-all crash after touchpad test. + Multicast NAND updater test version included + trac 8737 - Better wlan scan output from APs with malformed data + Support for new keyboard controller + Handle ramdisk location changes required by new Linux kernels + trac 8451 - Fixed test-all crash after touchpad test. + Turn on serial console for secure boot -- This mail was automatically generated See http://dev.laptop.org/~rwh/announcer/joyride-pkgs.html for aggregate logs See http://dev.laptop.org/~rwh/announcer/joyride_vs_update1.html for a comparison ___ 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: New joyride build 2506 - q2e19
Another strange thing I see with q2e19 is that at 19% battery, according to the battery gauge, the battery indicatory lamp started flashing red and orange. On Oct 4, 2008, at 7:23 PM, Mitch Bradley wrote: Is q2e19 going to be included in the 8.2 release? The reason I ask is that trac 8451, test-all crash after the touchpad test, found in q2e18 is very disconcerting. q2e19 is a quick-turn release (half-day turnaround from head's up to release) for a pre-build of a limited run of machines with a new keyboard controller. It has new and barely-tested EC code plus a barely-tested change to the keyboard driver. It might not survive the weekend before e20 is issued. The mouse test problem that you found is likely to be e19's demise. It's possible that the problem could affect the keyboard in some cases. I have determined that the mouse test problem is caused by some device - either the EC or the touchpad - returning a RESEND code instead of an ACK in response to the first IDENTIFY request. I have never seen that happen before. It doesn't happen all the time; a lot of the time it works. I'm working on a fix. ___ 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: New joyride build 2506 - q2e19
[EMAIL PROTECTED] wrote: Another strange thing I see with q2e19 is that at 19% battery, according to the battery gauge, the battery indicatory lamp started flashing red and orange. That would be a function of the EC code. Richard, any thoughts? On Oct 4, 2008, at 7:23 PM, Mitch Bradley wrote: Is q2e19 going to be included in the 8.2 release? The reason I ask is that trac 8451, test-all crash after the touchpad test, found in q2e18 is very disconcerting. q2e19 is a quick-turn release (half-day turnaround from head's up to release) for a pre-build of a limited run of machines with a new keyboard controller. It has new and barely-tested EC code plus a barely-tested change to the keyboard driver. It might not survive the weekend before e20 is issued. The mouse test problem that you found is likely to be e19's demise. It's possible that the problem could affect the keyboard in some cases. I have determined that the mouse test problem is caused by some device - either the EC or the touchpad - returning a RESEND code instead of an ACK in response to the first IDENTIFY request. I have never seen that happen before. It doesn't happen all the time; a lot of the time it works. I'm working on a fix. ___ 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
