Re: 8.2.1 Thoughts
On Thu, Feb 05, 2009 at 07:03:08PM -0500, Chris Ball wrote: The first useful test is does the 767 version of the wireless driver work with WPA with the new firmware, since that'll suggest to us whether we have a bad driver or bad firmware. I've taken a unit with staging-26 and another with 767, and swapped the firmware files, then rebooted. I went through several cycles of connecting, suspending, resuming, rebooting. af642c0558e716e3cb4b3d449a938cd8 usb8388.bin.build-767 5e38f55719df3d0c58dd3bd02575a09c usb8388.bin.staging-26 The unit with staging-26 kernel and the build-767 wireless firmware did not change behaviour much. It still prompted for Wireless Key Required on boot, or on resume from suspend. But sometimes it would connect using the stored key if this dialog was dismissed and the connection retried. The unit with build-767 kernel and the staging-26 wireless firmware changed behaviour to become almost the same behaviour as a staging-26 system. It would only connect after reboot or suspend if the Discard network history button was used. Conclusion: symptom follows kernel *and* firmware? -- James Cameronmailto:qu...@us.netrek.org http://quozl.netrek.org/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: 8.2.1 Thoughts
On Thu, Feb 05, 2009 at 06:53:44PM -0500, Michael Stone wrote: 1) Daniel Drake discovered some annoying wifi regressions (#9235). We need to find root cause here, e.g. by bisecting the kernel patches added since 8.2.0 and testing each resulting kernel with both the new and the old firmware. Briefly, how is this done? Where can I get the current kernel source as a bisectable repository, and is it as simple as reverting a patch, make, scp the kernel to a unit, then reboot and attempt to reproduce? -- James Cameronmailto:qu...@us.netrek.org http://quozl.netrek.org/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: 8.2.1 Thoughts
Hi James, Briefly, how is this done? Where can I get the current kernel source as a bisectable repository http://dev.laptop.org/git?p=olpc-2.6;a=shortlog;h=testing (git clone git://dev.laptop.org/olpc-2.6 cd olpc-2.6 git checkout -b testing origin/testing) and is it as simple as reverting a patch, make, scp the kernel to a unit, then reboot and attempt to reproduce? Yes -- in fact, you could just scp the libertas.ko/usb8xxx.ko modules over, after make modules M=drivers/net/wireless/libertas. The changes we're interested in occurred between the 767 tag, which is commit f10b654367d7065d50e7d5e3649933453cea3102, and HEAD. This commit¹ is known to break WPA until this fix², so I'd recommend testing either neither or both of these commits. The first useful test is does the 767 version of the wireless driver work with WPA with the new firmware, since that'll suggest to us whether we have a bad driver or bad firmware. Thanks very much! - Chris. ¹: http://dev.laptop.org/git?p=olpc-2.6;a=commit;h=b0a7455f0b ²: http://dev.laptop.org/git?p=olpc-2.6;a=commit;h=a3e1b6fe88 -- Chris Ball c...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: 8.2.1 Thoughts
On Thu, 5 Feb 2009, Chris Ball wrote: Hi James, Briefly, how is this done? Where can I get the current kernel source as a bisectable repository http://dev.laptop.org/git?p=olpc-2.6;a=shortlog;h=testing (git clone git://dev.laptop.org/olpc-2.6 cd olpc-2.6 git checkout -b testing origin/testing) and is it as simple as reverting a patch, make, scp the kernel to a unit, then reboot and attempt to reproduce? Yes -- in fact, you could just scp the libertas.ko/usb8xxx.ko modules over, after make modules M=drivers/net/wireless/libertas. The changes we're interested in occurred between the 767 tag, which is commit f10b654367d7065d50e7d5e3649933453cea3102, and HEAD. it's actually easier than that. here's a LWN article that talks about automating the bisect, but it covers the basics as well. http://lwn.net/SubscriberLink/317154/d3d710e2a6d5e97e/ David Lang This commit? is known to break WPA until this fix?, so I'd recommend testing either neither or both of these commits. The first useful test is does the 767 version of the wireless driver work with WPA with the new firmware, since that'll suggest to us whether we have a bad driver or bad firmware. Thanks very much! - Chris. ?: http://dev.laptop.org/git?p=olpc-2.6;a=commit;h=b0a7455f0b ?: http://dev.laptop.org/git?p=olpc-2.6;a=commit;h=a3e1b6fe88 -- Chris Ball c...@laptop.org ___ 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: 8.2.1 Thoughts
On Fri, Feb 6, 2009 at 1:03 PM, Chris Ball c...@laptop.org wrote: This commit¹ is known to break WPA until this fix², so I'd recommend testing either neither or both of these commits. I don't know how far they are from eachother. You can tell git bisect to avoid them... but they may mask the problem commit. It's possible to synthesize a history that removes that known WPA breakage and lets you do a clean bisect. Overkill though. m -- martin.langh...@gmail.com mar...@laptop.org -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
