/srv/irclogs.ubuntu.com/2013/10/07/#ubuntu-kernel.txt

=== fmasi_afk is now known as fmasi
* apw yawns08:10
* cking offers apw coffee08:11
* apw looks at the kettle, seems its tea for now, the coffee grinder is just toooo noisy to deal with this early in the morning08:12
infinityI think small town living is getting to you.08:12
infinityA coffee grinder at 9am is nothing compared to jackhammers outside at 6 in a real city.08:13
apwinfinity, oh so very true, so very very true08:15
* infinity can't wait to move back downtown next month.08:15
infinitySomething about the complete lack of street noise out in the suburbs just amplifies ten-fold the one car that DOES drive by at 3am.08:16
apwyeah that is true you need either silence, or a constant drone08:19
apwthough you could just fire up leviathan and get the same effect no ?08:19
ckingeither stick your head in a complete vacuum or inside a server, either suffice08:19
infinityapw: leviathan is right next to my ear, though, not quite the same as street noise.08:24
infinity(This, too, will change when I move)08:24
apwinfinity, and if i make it compile a nice kernel for you to get a bit more variablility?08:24
infinityHeh.  Are you hinting that you need the machine?08:25
infinityI thought you were all done being nice to flavours for this cycle.08:25
apwheh no don't need it08:28
apwi was just trying to help you sleep08:28
infinityToo kind.08:29
infinityapw: Is there another kernel coming before release, or are we shipping with what's in the archive?08:31
apwinfinity, we have a pending fix for confinment which i believe needs to go in, i should have it shortly for testing with a view to getting it in today08:32
infinityapw: Alright, cool.  Hopefully, small and testable fix(es) only from here out, unless we're doing a full SRU-style validation.  Don't want any unexpected regressions before release day.08:33
apwinfinity, yep i will confirm, but this is eminently testable, and will be pounded i am sure, and the other bits which come with have been validated already and are hyper-v specific08:34
infinityMmkay.08:35
apwsadly many of the hyper-v flaws prevent boot so are not handleable as a day008:35
apwinfinity, oh i lie the hyper-v bits mostly made the last upload, so its thiner than i thought08:37
infinityEven better.08:37
infinityapw: Did you catch my prattle in /msg over the weekend about dropping some build-deps for headers-only arches?08:38
apwinfinity, it is possible that that is sitting in /msg on my other machine (i am remote right now)08:38
apwso if you want to paste it back to /msg that'd work08:39
infinityAssuming a headers-only build doesn't need things like libdw-dev, libelf-dev, etc, it would be nice to arch-restrict those to only the arches that actually build kernels/tools.08:40
infinityPerhaps we should test this theory before we break anything.08:40
infinity(This is motivated by elfutils being broken on arm64 right now, and my wanting to actually build the headers correctly in the archive from the linux source package)08:40
infinityapw: If you hold off on your upload until after I've had a nap, maybe we can pick this up in the morning, and I can do some test builds on real hardware.08:41
apwinfinity, sure, i expect tim will be point on uploading tonight, or me in the am08:41
infinityapw: Alright, well pass along to Tim that I'd like to hold off for this change too, then. :P08:42
infinityOr maybe I'll find the brainpower and/or motivation to hunt down why elfutils hates me tomorrow.08:43
infinityBut I dunno.08:43
infinityStill seems silly to install build-deps one doesn't need for a header-only build.08:43
apwinfinity, so that'd be for powerpc i assume08:47
infinityapw: arm64, powerpc, x32, ppc64el08:49
infinityapw: The inverse is easier to express, in that you only need certain build-deps on [amd64 i386 armhf] until other arches also build kernels/tools.08:50
apwinfinity, yeah makes sense, it would be nice if you could have 'includes' for things like that08:51
apwBuild-dep-<random keyword>: stuf08:51
apwBuild-depends: Build-depends-<random keyword> [i386] sort of thing08:52
infinityapw: The whole deb-profile stuff (when done) sort of caters to this, though these aren't really build profiles.08:52
infinityapw: It's not uncommon, though, for build-deps to be autogenerated based on smarter lists (see d-i's control file, for instance, which is self-regenerating madness)08:53
jjohansencking: try pulling from the tree now08:55
infinityapw: Would be cute if you could hook it into the do_* targets somehow, but parsing that out to magically divine build-deps sounds painful.08:55
ckingjjohansen, thanks08:55
infinityapw: (Since you have some build-deps that are generic, some just for kernels, some just for tools...)08:55
apwinfinity, yeah indeed, it would be nice to have at least # Build-depends-tools: <list>08:56
apwin there so _we_ know which are added why08:56
infinityapw: Anyhow, engineering something fancy is probably out of scope for what will (hopefully) be the last upload in saucy.  But I'll play in the morning with getting a diff to arch-restrict a few build-deps to make headers-only builds more lightweight.08:57
apwinfinity, sounds great, as it is low risk08:58
infinityzequence: Thanks for the SRU kernels, BTW.  Everything's built and copied to -proposed now.09:02
=== psivaa-afk is now known as psivaa
zequenceinfinity: cool09:16
zequenceI'm off to the dentist soon again. Pain meds aren't helping anymore.09:17
zequenceWisdom teeth aren't all that wise, evolutionary-wise09:18
infinityzequence: I had mine done at 15.  My condolences for doing it as an adult.09:19
infinityzequence: At least you have an excuse to be whiney for a few days.09:19
apwzequence, ouch, you have my sympathy09:33
zequenceMight have melted some stiches by drinking rum the same day as the operation. So, I should probably just blame myself - or the dentist. Not sure yet :P09:46
=== fmasi is now known as fmasi_afk
=== psivaa is now known as psivaa-afk
* henrix -> lunch12:36
=== psivaa-afk is now known as psivaa
* apw runs for home ...13:06
=== fmasi_afk is now known as fmasi
sforsheertg: is there any reason to have the CONFIG_ANDROID options enabled in our non-touch kernels?13:36
sforsheertg: I ask because of bug #123516113:37
ubot2Launchpad bug 1235161 in linux (Ubuntu) "lowmemorykiller killing processes when swap still available" [Undecided,Confirmed] https://launchpad.net/bugs/123516113:37
rtgsforshee, hmm, lemme check13:39
rtgsforshee, how about CONFIG_ANDROID_LOW_MEMORY_KILLER=n ?13:43
sforsheertg: I definitely think that's what we should be using, but I'm wondering if we should go a step further and do CONFIG_ANDROID=n13:44
rtgsforshee, I was just looking at the other android staging bits. though most of them are built in, they don't really do anything unless prodded (so far as I've looked)13:45
sforsheertg: indeed, the rest probably are mostly harmless13:46
sforsheeI'm not so sure about including binder support however13:47
rtgsforshee, alarm-dev seems a bit more proactive....13:47
=== kentb-out is now known as kentb
rtgsforshee, can you think of any possible use folks might have for these android bits ? they _are_ staging. as such, they are also subject to abrupt termination.13:49
rtgor removal13:50
sforsheertg: not outside of the touch images. I'm sure people _could_ find uses for them, but I'd think it unwise to become reliant on them for sure.13:52
sforsheertg: my inclination is towards CONFIG_ANDROID=n, but at minimum the lowmemkiller should be disabled. It needs active management by userspace to be useful, afaict.13:53
rtgsforshee, agreed (about ANDROID=n). I'm whipping up a patch and test build...13:54
sforsheertg: ta13:56
nessitajsalisbury, hey there, you around? have some minutes?14:08
rtgsforshee, patch sent14:08
sforsheertg: ack14:09
nessitajsalisbury, regarding bug #1201528 (I was on a leave for 2 weeks so I'm catching up with it): not sure where to get kernel 3.11.0-7 from, on my saucy installation I have 3.11.0-11-generic, and on the precise installation I'm not sure where to install it from (I can not find 3.11.0-7 on http://kernel.ubuntu.com/~kernel-ppa/mainline/)14:10
ubot2Launchpad bug 1201528 in linux (Ubuntu Saucy) "[INTEL DP55WG,Realtek ALC889] - Audio Playback Unavailable" [Medium,Incomplete] https://launchpad.net/bugs/120152814:10
nessitaI guess I will leave a comment in the bug report14:10
nessitajsalisbury, replied to the bug report, now I need to reboot because audio playback broke while testing the latests kernel with mumble :-)14:16
jsalisburynessita, I'll checkout the bug comment14:36
jsalisburynessita, No need to test 3.11.0-7 anymore, since there is a newer kernel.  Just confirming the bug still exists in the latest saucy kernel is good enough.14:36
nessitajsalisbury, perfect, already did14:36
jsalisburynessita, thanks.  I'll post the next test kernel to test in the bug.14:37
nessitajsalisbury, awesome. Is there any way you could post a list of ~5 kernels to test? is easier for me to do so in batch, since I need someone else on mumble to chat with me to ensure proper testing14:38
jsalisburynessita, sure14:38
nessitathanks!14:39
jsalisburynessita, if we end up having to bisect further, that would only give us one kernel at a time to test though.14:40
nessitajsalisbury, no problem14:41
=== fmasi is now known as fmasi_afk
rtgjsalisbury, if you haven't already seen it, please work with the reporter on bug #1234662 and build him some test kernels.16:19
ubot2Launchpad bug 1234662 in linux (Ubuntu) "Ubuntu-lts-3.8.0 kernels corrupt ext[234] filesystems with 1k block size in Xen guests" [High,Confirmed] https://launchpad.net/bugs/123466216:19
xnoxIs there any general advice w.r.t. debugging kernel panic? "Unable to handle kernel paging request at virtual address c02fabe4 pgd = d5e24000" bug #123644416:19
ubot2Launchpad bug 1236444 in linux-goldfish (Ubuntu) "kernel panic" [Undecided,New] https://launchpad.net/bugs/123644416:19
xnox?16:19
rtgxnox, ow!16:21
xnoxrtg: i know that apparmor triggers it (disabled) later, "Setting up X socket directories..." triggers it.16:21
jsalisburyrtg, I pinged kamal about that bug on Friday.  It seems that commit can't be backported very easily to 3.8, which is why it wasn't picked up from stable.16:22
xnoxrtg: there are vague hints online that compiling with 4.7 helps (instead of 4.8) but we already do that.16:22
jsalisburyrtg, there is some history in #stable-kernel16:23
rtgxnox, actually, I'm using 4.6 on several of the Nexus kernels.16:23
rtgjsalisbury, ack16:23
rtgxnox, maguro, manta, and grouper16:25
xnoxrtg: what cross-prefix should I be using when cross-compiling goldfish? arm-linux-gnueabihf-, or CROSS_COMPILE=arm-linux-gnueabi-, or something else?16:26
xnoxrtg: or can you compile with 4.6 and give me the deb somehow, for me to try it?16:26
rtgxnox, yeah, gimme a min or 216:26
jsalisburyrtg, commit b764915 was cc'd to stable, but it doesn't look like it was picked up in any of the stable branches.16:27
jsalisburyrtg, except 3.1016:28
rtgjsalisbury, ok, just note it in the bug report I guess.16:28
jsalisburyrtg, ack16:28
xnoxrtg: cool.16:29
rtgxnox, http://kernel.ubuntu.com/~rtg/linux-image-3.4.0-1-goldfish_3.4.0-1.7_armhf.deb - Note that this has patches from jjohansen that fix socket containment.16:40
xnoxrtg: better. Let me re-enable apparmor, and reboot again.16:44
rtgxnox, better, as in no crashes ?16:47
xnoxrtg: yeap, all is perfect with http://kernel.ubuntu.com/~rtg/linux-image-3.4.0-1-goldfish_3.4.0-1.7_armhf.deb16:53
xnoxrtg: all init succeeded, all android lxc container finished booting, system is stable and works for >> 2 minutes16:54
rtgxnox, so, the question is was it the compiler or jjohansen's patches. do you have time to try another deb built with gcc-4.7 ?16:54
xnoxrtg: yeap, I have time to try another deb.16:54
rtgxnox, ok, 10 mins16:54
kamaljsalisbury, hey did you ever get any response from anyone re: your patch "Input: cypress_ps2 - Return zero finger count if palm is detected."17:13
xnoxrtg: I need to go, ping me URL to the new kernel, when ready. And i'll test it when I get back.17:15
rtgxnox, http://kernel.ubuntu.com/~rtg/linux-image-3.4.0-0-goldfish_3.4.0-0.7_armhf_gcc47.deb - Note this is a downgrade from the previous kernel (ABI change)17:17
xnoxrtg: panics.17:30
rtgxnox, dang compiler then17:31
xnoxrtg: =(17:31
jsalisburykamal, I didn't get any response from upstream, but I'll ping them again or see if it was accepted.18:43
kamaljsalisbury, if you haven't heard back, then it probably hasn't been ... yes, I recommend pinging dmitry and rydberg18:44
jsalisburykamal, ack18:48
apwrtg, did i see compiler issues with arm for goldfish?20:21
apwwe did get a new compiler this week, arm changes only20:23
apwi know jj wont see it quite like that :)20:24
apwbah20:24
rtgapw, yeah, I rebuilt with gcc-4.6 and all of xnox's problems seemed to go away.20:59
rtgapw, I pushed a patch to change the armhf compiler for goldfish21:13
* rtg -> EOD21:28
=== RAOF_ is now known as RAOF
=== JanC_ is now known as JanC

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!