[08:41]  * smb initiates the yawning sequence
[08:52] <ppisati> smb: you are not supposed to yawn, go back o your bed
[08:52] <ppisati> *to
[08:53] <smb> ppisati, Its late enough for me to yawn. ;-P Good morning
[09:39]  * cking now yawns
[09:59]  * cking does a clean install, back later
[10:32] <infinity> cking: Any interest in hanging out with humans for release sprinty things, or would you prefer not?
[10:33] <cking> infinity, i'd prefer not, I think if any iso testing is required I have loads of kit at home so its more productive if I'm in my office
[10:33] <infinity> cking: So, on the one hand, ECHAN, on the other hand, alright, thought I'd ask. :)
[10:34] <cking> thanks for asking, it's always good to be at the release sprint, but in the past i've always found I've needed kit that I can't bring into the office
[10:36] <infinity> cking: Right.  Well, pop in for finger sandwiches later. :P
[10:36] <infinity> (Made with real fingers)
[10:36] <cking> yeah, I'll try and do that, cant' miss the fingers
=== fmasi is now known as fmasi_brb
=== fmasi_brb is now known as fmasi
=== fmasi is now known as fmasi_lunch
=== fmasi_lunch is now known as fmasi
=== hggdh_ is now known as hggdh
[13:06] <Kano> hi, do you update the unstable branch soon?
=== ghostcube_ is now known as ghostcube
[15:07] <jsalisbury> **
[15:07] <jsalisbury> ** Ubuntu Kernel Team Meeting - Today @ 17:00 UTC - #ubuntu-meeting
[15:07] <jsalisbury> **
=== hatch__ is now known as hatch
[16:06] <arges> jsalisbury: hey
[16:06] <jsalisbury> arges, o/
[16:07] <arges> jsalisbury: bug 1283604 can I add it to teh list
[16:07] <ubot2> Launchpad bug 1283604 in linux (Ubuntu) "WARNING: CPU: 0 PID: 5517 at /build/buildd/linux-3.13.0/fs/sysfs/group.c:214 sysfs_remove_group+0xc6/0xd0()" [High,Confirmed] https://launchpad.net/bugs/1283604
[16:07] <jsalisbury> arges, sure thing
[16:07] <arges> jsalisbury: i have a fix already for it btw
[16:07] <jsalisbury> arges, awesome
[16:07] <jsalisbury> arges, I can't hear anything on mumble, its all breaking up, so I may reboot
[16:08] <arges> jsalisbury: ok
[16:57] <jsalisbury> ##
[16:57] <jsalisbury> ## Kernel team meeting in 5 minutes
[16:57] <jsalisbury> ##
=== jsalisbury changed the topic of #ubuntu-kernel to:  Home: https://wiki.ubuntu.com/Kernel/ || Ubuntu Kernel Team Meeting - Tues April 1st, 2014 - 17:00 UTC || If you have a question just ask, and do wait around for an answer!
=== jono is now known as Guest59567
[18:23] <rtg> dannf, how is 3.13.0-19.40 working for you ?
[18:49] <dannf> rtg: according to ikepanhc, quite well (he's done more testing than i)
[18:51] <rtg> dannf, ok, thats good to hear.
[18:51] <dannf> there are a couple more drivers we'd like to get in if we can get 'em tested in time (ipmi/xgene-gpio), but they may have to wait for an SRU proposal or 14.04.2
[18:52] <rtg> dannf, I can accommodate a new driver under SRU policy as long as there is no risk of regression to other subsystems.
[18:54] <dannf> understood
[18:55] <rtg> dannf, unless that happens this week, though, it ain't gonna make it until after release
[18:57] <dannf> rtg: also understood :) luckily these drivers aren't installtime requirements, so hopefully we can install w/ 14.04 and upgrade to a kernel w/ that support
[18:57] <dannf> should they be SRU'able
[18:57] <rtg> that works for me
[18:58] <dannf> rtg: 19.40 is the one from last week right - there hasn't been a second upload supporting x-gene correct?
[18:58] <dannf> wondering if we've been testin gthe latest
[18:58] <rtg> 19.40 is current
[19:01] <dannf> rtg: oh sweet - that has the udeb fix. time for me to start hacking on d-i :)
[19:03] <rtg> dannf, right, that spelling change was about the last fix I had for x-gene (that I knew of)
[19:03] <dannf> yep, that's all we have for you atm
[19:03] <ParkerR> Have their been any plans on an updated kernel for the Nexus 7? The latest even in trusty in 3.1 https://launchpad.net/ubuntu/trusty/armhf/linux-image-grouper
[19:03] <ParkerR> *is
[19:05] <rtg> ParkerR, all of the touch kernels are ging to stay at their Android release versions. Grouper will forever be 3.1
[19:06] <ParkerR> D:
[19:07] <ParkerR> I've been attempting a compile on my own but the 8MMB boot partition limit is kinda annoying
[19:07] <ParkerR> *8MB
[19:08] <ParkerR> rtg, Thaks for the response.
[19:08] <ParkerR> *Thsnks. I swear I can't type today
[19:08] <rtg> gotta love embedded systems
[19:08] <ParkerR> I give up :|
[19:09] <ParkerR> Mainly I've been compiling to get DRM_TEGRA. Plus the kernel has had many ARM improvments since 3.1. Oh well, I'll continue on this adventure.
[19:13] <rtg> arges, is bug #1297307 a duplicate of bug #1283604 ?
[19:13] <ubot2> Launchpad bug 1297307 in linux (Ubuntu) "sysfs group <address> not found for kobject 'target6:0:0'" [Undecided,Incomplete] https://launchpad.net/bugs/1297307
[19:13] <ubot2> Launchpad bug 1283604 in linux (Ubuntu Trusty) "WARNING: CPU: 0 PID: 5517 at /build/buildd/linux-3.13.0/fs/sysfs/group.c:214 sysfs_remove_group+0xc6/0xd0()" [High,Fix committed] https://launchpad.net/bugs/1283604
[19:17] <arges> rtg: i filed 1297307 and marked it a dup of 1283604
[19:17] <arges> i filed it first, then found the duplicate later
[19:17] <rtg> arges, ok, I was just catching up on my bug mail backlog
[19:18] <arges> rtg: i guess i didn't mark it as a dup... oh well thought i did ... fixing it
[19:18] <rtg> there is sure a slew of resume bug reports
[20:05] <rtg> sforshee, why is bug #1297370 invalid ?
[20:05] <ubot2> Launchpad bug 1297370 in linux (Ubuntu) "iwlwifi firmware error: 0x00000038 | BAD_COMMAND" [Low,Invalid] https://launchpad.net/bugs/1297370
[20:05] <sforshee> rtg: because I triggered it by writing to a sysfs file whose sole purpose is to create that error
[20:06] <sforshee> rtg: those bugs are just me testing some changes to apport to collect the real firmware crash bugs
[20:06] <rtg> sforshee, ah