[05:06] <rafiyr> Anyone know off the top of your head head what sorts of stuff an hid driver should do before sending usb messages to tell the device to self calibrate?
[07:10] <amitk> morning all
[07:41] <cooloney> 'ERROR: ld.so: object 'libfakeroot-sysv.so' from LD_PRELOAD cannot be preloaded: ignored.'
[07:41] <cooloney> does anyone know this error when 'fdr binary-xxx'
[07:50] <amitk> cooloney: I saw it too, but haven't nailed down the reason yet. Remove fakeroot from your command
[07:54] <cooloney> amitk: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=544471
[07:54] <ubot2> Debian bug 544471 in fakeroot "cap_sys_nice on executable leads to ERROR: ld.so: object 'libfakeroot-sysv.so' from LD_PRELOAD cannot be preloaded: ignored" [Normal,Open]
[08:01] <cooloney> amitk: i am goting to 'sudo su' and build the image without fakeroot now
[08:02] <amitk> cooloney: it's probably worth asking on #ubuntu-devel when rest of EU wakes up
[08:02] <cooloney> amitk: https://bugs.launchpad.net/ubuntu/+source/libavg/+bug/474004, comment #15
[08:02] <ubot2> Launchpad bug 474004 in libavg (Debian) (and 1 other project) "Please sync libavg 1.0.1-1 from sid (affects: 2) (heat: 24)" [Unknown,Fix released]
[08:30] <anoteng> Anybody familiar with git-bisecting the ubuntu kernel? I'm suspecting I keep producing the same .debs over and over again…
[08:44]  * apw yawns
[08:47]  * lag tells apw to put his hand over his mouth
[08:50] <apw> heh
[08:56] <apw> gah its sooo hot here already today
[08:57] <lag> Yep. I may have to dig the fan out from the garage in the not too distant future 
[11:29] <apw> commit 6f12efee9e86b52193aa2e7e14ad013fc3153a8a
[11:29] <apw> Author: Douglas Gilbert <dgilbert@interlog.com>
[11:29] <apw> Date:   Sun Jan 3 13:51:15 2010 -0500
[11:29] <apw>     skip sense logging for some ATA PASS-THROUGH cdbs
[11:30] <apw> lag, so its that one in the stable tree
[11:30] <apw> just tell smb that that one is linked to your bug
[11:30] <apw> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.6.32.y.git
[11:30] <apw> lag, that is the remote i added to get the stable branch into my lucid repo
[12:23] <apw> ogasawara, i see the kernel-janitor moving things Fix Committed, is that your doing?
[12:58]  * apw waves to pgraner 
[12:58]  * pgraner gives apw a shout out
[12:58] <apw> man its quiet out here today
[12:58] <apw> it must be the hear
[12:58] <apw> heat
[13:16] <popey> apw: public holiday in some regions AIUI
[13:16] <apw> ahh yes in .eu some places, i'd forgotten thanks popey 
[13:30] <amitk> ogasawara: When're you freezing for A1?
[13:31] <amitk> I expect it will be based on 2.6.35-rc1?
[13:39] <apw> amitk, the kernel has to be in the archive by the 1st of June, so I'd guess either 28th or 31st at the very latest
[13:39] <apw> i would not be supprised if -rc1 has not yet gotten in by then
[13:39] <apw> or to put it a different way, i might recommend that we stick with .34 than ship A1 with 35-rc1
[13:39] <apw> as -rc1 is normally a crashy heap
[13:40]  * amitk agrees, just wanted to confirm
[13:40] <amitk> -omap mainline flavour is almost ready and I'd like it in A1
[13:43] <apw> amitk, and i can see no issue with you being .34 and master .35-rc1 either
[13:43] <apw> oh one branch ... doh 
[13:43] <apw> so it has to be synced :)
[13:43] <apw> you just add to the weight for .34 if yours is there and working :)
[13:45] <lag> bug 584330
[13:45] <ubot2> Launchpad bug 584330 in linux (Ubuntu) "hid-gyration does not support GYR4101US remote (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/584330
[13:45] <lag> Am I within my limits to just okay this patch?
[13:46] <lag> It looks harmless 
[13:46] <apw> yeah that looks like a simple addition of an ID, hard to have real regression potential
[13:46] <lag> I am, as yet, unsure of my bounties 
[13:46] <apw> if its not had a test kernel done and published I would recommend you do that
[13:46] <lag> boundaries 
[13:46] <apw> then get it on the kernel-team list ... looks sane to my eye
[13:46] <lag> Will do
[13:47] <lag> Cheers apw
[13:47] <amitk> apw: it boots with ogasawara's latest, needs some more cherry-picking to get all the goodness. But I think I could have something by tomorrow and then let mathieu/cooloney handle it from there..
[13:48] <apw> amitk, i assume this is planned to be pulled into master?
[13:49] <amitk> apw: yes
[13:49] <apw> amitk, how big is the delta ?  i assume much of it will go away as .35 formed ?
[13:50] <amitk> apw: a patch or two
[13:51] <amitk> and yes, I only intend to cherry-pick from mainline. This kernel should strictly be the mainline version of omap
[13:52] <apw> amitk, better than we could have hoped
[13:56] <apw> amitk, we should start the dialog about .34/.35-rc1 for A1 wtth ogasawara when she wakes up
[13:58] <amitk> apw: sure, I agree that it might be good for userspace folks if we stuck to 2.6.34 so they could start fixing up their stuff and we might even boot :)
[14:07] <apw> it would be a rare thing that A1 boots for sure
[14:18] <lag> How often is git://kernel.ubuntu.com/ubuntu/ubuntu-lucid.git updated? 
[14:18] <apw> that is live
[14:18] <apw> that is _the_ master
[14:22] <apw> ie. it updates instantly when it changes, and that is manual, when smb et al push
[14:23] <sconklin-gone>  /nick sconklin
[14:24] <lag> So daily? weekly?
[14:25] <lag> How do I find out the difference between my local repo and the remote one? git diff master origin/master? 
[14:25] <lag> I'm guessing that will diff the HEADs
[14:28] <amitk> git log master..origin/master should give your all the new commits IFF the origin tree hasn't been rebased.
[14:30] <lag> Thanks amitk
[14:31] <apw> lag, ?? lag> So daily? weekly?
[14:31] <amitk> I think he was asking how frequently we push to the master repo
[14:31] <apw> lag if its a bare repo, you only have 'remote things'
[14:31] <lag> amitk: Correct
[14:31] <apw> oh thats ust as needed
[14:32] <apw> when there is change, when something is ready and becomes committed, that occurs by pushing
[14:32] <lag> I'm looking for an average figure 
[14:32] <apw> before then its just an experiemnt in 'my' local repo
[14:32] <apw> its completely arbitrary, for development likely every day
[14:32] <apw> for a stable release likely not at all for weeks and then big batches of stuff pushed over a few days
[14:33] <lag> i.e. If I do a git log master origin/master 5 days after my last fetch and nothing's changed, I should be worried?
[14:33] <apw> when security is coming silence for a while then blammo a complete release is pushed
[14:33] <apw> origin/master is a just a copy of the remote side when you last ran fetch
[14:33] <apw> so it provides no information on upstream
[14:34] <lag> That's true
[14:34] <apw> its possible git remote show origin may tell you more
[14:34] <apw> but i tend to just git fetch
[14:34] <lag> Okay
[14:34] <lag> I'll work the rest out :)
[14:34] <amitk> lag: as a working practice, if you add all the trees you care about as remote, then you can start your day with a 'git remote update' to see what changed
[14:35] <lag> Now this is the stuff I need
[14:35]  * lag writes down new commands
[14:36]  * abogani just noticed than section_image parameter is totally ignored...
[14:36] <lag> Oh, it doesn't list, it updates?
[14:36] <lag> Is that like doing a fetch on all the branches?
[14:37] <amitk> lag: right
[14:38] <lag> And then to see what we just fetched we do a? git status, or git diff?
[14:39] <amitk> just see the result of the command? It will print out stuff if things changed
[14:39] <lag> Cool
[14:40] <amitk> you can then choose to merge the remote branches into your local ones, or rebase your work on top of them.
[14:40] <lag> or reset?
[14:41] <amitk> yeah, sometimes that too :)
[14:47] <JFo> pgraner, I just wanted to mention that I have yet to see a self-review in my allhands page.
[14:47] <JFo> been looking since the e-mails came out
[14:48] <pgraner> JFo: ack, lemme check with HR
[14:48] <JFo> k, thanks 
[14:49] <JFo> apw, yeah, I wasn't sure how to break those items out on the bug handling BP
[14:50] <apw> JFo, sorry had to reformat them to get them on the list at all
[14:50] <pgraner> JFo: you are due for one and HR is investigating :-)
[14:50] <JFo> apw, no sweat
[14:50] <JFo> pgraner, cool
[14:50] <apw> hope that it makes sense how i've done it
[14:50] <JFo> apw, it does
[14:52] <lag> What's are the fundamental differences between 'fdr binary-generic' and 'fdr binary-arch'?
[14:53] <apw> binary-generic only makes one flavour
[14:53] <apw> and it doesn't make any ancillary things
[14:53] <apw> like the per architecture linux-tools in later series
[14:54] <lag> So, if I'm not building for server etc, I need to do generic?
[15:02] <apw> generic is the common flavour for both i386 and amd64
[15:02] <apw> so not a bad base choice, cirtianly i build -generic for both of those for a test kernel, thats the 90% case
[15:02]  * apw lunches
[15:14] <bjf> moin all
[15:14] <manjo> bjf, gm
[15:14] <amitk> moin bjf, manjo
[15:14] <manjo> amitk, long time no hear buddy
[15:14] <amitk> just busy slacking off :)
[15:14] <manjo> heh
[15:15] <bjf> amitk, that can be quite time consuming
[15:16] <amitk> you bet, sometimes just doing the work is easier the pretending to
[15:21] <vanhoof> pgraner: ping
[15:21] <cnd> apw, ogasawara: do we want to try to pull in upstream multitouch changes for alpha 1, or would we rather just wait for them to be pulled when we update maverick to 2.6.35?
[15:31] <pgraner> vanhoof: poing
[15:31] <pgraner> pong even
[15:41] <JFo> moin bjf 
[15:41] <bjf> moin big guy :-)
[15:41] <JFo> :)
[15:44] <bjf> JFo, you didn't get to a point where you'd made any changes to the test ISO scripts did you? that's what I'm going to work on first this week
[15:46] <JFo> no, I didn't change anything
[15:46] <JFo> so they are still as-is
[15:48] <bjf> cool
[15:57] <pgraner> apw: can you look at bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/576601
[15:57] <ubot2> Launchpad bug 576601 in linux (Ubuntu) (and 1 other project) "[MacBookPro 7,1]mcp89 sata link reset fails, no disks detected (affects: 58) (heat: 334)" [High,Triaged]
[15:57] <apw> pgraner, whos complaining about that one now
[15:57] <apw> never ever ever buy a new macbook, period.
[15:57] <pgraner> apw: all the new mac book users
[15:58] <apw> pgraner, so probabally about 10 people, is it really the highest priority bug we have?
[15:59] <pgraner> apw: no, basically make sure its liked to upstream and have someone watch it in case a patch shows in the .35 window
[16:00] <apw> pgraner, i have produced some test kernels in the past which popey ean for me
[16:00] <apw> yeah it is already upstream
[16:00]  * popey wakes up
[16:00] <ogasawara> apw: yah I have a lp script to mark bugs fix committed as I pull patches in.  I should update my credentials to not be the janitor.
[16:00] <ogasawara> amitk: I'm freezing for A1 on Friday
[16:01] <ogasawara> amitk: you mentioned you might have something by tomorrow?
[16:01] <apw> ogasawara, i quite like it i wonder if it should be the norm :)
[16:01] <ogasawara> apw: cool, I'll leave it as it is then.
[16:02] <apw> ogasawara, we were wondering about whether we should not go to 35-rc1 should it appear before then, as -rc1 are notorious crack
[16:02] <ogasawara> cnd: will the multitouch changes you're wanting going to land in 2.6.35-rc1?
[16:03] <apw> so that A1 has a higher chance of booting
[16:03] <ogasawara> apw: yah, I'd be worried about rc-1 not booting if I rebased right before A1
[16:03] <cnd> ogasawara: I would guess so
[16:03] <amitk> ogasawara: I might have the -omap flavour done by tomorrow
[16:03] <cnd> ogasawara: let me see if it's been merged already...
[16:03] <apw> ogasawara, obviously its your call, not sure when -rc1 might drop anyhow
[16:04] <ogasawara> apw: I'm leaning towards not going with 2.6.35-rc1 even if it lands in time to rebase
[16:05] <bjf> when will we start producing daily live images for maverick? will that be alpha-1?
[16:05] <cnd> ogasawara: all the MT stuff that's in Jiri Kosina's HID tree have been merged into 2.6.35
[16:05] <bjf> "we" as in canonical
[16:06] <cnd> ogasawara: however, they aren't earth shatteringly awesome, so they can probably wait until you merge -rc1
[16:06] <ogasawara> cnd: ack
[16:08] <bjf> apw, thanks for running the irc meeting
[16:08] <apw> bjf, no worries.  i also wrote up a howto for running the meeting which you might be the right person to read over and correct
[16:09] <bjf> apw, you didn't read my email to you? i already had a wiki page written up on how to run the meeting
[16:09] <apw> ahh bottom
[16:09] <bjf> https://wiki.ubuntu.com/KernelTeam/RunningTheIRCMeeting
[16:09] <bjf> apw ^
[16:11] <apw> bjf, mine is basically the same ... so please do zap it and point the link to yours
[16:11] <bjf> apw, ack
[16:12] <manjo> JFo, regression meeting yes/no ?
[16:12] <apw> i note the email addresses arn't quite what you actually send to, you send it to ubuntu-devel and to kernel-team i think
[16:12] <bjf> apw, will review that
[16:12] <JFo> manjo, yes and no, we will be discussing possible changes to said meeting
[16:12] <apw> JFo, sounds good, when ?  
[16:13] <manjo> JFo, 12cdt ? 
[16:13] <JFo> little under an hour 
[16:13] <bjf> apw, i think i switched to ubuntu-platform because my email to ubuntu-devel gets moderated
[16:13]  * manjo bleeping google calender 
[16:13] <apw> though ubuntu-platform is an internal list
[16:13] <JFo> yeah
[16:13] <bjf> apw, ah
[16:13] <apw> JFo, so 16:00 UTC ?
[16:14] <manjo> JFo, my bleeping google calendar says its 2hrs from now 
[16:14] <JFo> sounds about right
[16:14] <JFo> manjo, mine could be wrong
[16:14] <JFo> but I don't think it is
[16:14] <manjo> why can't google have UTC calendar
[16:14] <apw> manjo, it does
[16:14] <apw> you just need to set it into that correctly, the entire calendar
[16:15] <bjf> msg chanserv op #ubuntu-kernel
[16:15] <JFo> need a slash :)
[16:15] <JFo> <-captain obvious
[16:15] <manjo> apw, I see only GMT in my settings 
[16:15] <apw> manjo, that is UTC within a few microseconds
[16:16] <apw> note GMT does not change in the summer, in the UK we move between GMT and BST (british summer time)
[16:19] <cnd> JFo: apologies if you've already answered this, but is there a regression review meeting today?
[16:19] <JFo> cnd, there is
[16:19] <JFo> we are discussing the changes in the meeting
[16:19] <cnd> ok
[16:20] <JFo> in a little over 40 minutes
[16:20] <cnd> JFo: where are we holding the meeting? (mumble, skype)?
[16:20]  * apw votes for mumble, jfo you can make a new meeting room
[16:20] <JFo> mumble shoud be fine
[16:20] <apw> and infact you already have one
[16:20] <JFo> :-D
[16:21]  * JFo is ahead of the curve
[16:21] <cnd> \o/
[16:34] <awe> manjo: did the fix for PowerDVD land in an SRU kernel for karmic?
[16:34] <awe> manjo: i.e. the ironlake buffering issue
[16:34] <manjo> awe, yes that fix is already in karic 
[16:34] <manjo> not sure what iron lake is
[16:34] <awe> could you point me at the commit and/or kernel tag?
[16:34] <awe> manjo: code name for arrandale integrated graphics
[16:35] <awe> aka i915
[16:35] <manjo> awe, karmic commit id is commit 78781dd5db00147ba99bb72eab1e6257b042aec8
[16:35] <crocket> ubuntu!!!
[16:36] <manjo> crocket, yeeayy!
[16:36] <crocket> When I boot 2.6.32 lucid with KMS on, linux dies right after KMS turns on.
[16:36] <awe> manjo, thanks!!
[16:36] <crocket> It happens even under recovery mode with KMS on.
[16:37] <crocket> I have to put "nomodeset" in every grub entry.
[16:37] <crocket> My graphic card is ATI Mobility X1250.
[16:37] <amitk> mpoirier: 2.6.34-based omap3 kernel - display and usb works, nand driver broken, but xubuntu works fine. Find it here -> http://people.canonical.com/~amitk/ti/
[16:37] <crocket> With nomodeset, ubuntu lucid is better than 9.10
[16:37] <amitk> mpoirier: I'll submit it for upload
[16:39] <amitk> mpoirier: 2.6.34-based omap3 kernel - display and usb works, nand driver broken, but xubuntu works fine. Find it here -> http://people.canonical.com/~amitk/ti/
[16:39] <manjo> crocket, yeah some of the older radeon cards have had isses 
[16:39] <manjo> crocket, kms+compiz support might be flakey on some of the older radeons
[16:40] <crocket> manjo, 3D games run perfectly fine in windows. I think linux needs much more driver supports than now.
[16:41] <crocket> I can even run halo 2 in windows vista.
[16:41] <crocket> manjo, compiz works fine while KMS kills linux.
[16:42] <manjo> crocket, sure drivers need more work
[16:42] <crocket> manjo, do you mean I have to buy a new laptop or a new desktop for that?
[16:42] <crocket> Can I put a new graphic card in my laptop?
[16:43] <crocket> KMS is the only pain in my ass.
[16:45] <stenten> The maverick kernel (2.6.35) is planned to include a lot of improvements to the ati drivers. Should be fixed then. For now, it's not really that hard to add "nomodeset" to /etc/default/grub.
[16:46] <crocket> stenten : I'm sad
[16:48] <awe> manjo: ping
[16:48] <manjo> awe, pong
[16:48] <awe> don't think the referenced bug fixes the issue we saw with powerdvd
[16:49] <awe> we were testing with the -18.55 kernel
[16:49] <awe> looks like this commit was much earlier, so should've been included in -18.55
[16:49] <awe> unless of course the commits for i915 that landed in -18.55 backed this out
[16:50] <manjo> awe, crap. ok I will take a closer look, but you see the two bugs and they have the exact same errors in dmesg 
[16:52] <crocket> Until 2.6.32-22, KMS used to kill linux.
[16:52] <crocket> With linux 2.6.34-020634-generic, KMS doesn't kill linux but doesn't work anyway.
[16:52] <crocket> I just see a distorted screen before I see a login screen.
[16:53] <crocket> I should have seen plymouth
[16:54] <crocket> Would KMS work on 2.6.35?
[16:54] <crocket> I doubt it
[16:54] <awe> manjo: don't bother...  the heat has been lowered on this one, as things work fine in lucid
[16:54] <crocket> It's just 0.0.01 version upgrade.
[16:54] <manjo> awe, there was a massive backport of s**t from 33 to karmic to fix a lot of these video related problems... 
[16:55] <anoteng> Anybody familiar with git-bisecting the ubuntu kernel? I suspect I keep producing the same .debs over and over again. Anybody care to take a look at my commands and check if I'm doing something stupid? http://ubuntu.pastebin.com/Rfif04jx
[16:57] <crocket> manjo, When do I need to use a graphic card sold since?
[16:57] <awe> manjo: understood...  as I mentioned though, no need to dig any deeper.
[16:57] <awe> thanks for your help
[16:57] <crocket> Oops, it is a weird sentence.
[16:58] <crocket> I don't know how to express it better
[16:59] <manjo> crocket, can you try the mainline kernel build? http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/current/
[17:00] <crocket> manjo, Is it newer than 2.6.34-020634-generic?
[17:00] <manjo> crocket, that is the latest mainline kernel ... and see if that kernel works for you, if it does then 10.10 might have those patches 
[17:00] <manjo> right it is the latest upstream kernel packaged for ubuntu
[17:01] <crocket> manjo, do you know a good download manager? FlashGot + cURL are awkward.
[17:01] <manjo> wget ? 
[17:01] <crocket> It is also a CLI.
[17:01] <crocket> I want a GUI application that downloads flash videos easily so that I can use it with FlashGot.
[17:02] <manjo> crocket, that is question for #ubuntu channel 
[17:02] <crocket> Gwget and downloader for X hide in traybar readily.
[17:02] <crocket> ok
[17:02] <crocket> Jesus I have 4 kernels in my system
[17:05] <crocket> manjo, mine is amd64 ubuntu
[17:06] <manjo> crocket, amd64 is generic name for x64 
[17:06] <manjo> crocket, we follow debian naming convention
[17:06] <crocket> ubuntu surpassed debian, though.
[17:06] <crocket> However debian still presents more control.
[17:06] <manjo> its just legacy naming convention
[17:09] <crocket> dpkg -i is more convenient than ubuntu GUI package installer when installing more than 2 packages at once.
[17:15] <crocket> manjo, KMS looks in 2.6.24-999, but linux doesn't die.
[17:15] <crocket> oops
[17:16] <crocket> KMS looks worse in 2.6.24-999 than in 2.6.24-020634
[17:16] <crocket> It means I still need UMS and uvesafb
[17:17] <crocket> I specified video=1024x768-24 in grub.
[17:17] <crocket> Should I omit it and try again?
[17:21] <crocket> manjo!!!
[17:21] <crocket> manjo, KMS worked briefly after I omitted "video=1024x768" option from grub entry.
[17:21] <crocket> How can I change the resolution of KMS?
[17:22] <crocket> plymouth showed for a second on 2.6.34-999.
[17:22] <crocket> I should try on 2.6.34-020634, too.
[17:24] <crocket> manjo, plymouth also showed for a second on 2.6.34-020634
[17:25] <crocket> manjo, are you there?
[17:34] <manjo> crocket, this is with the lucid kernel ? 
[17:35] <Sarvatt> crocket: KMS doesn't work on RS600 in lucid, it'll work once 2.6.33.3 or higher drm is merged soon though
[17:35] <Sarvatt> https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/544590
[17:35] <ubot2> Launchpad bug 544590 in linux (Ubuntu Lucid) (and 1 other project) "[RS600] video freeze with KMS (X and plymouth) (upstream patches available) (affects: 3) (dups: 1) (heat: 32)" [High,Triaged]
[17:36] <Sarvatt> i'm guessing you have a dell latitude XT since thats the only machine i've seen that chipset on, AMD pulled it from the market after the merger
[17:44] <amitk> ogasawara: apw: omap flavour pull request sent
[17:45] <amitk> mpoirier: ^
[17:45] <crocket> hmm
[17:46] <ogasawara> amitk-afk: thanks
[17:48] <crocket> How can I make KMS appear early?
[17:48] <crocket> I included "radeon" in /etc/initramfs-tools/modules, but I just see my monitor disconnected from computer for a while.
[17:49] <Sarvatt> echo FRAMEBUFFER=y | sudo tee /etc/initramfs-tools/conf.d/splash then sudo update-initramfs -u
[17:49] <Sarvatt> did you see what I said right before you left?
[17:49] <crocket> Sarvatt : no
[17:49] <Sarvatt> crocket: KMS doesn't work on RS600 in lucid, it'll work once 2.6.33.3 or higher drm is merged soon though
[17:49] <Sarvatt> https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/544590
[17:49] <ubot2> Launchpad bug 544590 in linux (Ubuntu Lucid) (and 1 other project) "[RS600] video freeze with KMS (X and plymouth) (upstream patches available) (affects: 3) (dups: 1) (heat: 32)" [High,Triaged]
[17:49] <Sarvatt> i'm guessing you have a dell latitude XT since thats the only machine i've seen that chipset on, AMD pulled it from the market after the merger
[17:50] <crocket> Sarvatt, I use 2.6.34-999 and -020634
[17:50] <Sarvatt> well I'm just saying why the stock lucid kernel doesn't work :)
[17:50] <crocket> Sarvatt, I installed linux 2.6.34-999 recently.
[17:51] <crocket> Sarvatt, It's sudo update-initramfs -u -k all
[17:52] <crocket> without -k all, initrd only for the most recent kernel is updated.
[18:51] <crocket> kernel 2.6.34-999 has a bug.
[18:51] <crocket> During installation of 2.6.34-999, I see this message http://www.pastebin.org/275287.
[18:51] <JFo> ***Kernel/Tagging has been updated***
[18:52] <crocket> 2.6.34-020634 doesn't have that weird messages
[18:52] <crocket> JFo : what?
[18:52] <JFo> that wasn't for you crocket :)
[19:06] <amitk> mpoirier: yes, that is the request (omap-mainline for maverick) that I sent to the ML
[19:06] <amitk> feel free to test it out and comment
[19:07] <mpoirier> humm...
[19:07] <mpoirier> what did you do exactly ?
[19:07] <mpoirier> the same as me ?
[19:07] <mpoirier> the rebase I mean.
[19:07] <amitk> mpoirier: no, I took leann's tree and simply enabled the omap3 config
[19:08] <amitk> we needed it ASAP
[19:08] <mpoirier> ok
[19:08] <amitk> Do you have HW now?
[19:08] <mpoirier> i have a beableboard here next to my computer.
[19:09] <amitk> cool, so I'll move over some lucid bugs for you to look at :)
[19:09] <mpoirier> but hold on...
[19:10] <mpoirier> I understand that leann's tree (maverick) is now enabled on beableboard after your intervention.
[19:10] <mpoirier> correct ?
[19:10] <amitk> correct, it will be after leann pulls my patches
[19:10] <mpoirier> ok...
[19:10] <mpoirier> So you started with Leann's tree correct ?
[19:10] <amitk> yes
[19:11] <mpoirier> interesting.
[19:11] <mpoirier> I rebased against linus' tree 
[19:12] <mpoirier> I was lead to beleive ARM was not in Leann's tree.
[19:12] <mpoirier> Once done, I was going to rebase with Leann's to get the latest and greatest changes for Maverick.
[19:13] <amitk> errm, what do you mean by "ARM was not in Leann's tree"
[19:14] <mpoirier> I must have misunderstood something somewhere.
[19:14] <mpoirier> I has a chat with apw
[19:15] <jjohansen> mpoirier: perhaps the variety of topic branches?
[19:15] <mpoirier> He suggested that I rebase ti-omap againts Leann's.
[19:15] <jjohansen> mpoirier: some are is in leann's tree not all
[19:16] <mpoirier> again, there must have been a misunderstanding somewhere.
[19:16] <amitk> mpoirier: nevermind, it was still a good exercise to get familiar with the process (kernel compile, abi, etc.) and the tools (git, etc.). And you are going to maintain this going forward. :)
[19:16] <mpoirier> well,,
[19:17] <mpoirier> I'll probably scrap what I have and rebase ti-omap against Leann's.
[19:17] <mpoirier> as an excercise.
[19:17] <mpoirier> I will then compare my work with yours.
[19:18] <mpoirier> unless you have something urgent for me to address.
[19:18] <amitk> probably not worth it at this point, your time will be better spent making it work well. ATM, there is some flakiness in our USB support
[19:18] <mpoirier> ATM ?
[19:18] <amitk> at-the-moment
[19:18] <mpoirier> ok.
[19:19] <mpoirier> is the flakiness in Ubuntu code or community ?
[19:19] <amitk> our configs
[19:19] <amitk> + possibly upstream code (not sure)
[19:19] <mpoirier> I assume you have bugs for this ?
[19:19] <amitk> Just grab the kernel from my people page, and run it on your beagleboard
[19:20] <amitk> mpoirier: https://bugs.edge.launchpad.net/ubuntu/+source/linux-ti-omap
[19:20] <mpoirier> that shouldn't  take long.
[19:20] <mpoirier> then what ?
[19:20] <amitk> mpoirier: feel free to assign to yourself whichever ones you like
[19:20] <mpoirier> ok, i get it.
[19:21] <mpoirier> one more thing.
[19:21] <mpoirier> davidm is sending me some gumsticks ?
[19:21] <mpoirier> are you aware of this ?
[19:22] <amitk> no, but good. That way you'll have more that one omap3 platform to test the kernel on
[19:22] <mpoirier> ok, sounds good.
[19:22] <amitk> there are lots of people on #ubuntu-arm that want support for various omap3-based boards
[19:23] <amitk> it might be worth it to see if we can help mainline some of those patches and get better board support
[19:24] <mpoirier> ok
[19:25] <mpoirier> I switched to private channel - did you get it ?
[19:43] <crocket> Hi
[19:44] <crocket> linux 2.6.34 apparently tries to acquire EDID from a monitor that doesn't exist.
[19:44] <crocket> http://pastebin.org/275497
[19:44] <crocket> Read this
[19:47] <maks_> crocket: irc is not good for bug reporting.
[19:47] <crocket> where do I report it?
[19:47] <maks_> launchpad if it is an ubuntu bug
[19:47] <maks_> upstream if you use vanilla bugzilla.kernel.org
[19:48] <crocket> It's 2.6.34-020634
[19:49] <crocket> It's linux kernel
[19:49] <maks_> whatever this is a dev channel for support go to -> #ubuntu
[20:02] <ogasawara> bdmurray: can you point us to your bug gravity web pages?
[20:12] <bdmurray> ogasawara: I stopped running it since bug heat was rather close.  Are you looking for the linux one specifically or something else?
[20:13] <ogasawara> bdmurray: we were interested in the linux ones, but we thought you had calculated gravity a bit differently than the bug heat.
[20:14] <bdmurray> ogasawara: some points were assigned based on the reporter for gravity and are not for bug heat
[20:15] <ogasawara> apw, JFo, cnd, manjo: ^^
[20:15] <JFo> hmmm, I think that is useful
[20:16] <bdmurray> Oh and actually bug tags too aren't used by launchpad
[20:16] <manjo> JFo, we could use that script and add some kernel specific logic to make it work
[20:16] <JFo> much like our thoughts on commenters.
[20:16] <JFo> indeed
[20:16] <JFo> what do you mean bdmurray?
[20:16] <manjo> bdmurray, what does that mean ? 
[20:16] <bdmurray> gravity also considered specific bug tags like regression-
[20:16] <bdmurray> heat does not
[20:17] <bdmurray> I seem to recall gravity being in arsenal...
[20:17] <bjf> bdmurray, is there a "gravity" attribute for a bug_task?
[20:17] <bdmurray> gravity was used on a per bug, not task, basis
[20:18] <bdmurray> def gravity(self): in arsenal_lib.py
[20:18] <bjf> bdmurray, don't see a gravity attribute for a bug object either
[20:18] <bdmurray> bjf: gravity is not the in the API its my thing which bug heat was based on
[20:19] <bjf> bdmurray, ah, so if we wanted something different, there isn't anywhere in a bug object that we could store a value
[20:19] <bdmurray> bjf: and arsenal's gravity seems to not check the reporter afaict
[20:20] <bjf> bdmurray, it's recalculated for each bug each time a script is run
[20:21] <bdmurray> bjf: yes
[20:21]  * manjo on coffee break
[20:21] <jjohansen> -> lunch
[20:22] <JFo> hmmm, that sounds useful
[20:23] <bjf> JFo, what sounds useful?
[20:23] <JFo> apw, I have moved bug reporting bits (both LP and upstream) to https://wiki.ubuntu.com/Kernel/Bugs
[20:36] <bdmurray> bjf: you could check date_last_updated before calculating the gravity
[20:50] <JFo> ogasawara, here is what I have in rough form so far: https://wiki.ubuntu.com/Kernel/BugReview
[20:50]  * ogasawara reads
[20:51] <JFo> going to step away and think about it for a bit and then come back and do some further cleanup/addition based on my notes
[20:51] <JFo> that was an initial brain dump
[20:51] <ogasawara> JFo: cool, I'll jot down any tweaks I might see
[20:51] <ogasawara> JFo: at least run them by you before editing
[20:51] <JFo> k, sounds good
[20:52]  * JFo goes to get some water
[20:59] <ogasawara> JFo: looks good as an initial start.  I'm sure you'll add more bits about what level 1, 2, 3 triage is and also maybe mention the bug load (ie when we go over 50 bugs) and how we may then use that as leverage to get more people working on bugs.
[20:59] <JFo> yep
[20:59] <ogasawara> JFo: should probably work in that link to the Tags page you had
[21:00] <ogasawara> JFo: but looks good so far
[21:00] <JFo> cool, thanks for looking
[21:00] <ogasawara> JFo: I'm happy to do a second pass of it later, just ping me
[21:01] <JFo> ogasawara, will do :)
[21:01] <apw> jfo yeah i think it might make sense to have three sections one per triage level listing the things-to-do in each phase
[21:01] <JFo> apw, yep, it is in the plan
[21:02] <JFo> also want to do a further definition of each tag so that we can explain a bit further what is covered by a tag like kernel-core
[21:03]  * ogasawara breaks for lunch
[21:03]  * JFo noshes chips and salsa and gets it all over his keyboard
[21:10]  * apw discovers he has done 5 hours of builds, and they are all wrong :/
[21:10] <apw> JFo, you need a keyboard hoover, as do i
[21:10] <JFo> indeed
[21:10] <JFo> :-/
[21:13] <JFo> ogasawara, I just remembered (from looking at my notes) that James Westby(?) asked if we want kernel oops turned back on?
[21:13] <JFo> I meant to ask you that at UDS
[21:13]  * JFo failed
[21:45] <JFo> apw, ogasawara, here is the rough guide to Triage levels: https://wiki.ubuntu.com/Kernel/TriageLevels
[21:45] <JFo> very brief, but can be added to
[21:48] <JFo> I've also made some changes to the https://wiki.ubuntu.com/Kernel/BugTriage initial paragraphs to draw attention to a few of these pages
[21:53] <apw> JFo, looks good, rough but has the right info ... good one
[21:54] <JFo> cool
[21:55] <JFo> apw, just put the header bar in and all
[21:55] <JFo> so it looks a bit better
[21:59] <apw> jfo coming together... i think we need a triage icon ...
[21:59] <apw> will see if i can find something
[21:59] <JFo> k
[22:00] <apw> i think its important enough to have its own 'space'
[22:00] <JFo> I agree
[22:00] <JFo> and it will only grow, I'm afraid
[22:01] <JFo> btw all, I am currently expiring bugs. apologies for the strain on your bugmail
[22:03] <jjohansen> JFo: no apologies needed for expiring bugs
[22:03] <JFo> heh
[22:04] <bjf> JFo, sweet, they are starting to roll in
[22:04] <JFo> yep, I like the verbose output too bjf 
[22:05] <JFo> it is very informative
[22:05] <bjf> JFo, i'm guessing you'll expire about 3500 from this first pass
[22:06] <JFo> I suspect that as well
[22:06] <JFo> at least that i mean :)
[22:08] <apw> JFo, how does https://wiki.ubuntu.com/Kernel/ look
[22:08] <JFo> love it
[22:08] <JFo> my little bug :-)
[22:09]  * amitk checks what changed...
[22:09] <apw> i think they are in the wrong order, my mind says 'debug', 'triage', 'development', 'advanced' but that'll do for today
[22:09] <apw> amitk, look at the menubar
[22:09] <JFo> I see what you mean apw
[22:09] <JFo> we can fix tomorrow
[22:09] <amitk> aah, you added bug triage
[22:10] <apw> yeah it is becoming pretty big area now
[22:11] <bjf> apw, you may not need "Ubuntu Kernel Main" on the main page (but maybe you're going for consistency)
[22:11] <amitk> bjf: it is a single menubar used across all pages
[22:11] <bjf> amitk, ah
[22:11] <akgraner> bjf, ping a ling a ling
[22:11] <bjf> akgraner, pong
[22:12] <bjf> akgraner, what can I do for your highness?
[22:12] <akgraner> you write up your weekly kernel meetigns right?
[22:12] <bjf> akgraner, correct
[22:12] <akgraner> bjf, hehe
[22:12] <akgraner> bjf, where all do you send those minutes?
[22:12] <akgraner> I think the news team isn't picking it up
[22:13] <akgraner> and I want to make sure it makes it to the right places
[22:14] <bjf> akgraner, I send to the kernel team public mailing list and another internal list as well as posting them to: http://voices.canonical.com/kernelteam/
[22:14] <apw> JFo, ok reordered them
[22:14] <JFo> cool
[22:14] <bjf> akgraner, however i'm having "issues" with the voices blog
[22:15] <akgraner> bjf, ahh ok :-) I will make sure to snag them from the kernel ML then
[22:15] <akgraner> :-)
[22:15] <apw> bjf, i did not post last weeks to voices correctly
[22:15] <apw> (or indeed at all)
[22:15] <bjf> apw, no worries, no body reads it anyway :-)
[22:15] <apw> :)
[22:16] <apw> if its like my googley one, then you can backdate stuff anyhow
[22:16] <JFo> ogasawara, do you still want to use the 'bitesize' and 'cherry-pick' tags?
[22:16] <JFo> I have not been
[22:16] <JFo> but i can
[22:20] <amitk> apw: now the menubar should look much prettier (OCD!)
[22:21] <akgraner> I love the new look of your wikis :-)
[22:22] <amitk> akgraner: we should make it pink
[22:22] <bjf> amitk, purple
[22:23] <akgraner> purple
[22:23]  * akgraner loves purple
[22:23] <akgraner> amitk, did you see the NC wikis - Carolina Blue there :-)
[22:23] <amitk> bjf: no brad, pink. we want to attract more women to ubuntu development :)
[22:24] <akgraner> amitk, me sends a virtual kick your way! :-P
[22:24] <amitk> ouch
[22:24] <bjf> amitk, how can I properly respond to that without getting in trouble?
[22:24] <akgraner> hehe :-)
[22:25] <akgraner> you all rock - I love wikis so let me know if I can help ya - I can't write content, but I'll help where ever else I can
[22:26] <JFo> akgraner, I may get you to look at the stuff I am working up 
[22:27] <JFo> it would be a review from a user standpoint, but I welcome construction or setup fixes/suggestions too
[22:27] <akgraner> JFo, just ping me..
[22:27] <JFo> k
[22:33] <JFo> pgraner, apologies for the delay, maverick-bug-handling is now pending approval
[22:44] <JFo> all I can say is GOOD LORD!! bug 88746
[22:44] <ubot2> Launchpad bug 88746 in linux (Fedora) (and 14 other projects) "ehci_hcd module causes I/O errors in USB 2.0 devices (affects: 64) (dups: 17) (heat: 620)" [Unknown,Invalid] https://launchpad.net/bugs/88746
[22:44] <JFo> there are 500+ comments on that bug
[22:44] <ogasawara> JFo: good luck with that one.  I think I tried killing it 3 times and then gave up.
[22:45]  * JFo eyes WontFix :)
[22:45] <JFo> the fun part will be getting it open with LP timeouts
[22:46]  * JFo disables redirection
[22:46] <JFo> ... and waits
[22:53] <manjo> bjf, how did you get channel ops ? 
[22:53] <bjf> god blessed me
[22:54] <bjf> manjo, it's so i can change the channel topic, no other reason
[22:54] <manjo> :)
[22:57]  * JFo admires bjf's hat
[22:58] <manjo> JFo, hat ? 
[22:58] <bjf> JFo, ?
[22:58] <JFo> ops hat
[22:58] <manjo> oops hat ? 
[22:58] <JFo> ops as in channel operations
[22:58] <bjf> JFo, i'm trying right now how to take the hat back off
[22:58] <JFo> heh
[22:59] <JFo> think it is deop bjf 
[22:59] <JFo> not sure though
[22:59] <bjf> JFo, thanks
[22:59] <JFo> np :)
[23:02] <manjo> mumble sounds like we are in the same room... its fantastic!
[23:03] <bjf> sometimes i'm such a curmudgeon that I even amaze myself
[23:05]  * manjo looks up  curmudgeon
[23:05] <bjf> manjo, you'll see my picture :-)
[23:05] <manjo> bjf, I think " a crusty, ill-tempered, and usually old man " role is already taken 
[23:06] <JFo> by bjf happily
[23:12] <JFo> vanhoof, did you and I discuss bug 564984 before?
[23:12] <ubot2> Launchpad bug 564984 in linux (Ubuntu) "r8169 fails to autonegotiate speed/duplex (affects: 5) (heat: 30)" [High,Triaged] https://launchpad.net/bugs/564984
[23:12]  * manjo looks around and thinks he needs some food 
[23:27] <bjf> ogasawara, that audio patch has not made it upstream, I'm inquiring why not
[23:28] <ogasawara> bjf: ok thanks
[23:28] <JFo> cnd, you hear from Jerone on bug 581312?
[23:28] <ubot2> Launchpad bug 581312 in linux (Ubuntu) "Unknown key fee[x] pressed (affects: 1) (heat: 20)" [Medium,Triaged] https://launchpad.net/bugs/581312
[23:29] <ogasawara> bjf: I'll add a note to that affect to the wiki, and mark your follow up as DONE
[23:29] <bjf> ogasawara, ok, will let you know what I find out
[23:31] <vanhoof> JFo: dont think so
[23:31] <vanhoof> JFo: on a call atm
[23:32] <JFo> k
[23:32] <JFo> no sweat
[23:32]  * achiang wonders if this tool might be helpful to folks: https://launchpad.net/laika
[23:32] <JFo> just noticed it was assigned to me from QA
[23:33] <JFo> achiang, not for me, that list would be huge
[23:33] <achiang> JFo: yeah, i think you're an extreme edge case. most normal people aren't touching thousands of bugs every week. ;)
[23:34] <JFo> heh
[23:34] <achiang> JFo: although, if you can think of a way to make that script interesting for you, let me know.
[23:34] <JFo> jjohansen, is OSCON at the same time as platform sprint/
[23:34] <JFo> achiang, will do
[23:35] <achiang> JFo: maybe there's a more intelligent way to slice the data rather than dumbly just saying, "durrr what did i touch?"
[23:35] <JFo> maybe, but it will require a bit of thought
[23:35] <jjohansen> JFo: yeah
[23:35] <JFo> sucks
[23:35] <jjohansen> JFo: July 19-23
[23:35] <JFo> I thought so
[23:36] <JFo> I'm debating not going to OLS since it would be that weekend before it looks like
[23:36] <bjf> achiang, does your script use the launchpad api?
[23:36] <achiang> bjf: yeah
[23:37] <achiang> bjf: it's slow and probably buggy, but it's in the 'works for me' stage
[23:37] <bjf> achiang, we do a lot of lpapi scripts, i'm looking at yours
[23:38] <achiang> bjf: cool. i was pointed to bughugger earlier, but that doesn't really do what i want
[23:38] <achiang> bjf: also, apologies in advance. i'm a C hacker, not a python guy, so i'm sorry if i make your eyes bleed
[23:38] <bjf> achiang, np, i do both
[23:39]  * JFo takes off for the day
[23:40] <achiang> bjf: sample output: http://pastebin.ubuntu.com/439082/
[23:41] <ogasawara> jjohansen: just want to re-touch bases with you. . . when 2.6.35-rc1 drops and I rebase, I'm gonna basically drop the apparmour patches we're currently carrying and go with what's upstream.  you'll then send me an updated pull-request with anything additional that we need correct?
[23:42] <jjohansen> ogasawara: yeah, since AA isn't upstream it will be the AA version I am trying to push up stream
[23:42] <ogasawara> jjohansen: ack
[23:42] <jjohansen>  plus the compatibility patches I am currently revising
[23:43] <jjohansen> ogasawara: when are you expecting to rebase?
[23:43] <ogasawara> jjohansen: even if -rc1 drops before the Alpha1 freeze I'm thinking I don't want to push an rc1 kernel for Alpha1, because I'm worried it wouldn't boot for some.
[23:44] <jjohansen> right
[23:44] <ogasawara> jjohansen: so I'll likely rebase after Alpha1, and we can make this an Alpha2 work item
[23:44] <jjohansen> sounds good
[23:45] <jjohansen> ogasawara: also if you want I can't take pull your maverick rebase and drop the AA patches on it so you have pull requests against maverick instead of upstream, what ever is easiest for you
[23:46] <ogasawara> jjohansen: yah, pull request against maverick would be easier for me if it's not too much trouble for you
[23:46] <jjohansen> ogasawara: nope I'll be happy to do it
[23:47] <ogasawara> jjohansen: awesome, thanks.  I'll let you know when I've rebased to 2.6.35-rc1