=== BenC__ is now known as BenC === dlbike76 is now known as dlbike76_ [05:20] Hi I'm running kernel 3.5.0-18-generic on quantal and am seeing instances where the kernel is killing the chromium tasks [05:20] Is this a known problem? === dlbike76_ is now known as dlbike76 [05:22] I'm running lubuntu on a computer with limited RAM, and I didn't notice the problem while on precise. [05:23] I'm seeing the kernel sending sigkill to the various chromium tasks in the kern.log once memory usage gets to a certain point. [05:25] dlbike76: That would presumably be the OOM killer? [05:26] RAOF: OOM? [05:26] Out of memory killer. [05:26] Gotcha. [05:26] ie: We've overcommitted, and now something wants to cash the check for memory that we don't have, so we need to kill something. [05:26] Should that happen even if swap hasn't been fully utilized? [05:27] yea ... [05:27] swap can't always service memory requests [05:27] you can adjust the overcommit ratio [05:28] though at best it will probably get you a machine that runs slower for a long time before something is finally killed :] [05:29] chrome seems faster in part due to the way it uses memory to do its work, you might get more out of the situation with a browser not based on webkit [05:29] It's working pretty good otherwise. I'll just have to multitask less... [05:30] you can tell firefox how many images to keep decoded before discarding them, and how much of the back/forward cache to keep around; lots of knobs that won't get you around not having enough memory [05:31] I've been experimenting with various browsers to see which ones work best for the limited RAM that I currently have. [05:32] My biggest problem is that I went from a system with over 3GB RAM to a system with approx 300MB. [05:33] fun, i had to use my netbook when my laptop broke once :] could barely start the firefox session i regularly used, and do anything else [05:36] So is OMM Killer something new in the 3.5 kernel? [05:37] I don't remember this ever happening in 3.2, but I do remember the system slowing to a crawl at times. [05:38] it's not new, it's probably just a coincidence that you're noticing it kill chrome [05:44] Okay at least I know that it is working correctly. Thanks for the help ohsix and RAOF. === jk-- is now known as jk- === smb` is now known as smb [09:06] infinity, Hiya, somehow I think there was not time to look at the xen package? [09:10] * apw yawns [09:14] * smb remembers to make more tea [09:37] smb: Oh, uhm. Indeed. I got sidetracked with a bunch of other stuff. [09:38] smb: Say, you have a new core-dev on your team, you should make him review and sponsor. ;) [09:38] infinity, I asked him about another package and he hasn't done it for a whole week... :-P [09:38] apw, ^ ;) [09:38] smb: A whole week? Man, what a slacker. [09:39] you all smell [09:39] (... says the man who's had a review pending for Andy for months) [09:59] hello kernelers ... :-) [10:00] I noticed that with the new raring kernel I don't have aufs or overlayfs or whateveritis any more ... is that deliberate? [10:00] also modprobe says this "FATAL: Could not load /lib/modules/3.7.0-0-generic/modules.dep: No such file or directory" [10:05] Laney, i suspect its expected, undesired, i'll check a bit later [10:06] apw: OK, I'll go back to 3.5 then for now, cheers [10:09] Hello, I'm trying to debug the ubuntu kernel with kgdb over serial. How can I get a vmlinux file from the vmlinuz file so I can load it into gdb? or does the vmlinuz work fine? [10:17] petantik: Are you not building the kernel from source yourself? [10:18] einonm: I am but not using upstream kernel sources [10:19] einonm: einonm using the instructions here https://help.ubuntu.com/community/Kernel/Compile#Alternate_Build_Method:_The_Old-Fashioned_Debian_Way [10:21] So do you have a vmlinux image in your build directory. I'm not overly familiar with that way of building the kernel, but there should be a vmlinux produced after building. [10:21] what I'm trying to figure out is how to generate a vmlinux file instead of a vmlinuz file [10:21] einonm: let me check [10:21] The vmlinux file is generated before the vmlinuz file, and is used to generate the vmlinuz file [10:22] einonm: you're right, definitely a pebkac moment. [10:22] cheers [10:22] np :) [12:35] * henrix just received a build failure email for a build that is still pending...!?!? [12:35] apw: any idea what happened here? ^^ [12:36] apw: it was an armel build for 3.2.0-34.53 [12:36] henrix, the build may have failed due to buildd failure (say they rebooted a buildd) and then someone put the build back for rebuilding [12:36] so what you see if it pending for rebuild [12:36] henrix, got a pointer to the build [12:37] apw: yeah, but the link sends me to the "Lost something?" thing :) [12:37] henrix, well that probabally means it was indeed retried, as we do lose the errors then [12:38] apw: ok, so i'l just wait and see [12:38] which build was it, which series [12:38] i've just build tested armel again and it builds without an error [12:38] it was precise [12:38] 3.2.0-34.53 [12:39] henrix, yeah it seems to be building right now, so it must have been put back [12:39] apw: ok, thanks. let's wait and see what happens [13:03] apw, henrix: I restarted it 'cause it was a compiler seg fault [13:03] heh there you go then [13:04] rtg, i am working on fixing aufs and overlayfs in raring, so don't upload without me [13:05] cking, could you give me a quick review of your batter patch on git://kernel.ubuntu.com/ubuntu/ubuntu-nexus7.git master-next ? I've rebased against a new release and there were some conflicts in your battery status patches. [13:06] apw, ack. did you re-upload signed or do you plan to wait ? [13:07] rtg, no i didn't ... i will do that right now [13:07] oh perhaps i won't if that is holding us from breaking the images ... hmmm [13:07] rtg: ok, thanks [13:08] * henrix -> lunch [13:08] apw, can't build dailies without overlay or aufs ? [13:10] rtg, they won't boot without as far as i know [13:10] rtg, i have some test builds ongoing, i am doing overlayfs first, as thats the default [13:10] if that works we can upload that [13:10] apw, ok [14:02] * ppisati switches to the haswell box (back in a bit) [14:30] * henrix realises that herton is referred in lwn! \o/ [15:07] henrix, link ? [15:08] apw: it's on this week edition, kernel section: https://lwn.net/Articles/524304/ [15:09] apw: it's just the announment of the stable tree for 3.5 :) [15:10] heh ... good stuff [15:17] rtg, ogasawara, anything you want thrown in the next upload for raring ... i don't want to have any rebases in here really, as this enabled a heap of code [15:18] apw: nothing here [15:21] ogasawara: did you put somewhere the list of patches that you showed during the delta review? [15:21] ppisati, normally that is in the spec for the blueprint [15:22] ppisati: yah, in the spec. lemme find the url for you. [15:22] ppisati: https://wiki.ubuntu.com/KernelTeam/Specs/RaringKernelDeltaReview [15:23] cool, thanks [15:44] ogasawara, i have generated the 'per dev patch review' WIs and added them [15:44] apw: sweet, thanks [15:44] apw: I need to go through and update our milestone tracking too in our BP's since the new monthly checkpoints were added to LP [15:45] ogasawara, monthly what now ? [15:46] * rtg actually made a nexus7 kernel that boots [15:46] apw: there's the new monthly milestones now since we don't have alpha's [15:46] apw: eg ubuntu-13.04-month-1 [15:46] * apw hans rtg a pint ... well done [15:47] apw: hrm, I'm also now seeing the alpha's there too. I swore they were not there yesterday. [15:47] ogasawara, yeah, so we should be trying to fan out our WIs to the appropriate months [15:49] ogasawara, now all i need is some feeling for what month-1 etc means, any idea when they are [15:49] apw: nope. I checked yesterday to see if the release schedule had any specific date for what the month-1 deadline was, but found nothing. [15:50] ogasawara, the milestones themselves will have them, if i could remember where they are [15:50] https://bugs.launchpad.net/ubuntu/raring/+milestones [15:51] ogasawara, oh the alphas etc are 'optin' now [15:51] ogasawara, anyhow so its the 18th, -month-1 is like saturday, and so on [15:51] apw: ah ok. /me makes a note [15:53] I never knew of the /+milestones url, that's helpful [15:54] ogasawara, me either, i just guessed, right for once [15:54] is that a new LP feature? [15:55] cking, don't think so no [15:55] apw, due to the elegance and consistency of LP you can just naturally anticipate those features [15:55] it is the very first time that my guess found something, i am somewhat chuffed [15:56] apw: you just happened to stumble onto a LP easter egg [15:56] I though the way to find out LP features was to grok the source [15:56] *thought [15:57] * ogasawara back in 20 [15:59] https://launchpad.net/launchpad/+specs is interesting, all the eggs aren't in one basket [16:06] rtg, ogasawara, ok i have a kernel here with working overlayfs and aufs, so i am proposing to upload it now [16:07] apw, lock and load.... [16:11] BenC, i have just pushed a new raring master-next with working overlayfs which you need for your images to boot [16:11] apw: Ah, thanks [16:11] rtg, when you build source pacakges do you do so on 32 or 64 bit chroots ? [16:12] apw, generally both [16:12] apw: Is that -2.8? [16:12] BenC, yes [16:13] BenC, i have literally just pushed the master repo, packages are being prepped now [16:13] though i am running it here on my kit [16:27] BenC, oh you may want to fetch again so that the master branch is updated, else the rebase script may not work, as i found out when i did lowlatency :) [16:28] apw, what script ? ppc is a straightforward rebase against master isn't it ? [16:29] rtg, well it cannot be a strightforward rebase just because master is rebase as well, for lowlatency i use an update-from-master script which knows how to find the bottom of what to rebase etc [16:31] Mine seemed to find the correct places to rebase against using the tag [16:31] Maybe I'm lucky [16:34] apw: Starting a build, so I'll follow up in a couple hours [16:35] ogra_, are the nexus7 udeb files of any use ? the installer just blats an image onto flash, right ? [16:36] rtg, the d-i and netboot images use them don't they? regardless of final installation method [16:37] I installed my n7 kernel image from the .debs - but hey, I don't know the official way its done [16:37] apw, neither of which are useable by the nexus 7 [16:37] rtg, then it seems unlikely they can be being used indeed [16:37] lemme check with janimo [16:37] ^^ [16:43] * ppisati goes out for a bit... [16:55] hello kernel people. The new linux-libc-dev broke libnl and in turn a bunch of universe packages. [16:56] I'm now working on a patch to libnl's netlink-kernel.h to deal with the change and would appreciate one of you confirming it's the correct approach [16:56] the debdiff for libnl would be: http://paste.ubuntu.com/1360658/ [16:56] apw is likely the most informed about header issues [16:57] stgraber, hi [16:57] I'm currently doing a test rebuild of sssd (one of the affected package) with the updated version of libnl to see if that does the trick [16:57] apw: hi [16:57] stgraber, oh god that is utterly vile [16:58] stgraber, it is clearly doing something which it should not, relying on the names of _ prefixed defines [16:58] stgraber, what you have done seems as appropriate for the new headers as for the old, but *barf* [16:59] hehe, well, upstream fixed that in libnl3 (different api) and redhat is in the process of porting sssd to using libnl3 [16:59] so hopefully we can kill libnl1 soon and won't have that kind of problem again... [16:59] stgraber, but yeah i think you have no choice in your situation and you appear to have done something which means the right thing [17:00] good and the test build just succeeded so I'll push that to the archive now. Thanks for taking a look at the fix. [17:15] rtg, ogasawara, not sure who did the fold down last time we rebased, but when we did squashing aufs into its base patches (aufs-base and aufs-standalone) made it real complex to unpick and update [17:16] i've attempted to mark the ones which are annoying to lose separation on (no-squash) for next time [17:16] apw, prolly me [17:44] rtg, feel free to drop udebs [17:45] I suppose ubiquity does not use them either in case we ever want a proper ubuntu installer [17:45] janimo, already did, just uploaded to raring directly [17:45] rtg, great [17:45] janimo, also created nexus7 branch in ubuntu-raring-meta [17:45] rtg, should I push the firmware package from PPA to raring NEW too or Are you looking at that too? [17:46] rtg, nice, had no git tree for meta so far [17:47] janimo, where is the firmware package ? [17:47] in the ubuntu-nexus7 staging ppa raring pocket [17:48] janimo, lemme have a look... [18:15] * rtg -> lunch === yofel_ is now known as yofel [19:33] * henrix -> EOW [20:52] ogasawara: bug #1079385 looks like a duplicate of the overlayfs support issue; is there a master bug for this? [20:52] Launchpad bug 1079385 in upstart "init: can't start after load iso image on hyper-v server 2008 r2 sp1" [Undecided,New] https://launchpad.net/bugs/1079385 [20:57] looks like 1079193 [20:58] slangasek: yep, that's the one we shoved in the changelog [20:58] ok, thanks [21:17] apw: Can you help me out using insert-ubuntu-changes.pl? [21:19] nm, figured it out === BenC__ is now known as BenC [21:27] BenC: Oh hey. I wanted to chat with you. [21:27] BenC: Specifically about the udebs you dropped from PPC... [21:28] infinity: Yes? [21:28] BenC: The pcmcia stuff is absolutely usable on Apple hardware. Perhaps only disabling those for the e500 flavours would have made more sense than across the board? [21:28] BenC: (And the 8250 stuff also worked fine in the past, and should still do...) [21:28] infinity: unfortunately, there's no way to do that on a per flavor build [21:29] I have it on my todo list to re-enable that once I create a mechanism that does what we need it to [21:29] Hrm. [21:29] The udeb's are empty on e500* so It's not like I could just ignore a few modules [21:29] Yet another argument for "powerpc should have stayed in master, and only e500 should be out-of-tree"? :P [21:30] Having e500 randomly break previously-working non-e500 setups seems suboptimal. :/ [21:30] I've not heard of any other arguments for such a case :) [21:30] I did say I plan to fix it :) [21:30] IMO, it's kernel-wedge that is suboptimal [21:30] Yeah, I heard you. I'm just thinking in the more general case. [21:31] Also, having 8250 (for I assume serial console) be modular is less than desirable anyway…I can't imagine anyone using that in a sane way [21:32] My plan was to build it in on non-e500* to match up and not lose that udeb functionality, but I haven't decided yet [21:32] It wouldn't generally be for consoles, most PPC hardware I know has onboard serial that isn't 8250. [21:32] (Which, sure, also makes it less likely to be a useful udeb...) [21:32] I couldn't really think of a legit use case [21:33] Keeping the module but dropping the udeb is probably fine for the serial one. [21:33] But I'll take your word for it that it's important :) [21:33] For pcmcia, not so much. Those are kinda useful. [21:33] I've never heard of people using PCMCIA from powerbook's for things needed during install [21:34] Except maybe networking, but is that something not available on most PowerBooks anyway? [21:34] I could dream up a scenario where one might want an 8250 udeb to do some serial debugging or something weird, but it's pretty corner case, and not something I suspect anyone really cares about. [21:34] PCMCIA for networking would absolutely be the use-case. [21:34] Oh, wait, is airport on things like G5's attached to a PCMCIA port internally? [21:35] I think it is…so there's a good reason for having it [21:35] G5/G4 [21:35] That's also possible, I dunno, but I was just thinking of the ton of powerbooks with crap internal NICs and PCMCIA instead. [21:35] (Which was not an uncommon setup) [21:35] Either way, we don't make a habit of telling people "if you don't use the internal NIC, you no get networking during install". [21:35] Ok, I'll definitely work on getting PCMCIA udeb's back, and I'll mull over 8250 [21:35] Hence why we even have usb-network-udeb, etc. [21:36] (Or whatever it's called) [21:36] BenC: Of course, a rebase to -2 master is probably slightly more urgent, due to the overlayfs/aufs oopses in -1. :P [21:37] BenC: No pressure, welcome back to the kernel team, etc. [21:37] * infinity mails Ben a beer. [21:38] infinity: sure thing, and you missed the opportunity to buy me a real beer [21:38] Oddly, not many were willing to drink with me in Copenhagen [21:38] You were a hard man to find after hours at UDS. I could have just beered you at the smoke doors between sessions. :P [21:39] (Or maybe I was the hard one to find? I'm not sure...) [21:40] I believe I was being avoided due to the bar having jaeger on hand [22:40] BenC, this new upload didn't get an abi bump, i cannot see how it could not have been; do you still have skipabi/skipmodules turned on ? [22:41] (not that it matters anywhere near as much on ppc as you likely have no dkms, but ...) [23:01] infinity, this whole kernels are (new) and linux-signed can't build till they are done crap really makes getting kernels built a long arduious process [23:01] it would be good to get the signed in, so we get new kernels in the live's [23:03] apw: Yeah, yeah. Hold your horses. ;) [23:15] heh thanks :)