[08:15] hi, how do i build my own kernel ppa? [10:34] hi [10:35] LLStarks: https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel [10:35] BTW, see topic :-) [11:17] dileks, if i want to ppa really exotic and bleeding edge code without a debian folder, am i screwed? [11:17] cuz i suck at packaging [11:23] LLStarks: whats your goal? [11:24] dileks, drm-next is packaged, but i want to package airlie's drm-dmabuf2 tree [11:25] i can build the debs, but i have to clue how to translate that to a ppa [11:25] dunno if all patches from ubuntu apply then [11:25] it's a vanilla kernel [11:26] plus his upstream work [11:26] I am building with 'make deb-pkg' [11:26] its fine for (fast) testing from any kernel GIT tree [11:27] not make-kpkg? [11:27] build_linux-with-deb-pkg.sh: http://paste.ubuntu.com/981526/ [11:28] dunno if make-kpkg still works, it was never my 1st choice [11:29] concurrency 1- [11:29] *10 [11:30] isn't that excessive even on a quadcore with ht? [11:30] gonna pass out while this builds [11:31] a wise man gave me that empirical formula (longterm experiences): max_make_jobs = core(s) x2 +1 [11:32] is that assuming threads>cores? [11:32] you can reduce make-jobs-no of course [11:32] even on pentium-m =5 was OK [11:33] either way, j8 takes at least 20 minutes to build a full ubuntu kernel and this is a 2630qm [11:33] too afraid to strip stuff [11:33] BTW... [11:34] http://nopaste.snit.ch/139833 [11:35] if you dont need... CONFIG_DEBUG_INFO=n [11:35] thx [11:35] sleep time [11:35] it gets huge [11:35] not only deb-files [11:35] your local build-dir explodes to some GiB [11:36] IIRC there is one debug-info-reduce kernel-config. dunno how much space this saves and whats with "all" debug-symbols [11:37] CONFIG_DEBUG_INFO_REDUCED === yofel_ is now known as yofel === ayan_ is now known as ayan [18:17] Guys, I would like to highlight the RAID corruption bug introduced in upstream commit c744a65c1e2d59acc54333ce8 and fixed by commit 30b8aa9172dfeaac6d77897c67ee9f9fc574cdbb [18:18] The md subsystem maintainer (Neil Brown) observes today on the linux-raid mailing list that Ubuntu appears to be more susceptible to this problem than other distros [18:18] Would it be possible to expedite deployment of the fix? [18:18] The problem causes RAID metadata to be damaged upon shutdown, so that the array can't be reassembled after reboot === smb` is now known as smb [19:42] JanCeuleers, the fix is already in the kernel in precise-proposed, so it will be in the next update === panda is now known as Guest86272 [19:53] That's great, thank you. [19:53] Just want to mention that the longer it takes for the fix to become official, the more people will get stung by this. [19:54] (I'm not one of them) [22:28] https://01.org/powertop/blogs/ceferron/2012/powertop-v2.0-release [23:16] Hi! I'm experiencing network shutdowns when system is inactive. Anyone who knows if this is something known? [23:16] looked into logs? [23:18] dileks: yes, I posted those in a bugreport, I couldn't see anything strange. The fact is that I just reproduced the problem now in an hour and I noticed it is sufficient that the kernel recognizes a plugged mouse to restore the network. [23:18] bugreport is 997767 [23:19] I didn't think it was kernel-related, but now I'm starting to think it might [23:19] only think I see in dmesg is the mouse plugged in [23:21] [68627.945751] TCP: Possible SYN flooding on port 6882. Sending cookies. Check SNMP counters. [23:21] dileks: yes, I have it now as well. [23:21] do you think it may be related? [23:23] dunno [23:23] you tried static-IP setup instead of dhcp? [23:24] dileks: you mean stopping the dhcp server? [23:25] for static-IP you dont need a dhcp-server [23:27] dileks: yes, but this box also has a dhcp server that I don't think I'm using anymore. Do you mean I have to try to stop the server or that I have to configure the ethernet interface to not use the real dhcp server? [23:29] dont start services you dont need [23:29] dileks: it is a temporary situation… anyway ok, I can try to stop that and to configure static assignment [23:31] Oh… I see from dmesg that isc-dhcp-server terminated incorrectly many times. [23:33] yupp, thats why I asked you to try static-IP [23:34] 6882 is related to torrent i see… maybe I should also stop anything related to that... [23:41] dileks: I didn't mention anyway that without X/KDE I couldn't reproduce the problem [23:43] doesnt kde has a nm-frontend (nm-service)? [23:43] yes [23:44] I mean that I simply shutdown X and KDE and the connection stayed up for the entire day. [23:49] sounds like wake-on-lan is activated in your bios [23:50] possible. Why? [23:52] if you say shutdown computer [23:53] sorry, maybe I explained myself the wrong way. I shutdown the X server. I remained in the terminal without X running. [23:55] inspect with netstat [23:56] what exactly? This problem has started with 12.04. Never had this problem before. This desktop stays up 24h. [23:57] open ports/connections [23:57] network* [23:59] At the moment I have less than 20 connections. The problem is that when the problem occurs I cannot debug. Pluggin a mouse in the port is sufficient to start the network and solve the issue.