[00:09] <jjohansen> ogasawara: finally sent
[00:09] <jjohansen> sorry, its been a busy day
[00:09] <ogasawara> jjohansen: no worries
[01:29] <Sarvatt> ogasawara: big fat thumbs up on http://people.canonical.com/~ogasawara/lp644237/amd64/ here
[01:30] <Sarvatt> bah, I take that back, just needed more time to manifest - WARNING: at /home/ogasawara/maverick-amd64/ubuntu-2.6/arch/x86/include/asm/processor.h:1005 read_measured_perf_ctrs+0x78/0x90()
[01:33] <vanhoof> Sarvatt: try unplugging the power
[01:34] <vanhoof> Sarvatt: that seemed to trigger it in the bug report
[01:34] <vanhoof> not sure if thats true or not
[10:40] <tseliot> smb: do we have this commit in Maverick's kernel? http://git.kernel.org/?p=linux/kernel/git/x86/linux-2.6-tip.git;a=commit;h=54ff7e595d763d894104d421b103a89f7becf47c
[10:41] <smb> tseliot, I check to be sure but I think this came with some of the later stable updates which will not be intitially in
[10:42] <tseliot> smb: I'm asking as it's supposed to solve a problem with Nvidia's beta driver (that I plan on uploading after RC): http://www.nvnews.net/vbulletin/showthread.php?p=2320537
[10:44] <smb> tseliot, It was in 2.6.35.5 which is not included on its own. You may try to convince ogasawara to pick it pre-stable for the day-0 update.
[10:45] <smb> The upstream stable updates for 2.6.35.5..7 can only be uploaded when the day-0 is out in updates
[10:46] <tseliot> smb: ah, so things are frozen in the kernel now, I see
[10:47] <tseliot> a day-0 update would still be fine
[10:47] <tseliot> I'll discuss this with Nvidia too
[10:47] <smb> tseliot, As you _may_ have noticed from reading some mails. You are aware that we release on 10.10? ;-)
[10:47] <tseliot> smb: yes, kind of ;)
[10:47] <smb> Just checking :)
[13:46] <diwic> how can I run git blame but on an earlier version of the file than current HEAD?
[13:47] <smb> diwic, You can add a sha1 from the past
[13:48] <smb> git blame <sha1> <path to file>
[13:48] <smb> sha1 could also be a tag
[13:48] <diwic> hmm
[13:48] <diwic> it works now
[13:49] <diwic> I think you have to check out that old version through "git checkout" as well perhaps
[13:49] <smb> I did not think so
[13:50] <diwic> thanks anyway
[13:50] <diwic> :-)
[13:50] <smb> np :)
[15:31] <mpoirier> cooleney: I just checkout the lasted sound changes from TI - there is a lot of patches.
[17:50] <ogasawara> anyone seen JFo today?
[18:09] <jjohansen> ogasawara: hrmm, no but he was complaining of a really bad headache last night
[18:40] <ogasawara> Sarvatt: thanks for testing that kernel yesterday and also for posting a comment to the upstream bug report.  It looks like hpa has requested more info from you in the upstream bug report.  Care to follow up with him when you have a moment.
[18:40] <ogasawara> Sarvatt: https://bugzilla.kernel.org/show_bug.cgi?id=16322 (just for quick reference)
[18:41] <ubot2> bugzilla.kernel.org bug 16322 in Other "WARNING: at /arch/x86/include/asm/processor.h:1005 read_measured_perf_ctrs+0x5a/0x70()" [Normal,New]
[19:15]  * tgardner lunches. where has the day gone?
[19:20] <vanhoof> ogasawara: Sarvatt is out atm, i'll follow-up so that data gets posted
[19:20] <Sarvatt> vanhoof: I responded! :)
[19:21] <Sarvatt> waiting for this hour long build to finish to reboot with the messed up bios setting to get the info he wanted
[19:21] <vanhoof> Sarvatt: oh, i thought i saw an email saying you'd be afk for a while
[19:21] <vanhoof> maybe that was yesterday
[19:21] <Sarvatt> that was yesterday yeah
[19:21] <vanhoof> NM :D
[19:21] <vanhoof> see how much im paying attention!
[19:22] <vanhoof> Sarvatt: i think ogasawara is talking about the needinfo from https://bugzilla.kernel.org/show_bug.cgi?id=16322#c94
[19:22] <ubot2> bugzilla.kernel.org bug 16322 in Other "WARNING: at /arch/x86/include/asm/processor.h:1005 read_measured_perf_ctrs+0x5a/0x70()" [Normal,New]
[19:45]  * jjohansen -> lunch
[20:52]  * ogasawara lunch
[22:08] <sabdfl> hello rockstars
[22:08] <sabdfl> i heard i have you to thank for my longer battery life?
[22:08] <sabdfl> thank you :-)
[22:08] <sabdfl> quick question on iwlagn with 5300 chip
[22:09] <sabdfl> 03:00.0 Network controller: Intel Corporation Ultimate N WiFi Link 5300
[22:09] <sabdfl> that one
[22:09] <sabdfl> it fails every 3 minutes with N networks
[22:09] <sabdfl> firmware issue, Intel say they are working on a fix
[22:10] <sabdfl> workaround is simple:
[22:10] <sabdfl> mark@avril:~$ cat /etc/modprobe.d/intel-5300-iwlagn-disable11n.conf 
[22:10] <sabdfl> options iwlagn 11n_disable=1
[22:12] <sabdfl> upstream bug is at https://bugzilla.kernel.org/show_bug.cgi?id=16691
[22:12] <ubot2> bugzilla.kernel.org bug 16691 in Wireless "IPW5100: iwlagn broken with 2.6.34.x to 2.6.35.2 update" [High,New]
[22:12] <sabdfl> intel's talking about new firmware
[22:12] <ogasawara> sabdfl: thanks for the heads up, do you know if Intel mentioned an eta for a firmware update?
[22:12] <sabdfl> nope
[22:12] <sabdfl> seems they are worried about it
[22:13] <sabdfl> workaround is confirmed good on two different laptops at Chez Moi
[22:13] <ogasawara> sabdfl: I'll make sure we make a release note for this at the very least.
[22:13] <sabdfl> without it, all these intel-based laptops go bustificated quickly on n networks
[22:14] <sabdfl> i'd prefer we put the 11n_disable thing in, it's a real showstopper, and end-users won't find the workaround
[22:14] <ogasawara> sabdfl: other option would be to add a temporary quirk to module-init-tools till we get the newer firmware
[22:14] <sabdfl> right, 11n_disable should be removed when we get the new firmware
[22:15] <sabdfl> Comment #22 From wey-yi.w.guy@intel.com 2010-09-22 20:20:02
[22:15] <sabdfl> I don't want to close this bug and we are very active working on this and we
[22:15] <sabdfl> believe we already have a solution for it. We are in the process of figure out
[22:15] <sabdfl> how to deliver the experimental version of uCode for user to test it out.
[22:17] <ogasawara> robbiew: around?  ^^ 
[22:17] <robbiew> ogasawara: yep
[22:17] <ogasawara> robbiew: just a heads up about the above discussion
[22:18] <sabdfl> sorry robbie. this was all just going too smoothly :-)
[22:22] <robbiew> ogasawara: so planning on adding another 0-day update?
[22:24] <ogasawara> robbiew: it's rather an update to module-init-tools to add the temporary disablement.  we could do it as a 0-day upload or before if ok'd by the release team.
[22:25] <sabdfl> i bet we have a bug report for it
[22:26] <robbiew> ogasawara: hmm...seems harmless enough...as it's just an option (famous last words)
[22:27] <sabdfl> http://www.mail-archive.com/ubuntu-bugs@lists.ubuntu.com/msg2530831.html
[22:27] <ogasawara> robbiew: I haven't touched module-init-tools much, but I think I could try to throw together a test package for sabdfl to test
[22:27] <robbiew> sabdfl: ack, thnx
[22:28] <sabdfl> happy to test
[22:28] <robbiew> ogasawara: ok
[22:28] <sabdfl> affects Lenovo x201 and Dell TX2
[22:28] <sabdfl> at least, probably more
[22:29] <sabdfl> i don't think pure-n networks are that widespread yet, but still
[22:29] <sabdfl> only going to get more so
[22:30] <sabdfl> leeanne, feel free to bring me PPA for test or url to .deb. I'm packing it in for the evening but have time tomorrow. Am away over the weekend (kiko's wedding) and back Tues
[22:30] <sabdfl> ping me, not bring me
[22:30] <sabdfl> cheers
[22:30]  * robbiew didn't even know kiko was engaged
[22:30] <robbiew> lol
[22:31] <robbiew> ogasawara: I guess the only thing we have to remember is to disable this option once the fix arrives...but shouldn't be a big deal...n networks aren't THAT common yet
[22:32] <robbiew> obviously we need to release note it...so I'll attach bug 630748 to ubuntu-release-notes
[22:32] <ubot2> Launchpad bug 630748 in linux (Ubuntu Maverick) (and 1 other project) "iwlagn degrades quickly during normal wifi session (affects: 4) (dups: 1) (heat: 26)" [High,Confirmed] https://launchpad.net/bugs/630748
[22:33] <ogasawara> robbiew: I'll put a note in the changelog that the patch needs reverting once we get updated firmware.  I'll coordinate with tgardner to get it uploaded as I'm not sure I have upload rights for module-init-tools.
[22:34] <robbiew> ogasawara: ok...I targeted the bug to -updates, since a real FIX won't be available until then anyway
[22:34] <ogasawara> robbiew: ack