[04:55] <Sangeeth> Hello all!.. I am willing to join this team... Could someone guide me please....
[05:01] <Sangeeth> Could someone help me join this team???
[05:06] <Sangeeth> I had been included in this team by Tim Gardner... What's my next step?..
[05:08] <ikepanhc> eh wiki.ubuntu.com no response....
[05:09] <ikepanhc> Sangeeth: you may take a look at https://wiki.ubuntu.com/Kernel/ (but no response for me right now)
[05:10] <ikepanhc> Sangeeth: if you have any interesting idea, you may discuss here or on kernel-team mailing list, or discuss with anyone here :)
[05:11] <ikepanhc> Sangeeth: or propose any patch you think it will make Ubuntu Kernel better on kernel-team mailing list
[05:12]  * ikepanhc leaves a while for lunch
[05:18] <Sangeeth> I had been included in this team... Could some one explain me what's my next step...
[05:29] <Sangeeth> Somebody interested... A little guidance needed here...
[05:37] <JanC> Sangeeth: do you have kernel development experience?
[05:38] <Sangeeth> No... But i do have some knowledge on Kernel structure and working...
[05:39] <Sangeeth> JanC : No... But i do have some knowledge on Kernel structure and working...
[05:41] <JanC> well, I don't have any experience like that, but you might want to look at kernel-related bugs on launchpad about things that don't work, and see if you can find a solution (and of course propose that solution then)
[05:42] <Sangeeth> But, even I see some bugs, they are all completely strange to me... I need someone to guide me through the initial steps... I'm good at C , C++....
[05:43] <achiang> http://kernelnewbies.org/
[05:43] <JanC> the easiest bugs are those that already have a fix elsewhere, that way you can get used to how the kernel team works
[05:44] <JanC> and maybe achiang can help you some more  ☺
[05:45] <achiang> no, sorry, i've used up my help allocation for tonight. ;)
[05:45] <achiang> 22:45 here, and i'm winding down for bed.
[05:45] <achiang> Sangeeth: but yeah, start at kernel newbies, and see how far you get
[05:46] <JanC> achiang: meh, it's 6h45 here, so you're early to go to bed  :P
[05:46] <JanC> (okay, I don't have to get up early)
[05:47] <achiang> Sangeeth: actually, the suggested path to becoming a kernel developer is to get linux working perfectly on every piece of hardware that you own
[05:47] <Sangeeth> achiang : What is Kernel Newbies and where could i find it...
[05:47] <achiang> Sangeeth: um, did you see the url i posted about 9 lines up?
[05:47] <Sangeeth> achiang : Ya... It's there...
[05:48] <achiang> so go read it?
[05:48] <JanC> there might be some ubuntu-kernel specific stuff too (not sure if there is a "bite-sized" or "papercut" or similar tag in LP for the kernel?)
[05:49] <Sangeeth> achiang : Ok... It will be good if i am assigned with some minimal bugs in launchad... Could i get some help from you???
[05:49] <achiang> Sangeeth: what is it exactly you're trying to do?
[05:49] <JanC> Sangeeth: maybe check on https://wiki.ubuntu.com/Kernel/ if there is a specific tag for that
[05:51] <Sangeeth> achiang : I'm new to the open source community and I would like to get involved in the Kernel, the core area, than the other areas of ubuntu... But i have no idea, where to start...
[05:51] <jk-> Sangeeth: please read what JanC and achiang have wrote already, it is good advice.
[05:52] <Sangeeth> achiang : I'm good at C, C++... Will that be helpful in Kernel Development or Mod...
[05:52] <JanC> except the wiki seems to be down  ;-)
[05:52] <JanC> Sangeeth: the kernel is in C (no C++ allowed)
[05:52] <Sangeeth> JanC : Ya... :) But, no problem... I found it via cached pages of Google...
[05:53] <maco> JanC: hehe which is why i still never got around to learning C++ 
[05:53] <maco> and the wiki's not flat-out down
[05:53] <Sangeeth> JanC : Ok... Got it... C... Then what is my next step... 
[05:53] <maco> it's going in and out
[05:53] <achiang> Sangeeth: like i said: start by reading every page on http://kernelnewbies.org . second, get linux working perfectly on every piece of hardware you own. once you do those two steps, you'll have a much better idea of other places you can help contribute
[05:53] <Sangeeth> maco : :-))
[05:54]  * maco should read that site at some point
[05:54] <maco> actually should read it soon for that matter
[05:54]  * ikepanhc is back and reading
[05:55] <Sangeeth> achiang : What is the second you are mentioning??? I couldn't get it...
[05:56] <achiang> Sangeeth: if you own a laptop (or other computer), then make sure every piece of hardware is functional. make sure things like suspend/resume work. etc.
[05:57] <Sangeeth> achiang : Ok... What do you mean by suspend/resume???
[05:57] <JanC> achiang: "linux" already works on all hardware I own, that's exactly why I bought the hardware to begin with, so I hope Sangeeth has more "luck"...  ;-)
[05:57] <achiang> JanC: if you ask extremely broad questions, you get extremely broad answers. :-/
[05:58] <Sangeeth> achiang : The page you gave me is about the general Linux Kernel... Isn't the Ubuntu Kernel a bit extended/modified from the Linux kernel???
[05:59] <JanC> Sangeeth: you might want to learn to work with 'git' if you want to see the difference
[06:00] <achiang> Sangeeth: there are more similarities than there are differences.
[06:01] <Sangeeth> Janc : achiang : Please tell me the first step exactly to learn the Kernel of Ubuntu... Is it the Kernel Newbies...
[06:01]  * achiang is getting trolled?
[06:01] <JanC> AFAIK most changes are things like newer drivers
[06:02] <JanC> for ALSA & wireless & such
[06:02] <ikepanhc> Sangeeth: I will suggest in two ways - try to build a kernel with debian/rules command and be good in git
[06:03] <Sangeeth> Janc : Ok.... Could you lead me to a simple bug, where i could learn, what actually is happening and what is to be done....
[06:03] <jk-> achiang: perhaps?
[06:04] <Sangeeth> ikepanhc : Build?! I'm a perfect rookie... By the way, GIT? For what it is used?
[06:05] <JanC> Sangeeth: okay, start with learning get then (it's the version control system used for the kernel source code)
[06:05] <JanC> s/get/git/
[06:05] <achiang> jk-: maybe some AI researcher unleashed a new turing machine onto freenode
[06:05] <ikepanhc> Sangeeth: Ubuntu is based on debian, and you need to install a kernel image in debian command, so you need to know how to use debian/rules to build your kernel image
[06:06] <Sangeeth> JanC : ok... What is a version control system and what is the command you gave me?.. Should you use it at terminal???
[06:06]  * ikepanhc agrees with JanC
[06:07] <Sangeeth> ikepanhc : Could you explain it still simply...
[06:07] <ikepanhc> Sangeeth: well, start from git: http://en.wikipedia.org/wiki/Git_%28software%29
[06:07] <JanC> Sangeeth: there are some good introductions to git, and I would be surprised if they aren't linked somewhere from kernelnewbies and/or from the Ubuntu kernel wiki
[06:08] <Sangeeth> ikepanhc : Thanks...
[06:08] <Sangeeth> JanC : No worries.... I'm about to try wikipedia...
[06:09] <Sangeeth> ikepanhc : Ok about GIT... But what did you said in your first point??? Some Kernel image, debian commands??? What are they???
[06:10] <ikepanhc> Sangeeth: you can have git on your Ubuntu, just simply type: sudo apt-get install git-core
[06:10] <Sangeeth> ikepanhc : Thanks...
[06:11] <Sangeeth> ikepanhc : After I studied about GIT and other Kernel basics, to get involved in kernel dev or mod of ubuntu, where should i go...
[06:12] <ikepanhc> Sangeeth: the best way to stay on this channel and subscribe kernel team mailing list
[06:12] <Sangeeth> ikepanhc : Will i be assigned any bugs or modules of projects, by the team leader in launchpad???
[06:13] <Sangeeth> ikepanhc : I had already subscribed and got a few audio bugs??? I was wondering, how could i give a solution....
[06:13] <ikepanhc> Sangeeth: you will not, but you can assign bugs you are interested to yourself
[06:14] <ikepanhc> Sangeeth: if you have a solution, you may try to post the git commit on mailing list, or to LKML
[06:14] <Sangeeth> :( :( :(
[06:14] <Sangeeth> What is LKML???
[06:14] <JanC> Linux Kernel Mailing List
[06:14] <ikepanhc> linux kernel mailing list, the mail list for upstream kernel
[06:15] <JanC> if you subscribe to that, be prepared to get between 150 & 500 mails / day  ;)
[06:16] <Sangeeth> JanC : Ya... I already got 5... But, what should i do to solve them??? All are ALSA bugs...
[06:16] <achiang> Sangeeth: i'll say this one more time. you are asking questions that are ALREADY ANSWERED in http://kernelnewbies.org . that page provides much of the background information that you seek about kernel development. once you become more familiar with the entire process, the ubuntu-specific portions will become much more clear to you. as it is, right now, you are just wasting multiple people's time.
[06:17] <Sangeeth> ikepanhc : Is the git-core, you said, is enough or should i have to install some other things???
[06:17] <ikepanhc> Sangeeth: its more then enough
[06:17] <JanC> Sangeeth: well, you can check if that bug is fixed in upstream ALSA, or ask the person reporting the bug to try out a more recent kernel (there are .deb packages for that in a place listed on the kernel wiki)
[06:18] <Sangeeth> achiang : I'm sorry... As you describe, i'm a newbie and interested a lot on Ubuntu and its kernel... Sorry again...
[06:19] <JanC> Sangeeth: don't worry, it just needs a lot of work & time to learn everything  ;)
[06:19] <Sangeeth> JanC : Ok... But, how could i contribute to that bug???
[06:19] <Sangeeth> JanC : like solving the bug???
[06:19] <ikepanhc> the wiki seems back: https://wiki.ubuntu.com/Kernel/Dev
[06:19] <achiang> Sangeeth: yes, i understand that. we were all newbies once. everyone goes through this same process. that is exactly the reason why the community created that web page. so please do read it, and it will explain quite a bit
[06:20] <ikepanhc> Sangeeth: this is the major knowledge base of the kernel team, but start from the kernelnewbies.org will be a better idea
[06:21] <Sangeeth> JanC : A friend of mine is working on drizzle and uploading weekly patches assigned by his mentor... How could i be possibly able to contribute like the same to Ubuntu Kernel team...
[06:21] <JanC> Sangeeth: following everything discussed here & on the mailing list for some time might help too
[06:21] <JanC> Sangeeth: I'm not sure there are mentors who have much time  :-/
[06:22] <Sangeeth> JanC : His mentor actually is one of the developers of that project...
[06:22] <JanC> although many people will be happy to answer specific questions
[06:22] <Sangeeth> JanC : Isn't there any such projects undergoing in Ubuntu Kernel division???
[06:24] <JanC> Sangeeth: in theory, that should be kernel-newbies  ;)
[06:24] <Sangeeth> JanC : What are you exactly working at in the ubuntu kernel???
[06:25] <JanC> although in many cases, the best people to ask questions are the developers of the particular driver or kernel subsystem you're working on
[06:25] <Sangeeth> JanC : Whether you all in the team, divide the tasks between you or take up your own ideas and develop a patch???
[06:27] <JanC> Sangeeth: i'm not, I've just been following kernel development (remember I said I didn't have real experience with kernel development?)
[06:27] <Sangeeth> JanC : Ok... Have you done any patches or fixed some bugs???
[06:28] <JanC> not in the kernel
[06:28] <Sangeeth> JanC : In what else then???
[06:30] <JanC> Sangeeth: some small things in GParted, for example, but really, that's not really related to the kernel  ;)
[06:32] <Sangeeth> JanC : Ok... I know c, c++.. Is there anyways i could involve in dev/ patch dev of any apps or someother things...
[06:33] <Sangeeth> ikepanhc : Installed git through terminal... What's my next step??
[06:34] <ikepanhc> Sangeeth: well, https://wiki.ubuntu.com/Kernel/Dev gives you lots of information
[06:35] <Sangeeth> ikepanhc : Ok... Thanks...
[06:35] <JanC> Sangeeth: for things probably not related to the kernel, the patch review team might be a good place to start, I'm sure nigelb or some other person in #ubuntu-reviews could help you with that
[06:37] <Sangeeth> JanC   Achiang  ikepanhc  : Thanks a lot for all your info... I gained some knowledge about how to start with my expedition on Ubuntu Kernel.... Thanks a lot, once again...:)  :)  :)
[06:49] <orangey> hello all!
[06:49] <orangey> I'm trying to compile a new kernel
[06:49] <orangey> and I'm doing it with: sudo make -C /usr/src/linux-headers-`uname -r`  M=`pwd`
[06:50] <orangey> however, it will NOT compile this new file!
[06:50] <orangey> it DOES compile properly all the OLD files, though
[06:51] <jk-> orangey: you added a new file? or changed an existing one?
[06:51] <orangey> added a new one
[06:51] <orangey> usb_wwan.c
[06:51] <jk-> did you update the Makefile too then?
[06:52] <orangey> yes
[06:52] <orangey> I've updated every makefile I can find
[06:52] <jk-> you only need to update one
[06:52] <orangey> well, I updated two : )
[06:52] <orangey> one in the headers directory
[06:52] <orangey> and one in the directory I was working in
[06:56] <orangey> if I were to get it to only compile this ONE file (it truly compiles every other one), I think I'd be home free
[06:58] <orangey> thoughts?
[07:56] <kraut> moin
[08:29]  * apw yawns
[08:29]  * smb yawns back
[08:30]  * cooloney yawned 6 hrs ago
[08:30] <apw> heh
[08:30] <smb> No way to win this
[08:30] <cooloney> lol
[08:30] <apw> yay emergency budget day ... say goodbye to income
[08:30] <cooloney> how's going, folks
[08:31] <jk-> emergency budget day?
[08:31] <smb> apw, Your MPs neet new things?
[08:31] <apw> yeah we are broke, time to suck those with money harder to fix it
[08:33] <smb> Heh, ours suck those with not so much money. Probably hoping they cannot afford to retaliate
[09:06]  * smb waves to cking 
[09:06]  * cking waves to all
[09:07] <jk-> hey cking
[09:10] <cking> jk-, howdy do
[09:11]  * jk- is lost in a forest of topic branches
[09:11]  * apw does not like the sound of that
[09:12] <jk-> apw: s'ok, I won't be asking you to merge them :D
[09:13] <jk-> I need a 'git replant' - like rebase, but move a set of sub-branches to a later commit
[09:15] <apw> jk-, heh sounds handy
[09:18] <jk-> should've taken that graph theory unit at university :D
[09:32] <smb> apw, Do you know were to find entry information to JFo's community bug days? I only seem to find quite old pages.
[09:33] <apw> smb, hrm no i've not remembered seeing any output regarding bug days recently
[09:33] <smb> jk-, I got a rebase branch script but it might be too much geared towards releasing...
[09:33] <smb> apw, Hmmm, ok. So maybe I point people asking me about contributing directly to his ... backside
[09:35] <apw> smb, heheh yeah something like that
[10:16] <RAOF> apw: Yo!  I'm looking at your WIs on http://tinyurl.com/24yqzyw - have you looked at them, and I want to discuss whether you think it still makes sense to do them.
[10:17] <apw> RAOF, yo ...  have been meaning to talk to you about those, last i looked the patches were all over the place
[10:17] <apw> have they settled down?
[10:19] <RAOF> I don't think they're moving much any more, but I think that's in part because they're slightly dead.
[10:20] <apw> hrm, thats not good.  if they are dead do they do us any good any more?
[10:20] <apw> these were sorting out the regressed i8xx platforms iirc
[10:22] <RAOF> Not all the regressed i8xx platforms, actually - there's a similar bug for i845 and i865 that I don't think the patch addresses.
[10:22] <apw> i suspect i am vague enough that i am reliant on your oppinion
[10:24] <RAOF> For Maverick I've got the help of an intel dev to just plain re-add the EXA acceleration stuff which isn't reliant on the AGP interface working properly (which it doesn't on the i8xx stuff).
[10:24] <apw> heh, did they recently remove that?
[10:25] <RAOF> No - ages ago.  In 2.9 I think, which we've carried since Karmic.
[10:25] <RAOF> These i8xx problems weren't a regression in _Lucid_ , except as compared to Hardy :)
[10:27] <apw> ahh i see ... so do you think we'll get them back in Maverick, i assume not, NN perhaps ?
[10:28] <RAOF> I'm confident we'll get a usable -intel driver that doesn't use GEM for those cards in Maverick, yes.
[10:28] <apw> i sense you are suggesting these patches are not worth persuiing ?
[10:28] <apw> cirtainly any work i don't have to do is a bonus for me
[10:28] <RAOF> :)
[10:30] <RAOF> It might be nice for Lucid to have the v9 patch via an SRU, but I understand if that's hugely scary.  I don't think that we need to carry it for Maverick.
[10:30] <RAOF> And by “nice” I guess I mean “in the land of unicorns and unlimited kernel-team manpower”.
[10:31] <hyperair> lol
[10:31] <apw> RAOF, i have a note here which says "major pre-requisites" when i looked at it ... hmmm
[10:31] <RAOF> Hm.  Dinner time!
[10:32] <RAOF> apw: That might have something to do with the patch splitting the intel-agp modules into different pieces.
[10:42]  * apw drops offline for a bit
[11:17] <apw> RAOF, yeah there was some re-jigging for sure in there
[13:01] <abogani2> What should be effetc of the "do_common_headers_indep" option?
[13:06] <apw> abogani2, it defines whether the 'flavour independant headers' are generated in the binary-indep pass on i386 or in an architecture specific pass
[14:24] <tseliot> apw: does it hurt if I do "debian/rules updateconfigs" after changing the code?
[14:26] <tseliot> mjg59: BTW the patch works, a bug in grub2 prevented me from using acpi_osi=\"!Windows 2009\". The video switch key works fine with my patch now
[14:26] <mjg59> Ha
[14:26] <mjg59> Ok, excellent
[14:26] <mjg59> Want to send it upstream?
[14:27] <cking> tseliot, what was wrong with grub2?
[14:27] <mjg59> cking: It eats the quote marks
[14:28] <tseliot> mjg59: sure, I'm bugging Alex about that too. Where should I send it? (of course I'll give credit to both of you guys for your help)
[14:28] <cking> doh
[14:28] <tseliot> cking: yes, that's the problem
[14:28] <tgardner> apw, this is quite a handy reference: http://book.git-scm.com/index.html, I didn't realize it existed.
[14:28] <smb> tseliot, When you did not change any options it should not hurt. But you can check afterwards with git status to see if it has. The stuff in debian.master/configs should be unchanged
[14:30] <mjg59> tseliot: drm-devel@lists.freedesktop.org
[14:30] <mjg59> tseliot: You'll need to send it with a Signed-off-by: line. See the SubmittingPatches doc in the kernel source.
[14:30] <tseliot> smb: ah, ok. I was only asked about external firmware support when I ran that command (and I pressed Enter)
[14:31] <tseliot> mjg59: ah, drm-devel, not dri-devel?
[14:31] <smb> tseliot, If you get asked then it likely changed something.
[14:31] <mjg59> tseliot: Sorry, dri-devel, yeah
[14:32] <tseliot> smb: that's what I thought
[14:32] <tseliot> mjg59: ok, I'll send it there then, thanks again for your help. It's been a good learning experience for me
[14:37] <tseliot> mjg59: does this commit comment look good to you? http://pastebin.ubuntu.com/452930/
[14:39] <mjg59> Yeah, sounds fine
[14:43] <tseliot> good
[15:18] <mpoirier> ogra ?
[16:08] <JFo> bjf, you around?
[16:09] <bjf> JFo, yup
[16:09] <JFo> just saw the tag kernel-workflow. what is that?
[16:09] <bjf> JFo, not me
[16:09] <JFo> hmmm
[16:10] <bjf> JFo, going hunting in the scripts
[16:10] <JFo> looks like the new script added it
[16:10] <JFo> Bug 592039
[16:10] <ubot2> Launchpad bug 592039 in linux (Ubuntu) "Please enable vmware-balloon driver in kernel config (affects: 1) (heat: 387)" [Undecided,New] https://launchpad.net/bugs/592039
[16:10] <JFo> err rather process-new
[16:11] <bjf> JFo, i just grep'd the scripts on my system and didn't find that string
[16:11] <JFo> interesting
[16:11]  * JFo digs
[16:12] <bjf> JFo, i'm pulling down a new version
[16:12] <JFo> k
[16:14] <bjf> JFo, not found
[16:14] <JFo> very odd
[16:14] <JFo> because it is saying it was added by me along with a kj-triage
[16:14] <JFo> which means it is a script doing it
[16:14]  * JFo digs further
[16:15] <bjf> JFo, we do look for a "workflow" tag but we don't add one
[16:15] <JFo> very odd
[16:15] <bjf> JFo, grep your scripts for it
[16:15] <JFo> I am
[16:16] <JFo> none have it
[16:26] <ogasawara> aight, dudes we need a status check for A2 work items (ie will they be done or not in time for the milestone)
[16:27] <ogasawara> apw: review the i8xx patch ?
[16:27] <ogasawara> apw: produce a PPA for the i8xx patch to allow testing?
[16:27] <ogasawara> apw: enable linux-tools for mainline builds
[16:27] <ogasawara> apw: help abogani mockup -preempt derivative for universe?
[16:28] <ogasawara> apw: Address assigned set of Ubuntu Patches?
[16:28] <ogasawara> apw: evaluate union-mount as a replacement for AUFS?
[16:28] <ogasawara> apw: investigate whether upstream would accept mounting /proc and /sys automatically ?
[16:28] <ogasawara> apw: I imagine some of those can be pushed to A3 as they're not A2 release critical
[16:28] <apw> ogasawara, yeah let me get at the list and push some out
[16:29] <ogasawara> apw: sweet, thanks
[16:29] <ogasawara> cking: Investigate situation with Intel graphics drivers on EFI? Will we be able to mark that work item complete by A2?
[16:30] <ogasawara> cnd: LP: 333990 : [Karmic]Please enable PCI express ASPM (powersave) (pm-utils-powersave-policy) ?
[16:30] <ogasawara> cnd: seems you're working on that bug, think the fix will land in pm-utils by A2?
[16:30] <ogasawara> bug 333990
[16:30] <ubot2> Launchpad bug 333990 in linux-2.6 (Debian) (and 4 other projects) "[Karmic]Please enable PCI express ASPM (powersave) (affects: 3) (heat: 28)" [Unknown,Unknown] https://launchpad.net/bugs/333990
[16:30] <ogasawara> hrm, no bot
[16:30] <ogasawara> manjo: blacklist old firewire stack & enable new stack ?
[16:31] <ogasawara> manjo: add basic tests to kernel-qa to test new firewire stack.
[16:31] <ogasawara> manjo: how's the firewire stack changes coming?
[16:31] <cnd> ogasawara: for the ASPM bug, the fix will come in the form of a new version of pm-utils
[16:31] <cnd> the new version was just released this weekend
[16:31] <ogasawara> cnd: cool
[16:31] <cnd> as soon as debian packages it, we can copy it over
[16:31] <cnd> but I don't know if that will be before A2
[16:32] <tgardner> cnd, debian sync is done on thursday, so likely not
[16:32] <ogasawara> cnd: sounds like it's on it's way, so we can push to A3 if we have to
[16:32] <cnd> at the same time, we will have to deprecate pm-utils-powersave-policy
[16:32] <Q-FUNK> apw: about bug #241307 why did you unsubscribe yourself?  Plenty of info was provided to track the source of the issue, down to a specific release with the exact diff.
[16:32] <ubot2> Launchpad bug 241307 in linux (Ubuntu Hardy) (and 1 other project) "[Geode SC] [DBE60] kernels >= 2.6.22 fail to boot [A20 interrupt] (affects: 5) (heat: 32)" [High,New] https://launchpad.net/bugs/241307
[16:33] <ogasawara> JFo: your work items for the firewire stack are likely dependent on it being enabled in time for A2, so I might retarget those to A3
[16:33] <apw> Q-FUNK, i unsubscribed myself because I didn't have time to work on the 159 bugs I had ended up subscribed to, it was giving a false impression i was working on them and preventing anyone else in the team looking at them
[16:33] <JFo> ogasawara, sounds good :)
[16:34] <JFo> thanks for letting me know 
[16:34] <Q-FUNK> apw: ok. fair enough.  it's just that it becomes rather frustrating to file bugs, get involved in tracking down the cause and not see the bug acted upon.
[16:34] <JFo> ogasawara, are those on a blueprint somewhere?
[16:35] <ogasawara> JFo: https://blueprints.edge.launchpad.net/ubuntu/+spec/kernel-maverick-firewire-stack
[16:35] <JFo> thank you :)
[16:35] <apw> Q-FUNK, i cannot disagree with you there, i block unsubscribed to bugs I had not touched for months, there was no thought involved
[16:36] <Q-FUNK> apw: understood. :)  my comment mostly was about how some bugs simply never get acted upon.
[16:36] <apw> Q-FUNK, though the last commentary i can see in there says that commenting out some code used to work but doesn't
[16:36] <apw> anymore, so its not clear we have a real fix in there
[16:37] <Q-FUNK> apw: right, because there's been more drastic changes to that code since then, so we can no longer revert a specific commit.
[16:38] <Q-FUNK> apw: which is only predictible.  the longer it takes to react to a bug, the higher the probabilities that upstream furhters hacks the code to a point where reacting becomes a PITA.
[16:38] <apw> Q-FUNK, indeed sadly.. not having such a beast makes it hard to debug
[16:39] <apw> Q-FUNK, i think i replied to you on another of your bugs just a sec ago, completley unrelated, about /proc/config.gz
[16:39] <Q-FUNK> apw: yes, you did and I responded. :)
[16:40] <apw> smb, you got a hardy install ?  can you check your /boot/configs-* are full configs for me
[16:41] <apw> Q-FUNK, cirtainly all the ones  I have access to here are complete
[16:41] <Q-FUNK> ogasawara: I noticed that you added a task to the libc6 blueprint.  is this about merging the NOPL patch?
[16:41] <smb> apw, I got one. Give me a min to boot up
[16:42] <ogasawara> Q-FUNK: we're not quite sure what that work item will entail as the spec/blueprint it not yet written, ie i'm blocked
[16:42] <apw> smb, the ones on chinstrap look to be complete
[16:42] <Q-FUNK> ogasawara: I'm rather worried to find that i686-only libc6 binaries have already been pushed and approved, despite a lack of complete paper trail.
[16:43] <ogasawara> Q-FUNK: you probably want to take it up with doko as it's his spec
[16:43] <Q-FUNK> ogasawara: I did. his response wasn't too cooperative.
[16:44] <ogasawara> Q-FUNK: not sure what you'd like me to do about it?
[16:44] <smb> apw, There is lots of stuff in there. Anything that would indicate not-full configs?
[16:44] <Q-FUNK> ogasawara: since one of the possible solutions seems to be to merge a kernel patch to emulate the mission CPU instruction, I think that this is something that you could affect?
[16:45] <mjg59> A kernel patch that's been rejected by upstream
[16:45] <Q-FUNK> mjg59: without much of any justification, at that.
[16:45] <ogasawara> Q-FUNK: possibly, but until I see them make that request I'm not going to act on it
[16:46] <apw> as in a patch to emulate CMOV or whatever ?
[16:46] <Q-FUNK> ogasawara: noted.
[16:46] <Q-FUNK> to emulate NOPL
[16:46] <apw> presumably they said, just compile your kernel for i586, and rejected it
[16:47] <Q-FUNK> http://marc.info/?l=linux-kernel&m=126748102722641&w=2
[16:48] <mjg59> apw: Upstream doesn't want single-issue emulation
[16:48] <mjg59> They want a more generic framework
[16:48] <Q-FUNK> it's a chicken and egg case. either fix gcc to stop using NOPL with -m686, fix libc6 to produce finer optimization that won't break support for Geode, or patch the kernel to emulate the missing instruction.  
[16:48] <apw> ahh the perfection argument
[16:49] <Q-FUNK> right now, everyone is throwing the baby around.
[16:49] <mjg59> It's not actually gcc that's the issue - it's binutils
[16:50] <Q-FUNK> upon initial reading, it indeed seemed to be GAS.  now, I'm not so sure.
[16:50] <Q-FUNK> these guys have encountered the same issue and have a whole thread about it:  https://bugzilla.redhat.com/show_bug.cgi?id=579838
[16:50] <ubot2> bugzilla.redhat.com bug 579838 in glibc "glibc not compatible with AMD Geode LX" [Medium,Assigned]
[16:51] <Q-FUNK> the plethora of related discussions this bug links to is fascinating.
[16:54] <ccheney> is jjohansen working today?
[16:59] <ogasawara> jjohansen: I was just doing a quick status check for A2 work items, just want to get some quick updates from you if the following will be done by A2:
[16:59] <ogasawara> jjohansen: update compatibility patch for old kernel interface (kernel-maverick-apparmor)
[17:00] <ogasawara> jjohansen: sync distro apparmor to upstreaming version of apparmor (kernel-maverick-apparmor)
[17:00] <ogasawara> jjohansen: Refresh Xen patchset and get xen version of EC2 kernel working in Maverick (kernel-maverick-pv-ops-ec2-kernel )
[17:00] <jjohansen> ogasawara: You'll get the Xen patchset today I've got some testing and cleanup todo
[17:01] <jjohansen> ogasawara: and then I will finish up the AA testing and you should get the rebase tomorrow
[17:02] <ogasawara> jjohansen: cool
[17:06] <JFo> tgardner, http://qa.ubuntu.com/reports/jfo/kernel-Top50.html
[17:29] <sconklin> smb: http://people.canonical.com/~sconklin/radeon_flicker/
[17:30] <sconklin> smb: for some of these, it is also reported that booting with radeon.new_pll=0 solves the issue
[17:30] <sconklin> smb: so please  try the test kernel and the boot option, but not both together
[17:31] <smb> sconklin, Ok, made note of both and will try maybe tomorrow
[17:31] <sconklin> smb: thank you
[17:50] <manjo> cking, around ? 
[17:50] <cking> manjo, still around dude
[17:51] <manjo> cking UEFI Banter ?
[17:51] <manjo> cking,  UEFI Banter ?
[17:52] <cking> manjo, hold on a sec.. firing up
[17:53] <manjo> cking, can you hear me ? 
[17:54] <cking> nope - can you hear me?
[17:54] <manjo> yes
[17:54] <manjo> let me check my audio settings
[17:54] <manjo> s**t its broke
[17:55] <cking> urgh
[17:55] <manjo> ok anyway
[17:55] <manjo> the current ISO does not boot 
[17:55] <manjo> it shows the initial splash and then a blinking cursor 
[17:55] <manjo> cking, any thoughts ? 
[17:56] <cking> urm, did any previous ISO boot?
[17:56] <manjo> yes from previous week
[17:57] <manjo> the iso I tried on sat also had the same issue
[17:57] <cking> manjo, which ISO image is this
[17:57] <cking> ?
[17:57] <manjo> amd64
[17:57] <cking> ok - and when did you download it?
[17:57] <manjo> with grub-efi
[17:57] <manjo> this am
[17:58] <manjo> this iso is suppsed to have the new installer changes
[17:58] <cking> lemme download and see
[17:58] <manjo> but you don't have uefi do you ? 
[17:58] <cking> meanwhile can you roll back to a previous version and do the install manually
[17:59] <cking> manjo, I have VirtualBox
[17:59] <manjo> cking, ah
[17:59] <cking> gonna take me 12 mins to download it
[18:00] <cking> manjo, when did install changes land?
[18:00] <manjo> cking, I believe this weekend/this morning 
[18:01] <cking> manjo, where are you now locale-wise?
[18:01] <manjo> cking, still in TX will catch a plane this afternoon 
[18:02] <cking> manjo, you think this is specific to the ISO image changes with the installer?
[18:03] <manjo> cking, no not sure 
[18:04] <cking> manjo, today's ISO may not fit on a 700MB CD-ROM, so that may be an issue
[18:14] <manjo> cking, no I stripped off some packages like openoffice to make it fit, 
[18:14] <manjo> my iso is 633 only
[18:16] <manjo> cking, once I boot the live CD is there any way of telling what my grub env settings are ? the grub tool to modify env block does not list anything 
[18:17] <cking> manjo, not sure what you mean by "env block"?
[18:18] <manjo> grubenv 
[18:19] <manjo> GRUB Environment Block
[18:21]  * cking looks on google...
[18:23] <apw> http://tools.ietf.org/html/draft-ietf-softwire-ipv6-6rd-10
[18:24] <JFo> <-lunch
[18:30] <cking> manjo, hrm, downloaded and got it to boot in my system. Dunno why it hangs on your box
[18:32] <cking> lemme do a full install an see what's cooking
[18:32] <manjo> cking, this is with efi grub ? 
[18:32] <cking> doing an EUFI install now
[18:34] <manjo> cking, let me download the iso again... May be zsync corrupted my iso... 
[18:34] <cking> maybe, hard to tell at this point
[18:34] <cking> md5sum is your friend
[18:52] <cking> manjo, you tested it on the box I sent you?
[18:52] <manjo> yes
[18:53] <cking> urm, well, maybe worth booting with acpi=off if you see these issues again on real H/W 
[18:54] <cking> if that fails, revert back to plan B - karmic and hand install 
[18:55] <manjo> cking, I have a maverick based iso that boots, just that the recent iso does not boot for some reason
[18:56] <manjo> the recent iso has 2.6.35 kernel and the new installer 
[18:56] <cking> manjo, well, maybe asking cjwatson - he's got H/W very recently so things may change very rapidly over the next few days
[18:56] <manjo> cking, I suspect it is a grub issue so building another iso with hacked grub env options 
[18:58] <cking> manjo, unless one installs on the older ISO, updates the kernel and then see's it die - that will show if it's the kernel or not
[19:04]  * tgardner lunches
[19:21] <JFo> apw, are you waiting for me on something for permissions on the kernel-ppa for the testing dir??
[19:21] <JFo> if that sentence makes any sense
[19:21] <apw> JFo, nope, i have it prototyped and 'working' just not written it up and passed it over to you and bjf
[19:22] <JFo> ah, cool
[19:29] <jjohansen> -> Lunch
[20:14] <bjf> tgardner, ?
[20:18] <tgardner> bjf, ?
[20:21] <ogasawara> ogasawara@tangerine:~$ mkdir maverick-amd64
[20:21] <ogasawara> mkdir: cannot create directory `maverick-amd64': Permission denied
[20:21] <ogasawara> tgardner, bjf: ^^?
[20:21] <tgardner> ogin $HOME ?
[20:22] <tgardner> ogasawara, in $HOME ?
[20:22] <ogasawara> tgardner: yep
[20:22] <bjf> ogasawara, all home dirs owned by root
[20:22] <tgardner> I guess that makes sense since they are all root.root
[20:22] <JFo> X/
[20:22] <tgardner> ogasawara, gimme a bit....
[20:23] <ogasawara> tgardner: thanks
[20:24] <bjf> tgardner, hmm, was saying that on mumble but I guess my mumble session is busted
[20:25] <JFo> apw, if you are still around, mind commenting on bug 538648
[20:26] <ubot2> Launchpad bug 538648 in xserver-xorg-video-intel (Ubuntu) (and 2 other projects) "[Intel GM45] Irregular sync flashes on 8086:2a42 (Needs i915.powersave quirk) (affects: 63) (dups: 6) (heat: 392)" [Medium,Invalid] https://launchpad.net/bugs/538648
[20:26] <JFo> apparently a test kernel you gave them does the trick
[20:26] <tgardner> ogasawara, try now
[20:27] <ogasawara> tgardner: works now, thanks
[20:37]  * ogasawara lunch
[20:44] <JFo> ogasawara, when you return from lunch :) bug 589439
[20:44] <ubot2> Launchpad bug 589439 in linux (Ubuntu) "configuration gotchas with Maverick 2.6.35 kernel... (affects: 1) (heat: 10)" [Medium,Triaged] https://launchpad.net/bugs/589439
[20:44] <JFo> looks interesting to you
[20:44] <JFo> hopefully
[20:57] <JFo> cnd, you around?
[20:58] <cnd> yep
[21:01] <JFo> could you take a quick look at bug 579783
[21:02] <JFo> cnd ^
[21:02] <ubot2> Launchpad bug 579783 in linux-firmware-nonfree (Ubuntu) "Hauppauge hvr-2200 firmware not included (affects: 2) (heat: 95)" [Undecided,Triaged] https://launchpad.net/bugs/579783
[21:02] <cnd> JFo: yep
[21:02] <JFo> thanks :)
[21:02] <cnd> I periodically get to the firmware bugs
[21:02] <JFo> cool
[21:04] <JFo> bjf, do you still want bug 279102 assigned to you?
[21:04] <ubot2> Launchpad bug 279102 in linux (Ubuntu) (and 1 other project) "Unreliable network connection with B44 driver (affects: 17) (dups: 3) (heat: 134)" [Medium,Triaged] https://launchpad.net/bugs/279102
[21:06] <bjf> JFo, no, i made it unassigned
[21:06] <JFo> cool
[21:06] <JFo> just wanted to check :)
[21:44] <JFo> tgardner, you still around?
[21:45] <JFo> looks like we have a problem in the kernel-ppa
[21:45] <JFo> http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/2010-06-09-maverick/
[21:45] <tgardner> JFo, for  FEW MORE MINUTES
[21:45] <tgardner> opps
[21:45] <JFo> we aren't building an image-
[21:45] <JFo> heh
[21:45] <JFo> no problem
[21:45] <JFo> huh
[21:45] <JFo> strike that
[21:45] <JFo> looks like we failed to build a few images
[21:46] <JFo> the mavericks failed to build image debs from the 5th to the 10th
[21:46] <JFo> from what I see
[21:47] <tgardner> JFo, send apw an email. he's the most familiar with his cod infrastructure
[21:47] <JFo> k, will do
[21:47] <JFo> just wanted to tell someone :)
[22:05] <apw> ogasawara, are you running your -4 kernel on any intel graphics h/w ?  seeing some nasty flashing here
[22:08] <ogasawara> apw: I've had it running here on my hp-mini all intel, but not noticing any flashing
[22:08] <bjf> apw, works fine for me
[22:08] <ogasawara> apw: let me update it to the latest bits in the archive
[22:08] <apw> ogasawara, was seeing flashes of black full screen as it were, seems ok when it is being used
[23:03] <gaurav> hello, i am using thinkpad x201, i have to boot into ubuntu by adding '915.modeset xforcevesa nomodeset' in the grub menu while booting. I was told to enable thinkpad acpid module and recompile the kernel.
[23:07] <jjohansen> -> walk