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