[04:12] I just 'love' this... I try to use the newer flash in firefox and when launched from cli. I see this message when I try to play the flash '2.4+ kernel w/o ELF notes? -- report this'. You guys have any idea what it might be complaining about? [04:14] I see in the kernel config for the latest generic there's not much about ELF that's not added [04:18] I wonder if that [04:18] I wonder if that has something to do with why flash doesn't work for crap for me on this system [07:13] apw: after ethtool -K eth0 tx on, the data still moves fast [07:13] apw: so the problem actually doesn't reassert itself === amitk is now known as amitk-afk === amitk-afk is now known as amitk === smb` is now known as smb [08:49] akheron, interesting, could you document that in the bug as well [08:49] akheron, perhaps there is a source end clamping issue after all [08:50] akheron, One thing I was wondering as well, was that tcpdump taken in the domU or dum0? [08:51] apw, Good morning btw. :) [08:54] smb morning [08:56] moin [08:56] smb: the tcpdump in the bug desc is not mine [08:58] smb: but I had the same dump in my domU, didn't dump at dom0 [08:59] akheron, Ah ok. Hm, wondering whether it would add some insight to dump dom0. But probably its just the same [08:59] probably yes [09:05] apw: commented on the bug now [09:06] gah, there's a typo [09:06] I can't edit comments? [09:07] nope, that would be useful === diwic is now known as diwic_afk [12:21] hey [12:22] did anybody else report problems with the newest kernel in natty in vms? I can't start X in there: [12:22] [ 8.358283] WARNING: at /build/buildd/linux-2.6.37/drivers/pci/pci-sysfs.c:758 pci_mmap_resource.clone.9+0x156/0x1a0() [12:22] [ 8.358297] Hardware name: Bochs [12:22] [ 8.358300] process "Xorg" tried to map 0x00100000 bytes at page 0x00000000 on 0000:00:02.0 BAR 0 (start 0x f0000000, size 0x 2000000) [12:22] full dmesg log: http://people.canonical.com/~dholbach/tmp/dmesg.log === diwic_afk is now known as diwic [12:38] dholbach, nope noone mentioned it before you [12:38] want me to file a bug? with -4 it works [12:39] dholbach, please and assign it to me [12:39] will do [12:39] apw, what would a good bug title be so you can find it more easily? [12:39] "doesnt work" [12:39] :) [12:40] "IT DOESN'T WORK!!!!111!!!1!!111!11" [12:44] apw, ok nevermind, bug 676963 [12:44] Launchpad bug 676963 in linux (Ubuntu) "process "Xorg" tried to map 0x00100000 bytes at page 0x00000000 (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/676963 === cking is now known as cking|afk === cking|afk is now known as cking [13:17] dholbach, http://www.spinics.net/lists/kernel/msg1111743.html [13:17] apw, ^ upstream detection of regression of lp#676963 [13:19] smb thanks ... that thread says "its fixed in master" ... so i'll go look [13:29] smb, thanks [13:35] hi list I recently began doing kernel programming [13:35] I was able to develop a character device driver [13:35] based on my search on internet and docs here and there [13:36] I want to do bug fixing [13:36] and I had a look at the ubuntu kernel bugs page [13:36] I am reasonably Ok in C and programming [13:36] have been practising things for quite some time [13:36] I am not sure as which bug should I start with [13:36] can some one suggest me some thing [14:01] bond, JFo normally has a list of bugs which are of priority to us perhaps something off there would be suitable [14:11] sconklin, now that we have kernels in proposed, have you have any feedback from cert that they've gotten started? [14:11] had* [14:20] (or indeed have they been told they are there) [14:21] skaet, ? ^^ [14:22] tgardner, heard from victorp and they're ready to go as soon as sconklin sends the signal. [14:23] skaet, what signal? I think all we are lacking are the meta packages. [14:23] think the process is still going to be a bit manual in terms of the handover, until we get some flows and expectations nailed down. [14:24] skaet: If the packages are there, then they can start. I'll ping victor (I just walked in) [14:24] signal is to tell victorp(?) that its ready to be kicked of (via IRC, phone, email, etc.) [14:24] sconklin, yup, that's what seems to be needed right now. :) [14:24] sconklin, make sure they aren't depending on the meta packages to be up to date. [14:25] tgardner: they probably are, but I'll ask [14:25] sconklin, shall I upload those packages whilst you're talking to them? [14:26] tgardner: make it so ;) [14:26] :) [14:29] sconklin, maverick meta looks OK. 2.6.35.23.25, and the kernel ABI is 2.6.35-23.40 ( have to say it outlous 'cause these numbers make me dyslexic) [14:29] outloud* [14:29] tgardner: thanks [14:30] I don't recall an abi bump for either, but my memory is not to be relied on [14:31] sconklin, and lucid meta is 2.6.32.26.28, the kernel ABI is 2.6.32-26.47, so it all looks good. [14:32] tgardner: thianks, I've just informed Victor, and they'll start testing. [14:32] they both look up to date to me [14:33] sconklin, bjf[afk] i have moved the pre-preproposed kernels over to master-next for maverick and lucid [14:33] apw, I saw those go by on the c-k-t list this AM [14:34] oh yeah, thats where the accept emails go [14:34] apw, you did that yesterday around noon, right? [14:34] nope, today around 10 my time [14:35] apw: hmmm, there was a pile of stuff on both -next branches yesterday . . . [14:35] could somebody have a look at bug 674952 ? [14:35] Launchpad bug 674952 in linux (Ubuntu) "natty kernel doesn't work with voice input by microphone (affects: 1) (heat: 8)" [Undecided,New] https://launchpad.net/bugs/674952 [14:35] * sconklin looks at the repo [14:36] sconklin, huh? i only switched over the checker to -next today at 10, so that was the first it would have noticed [14:36] sconklin, what apw meant was is that he switched the pre-proposed builds to pull from master-next, [14:36] oh, I get it now. [14:36] Sweet, and thanks apw [14:36] Only one cup of coffee so far [14:36] sconklin, keep me in the loop if you are making -next for any other repos [14:37] apw: ack === bjf[afk] is now known as bjf === jdstrand_ is now known as jdstrand [15:04] dholbach, ok i've posted some test kernels in your bug if you could test for me ... :) [15:05] apw, sweet - thanks [15:12] dholbach: the lucid kernel in -proposed may fix your audio problem, it would be great if you could test it for me [15:12] sconklin, I'm in the office now, I'll test it tonight and send you a mail [15:12] I'm VERY much looking forward to it working again [15:12] :-) [15:13] sconklin, if we just start telling people the -proposed kernel will fix their bug, we get more -proposed testing, good plan [15:13] sconklin, :-) [15:13] haha [15:13] bjf: heh, yeah - only this time there's some fact-based reasoning behind that ;-) [15:13] bjf, there might be a future in marketing for you! [15:14] dholbach, i thought i was in marketing [15:14] right......... [15:14] :-) [15:18] apw, it works [15:18] dholbach, ack thanks [15:19] good work [15:19] thanks apw, sconklin, smb, ... and bjf: you rock! :) [15:20] dholbach: That's provably true now, and I'll continue their roadie training so they have a second career to fall back on ;-) [15:21] haha, excellent :) [15:22] bjf, don't forget to upload the LBMs for lucid/maverick [15:22] tgardner, ack [15:22] lots of ogasawara goodness therein [15:47] * apw pops to the bank === yofel_ is now known as yofel [18:14] bjf, sconklin, smb: https://wiki.ubuntu.com/ReleaseTeam/Meeting/2010-11-22-SR can you look over and add any points/questions as necessary pls. [18:14] * smb looks [18:16] skaet, speaking of which, do you have any bugs other than the one noted for me to keep an eye on? [18:16] JFo, yo ... yogout [18:16] did you just call me yogurt? ;-) [18:17] JFo, for the tomorrow agenda - just culling through the bugs right now. Will post something out after lunch. :) [18:17] coolness thanks :) [18:18] anyone decent with bug mail w/ lp? [18:18] i keep getting everything (including direct subscriptions) in kernel-bugs [18:18] i even tried leaving the team, but they're still coming [18:18] * vanhoof cant figure out why [18:18] You received this bug notification because you are a member of Kernel [18:18] Bugs, which is subscribed to linux in ubuntu. [18:19] ... must be some indirect association? [19:07] * tgardner lunches [19:11] vanhoof, probabally some other team is a member of that team, you can tell somewhere though [19:12] never sure how though [19:12] apw: i cant seem to find anything :\ [19:12] its weird, this just started on Nov 5th [19:12] at 3am [19:12] i certainly wasnt playing w/ mail or lp at 3am [19:13] that is probably when that crackhead put all those lists on Kernel-Bugs [19:13] I remember seeing the e-mail [19:13] which crackhead? [19:13] can't remember the guy's name now [19:13] annoying-mailing-list-dude? [19:14] but there was someone creating all these lists and adding tons of others [19:14] yeah :) [19:14] so not a literal crackhead :) [19:15] vanhoof ubuntu-kernel-team is a member of kernel-bugs [19:15] and i suspect you are an indirect member of that [19:17] apw: right, but would that trump me being a subscriber? [19:17] bugs i subscribe to are landing in kernel-bugs w/ that verbiage in them [19:17] * vanhoof is puzzled [19:18] is "kernel-bugs" a legitimate group or one the crackhead created? [19:18] legitimate [19:19] created by Brian Murray [19:19] iirc [19:19] been around a while [19:19] well he's a crackhead :-) [19:19] heh [19:19] sigh* [19:19] <-late lunch [19:19] I have got to do better at looking at the time === JFo is now known as JFo-food [19:25] #include [19:26] JFo-food: where did that email get sent? [19:26] this is pissing me off :\ [19:45] vanhoof, what do you mean? [19:46] Oh, Kernel-bugs... let me look [19:48] vanhoof, when you look at https://launchpad.net/~kernel-bugs what does it say in the active members section? [19:50] 62 active members [19:50] You are a member of the team that owns this team. You are not currently an active membe [19:51] not a member here [19:51] Sarvatt: those b43 updates went to kernel-bugs, even though im a subscriber [19:51] Sarvatt: which is why i didnt see it :) [19:51] so vanhoof you do or do not want mail from there? [19:51] just so I understand [19:52] Sarvatt, are you a member on https://launchpad.net/~ubuntu-kernel-team? [19:52] yeah I've been following, it's something you're in that i'm not. he doesn't want to be in it [19:53] nope! [19:53] JFo-food: well ive been in it since june [19:53] yeah, I see that [19:53] Sarvatt, want to be? :) [19:53] JFo-food: i left last night in an effort to fix mail [19:53] hmm [19:53] not if it's going to screw my mail filters :) [19:54] heh [19:55] it shouldn't [19:55] I don't see anything that would make me think something here is what hosed you vanhoof [19:55] ok [19:55] here's an example: [19:55] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/663442 [19:55] Launchpad bug 663442 in linux (Ubuntu Maverick) (and 1 other project) "S3 resume fails to restore video on Intel Sandybridge platforms (affects: 2) (heat: 127)" [Undecided,Fix committed] [19:56] all that lands in kernel-bugs [19:56] maybe i should have a few beers and search aruond :D [19:56] what mail client are you using? [19:57] tbird [19:57] because there may be a duplicates handling issue at play here === JFo-food is now known as JFo [19:58] yeah good idea [19:58] JFo-food: do you have the mailing list as the team contact address list for the team maybe? I dont have that problem with X bugs I'm subscribed to while being subscribed to the ubuntu-x-swat list manually, I think we did that for this exact problem [19:59] where do you mean Sarvatt? [19:59] (for kernel-bugs) [19:59] no, that isn't my team. [20:00] it has it's own e-mail address [20:00] https://launchpad.net/~kernel-bugs - change details - set contact details [20:00] oh ok, what a pain in the butt :) [20:00] it has no contact e-mail address set [20:00] yeah [20:00] :) [20:00] Sarvatt: do me a favor [20:00] it does have a list that I am not subscribed to [20:01] Sarvatt: update 663442 with something [20:01] i want to watch procmail [20:01] vanhoof, think it is the duplicate handling I mentioned? [20:02] well im doing no filtering in thunderbird [20:02] unless its server side duplication handling [20:02] hmmm [20:03] vanhoof: done [20:03] Sarvatt: k [20:06] * vanhoof waits for mail [20:12] hi guys, I have a question about a bug that was solved with a patch, but that patch wasn't integrated upstream in the kernel. I know maybe this is not the appropriate place, but maybe someone could point me to the right direction :) [20:12] Sarvatt: JFo here we go [20:12] From bounces@canonical.com Thu Nov 18 20:12:09 2010 [20:12] Subject: [Bug 663442] Re: S3 resume fails to restore video on Intel [20:12] Folder: /home/vanhoof/af/autofolder 5097 [20:12] autofolder: launchpad lpproj="kernel-bugs" [20:12] autofolder: delivering message via dovecot to folder lp.kernel-bugs [20:12] Launchpad bug 663442 in linux (Ubuntu Maverick) (and 1 other project) "S3 resume fails to restore video on Intel Sandybridge platforms (affects: 2) (heat: 22)" [Undecided,Fix committed] https://launchpad.net/bugs/663442 [20:12] wtf ... [20:12] very odd [20:13] you said you were unsubscribed or never subbed to the kernel-bugs list yes? [20:13] i unsubscribed last night [20:13] ah [20:13] may not have been done yet then [20:13] (it is possible) [20:13] try it again [20:13] :) [20:13] shades of reboot [20:13] this is the bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/278648?comments=all . until now I used a patched kernel, but this solution is not available in maverick. [20:13] Launchpad bug 278648 in linux-ubuntu-modules-2.6.24 (Ubuntu) (and 1 other project) "[regression]snd-hda-intel sound input does not work at all with Conexant CX20549 (Venice) chips (affects: 12) (dups: 1) (heat: 67)" [Undecided,New] [20:14] lol [20:14] i find it hillarious my email address is chris.van.hoof [20:14] lol [20:14] I didn't notice that [20:15] i dont use it [20:15] use the alias for in/out [20:15] you should get it changed to chris.von.und.zu.hoof@ [20:15] :) [20:15] X-Launchpad-Message-Rationale: Subscriber (linux in ubuntu) @kernel-bugs [20:15] weird [20:15] yeah, so no unsub processed [20:15] did you try the unsubscribe again? [20:16] oh wait a sec... [20:16] i cant [20:16] i can join/part it [20:16] :-| [20:18] JFo: just joined and left again [20:18] we'll see :\ [20:18] k [20:18] good luck [20:18] * JFo is looking at something that could be related [20:19] JFo: is there launchpad support? lol [20:19] i tried #launchpad, no luck [20:19] * vanhoof could just file a bug i guess [20:19] dunno [20:21] JFo: well thanks for looking for me [20:21] I see that I am getting the e-mail from them, but I am not subscribed either [20:21] hmmm [20:22] vanhoof, my pleasure [20:22] JFo: so you're seeing it too? [20:23] wonder if you are getting them via the ubuntu-kernel-team [20:23] yea [20:23] I see Robert's mail as the last one [20:23] JFo: find a bug you're physically subscribed to [20:23] see if its in the right place [20:23] and apparently I have been getting them too since the 5th [20:24] so it would seem I am in the same boat [20:24] hmm [20:24] bryceh: are you around? what did you do to ubuntu-x-swat to make it stop doing what they're describing? [20:24] JFo: too odd its on the 5th ... [20:24] yeah [20:24] bryceh: tormod complained everyone on the team was subscribed to bug mail so you made a mailing list and let people opt in to the bug mail [20:24] makes me think something is broken on the back end [20:25] unless something was changed by accident [20:25] but ive looked everywhere [20:25] everyone on kernel-bugs is getting bug mail looking at the mailing list subscriber list [20:25] and if its impacting you ... [20:25] Sarvatt: im not even in kernel-bugs anymoer and im getting it [20:25] and I only see one subscriber to kernel-bugs e-mail [20:27] huh, and it looks like the team mail list is deactivated on that page anyway [20:27] from looking here: https://launchpad.net/~kernel-bugs/+mailinglist [20:28] Sarvatt: where did that sandybridge email land for you? [20:28] whats in the header under X-Launchpad-Message-Rationale [20:32] * jjohansen lunches [20:36] yeah, I dunno how/why we are getting this e-mail now. the mail list for kernel-bugs is deactivated [20:37] * JFo sends a test e-mail to the list [20:38] sent [20:40] got mail delivery failure to kernel-bugs@lists.launchpad.net [20:40] so that isn't where it is coming from [20:40] vanhoof, ^^ [20:42] found this though: https://lists.ubuntu.com/mailman/listinfo/kernel-bugs [20:42] so that may be where it is coming from [20:44] bdmurray, any idea why we are suddenly seeing e-mail from kernel-bugs since the 5th of November with no interaction from us? [20:44] I tried to unsubscribe but I got Error: Illegal Email Address: Jeremy Foshee [20:45] Sarvatt, yeah [20:45] ooh wait [20:45] I think I may have figured it out vanhoof [20:46] Sarvatt, yeah by default teams are set up to send bug mail to all members [20:46] JFo: can I see one of these emails with all the headers [20:46] sure [20:46] * vanhoof reads [20:47] I'm trying to remember exactly how it was done [20:47] I *think* I created a second team ${team}-bugs and set it as the bug contact for the team [20:47] sent bdmurray [20:49] JFo: you figure something out? [20:49] maybe vanhoof gimme a sec :) [20:49] heh [20:49] X-Launchpad-Message-Rationale: Subscriber (linux in ubuntu) @kernel-bugs [20:50] the "kernel-bugs" team is subscribed to all linux bug reports [20:50] however all the mail should go to the kernel-bugs mailing list [20:50] right, but we only suddenly started getting e-mail on the 5th [20:50] that seems odd [20:50] and [20:51] bugs im a direct subscriber on are only going to kernel-bugs [20:51] with the same header you just posted [20:51] how wound we individually unsubscribe if that was wanted bdmurray? [20:51] This team's mailing list has been deactivated. [20:51] right [20:51] and yet we are getting e-mail [20:51] :) [20:51] well because it is deactivated it likely goes to the team members [20:52] did the mailing list get deactivated on the 5th? [20:52] I thought the email address used to kernel-bugs@lists.ubuntu.com [20:52] aha, https://edge.launchpad.net/~ubuntu-x-swat/+contactaddress [20:52] by default the email notifications are set to go to 'Each member individually'. You can set up a mailing list for the team and then direct the bug mail to go there instead. [20:53] then people can sub/unsub as appropriate [20:53] check this out [20:53] https://lists.ubuntu.com/archives/kernel-bugs/2010-November/thread.html [20:53] bdmurray, I sent an unsubscribe through https://lists.ubuntu.com/mailman/listinfo/kernel-bugs but I have gotten nothing back yet [20:53] Starting: Mon Nov 1 00:02:04 GMT 2010 [20:53] Ending: Fri Nov 5 05:15:12 GMT 2010 [20:54] JFo: I believe the team email address used to be k-bugs@lists.ubuntu.com and somebody changed it [20:55] I am thoroughly confused now [20:56] so perhaps it should be changed back to k-bugs@ ? [20:56] I'd be happy to mumble about it [20:57] well aside of the fact that I like the song I am listening too ;-) [21:02] heh [21:04] JFo: think we should change it? [21:05] I just want the mail to go to the right place again. [21:05] I don't care how we accomplish that [21:05] :) [21:05] I'll fix it then [21:05] hmm, can't [21:05] thank you bdmurray sorry to pull you into all of this [21:05] uh oh [21:06] anyway set team email to kernel-bugs@lists.ubuntu.com [21:21] hi, anyone wanting to look into that conexant problem? :) [21:21] JFo: bdmurray thanks guys :) [21:21] * vanhoof feels better about life now [21:32] * ogasawara lunch [22:14] bdmurray: JFo: https://launchpad.net/~kernel-bugs ... didn't you just set this to the list? [22:14] no, that mail list is deactivated [22:15] list is @ubuntu.com [22:15] Team details [22:15] Email: [22:15] No contact email Set contact address [22:16] oh i see [22:16] he said he cant do it [22:17] JFo: want me to set it? [22:17] no [22:17] I'd ask pete about it as he is the penultimate owner [22:19] JFo: right, i guess what im saying is that ntohing has been changed yet [22:19] I have no idea [22:20] all I do know is that nothing has changed [22:20] still getting the e-mail I mean [22:23] im still getting kernel-bugs [22:26] what's the tool to track disk access? it'll show each block and the process responsible... can't remember now [22:28] blktrace! === bjf is now known as bjf[afk] === dannf is now known as dannf_afk