=== dannf_afk is now known as dannf [01:27] heads up that X is broken in 2.6.37-5 with kvm/vmware and on a ton of old UMS drivers until this commit comes in in case it comes up - http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=8c05cd08a7504b855c265263e84af61aabafa329 [01:44] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/676759 [01:44] Launchpad bug 676759 in linux (Ubuntu) "X fails to start in vmware/kvm and with various UMS drivers on 2.6.37-5 (affects: 3) (dups: 1) (heat: 20)" [High,Triaged] [01:45] Sarvatt: ack [02:12] is anyone successfully using the natty kernel? I'm seeing really broken NFS with it (file locking appears hosed). [02:13] nfs locking hosed.... [02:13] this is different somehow? [02:15] lifeless: yes. I've had no problems for years. [02:29] I'm using the natty kernel, but I don't use NFS. Nothing seems to be more broken than usual. [02:30] I'll track it down tomorrow... === amitk is now known as amitk-afk === amitk-afk is now known as amitk === robbiew1 is now known as robbiew [07:50] I bet this fixes NFS for me... http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=8e35f8e7c61c88f9a979a4e6f7f4ffd4c158a88a [07:50] * kees waits for -rc3 [07:50] :) [07:59] So what is the deal with the new patch? [07:59] Are you guys gunna take the bashrc workaround instead? [08:02] Hello? [08:04] TheSarge: patience :) Most of the kernel team working on the Ubuntu distro kernel are in the European timezone - so they are probably stumbling around looking for coffee at the moment. [08:05] (and US timezone) === doko__ is now known as doko === smb` is now known as smb === yofel_ is now known as yofel [12:09] Hi I am new member here I just had posted on mailing list [12:09] for doing some thing on the kernel front [12:09] I am having a Laptop [12:09] and that is the only hardware available to me [12:10] I have developed a character device driver recently [12:10] and have been reading a lot of things related to [12:10] devices such as CMOS ,Network and etc etc [12:10] so I wish if I can contribute to [12:10] the kernel development or bug fixing some way [12:10] so show me some way [12:11] I am very interested for the wireless devices area [12:11] but I do not have hardware for that [12:13] I have checked this page https://wiki.ubuntu.com/KernelTeam/BugTriage [12:14] and also looked at this page https://wiki.ubuntu.com/Kernel/Dev/KernelPatches [12:16] I have also checked this page https://bugs.launchpad.net/ubuntu/+source/linux/+bugs [12:16] let me know how can I start [12:16] working [12:19] Hello to all devs. Can someone please tell me, if there will be enabled again OSS emu sometime in the future in the stock kernel? [12:21] JeanPijon, that is unlikely [12:22] JeanPijon, you probably want to follow https://bugs.launchpad.net/ubuntu/+source/linux/+bug/579300 [12:22] Launchpad bug 579300 in linux (Ubuntu) "Please disable CONFIG_SOUND_OSS* and CONFIG_SND_*OSS* (affects: 19) (heat: 130)" [Wishlist,Fix committed] [12:23] joaopinto: I have read this, so there won't be stock kernel with this feature enabled? [12:24] that is what looks from the bug reading [12:24] it was one of those hard changes [12:25] joaopinto: I see, but there will be probably problems with many applications (such as MythTV)... and it results [12:25] JeanPijon, how come that MythTV does not support ALSA? [12:26] diwic, from the bug report, "It turns out this OSS garbage is responsible for my (cx8801) TV tuner cards' being able to capture audio from analog cable." [12:27] joaopinto, diwic, so it results to the way NOT to update any kernel, until those applications will be rewrited:( [12:28] joaopinto, so is it the hardware or the software that does not support ALSA? [12:30] joaopinto, googling both MythTV and CX8801 it seems like there is support for ALSA on both sides. [12:30] JeanPijon, or help us fix the problems with ALSA [12:31] diwic: Sure, but I don't think I am the right person to code the kernel:( [12:32] JeanPijon, you can at least file bugs for your issues and help out with testing if we come up with a fix [12:33] diwic: Absolutely right, I will try, but again, there is no possibility for now, except to recompile own kernel with that modules enabled... [13:00] smb, whats the status of: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/669496 [13:00] Launchpad bug 669496 in linux (Ubuntu) "natty kernel fails to mount root on ec2 (affects: 1) (heat: 210)" [Critical,Confirmed] [13:01] smb, seems it is on the release meeting agenda === diwic is now known as diwic_afk [13:51] apw, It seems to affect only i386 and amd64 with t1.micro. Unfortunately when it fails it usually gives no logs at all. jj had captured some but I have to check whether he attached them to the bug [14:02] Hi on this thread https://lists.ubuntu.com/archives/kernel-team/2010-November/013541.html I was suggested to join this IRC [14:09] jtapas, hi you are interested in helping with kernely things i think [14:10] this is the place where all those interested in ubuntu kernely things hang out [14:10] so you are in the right place [14:13] smb, ok so i'll write that up as a limited exposure and testing still possible, investigation continuing [14:13] apw, sounds good to me. I am just now updating the bug as well with that facts [14:17] yes [14:17] @apw [14:17] yes I am interested in developing or doing kernely things [14:18] jtapas, so i guess the question is what sort of things are you interested. we have lots going on [14:18] I like network sort of things [14:18] I believe he mentioneed wireless [14:18] ranging from initial triage of bugs through to patching and upstreaming patches [14:18] ya [14:18] wireless is one thing that does fascinates me [14:18] the only hardware I have is [14:18] my laptop [14:19] ok well if you are interested those kinds of things then i think we do tag bugs which are related to that [14:19] ok [14:19] is it kernel-wireless ? i forget exactly [14:19] jtapas, This is not uncommon when looking at bugs [14:19] We rarely have the hardware ourselves [14:19] you might want to have a poke about in those and see what you can help wil [14:19] with ... [14:19] cirtainly one learns a lot about a thing by looking at the bugs there [14:20] I do not know if i am right or wrong but I feel that to have a fix or [14:20] driver u need to have that hardware [14:20] is that not the case [14:20] This is where talking to people comes into play. :) [14:20] ok [14:20] so how can I start with [14:21] let me know reading and reading books I have cooked myself too much [14:21] I want to actually do some real work [14:21] which u people enjoy doing [14:22] jtapas, JFo is our "master triager" sort of. So he would know a bunch of reports grouped for people wanting to help [14:23] ok JFo is it a human [14:23] Sometimes yes and no [14:23] He tends to run his scripts in his name but he is a human too [14:23] so u mean to say that I should contact him [14:23] is he on this IRC [14:23] yeah jfo looks after our incoming bugs, and helps us find the interesting ones. he is normally here [14:24] Right, he will be here on irc too [14:24] hrm, but not at the moment [14:24] Ok when can I expect him generally [14:24] UTC time I will be online at that time [14:24] apw Still relatively soon in the morning his place [14:25] smb, its 9:30 his time, not so early [14:25] But more or less soonish. Depenends on the human factor [14:25] apw, Maybe he was able to sleep for a change [14:25] yeah maybe, that guy needs to relax [14:25] my time zone is +0530 of UTC r u referring to UTC time at 09:30 [14:26] jtapas, he is east coast US, so i am guessing your are similar [14:26] jtapas, It is 9:30 where he is [14:26] So thats 14:30 UTC [14:26] ok [14:26] 'about now' :) [14:26] ya :) [14:26] * apw incants to try and raise him [14:26] jFo, JFo, Jfo ... [14:27] man it worked for bloody mary on the tv last night [14:27] Ok then I shall wait for the guy to let me understand where to start [14:27] the other place to look is in our Kernel wiki, that has lots of information on how we do things [14:27] https://wiki.ubuntu.com/Kernel/ [14:29] ya I had looked that page also [14:32] the stuff on trige would help you understand what the status of bugs means etc [14:33] and on the tagging page you should find the lists of tags we use to mark bugs [14:33] ok [14:33] are you referring to this page https://wiki.ubuntu.com/Kernel/BugTriage [14:37] I see a lot of bugs here https://bugs.launchpad.net/ubuntu/+source/linux/+bugs [14:38] but if I pick one and start doing some thing then that would not be heading to any direction [14:38] since I never fixed any bug till today in my life [14:38] though I wrote a char driver [14:39] jtapas, working at the distro level generally involves digging into peoples issues, and trying to help them [14:39] and at kernel level [14:39] the other place people help is with askubuntu, which helps with things including onfiguration and usage issues [14:40] how did u people started fixing such kernel bugs [14:40] since all here are developers so I believe [14:40] some where u must have started [14:40] I will follow the same [14:40] it might take time [14:41] but I feel I will be able to do it with some patience and practise [14:41] yep, i just dug into the bug list, picking out bugs I knew things about, using the source of the kernel to help understanding them and trying to fix [14:41] currently I am not clear [14:41] and how much time it took u to fix the first bug [14:41] so as you like networking i would look at some in gneeral networking perhaps as you can fix those [14:41] ok [14:41] i think i fixed a few in my first week, but i was working on it full time [14:41] ohh I see [14:41] a lot of the time you find the issue is already fixed in much newer kernels [14:42] hmmm [14:42] did u had the devices for which u fixed the bugs [14:42] so one can use that information to pull back the fix, or to do the equivalent [14:42] Ok [14:42] often we ask people to try newer kernels and mainline kernels from the mainline kernel archive [14:42] to see if later kernels have a fix === diwic_afk is now known as diwic [14:43] r u referring to vanilla kernel from kernel.org [14:43] or the one from ubuntu repositories [14:43] jtapas, yes we build those installable for ubuntu systems every day [14:44] https://wiki.ubuntu.com/Kernel/MainlineBuilds [14:44] ok [14:44] those are made automatically as they release, and we use those as a debugging resource [14:44] ok [14:44] let me read that doc [14:44] I will get back here once I read it [14:50] ok what I understand from the link of MainlineBuilds is u apply Ubuntu specific patches to kernel which is on www.kernel.org and test [14:50] if those patches work [14:50] or not [14:50] is that correct [14:53] jtapas, no those kernels have our _config_ only applies [14:53] they are useful to know if the ubuntu patches are causing an issue [14:53] I did not get that [14:54] why do u test your config [14:54] are u referring to the config file in arch subdirectory [14:54] well a distro needs cirtain things turned on to be useful [14:54] ok [14:54] so we build with the ubuntu config to make sure the kernels are likely to be usable on an ubuntu root [14:55] ok [14:56] so let me know if this time I understand :u take a kernel from kernel.org and [14:56] give ur default config [14:56] and test if it works for ubuntu [14:57] if that is the case then I am curious to understand why do u do that [14:57] does the kernel from kernel.org not work for Ubuntu [14:57] the ubuntu kernel includes fixes for various things [14:58] sometimes those things fix the person they are intended for, but break someone else [14:58] so sometimes a failure can be related to a fix we carry above and beyond the base point [14:58] these are ubuntu kernels? [14:58] ok [14:58] the mainline kernels are mainline virgin trees, configured for ubuntu [14:58] ok [14:58] used as testing points. they allow testing without our patches, and on newer versions than our stock kernels [14:58] both are useful [14:59] ok [14:59] on that page it is mentioned u built 4 sets [14:59] of kernels [14:59] 2 from Linus's tree and [14:59] 2 from DRM [15:00] what is the difference between the two [15:00] are these both different kernels [15:00] I have compiled kernels in past [15:00] but I never came across such thing [15:00] Linus's tree and DRM [15:00] development repositories [15:11] linus tree is the master upstream repository [15:11] from that we build each release he does (ie each tag) and we also build a random daily [15:11] snapshot, ie whatever is in the tree at 10am UTC every day [15:12] the other two are maintainer trees for sub-systems we care about a lot [15:12] in this case two graphics trees. they contain stuff likely to be in the next release from linus, but before he gets them [15:12] so we can see if there is anything coming which may help us [15:13] ok [15:13] I checked this page https://wiki.ubuntu.com/Bugs/HowToTriage/Charts [15:14] the laptop I have I use it in my work place also [15:14] if I try these new kernels and bug fixing on [15:14] a virtual machine would that be fine [15:14] or I need do all on the bare metal [15:18] jtapas, some of us do testing in VMs too === bjf[afk] is now known as bjf [15:18] specially in early cycle like now when the release is not very stable [15:20] ok [15:22] since I am new also so I will take some time to understand all this but I am happy that at least I am heading in some direction [15:23] you mentioned above in coversation ubuntu specific __config_ files [15:23] applied to mainline kernel so can you give me [15:23] link to those configurations which exactly you are pointing to [15:24] I want to see what is ubuntu specific __config_ in Ubuntu's situation and how is it [15:24] different from the mainline kernels config files [15:37] smb: thanks for testing Dapper [15:38] ogasawara, No problem, its installed so its not much effort === diwic is now known as diwic_afk [16:28] http://people.canonical.com/~platform/workitems/natty/canonical-kernel-team.html [16:29] cking, ^^ [16:41] tgardner, i have a couple of config changes i want to put in the same one [16:42] apw, you have time to roll it? you're nearing EOD. [16:42] yeah no problem [16:42] take it away... [16:43] * ogasawara bails for appt, back in a bit [16:54] sconklin, bjf Pushed and uploaded a lucid-ec2 package which is rebased to the phase2 lucid kernel [16:55] jjohansen, And btw realized that there is nothing to do for Maverick \o/ [16:55] smb, thanks though i have no idea what the "phase2 lucid kernel" is [16:56] bjf, The one you have currently in proposed and has the reverts. Hey I am just using your new wording. ;-P Or is that phase 0 and 1? ;-) [16:57] smb, oh, crack week v.s. stable week [16:57] apw, want to plan a chat on Monday (morning for me)? [16:57] JFo, can do [16:58] cool [16:58] ping me when you get in [16:58] will do [16:58] tgardner, Yes [16:58] tgardner: verification kernel vs. testing kernel. [16:59] sconklin, I think that is the same with less opinion [17:02] JFo I was suggested you are "master triager" sort of here ,I am some one who wants to contribute to bug fixing etc on wireless area and kernely things on Ubuntu can u say some thing about this I had been waiting for you to come online [17:02] hey, sure [17:02] sorry about that. Sometimes I don't realize IRC isn't up for a while(happens often in the AM) :) [17:03] any specific portion of the kernel interest you jtapas? [17:03] I want to do some thing on wireless area also I was looking at many links [17:03] https://blueprints.launchpad.net/ubuntu/+spec/cloud-server-n-ec2-cluster-compute [17:03] and the above link seemed interesting to me [17:04] though not sure as what I can contribute at this point of time [17:04] wireless does appeal me [17:04] no problem, there are many ways to contribute [17:04] excellent [17:04] * JFo looks at the BP [17:04] I want to do bug fixing [17:04] on such areas [17:05] excellent! I am happy to have you here then :) [17:05] yea :) but I am just beginner and it will take me time [17:05] to understand things and then to be able to [17:05] actually contribute some thing worth [17:05] may take time [17:05] I am a bit slow learner [17:05] smb is our kernel server liason and jjohansen to a degree, so they will have the most info on that relationship [17:05] that's ok [17:05] ok [17:06] those things worth doing sometimes take time :) [17:06] ok [17:06] This blueprint is about images for amazon ec2, nothing wireless there [17:06] so I have been reading lot of wiki pages here [17:06] on Ubuntu kernel pages [17:06] excellent [17:06] smb, yeah [17:06] In general I don't think blueprints are a place to start when one wants to do bugs [17:06] ok [17:06] I agree [17:06] but that is ok [17:07] we can look at some bugs :) [17:07] yea [17:07] I did had looked the Kernel Wireless page [17:07] but that redirects outside [17:07] the Ubuntu domain [17:07] http://wireless.kernel.org/en/users/Documentation/Reporting_bugs [17:07] to the above page [17:07] jtapas, have you looked at the Triage pages found here:https://wiki.ubuntu.com/Kernel/BugTriage ? [17:07] yes [17:07] I did looked and the mail [17:07] excellent [17:08] also in which the questions were answered [17:08] I want to start with some thing easy [17:08] ok [17:08] that will take me some time to understand [17:08] hmm [17:08] so if you think you can give me one such bug I want to [17:08] let me see... [17:09] * smb thinks wireless and easy are slightly orthogonal. But that is just my opinion [17:09] ok [17:09] are you wanting to learn about how wireless works in the kernel or try to help with wireless misconfiguration on bugs? [17:09] I would agree with smb [17:09] I want to do some thing kernely [17:09] and wireless seemed promising to me [17:09] so I asked [17:10] by that you mean development? [17:10] ya [17:10] exactly [17:10] ok [17:10] let me see... [17:11] so, in order to ensure we are all on the same page... [17:11] I just wanted to mention that 'wireless' really covers a lot of ground [17:11] ok [17:12] and is mainly handled by the modules themselves that are created and provided by outside companies [17:12] ohh [17:12] it is not some thing specific to Ubuntu [17:12] smb, correct me anywhere here if you see that I am wrong [17:12] jtapas, no, it is specific to the overall kernel itself [17:12] ok [17:12] and is different in each of the modules [17:12] ok [17:13] hence my question about whether you wanted that or helping to fix misconfiguration etc. [17:13] I do want that [17:13] development [17:13] it may take time for me to understand [17:13] but do not worry about that part [17:13] In many cases (those that we have the most issues with) the driver is messy [17:14] ok [17:14] I'm not worried :) [17:14] I just want to give you the best information [17:14] ok :) u mean messy to misconfiguration [17:14] ya ya right [17:14] and point you in the right direction [17:14] ok [17:14] well, that and the code is very questionable in some cases [17:14] ok [17:15] meaning that over time they have done things to make bits work that didn't improve the overall quality of the code [17:15] not that they are bad [17:15] ok [17:15] ok [17:15] just that many of them would require a rewrite to be improved [17:15] which is a major undertaking [17:15] ya that will be a good start [17:15] but I digress [17:16] ok [17:16] so, the kernel handles pretty much all modules it loads the same [17:16] ok [17:16] can anyone tell me why this is happening when i try to load my module? http://pastebin.com/55dBXeKE [17:16] the difference is to do with what the module does or controls [17:16] module source: http://pastebin.com/asn5Bt9p [17:16] makefile: http://pastebin.com/30c5WLHU [17:17] ok [17:17] but it is not entirely that simple either [17:17] JFo: btw, it has to be that ~kernel-bugs had its list removed. I just removed myself from ~u-k-t, and what'dya know, everything works again [17:17] ok [17:17] vanhoof, hmmm [17:17] but you had to remove yourself from u-kt though [17:18] sounds odd [17:18] JFo: i think i found that 'crackhead' stuff you mentioned, which also happened on the 5th [17:18] jtapas, give me one sec to check something [17:18] ok [17:18] vanhoof, yeah, I think something there is what did it [17:18] I see that in my 'Indirect' folder [17:18] Vishnu (vishnuvishnu.2012) added Kernel Bugs (kernel-bugs) (which you [17:18] are a member of) as a member of sljdg (hjgf). [17:19] yep, that's the stuff [17:19] all on the 5th [17:19] i keep getting the following when trying to build my module: WARNING: "kallsyms_lookup_name" [/home/daan/Code/Phrack/phrack.ko] undefined! [17:19] looks like someone was trying to escalate privilege in the groups [17:19] and this when trying to load it: Unknown symbol kallsyms_lookup_name [17:19] may have succeeded [17:19] i am pretty sure i included the right header (linux/kallsyms.h) [17:20] and my kernel also exports the symbol [17:20] bdmurray, I'm still getting the mail. Any ideas? [17:20] JFo: ~k-bugs was never set to the list [17:20] JFo: i dont think bdmurray can set it [17:20] I just want to know where it is suddenly coming from and nuke whatever that is [17:20] :) [17:21] And I'm telling you set the email address for the team to k-bugs [17:21] I can't do it since I'm not in ubuntu-kernel-team - they are the owner of kernel-bugs [17:21] bdmurray, k-bugs@l-u-c? [17:21] oh ok [17:22] sorry, that must have been after my brain scramble yesterday [17:22] yes, set the email address to kernel-bugs@lists.ubuntu.com [17:24] k, done [17:24] but apparently there is a confirmation sent [17:24] and I am not subscribed to the list [17:25] wonder how that will work out :) [17:25] ok, moving on [17:25] jtapas, apologies [17:25] no problem [17:25] so, it is not entirely as simple as generically handling modules [17:25] what I understand from ur conversation till now is [17:25] to be able to start some where [17:25] this will be a good warm up [17:25] I think so, ye [17:25] err yes [17:25] that way when I jump to actual bug fix etc [17:26] I will be able to do some thing [17:26] indeed [17:26] so that is fine with me [17:26] even I want to start with some thing that I can at this point understand [17:26] this is a time consuming process and needs [17:26] practise I feel [17:26] and once you get the idea of the scope of the bugs, you will have a better understanding of the wireless modules once you start looking at them from a dev standpoint [17:26] so do give any link [17:26] right [17:27] so go ahead and give links which you feel I should be starting [17:27] at least I begin some where [17:27]