[12:08] <poelzi> a question. do you guys plan to enable the autogrouping feature in 2.6.38 ?
[12:39] <abogani> poelzi: It is already enabled.
[12:46] <poelzi> abogani: is there a common way to disable it. my current project ulatencyd does the same job more advanced. i just made packages in they should disable the autogrouping then
[12:56] <poelzi> ahh. i found it
[13:16] <apw> poelzi, there is meant to be a kernel comamnd line option and a sysctl with the full patch
[13:16] <apw> poelzi, not sure they are there for the one which is in natty as uploaded
[13:17] <poelzi> apw: i just looked it up and i'm now using the sysctl to disable autogrouping when detected
[13:18] <apw> not sure if the v2.6.37 version we have applied has those toggles or not
[13:18] <poelzi> that would be quite bad
[13:18] <poelzi> but i guess the autogrouping will schedule only once ?
[13:19] <apw> poelzi, *shrug* it won't be in the archive that long, and natty is often broken
[13:19] <poelzi> as ulatencyd uses netlink to schedule new processes quite fast, it should move it away
[13:20] <apw> poelzi, sounds about right
[13:49] <jibel> apw, Hey, could you have a look at bug 703553, it's been introduced by the kernel in maverick-proposed apparently.
[13:49] <ubot2> Launchpad bug 703553 in linux (Ubuntu Maverick) (and 1 other project) "After upgrade to linux-image-2.6.35-25 graphics are broken (affects: 14) (dups: 2) (heat: 62)" [High,Confirmed] https://launchpad.net/bugs/703553
[13:54] <apw> jibel, looks bad to me, i've subscribed the stable team ... they will be pleased
[13:54] <jibel> apw, thanks. 
[14:01] <apw> bjf[afk], ^^
[15:29] <bjf> apw, yes, I saw it earlier
[15:32] <apw> bjf, cool
[15:32] <bjf> apw, not really :-)
[15:32] <apw> bjf, cool for me its on your list not mine :)
[15:54] <bjf> ##
[15:54] <bjf> ## Ubuntu Kernel Team Meeting - Today @ 17:00 UTC - #ubuntu-meeting
[15:54] <bjf> ##      agenda: https://wiki.ubuntu.com/KernelTeam/Meeting
[15:54] <bjf> ##
[15:55] <sforshee> regarding bug 702407, I have a pretty trivial patch that helps with diagnosing hotkey issues on thinkpads. Would this be something we would want in a lucid/maverick SRU?
[15:55] <ubot2> Launchpad bug 702407 in udev (Ubuntu) (and 1 other project) "thinkpad_acpi generated EV_KEY events are mssing scancodes (affects: 1) (heat: 8)" [Medium,Fix committed] https://launchpad.net/bugs/702407
[15:55] <sforshee> I've submitted the patch upstream and it's been acked by the maintainer, but it isn't merged into any trees yet
[15:57] <smb> We probably should wait until it hits upstream. As it is not directly a bug that is fixes the argument may be sort of aiding enablement. Which may rather qualify it only for Lucid as Maverick more and more reaches the end for that kind of things
[15:58] <mjg59> sforshee: I'll merge that this week
[15:59] <apw> sforshee, then i could suck that in to natty for the -rc1 kernels for you to test
[15:59] <sforshee> mjg59: great, thanks!
[15:59] <apw> smb, i think we should consider it for L and M as it does mean that pitti can fix a lot more stuff without bothering us
[16:00] <apw> and sforshee congrats, thats great
[16:00] <sforshee> apw, thanks
[16:00] <smb> apw, He might be more relaxed about that change (not fixing a bug) in that case as he is affected. :)
[16:05] <tgardner> apw, will soon push a patch for bnx2 firmware file name updates in d-i/firmware/nic-modules 
[16:05] <tgardner> just test building to make sure
[16:06] <apw> tgardner, again?  what the heck is with that driver changing each and every time
[16:06] <apw> tgardner, and mei aculpa i did not do a full build yet
[16:06] <tgardner> apw, I guess its just firmware version updates.
[16:07] <apw> tgardner, yeah, just odd that that one driver is always the one which does it
[16:07] <tgardner> apw, not so odd really. there are only 2 drivers in that udeb that need firmware, and the e1000 seems to be pretty stable.
[16:08] <apw> tgardner, i just didn't want you getting over excited and doing the rebase too, it took me a day and half with all the issues in ubuntu/ drivers
[16:08] <apw> so i pushed it before i had time for a full rebuild test
[16:08] <tgardner> apw, no worries. I just sat around and drank beer and chased woman for 3 days :)
[16:09] <apw> tgardner, sounds wonderful ;)
[16:10] <apw> tgardner, let me know when you've pushed and i'll get my builds going
[16:10] <tgardner> apw, pushed
[16:21] <apw> sforshee, have you got a bug number for that thinkpad patch ... do i can track it as it merges
[16:21] <apw> so
[16:21] <sforshee> apw, 702407
[16:23] <apw> sforshee, doh its in my web browser already ... mind==gone
[16:24] <sforshee> apw, np, it's near the end of your day so you have an excuse
[16:33] <bjf> ##
[16:33] <bjf> ## Kernel team meeting in 30 minutes
[16:33] <bjf> ##
[16:34] <Diels-Alder> hi everybody
[16:35] <Diels-Alder> I need an information
[16:35] <Diels-Alder> do you know the first kernel that fully support core i7?
[16:36]  * apw wonders which code name i7 had
[16:37] <smb> Had been running 2.6.32 with one, though that probably was not the first one
[16:37] <elmo> nehalem
[16:38] <Diels-Alder> yes nehalem core i7 930
[16:41] <apw> yeah my earliest experience i think was on Lucid for those
[16:43] <smb> apw, Sounds reasonable. There is a patch to recognize Nehalem IDs in coretemp going into 2.6.27-rc4
[16:44] <smb> which seems about the first places to see that word. Whether that means full support is something else
[16:49] <Diels-Alder> thanx
[16:49] <Diels-Alder> byebye
[16:51] <tgardner> bjf, pushing Maverick LBM to canonical-kernel-team PPA
[16:51] <tgardner> sconklin, ^^
[16:51] <bjf> tgardner, ack
[16:51] <sconklin> tgardner: ack
[16:54] <bguthro> I think .35 had the first full Ironlake support, as part of the i7 - so if by "full support" you include graphics, I think it was .35
[17:01] <tgardner> sconklin, as part of your source package checklist, do you verify the upload pocket is correct for the canonical-kernel-team PPA? e.g., maverick v.s. maverick-proposed ?
[17:01] <bjf> ##
[17:01] <bjf> ## Meeting starting now
[17:01] <bjf> ##
[17:02] <sconklin> Not on the manual checklist, bradf can say whether it's in the script
[17:03] <bjf> tgardner, noted
[17:25] <komputes> Anyone seen rtg recently?
[17:29] <apw> komputes, if thats about the touchpady thing, then its now Fix Committed for both maverick and lucid
[17:30] <komputes> apw: it is, when can we expect the update?
[17:31] <apw> komputes, i think we are in the middle of an SRU cycle, so if a perfect world i think its about 3 weeks from release if its in master-next
[17:32] <komputes> apw: will pass that along, thanks for the info
[17:34] <tgardner> bjf, sconklin-afk - did the armel build issues get sorted? I notice that the maverick meta still has them disabled.
[17:35] <bjf> tgardner, not that i'm aware of, sconklin is tracking it
[17:35] <tgardner> bjf, ok. I'm gonna whack on maverick meta to enable the new compat-wireless-2.6.37 package
[17:36] <bjf> tgardner, ack, sconklin ^
[17:36] <apw> tgardner, i suspect till we ask for a build in there we won't find out
[17:37] <jjohansen> rebooting
[17:38] <tgardner> apw, I guess I was asking 'cause I wanted to know that someone was actually working on it.
[18:00] <tgardner> sconklin-afk, bjf: could you use your not inconsiderable influence to get linux-backports-modules-2.6.35 copied to -proposed from the canonical-kernel-team PPA ?
[18:00] <bjf> tgardner, ack, will ping pitti
[18:00] <cking> bjf, where is that webby page of patches that need testing in proposed?
[18:01] <bjf> cking, https://kernel-tools.canonical.com/srus.html
[18:01] <cking> ta muchly
[18:02] <cking> and when's the next proposed - in 2 weeks time?
[18:02] <cking> (for maverick)
[18:05] <bjf> cking, roughly, yes
[18:09] <tgardner> bjf, I'm wondering if its really worth uploading LBM and meta to the canonical-kernel-team PPA if there are no CVEs ? Why not go straight to -proposed ?
[18:10] <bjf> tgardner, sconklin and i were talking about the same thing last week
[18:10] <cking> hrm, the Dell AMI all-in-one patch - got acked but did it get applied?
[18:10] <bjf> tgardner, i hate to have multiple processes but it seems to be more work to put things in the ppa
[18:11] <bjf> cking, yes, I put in into maverick yesterday
[18:11] <tgardner> bjf, seems like its only the kernels that are required to go through c-k-t
[18:11] <bjf> tgardner, ack
[18:12] <tgardner> bjf, well, I'll just upload meta to -proposed directly, then when LBM gets pocket copied everything ought to be copascetic
[18:12] <bjf> tgardner, ok, sounds reasonable
[18:14] <cking> bjf, thanks!
[18:24] <bjf> brb
[18:44] <bjf> apw, have a screenshot of the panic if you care :-)
[18:44] <apw> yep paste it up
[18:45] <bjf> it's in the root of my zinc account
[18:45] <bjf> apw, i have a thought on it
[18:45] <bjf> apw, i booted with a live image and mounted the root partition
[18:46] <bjf> apw, i noticed that though i'm booting 2.6.37-12, my initrd.img is still pointing at a -7 img
[18:46] <bjf> apw, looking in the boot directory, there isn't a -12 initrd.img file
[18:54]  * tgardner --> lunch
[19:04] <jbarnes> can someone make sure avahi gets patched so upstream kernels will work?
[19:05] <jbarnes> see http://www.spinics.net/lists/netdev/msg152775.html
[19:06] <cking> apw, ^
[19:06] <jbarnes> oh and making sure /sbin/installkernel gets fixed too would be a plus :)
[19:06]  * jbarnes has been waiting impatiently for 3 years for that fix
[19:29] <smb> :
[19:30] <tgardner> jbarnes, can you refresh my memory on your issues with installkernel?
[19:31] <jbarnes> tgardner: it doesn't make a new initrd nor update-grub to add it to the boot menu
[19:33] <tgardner> jbarnes, I guess I've never used it. lemme look. its part of debianutils
[19:38] <jbarnes> tgardner: I always just add mkinitramfs -o /boot/initrd.img-$ver $ver and update-grub to the end of the script
[19:38] <jbarnes> it's an easy fix
[19:38] <jbarnes> I just have to do it everytime I install a new dev machine :)
[19:39] <tgardner> jbarnes, Clint Adams <clint@gnu.org> appears to be the upstream for this. Have you sent him a patch?
[19:40] <jbarnes> no, iirc there's an upstream bug and fix, but it hasn't landed in debian
[19:43] <tgardner> jbarnes, I'll drop a note on the debian kernel list to find out if there is a good reason why mkinitramfs and update-grub shouldn't be run, especially if its an x86 arch.
[19:43] <jbarnes> thanks
[19:44] <tgardner> jbarnes, do you have a pointer to the bug? If not I can likely find it.
[19:45] <jbarnes> not offhand, apw gave it to me last time
[19:45] <bjf> Home: https://wiki.ubuntu.com/Kernel/ || Maverick Kernel Version: 2.6.35 || Ubuntu Kernel Team Meeting - January-25 - 17:00 UTC || If you have a question just ask, and do wait around for an answer!
[19:53] <tgardner> jbarnes, is http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=607411 what you're thinking of?
[19:53] <ubot2> Debian bug 607411 in debianutils "installkernel should run-parts /etc/kernel/postinst.d" [Wishlist,Open]
[19:53] <jbarnes> tgardner: yeah looks like that would do it
[19:54] <tgardner> jbarnes, I'll mess with it. I can likely get it fixed for Natty
[19:54] <jbarnes> sweet
[20:03]  * jjohansen -> lunch
[20:49] <apw> jbarnes, i have the avahi issue reported with the upstream avahi
[20:49] <apw> jbarnes, i assume that they are not going to back out the change
[20:49] <jbarnes> cool
[20:50] <tgardner> apw, did you get it uploaded?
[20:51] <apw> tgardner, not as yet, the advice from foundations was to wait a couple of days to let upstream fix it, if that occurs in time the we can just sync the fix in, if that isn't here in time then we do my fix
[20:51] <tgardner> apw, so, in the meantime everything is broken?
[20:51] <apw> tgardner, only if you have .38 installed which isn't in the archive
[20:52] <apw> basically they said shove it in if we upload .38
[20:52] <tgardner> ok
[20:53] <apw> i will ask my friendly tgardner to sponor my upload should that happen
[20:54] <tgardner> apw, I'm not gonna be around much tomorrow. Likely gone by 0900 my time
[20:54] <apw> tgardner, no worries, i am sure martin or colin will handle it, they are both aware
[22:18] <manjo> sforshee, did not see a mail from you yet ... 
[22:19] <manjo> bjf, call is 6pm pacific ? 
[22:19] <bjf> manjo, that's what the email says
[22:20] <manjo> bjf, just making sure, that is 8pm for me 
[22:23] <sforshee> manjo, I sent one on Thursday, I'll try resending
[22:24] <manjo> sforshee, thanks
[22:24] <sforshee> manjo, just resent the message, let me know if you don't get it sometime soon
[22:25] <manjo> sforshee, did you send it to marjo ? :) 
[22:25] <manjo> will wait for it ... 
[22:26] <sforshee> manjo, i replied to the message you sent me
[22:27] <manjo> ok
[22:43] <sforshee> manjo, did the email ever arrive?
[22:45] <manjo> sforshee, just pm me .. I did not get it 
[23:14] <bjf> apw, I "fixed" my natty, I reinstalled Alpha 1 and then just updated the kernel. The initrd was correctly updated. I rebooted and then dist-upgraded and rebooted again and I'm up
[23:16] <bjf> apw, if you just do a straight dist-upgrade from an alpha 1 install "bad things happen"
[23:20] <jjohansen> bjf: is that a new problem?  I have a machine that I have been updating and haven't run into any problems
[23:20] <jjohansen> well besides it still doesn't have video
[23:21] <bjf> jjohansen, i had a natty that was dist-upgrading just fine until the friday before the sprint and then it just came apart
[23:21] <bjf> jjohansen, i was forced to install Maverick to have a system to take with me
[23:22] <jjohansen> bjf: interesting, I know I have dist-upgraded during the sprint
[23:22] <bjf> jjohansen, I just tried putting natty on it today and ran into the same issue, above is my work around
[23:22] <jjohansen> hehe, well I still have maverick + natty kernel on the machine I was going to take
[23:22] <jjohansen> bjf: okay, I'll take a stab at replicating here
[23:49] <mrtadis> Hi, my Ubuntu 10.04 laptop wakes up from suspend unexpectedly. Does the OS logs what was the wake-up source?