18:03:43 #startmeeting 18:03:43 Meeting started Fri Jul 20 18:03:43 2012 UTC. The chair is davej. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:03:43 Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:03:43 #meetingname Fedora Kernel meeting 18:03:43 The meeting name has been set to 'fedora_kernel_meeting' 18:03:43 #meetingtopic Fedora Kernel meeting 18:03:47 #addchair jforbes jwb 18:04:22 * davej stretches 18:05:09 not a huge amount to talk about today, so we're probably just to talk about the state of the various branches, and then do open floor. 18:05:47 f16 & f17 are still on the latest 3.4 stable kernel 18:06:28 we've been making some progress at closing out some of the older bugs against those releases this last few weeks 18:06:46 16 in particular at one point was almost touching 600 bugs. Now down to just over 500. 18:06:52 'just' 18:07:35 jwb: anything to add for 17 ? 18:09:12 ugh, sorry 18:09:34 no, not much to add for F17. basically chugging along 18:09:46 fixed up a few custom compile failures today 18:10:49 looking over the 17 bugs that are open, nothing jumps out as a particular problem area, (well no more than usual, wireless bugs aplenty etc) 18:11:07 yeah. wireless, some suspend/resume issues, a few backlight ones 18:11:20 those are the big three areas i've noticed 18:11:32 I'm hoping to get 16's bug list more current soon, to try and get a better picture as to what's still a problem there 18:12:12 I was thinking earlier today, that it's weird that given it's the same code, the number of times we get the same bug reported on 16 and 17 is kinda low, unless it's in something like iwlwifi 18:12:40 yeah, i'm kind of surprised at that too 18:13:09 I don't know if it's just different userspace interaction, or just more users testing the latest release. 18:14:18 jforbes: want to say something about rawhide ? 18:14:25 Seems F16 is more likely to get bugs filed against older kernels 18:15:07 Rawhide is tracking 3.5-rc7, I expect 3.5 to be released soon, doubt there will be an rc8. Most of the commits this week have been minor bug fixes and additional device support 18:15:46 a couple of the md bug fixes look good, but probably not enough to warrant an rc8 18:15:47 rc7 had a resume issue, right? already fixed? 18:15:57 nirik, yeah and yeah 18:16:06 nirik: yes, that commit is in 18:16:07 bug from the leapsecond rework 18:16:18 * nirik hit that, but it was already fixed by the time I looked to report it. Good work. ;) 18:16:38 yeah. we tracked upstream HARD on that one. tons of work ;) 18:16:54 heh 18:17:07 I noticed that dracut seems to require modules.dep as of today to build an initramfs and rc7 git0 didn't have that. 18:17:48 what? modules.dep is created at RPM install time 18:18:21 brunowolff: problems installing git0? 18:19:39 Something odd might have happened. I'll look at reinstalling that kernel again and see if I can run dracut on it again successfully. 18:20:42 I don't know what would have removed modules.dep. And when I had previously run dracut (via the kernel script) it worked fine. 18:21:05 I am running a debug kernel right now, but i get annoying lag. 18:23:24 3.5 looks pretty solid in my local testing 18:23:39 (asides from the dumb bugs my fuzzer is catching, but there's fixes in flight for those) 18:23:48 i've seen the same 18:23:59 I have been fairly happy with it. 18:23:59 we're shooting for 3.6 for F18, right? 18:24:05 I don't have any reservations about pushing that out to 16/17 when it's released 18:24:11 Hope so 18:24:13 jwb: yeah, I think we've got time 18:24:39 It looks like my problem was just on one machine. I double checked on another and modules.dep is there. 18:26:34 My guess is that I must have run the wrong kernel script at some point. Thanks for noticing that it must have been something I did. 18:27:41 anyone got anything else ? 18:28:01 nothing here 18:28:14 have a question on the testing stuff 18:28:34 realized today that we had a small push last month and then things seemed to have gone quiet 18:29:08 yeah, we should revive that effort again. I think the focus on the bug backlog has been a good thing, but we should at least do another week on it next month. 18:29:25 we could schedule a virtual FAD for it 18:29:42 you want to set that up ? 18:29:50 can't hurt to get more attention I suppose 18:29:51 sure, can do. 18:30:17 i figure even if it results in just us working on it, at least we haven't wasted much more than an email and a blog post maybe 18:30:28 We could, and I need to push my local tree as well, though I haven't looked at it in a couple of weeks, other than actually running it 18:30:56 getting some more tests in there would be good too. 18:31:09 code hoarder jforbes ? 18:31:14 :) 18:31:45 more a slipping my mind 18:32:04 ok, I think we might as well call this done. end ? 18:32:11 yep 18:32:16 #endmeeting