Re: First impressions of joyride-2280
Richard A. Smith wrote: Ton van Overbeek wrote: - The polling of the EC every 30 seconds has disappeared. At least it does not show up in the dmesg output. - More important, the touchpad seems to behave much better. May be related to the reduced polling of the EC. That makes sense if previously you were seeing jumpy touchpad behavior every 30 seconds or so. During EC command processing the kernel disables interrupts which means that you won't be responding to data from the touchpad. The update rate for the touchpad is 12ms so if you hang out for longer than 12 ms we think you lose motion data. I don't know how deep the buffer is on the touchpad but it does not seem to be very deep. The EC only buffers a single byte. I might have spoken too soon. Yesterday the touchpad jumping was back in joyride-2280. In my initial run of joyride-2280 the battery was full and the XO was connected to the mains power. This time I was on the battery and the battery was running down. In dmesg I noted a lot of EC traffic approximately every 2 minutes. Does the frequency of EC polling increase when the battery runs down? Also in the touchpad recalibration messages I see a lot of nested calibration requests: several other calibration queued while performing one. This does not seem right to me. Again, Update.1 (build 708) behaves much better. For me personally this (the touchpad problem) is the biggest show stopper for 8.2.0 !!! Ton van Overbeek ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: First impressions of joyride-2280
On Tue, 2008-08-12 at 09:17 -0400, Ton van Overbeek wrote: I might have spoken too soon. Yesterday the touchpad jumping was back in joyride-2280. In my initial run of joyride-2280 the battery was full and the XO was connected to the mains power. This time I was on the battery and the battery was running down. In dmesg I noted a lot of EC traffic approximately every 2 minutes. Does the frequency of EC polling increase when the battery runs down? This is normal. It's not polling as such. The hardware generates an interrupt when the battery charge drops by 1% (or when AC power is connected/disconnected, etc). The software then queries the EC to figure out the new charge levels and power status. Also in the touchpad recalibration messages I see a lot of nested calibration requests: several other calibration queued while performing one. This does not seem right to me. You should post some logs to clarify exactly what you mean. Again, Update.1 (build 708) behaves much better. The touchpad in joyride is much better behaved recently, but I agree that it has regressed since update1 (where I never saw a problem). Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: First impressions of joyride-2280
Daniel Drake wrote: On Tue, 2008-08-12 at 09:17 -0400, Ton van Overbeek wrote: I might have spoken too soon. Yesterday the touchpad jumping was back in joyride-2280. In my initial run of joyride-2280 the battery was full and the XO was connected to the mains power. This time I was on the battery and the battery was running down. In dmesg I noted a lot of EC traffic approximately every 2 minutes. Does the frequency of EC polling increase when the battery runs down? This is normal. It's not polling as such. The hardware generates an interrupt when the battery charge drops by 1% (or when AC power is connected/disconnected, etc). The software then queries the EC to figure out the new charge levels and power status. Also in the touchpad recalibration messages I see a lot of nested calibration requests: several other calibration queued while performing one. This does not seem right to me. You should post some logs to clarify exactly what you mean. I have posted a log (output of dmesg) of a joyride-2280 run attached to ticket #7788. See trac for a description. Please have a look there. I will now switch to a later joyride to see if the problem persists. Hope you can make sense of the dmesg output. Ton van Overbeek ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: First impressions of joyride-2280
On Aug 11 2008, at 11:09, Ton van Overbeek was caught saying: - TamTam sound seems to work OK for me. No hic-ups or noise. Odd given that we have yet to commit the changes for #7603. - After suspending with the power button however (screen goes off) and resuming with the power button, eth0 is down and does not come up automatically. Manually bringing it up with ifconfig and assigning it the same ip4 address as before allows to continue the external ssh session. Reproduced this here. I was able to just do an ifconfig up eth0 after resume and NM reinstantiated the connection to my AP and my TCP sessions stayed up but this obviously wrong behaviour. ~Deepak -- Deepak Saxena - Kernel Developer - [EMAIL PROTECTED] ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: First impressions of joyride-2280
Hi, - After suspending with the power button however (screen goes off) and resuming with the power button, eth0 is down and does not come up automatically. Manually bringing it up with ifconfig and assigning it the same ip4 address as before allows to continue the external ssh session. Reproduced this here. I was able to just do an ifconfig up eth0 after resume and NM reinstantiated the connection to my AP and my TCP sessions stayed up but this obviously wrong behaviour. I think I'm going to back out the change that tells NM to sleep and wake during sleep mode. NM should be doing all the same things it does to find a connection at startup, but it's clearly not working. Maybe we'll be able to re-enable this after we move to NM 0.7. This means that the XO won't look for a new connection when coming out of sleep, and will re-use whatever you were connected to before. - Chris. -- Chris Ball [EMAIL PROTECTED] ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: First impressions of joyride-2280
On Mon, Aug 11, 2008 at 02:15:28PM -0400, Chris Ball wrote: Hi, - After suspending with the power button however (screen goes off) and resuming with the power button, eth0 is down and does not come up automatically. Manually bringing it up with ifconfig and assigning it the same ip4 address as before allows to continue the external ssh session. Reproduced this here. I was able to just do an ifconfig up eth0 after resume and NM reinstantiated the connection to my AP and my TCP sessions stayed up but this obviously wrong behaviour. I think I'm going to back out the change that tells NM to sleep and wake during sleep mode. NM should be doing all the same things it does to find a connection at startup, but it's clearly not working. Maybe we'll be able to re-enable this after we move to NM 0.7. Just in case, this might just be http://dev.laptop.org/ticket/7740 - NM doesn't always notice changes because haldaemon doesn't always notice changes. I've been quite happy with how NM does its wake-up logic after coming out of XO sleep, despite [1]. I'm using joyride-2271, so if it's clearly not working, perhaps it's a recent regression? I can help joyride-bisect or something. I'd hate to have the baby thrown out with the bathwather, if indeed you do prefer NM to re-do its wake-up logic in this post-sleep case. This means that the XO won't look for a new connection when coming out of sleep, and will re-use whatever you were connected to before. Is there a way to force NM to re-scan (do it's wake behavior) in the GUI? If not, and if NM won't notice you've lost the AP and re-wake, your change will be useful when you just close/open and don't move around but annoying when moving locations. - Chris. Martin 1. http://lists.laptop.org/pipermail/devel/2008-August/017686.html pgpEBMH2qa8iI.pgp Description: PGP signature ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
