[08:00] <vishwa_ti> Hi folks
[08:00] <amitk> Guys, is this cpu to old to support acpi-cpufreq ? http://pastebin.com/nti2sKSZ
[08:00] <amitk> vishwa_ti has this problem
[08:01] <amitk> apw: lag: ^
[08:03] <slangasek> so would anyone here like to have the mini-PCIe card to blame for bug #654937?  iwlagn replacement card is now on order :)
[08:03] <ubot2> Launchpad bug 654937 in linux (Ubuntu) "r8192se_pci: rtl8191SEVA2 fails to transmit certain mumble packets (affects: 1) (heat: 497)" [Undecided,New] https://launchpad.net/bugs/654937
[08:03] <slangasek> (also, bug #655769)
[08:03] <ubot2> Launchpad bug 655769 in linux (Ubuntu) "running powertop with r8192se_pci module loaded results in a kernel panic (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/655769
[08:04] <amitk> vishwa_ti: btw, do you have speedstep settings in your bios enabled (if any?)
[08:06] <vishwa_ti> amitk: I have done any settings explicitly..is it disabled by default?
[08:06] <amitk> vishwa_ti: depending on how old the machine is, it might be
[08:07] <vishwa_ti> amitk: let me check that
[08:07] <lag> amitk: WGT http://pastebin.com/nti2sKSZ - you need to speak with cking
[08:07] <lag> He shouldn't be too long
[08:08] <amitk> lag: true, thanks
[08:09] <lag> amitk: vishwa_ti: http://wiki.archlinux.org/index.php/Cpufrequtils#Intel
[08:09] <lag> Seems to answer your question 
[08:12] <amitk> lag: IIRC we compile-in all drivers (and link them in order of preference), so if it isn't getting auto-loaded there is a chance that it isn't supported
[08:14] <lag> amitk: This may well be true
[08:14]  * smb yawns
[08:14] <lag> amitk: But as a debugging exercise vishwa_ti could at least give it a go
[08:15] <lag> amitk: So I'm guessing that the module isn't being loaded automatically then?
[08:15] <lag> Morning smb
[08:15] <smb> morning 
[08:16] <vishwa_ti> I enabled speedstep settings in bios..still I do not see acpi-cpufreq
[08:17] <amitk> lag: there is no 'module' since it is compiled-in. And /sys/devices/system/cpu/cpu0/cpufreq/scaling_driver is read-only. So I don't think we can force it from sysfs. THere is perhaps a command-line parameter to force cpufreq driver...
[08:17] <amitk> vishwa_ti: you won't see anything in lsmod. Check /sys/devices/system/cpu/cpu0/cpufreq/scaling_driver
[08:17] <lag> amitk: Let me have a look
[08:17] <vishwa_ti> ya now I see acpi-cpufreq when I cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_driver
[08:18] <amitk> vishwa_ti: \o/ you're set! You should also see ondemand now
[08:18] <vishwa_ti> yep..
[08:18]  * amitk packs up
[08:18] <lag> :)
[08:19] <amitk> thanks lag
[08:19] <lag> amitk: np
[08:19] <vishwa_ti> thanks a lot amitk, lag
[08:20] <lag> vishwa_ti: You're very welcome
[08:27] <apw> slangasek, i am sure tim will want it
[08:29] <lucent> I'm the guy posting about firewire device and data corruption on the mail list :)
[08:30] <lucent> eager to test patches I heard mentioned
[08:30] <TeTeT> apw: Hi, can I get your help with getting an SRU done for bug 586325? Our customer LVM is waiting for the patch to appear in an official kernel since quite a while
[08:30] <ubot2> Launchpad bug 586325 in linux (Ubuntu Lucid) (and 2 other projects) "[i965q] Fujitsu Siemens Esprimo E: changing resolution results in non working X (affects: 1) (heat: 40)" [Undecided,Triaged] https://launchpad.net/bugs/586325
[08:31] <smb> lucent, I believe it was manjo saying he had patches. Though his day begins later
[08:32] <lucent> smb: thanks! good to know
[08:37] <apw> TeTeT, looking
[08:53] <lag> lucent: I believe he's going to update bug 657081 when he has a kernel ready
[08:53] <ubot2> Launchpad bug 657081 in linux (Ubuntu) "New firewire stack unreliable with Texas Instruments TSB82AA2 IEEE-1394b (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/657081
[08:54] <lucent> I'm excited :)
[09:09] <apw> smb, launchpad working [sic] for you ?
[09:10] <apw> seems more broken than usual for me
[09:10] <smb> apw, It works for me as much as I use it currently (which is not at all)
[09:11] <JFo> it is failing for me more than normal
[09:11] <diwic> apw, I think we need to report these things to Marjo so he'll get feedback from more than my (limited) experience of LP
[09:11] <JFo> marjo isn't able to help this
[09:11] <JFo> this needs to be reported to Francis I imagine
[09:11] <smb> apw, Hm, it seems to bring up bug reports I had been looking at in the past, but this is not a very conclusive teste
[09:12] <apw> not getting timeouts even so i assume its in a HEAP
[09:12]  * JFo tries something
[09:12] <smb> apw, I assume you stopped going to edge
[09:12] <diwic> JFo, if Marjo is our representative, it'll be good for him with more than the one example I gave him of LP failure
[09:13] <JFo> ah yes, that bit is true
[09:13] <apw> well the link i was using was a raw link so to 'non-edge' in the first instant
[09:13] <apw> it has now switched over to edge, so its make progress, at a glacial pace
[09:13] <smb> apw, At the moment at least for the bug report I tried the reload time seemed reasonable
[09:14] <smb> apw, whicht link do you try
[09:14] <apw> https://launchpad.net/bugs/657081
[09:14] <ubot2> Launchpad bug 657081 in linux (Ubuntu) "New firewire stack unreliable with Texas Instruments TSB82AA2 IEEE-1394b (affects: 1) (heat: 6)" [Undecided,New]
[09:14] <smb> report is up here
[09:14] <apw> ok that one works
[09:14] <apw> https://launchpad.net/bugs/586325
[09:14] <ubot2> Launchpad bug 586325 in linux (Ubuntu Lucid) (and 2 other projects) "[i965q] Fujitsu Siemens Esprimo E: changing resolution results in non working X (affects: 1) (heat: 40)" [Undecided,Triaged]
[09:14] <apw> and that one doesn't seem to ... wtf
[09:15] <smb> apw, done
[09:15] <diwic> never underestimate Murphy's law
[09:15] <apw> double wtf
[09:15] <smb> apw, I can even see the last of the 118 comments
[09:16] <smb> apw, One would not believe that I am farther away from it
[09:16] <apw> finally got the content... what is up with this thing
[09:18] <smb> apw, Maybe you looked at too many bugs and now got bandwith controlled because clearly you are a bot. :-P
[09:18] <apw> heh nothing would supprise me anymore
[09:19] <TeTeT> lol
[09:29] <lag> smb: bug 22070
[09:29] <ubot2> Launchpad bug 22070 in linux-source-2.6.20 (Ubuntu Maverick) (and 8 other projects) "Logitech Quickcam Messenger is not usable (affects: 15) (dups: 3) (heat: 140)" [Undecided,Invalid] https://launchpad.net/bugs/22070
[09:30] <lag> Ignore the 2.6.20
[09:30] <lag> This is a current Lucid bug
[09:49] <bo> apw: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/658789
[09:49] <ubot2> Launchpad bug 658789 in xorg (Ubuntu) "black screen on sony vpccww1, nouveau on nvidiagt230m, maverick. External hdmi monitor works (affects: 1) (heat: 6)" [Undecided,New]
[09:50] <apw> bo to
[09:50] <apw> ta
[09:52] <bo> ?
[09:54] <apw> TeTeT, do you have kit to test this resolution bug ?
[09:54] <apw> the patch does not backport trivially and so will require testing before we can SRU it
[09:55] <TeTeT> apw: yes, I do have an Esprimo E here
[09:56] <TeTeT> apw: smb provided me with a patched kernel back in June, this runs in production now at the customers site. but they have missed the last updates of the kernel cause of this
[09:57] <apw> smb, you have a backport of that resolution patch already ?
[09:58] <smb> TeTeT, Hm, was that when I just made something compile for you or picked in the patch myself...? I fail to remember now
[09:59] <smb> apw, I would need to check, seems like an awfully long time ago
[09:59] <lucent> ...in a galaxy far far away
[09:59] <TeTeT> smb: not sure what you did, I know I failed with the kernel due to the abi bump
[09:59] <apw> there is no mention of your involvement in the bug
[09:59] <TeTeT> apw: he just setup the kernel for me so it would compile in a PPA
[10:00] <smb> TeTeT, Then it is probably the thing were I just made the kernel compile in some way but had not really looked into what was added to it
[10:00] <TeTeT> apw: this is the PPA: https://edge.launchpad.net/~tspindler/+archive/ubuntu-kernel-lvm
[10:01] <apw> TeTeT, do you have a source tree for that somewhere?  so i can see what version of the patch was tested ?
[10:13] <TeTeT> apw: I'm afraid I deleted that tree a long time ago due to space constraints. I check if I have it as an email somewhere, at least the patch
[10:14] <apw> TeTeT, ok so the testing on that is moot then as we don't know if its the same patch, its likely not to be honest as it is so old
[10:16] <TeTeT> apw: ok, but testing should not be a problem. The customer has a test lab with T61, x61 and the Esprimo E setup to check
[10:17] <apw> TeTeT, i am somewhat supprised this is something they hit often
[10:18] <TeTeT> apw: they have a Java application that only runs in 1024x768, this is why a lot of their employees switch between resolutions. They come from RH and it used to work there
[10:18] <apw> TeTeT, and you said you had the affected machine too?  so you could pre-test it before sending a test to the customer ?
[10:19] <TeTeT> apw: yes, I can test it on a T61 to make sure it's not breaking anything else and on the Esprimo E
[10:19] <apw> ok cool.  i'll get you some test kernels shortly
[10:20] <TeTeT> apw: this is the patch I sent to smb: https://pastebin.canonical.com/38506/
[10:20] <TeTeT> apw: can resend the email if you want
[10:23] <apw> TeTeT, its close to the current version, and we want that latest one tested anyhow as that is the official upstream solution
[10:33]  * apw feels all sneezy ... damn that steve
[10:34] <smb> Nothing as annoying as catching the cold from your colleagues...
[10:34] <apw> indeed
[10:50] <apw> smb are we aware of any issues mounting root, with lsi h/w ?
[10:50] <apw> (for lucid)
[10:51] <apw> possibly with a udev segfault ?
[10:51] <smb> apw, I am aware of certain newer controllers not being supported at all and potential multipath issues. But failing to moint root, not yet
[10:51] <apw> claims of 'changes to sysfs layout breaking udev' ... no evidence as such tho.
[10:52] <smb> apw, any hinting to changing sysfs between what and lucid?
[10:52] <smb> not aware of a change that would change the sysfs layout whithin the stable release
[10:53] <apw> me either, i suspect its utter conjecture ... asking them to file a bug
[11:05] <apw> TeTeT, ok i've put a link to the kernels in the bug
[11:09] <TeTeT> apw: thanks, I'll try these today
[11:10] <apw> smb, the patch (untested) for that issue is here: http://people.canonical.com/~apw/lp586325-lucid/0001-drm-i915-Unset-cursor-if-out-of-bounds-upon-mode-cha.patch
[11:11] <smb> apw, Ok, thanks. I will add it to the next round of proposals for drm33 stable updates
[12:07] <JFo> back on after a while, I must sleep a bit.
[14:40] <apw> smb, you need to mark your blueprints as a 'series goal' of natty
[14:41] <apw> (now that natty exists :))
[14:41] <smb> apw, Ok, will do so in a minute or two. Thanks. :)
[15:16] <tgardner> apw, do we need CONFIG_INIT_PASS_ALL_PARAMS=y in the natty enforcer?
[15:17] <apw> tgardner, i recon so yes
[15:18] <apw> tgardner, shall i shove that in before i close hthis puppy
[15:19] <tgardner> apw, sure
[15:19] <tgardner> just so we don't forget
[15:21] <tgardner> apw, am also thinking we should drop armel from natty for now
[15:22] <tgardner> natty master, that is
[15:22] <apw> tgardner, ok can do
[15:22] <apw> will that render the ISOs unbuildable, ie. do we need to move those out to a new branch in short order
[15:22] <tgardner> apw, hmm, how do we get a linux-libc-dev in place though?
[15:22] <apw> well there is one now, from the previous version
[15:23] <apw> we'll use that to build ourselves
[15:23] <apw> as much as we rely on it, which is basically not at all
[15:23] <apw> or did you mean for arm
[15:23] <tgardner> apw, right. I'm not too worried about ISO building just yet. lets sort which branches we're gonna carry going forward.
[15:24] <apw> iirc we carried just the linux-libc-dev for armel in master, ie. it built from there
[15:24] <tgardner> apw, thats my recollection as well
[15:25] <apw> Package: SRCPKGNAME-libc-dev
[15:25] <apw> Architecture: i386 amd64 lpia ia64 powerpc sparc armel
[15:25] <apw> from lucid
[15:26] <tgardner> apw, I was thinking more about dropping the development arm flavours for now. leave versatile for qemu.
[15:26] <apw> that sounds acceptable, and easy to test
[15:27] <apw> i guess most of them will come in in at least some form from linaro anyhow
[15:27] <tgardner> apw, yep, I'm gonna try to get Rigby to do all the work
[15:27] <tgardner> for the master kernel version at least
[15:28] <apw> do we need to be having a session/part of a session on arm or do we assume others will cover that
[15:28] <apw> and we can just rock up and say no :)
[15:28] <tgardner> I suppose we should talk to them about it, huh?
[15:28] <cking> apw, here's a graph of the write rate as the head moves across the disc: http://zinc.canonical.com/~cking/write-rates.png
[15:29] <apw> i guess we can add it to our agenda for the 'flavours' one
[15:29] <apw> cking, those regular up-ticks are unexpected
[15:29] <bjf> tgardner, are you expecting the stable team to pick up the linaro pull requests now?
[15:30] <tgardner> bjf, I was just test building it. but for the future I've no strong preference. Guess we should decide.
[15:30] <tgardner> I've sorta been covering the arm bases
[15:31] <cking> apw, why? it's a mechanical, surely you can expect perfect linear I/O transfer rate
[15:31] <apw> i assume you mean 'can't'
[15:32] <apw> not expecting perfection, by my brain says there is a periodic uptick
[15:32] <apw> three showing on there, and wondering whether they are real
[15:32] <apw> or just noise
[15:32] <apw> 3 maybe 4
[15:32] <cking> apw, I've got finer grained data to work on, I could shove it into a fft and see if there are any underlying harmonics
[15:33] <apw> :)
[15:33] <cking> could be because somebody walked passed the machine and this disturbed the heads slightly ;-)
[15:34] <cking> urgh, nearly time for tooth extraction.
[15:37] <smb> apw, Are you still on the specs document. Clicked on edit to change a link and saw you have a lock there
[15:38] <apw> smb, hrm not sure i think i have
[15:39] <smb> apw, OK, I aborted. Just to let you know, stable process is clearly hardware and not devprocess ;-)
[15:39] <apw> smb, nope when i dit the Specs page it says i don't have a lock
[15:39] <apw> smb, what they moved it _again_ ?
[15:39] <apw> someone needs to fix the system so we don't have to rename the damn things every time someone changes their mind
[15:39] <smb> If it worked before then yes. Or was a typo there
[16:01] <apw> tgardner, are we calling the first upload -1 or -0
[16:01] <tgardner> apw, don't care. the current ABI number is fine.
[16:02] <apw> tgardner, ack
[16:23] <hermes> Fellow Programmers, I am a Linux Enthusiast and I am inclined towards system programming. I am looking forward to contributing in whatever way possible towards the Kernel. Could anyone help me getting started?
[16:25] <bjf> hermes, http://wiki.ubuntu.com/Kernel
[16:26] <hermes> bjf: I think I want to precisely ask like, would I have access like to the current issues or bugs in kernel and could I try to get my hands dirty and submit a patch for evaluation
[16:27] <hermes> bjf: Or like a team who work on something, and I could get involved to contribute with them
[16:27] <apw> all of our bugs are public, as is our mailing list, and all contributions are welcome
[16:28] <hermes> apw: great
[16:29] <bjf> hermes, JFo can help you get going on looking at bugs
[16:31] <hermes> bjf: thats is great, I would want a little help initially to get set myself up
[16:39] <bjf> ogasawara, you have some stable release patches queued for maverick somewhere? you planning on pushing those today?
[16:40] <ogasawara> bjf: yep, I've got them ready to push.  just wanted to double check with you guys first that it's ok
[16:40] <ogasawara> bjf: I've also already build and boot tested
[16:40] <ogasawara> bjf: then I think I can officially hand off the Maverick git repo to you guys
[16:40] <bjf> ogasawara, good for me, i think it's cool with sconklin and smb
[16:40]  * smb is cool 8he thinks)
[16:40] <tgardner> ogasawara, aren't you officially on stable duty for the next while?
[16:41] <ogasawara> tgardner: yep, but will go through sconklin for that
[16:41] <tgardner> ack
[16:43] <AndChat|> I kno u guys r busy but I've got an issue in the kernel i'd like to shine some light on
[16:44] <apw> AndChat|, you'd need to elucidate
[16:44] <AndChat|> http://ubuntuforums.org/showthread.php?t=1593695
[16:49] <AndChat|> Basicly myth hangs when using dvb module cx23885 to tune channels causing kernel oops
[16:50] <ogasawara> bjf, smb, sconklin: pushed 2.6.35.5, 2.6.35.6, and 2.6.35.7 patch sets to Maverick tip
[16:50] <bjf> ogasawara, cool, thanks
[16:51] <smb> ogasawara, I am probably throwing myself behind the train but did those have tracking bugs?
[16:51] <hermes> bjf: Should I ask JFo personally or shud I ask him here
[16:51] <ogasawara> smb: yep, lemme find them real quick
[16:52] <ogasawara> bug 645522
[16:52] <ubot2> Launchpad bug 645522 in linux (Ubuntu Maverick) (and 1 other project) "Maverick update to 2.6.35.5 stable release (affects: 2) (heat: 199)" [Medium,In progress] https://launchpad.net/bugs/645522
[16:52] <ogasawara> bug 649208
[16:52] <ubot2> Launchpad bug 649208 in linux (Ubuntu Maverick) (and 1 other project) "Maverick update to 2.6.35.6 stable release (affects: 2) (heat: 392)" [Medium,In progress] https://launchpad.net/bugs/649208
[16:52] <ogasawara> bug 651425
[16:52] <ubot2> Launchpad bug 651425 in linux (Ubuntu Maverick) (and 1 other project) "Maverick update to 2.6.35.7 stable release (affects: 1) (heat: 498)" [Medium,In progress] https://launchpad.net/bugs/651425
[16:52] <sconklin1> Cable company is here to install my faster network. It shouldn't cause an outage . . . . but if I drop away that's why
[16:52] <bjf> hermes, here is good a good start
[16:52] <tgardner> smb, behind the the train ?
[16:53] <ogasawara> tgardner: heh, I guess that's better than in front of it :)
[16:53] <smb> ogasawara, cool, just wanted to make sure we got them to add to the changelog
[16:53] <hermes> bjf: alright
[16:53] <ogasawara> smb: I added them as BugLinks to the commits which update the version
[16:54] <smb> tgardner, ogasawara, right but if the purpose is to stop it... well probably as useless to throw one before than after. :)
[16:54] <tgardner> ah, I get it.
[16:55] <hermes> I am fairly new to the kernel programming, but I have a keen inclination towards systems programming. 
[16:55] <hermes> Could anyone suggest me what shoud I start looking at 
[16:55] <hermes> JFo: if you could help me get started I would appreciate than man
[17:02] <sconklin1> hermes: a good first set of tasks are just to pull the kernel source from the distribution git repositories and build it locally
[17:08] <bjf> apw, tgardner do we have a start of an agenda for the mini-sprint in boston after uds?
[17:28] <apw> bjf, i've not put anything anywhere yet, though we did have something ...
[17:28] <apw> i think there is a spot for the agenda on the wiki page though
[17:29] <apw> tgardner, is there a trick to getting the chroot builder scripts to work?  the config perhaps?  i am not getting any deb or deb-src lines in my /etc/apt/sources.list
[17:29] <apw> specifically for armel
[17:29] <tgardner> apw, which chroot flavour?
[17:30] <apw> armel for maverick
[17:30] <apw> as made by a make_release
[17:30] <tgardner> sdhould be 'sudo ./make_chroot maverick armel'
[17:30] <apw> where does POCKETS get set ?
[17:31] <tgardner> it tries to figure out if you are me, pete, then defaults to the regular mirror
[17:31] <apw> i'm running it with my own on the command line
[17:31] <tgardner> kteam-tools/chroot-setup/scripts/chroot-defs.conf
[17:31] <tgardner> function get_pockets ()
[17:32] <apw> tgardner, yeah gets passed that
[17:32] <apw> yet behaves as if it does nto contain 'release'
[17:32] <tgardner> apw, hmm, etc/sources.list is trashed?
[17:33] <apw> tgardner, yeah its empty, present but empty
[17:34] <tgardner> uh, thats not cool
[17:34] <apw> tgardner, i guess i get to debug it :/
[17:34] <tgardner> write_mirror is where that gets updated
[17:34] <cking> is there a k-t meeting today?
[17:35] <bjf> cking, nope, done until post uds
[17:35] <bjf> cking, you can quit for the day :-)
[17:35] <cking> in which case, I will be slipping off "early" today
[17:36]  * smb suddenly feels very gone
[17:38] <manjo> any idea when the natty tree will be open ? 
[17:38]  * tgardner wonders if manjo has been living in a cave
[17:39] <cking> living a cave is what trolls like me do
[17:39] <apw> manjo, i'd not say for a couple of months yet
[17:39] <apw> else how can we have a holiday
[17:40] <manjo> apw, yep got that.. was wondering if we know what month etc ? I wanted to answer a partner on the time frame
[17:41] <cking> didn't we agree to keep it the same as maverick?
[17:41]  * apw *blink*
[17:42] <cking> apw, http://zinc.canonical.com/~cking/iotest-4k-writes.png - more graphs
[17:42] <apw> cking, i was rather partial to hardy's kernel ...
[17:42] <cking> yeah, we should revisit it I think for natty 
[17:44] <apw> manjo, have you looked for the tree ?
[17:47] <manjo> yep I have it cloned on tangerine
[17:47] <tgardner> manjo, in that case you shold know the tree has been open for 6 weeks or more
[17:48] <apw> and if you meant the archive, it'll be open as soon as the toolchain is in
[17:51] <manjo> can you guys hear me on mumble?
[17:51] <smb> manjo, no
[17:51] <manjo> crap
[17:52] <manjo> is it mumble or you guys fscking with me ? :) 
[17:53] <tgardner> manjo, eh? I can't hear you.
[17:54] <cking> manjo, cannot hear you
[17:57] <manjo> fack I give up 
[17:57] <bjf> manjo, we can barely hear you
[17:57] <cking> manjo, how's that HDD testing progressing?
[17:58]  * cking thinks a mumble plug in to android is required
[17:58] <manjo> cking, I ran stress for 3 days, sat, sun, monday, I had to kill it this morning.
[17:58] <manjo> cking, I am going to try your test kit you point us to
[17:59] <manjo> so far it looks good, I too try dding 2.5T worth of data into the disk and that works
[17:59] <manjo> I have brian from AMI testing the latest maverick on their bios 
[17:59] <cking> manjo, collect the output and send it to me, I can analyse the throughput with some gnuplot magic
[17:59] <manjo> they have started to integrate maverick iso into their test bed
[18:00] <manjo> I chatted with him this morning and he will share the test results on their bios as soon as he is done documenting it 
[18:00] <cking> is this firmware BIOS+ACPI or UEFI+ACPI?
[18:01] <manjo> cking, they are testing a few different BIOS versions to make sure the patches they put in for different distros are holding up 
[18:01] <manjo> cking, UEFI 
[18:01] <cking> in which case, it's not BIOS, it's UEFI :-)
[18:01] <manjo> yeah :) 
[18:02] <manjo> UEFI BIOS
[18:02] <manjo> easy to type bios
[18:02] <cking> nooooo. UEFI is not BIOS
[18:02] <manjo> my fingers type bios more easily than UEFI
[18:02] <cking> heh, easy to do. BIOS has been around for donkeys
[18:03] <manjo> so. we have quiet a bit a testing going on with Maverick in AMI
[18:03] <lag> No meeting today?
[18:03] <cking> lag, nope
[18:03] <lag> 'cos Maverick has been released?
[18:03] <manjo> lag, usually not until after uds
[18:04] <lag> Woooooooooooooooo
[18:04] <manjo> probably after November 6, bjf ?
[18:04] <manjo> cking, I poked the guy at Seagate to send us some disks
[18:05] <cking>  manjo, what spec are these?
[18:05] <manjo> cking, 3T disks
[18:05] <cking> sweet
[18:05] <lag> manjo: Can you poke the guy as Seagate to send me some of those disks?
[18:05] <manjo> not sure if they are 4K or not 
[18:05] <bjf> manjo, lag, the topic seems to indicate Nov. 9 :-)
[18:05] <manjo> lag, this is for testing ?
[18:05] <cking> bjf, you expect us to read?
[18:06] <manjo> tgardner, tangerine is in boston ?
[18:06] <tgardner> manjo, yep
[18:06] <manjo> tgardner, I have an extra 2.5T disk ... do you want to add it to tangerine ?
[18:07] <tgardner> manjo, tangerine only supports 2.5" disks
[18:07] <manjo> bummer
[18:09] <manjo> cking, if the seagate disks arrive before UDS I will bring you one 
[18:09] <manjo> I have not heard back from them as yet
[18:11] <cking> I'm not wetting myself waiting for them
[18:11] <lag> manjo: Of course
[18:17] <manjo> lag, :) ok 
[18:44] <maxb> Hrm. The fact that the kernel no longer lets you attach a debugger to your own processes didn't make the release notes
[18:44] <maxb> Anyone point me to have to turn it off, given that omission? :-)
[18:46] <tgardner> maxb, kees should be able to remember how. its a sysfs flag somewhere.
[18:46] <jjohansen> maxb: change /proc/sys/kernel/yama/ptrace_scope 
[18:47] <maxb> yama?
[18:47] <jjohansen> set it to 0 for no extra ptrace control
[18:47] <jjohansen> it is a collection of security restrictions that have been floating around for years
[18:47] <kees> maxb: why did it not make the release notes? it's been in the notes for like 5 months
[18:47] <jjohansen> ptrace restrictions, symlink, hardlink
[18:47] <maxb> https://wiki.ubuntu.com/MaverickMeerkat/ReleaseNotes <-- am I in the wrong place?
[18:59] <bo_> apw: I filed a bug with kernel drm information as you asked to do.
[19:00] <kees> maxb: hm, here it is https://wiki.ubuntu.com/MaverickMeerkat/TechnicalOverview
[19:01] <kees> maxb: gah, but it vanished from there too
[19:03] <kees> maxb: https://wiki.ubuntu.com/MaverickMeerkat/TechnicalOverview?action=recall&rev=38  <- search for "ptrace" there
[19:03] <kees> maxb: I'll try to get the releasenotes updated
[19:22]  * tgardner lunches
[19:26] <jjohansen> bjf: when is the Lucid EC2 update going to get pushed?
[19:27] <bjf> jjohansen, should be in -proposed now, checking
[19:30] <bjf> jjohansen, -309.17 is in proposed, that was uploaded after your rebase
[19:30] <bjf> jjohansen, are you asking when will it be promoted to -updates?
[19:31] <jjohansen> bjf: ah yeah an estimate
[19:32] <bjf> jjohansen, at least another week
[19:32] <jjohansen> okay, thanks
[19:34] <gilson585> Can someone assist me on bug 659348
[19:34] <ubot2> Launchpad bug 659348 in linux (Ubuntu) "dvb module cx23885 hangs mythtv-setup (affects: 2) (dups: 1) (heat: 14)" [Undecided,New] https://launchpad.net/bugs/659348
[19:34] <jjohansen> bjf: thanks, it came up in the server team meeting
[19:35] <bjf> jjohansen, that's what i figured
[19:58]  * jjohansen -> lunch
[20:14] <ivoks> hi
[20:14] <ivoks> did you notice that -virtual is missinf nfs modules?
[20:14] <ivoks> (in maverick)
[20:19] <ivoks> that's bug 659084
[20:19] <ubot2> Launchpad bug 659084 in linux-meta (Ubuntu) "2.6.35-22-virtual is missing nfs modules (affects: 1) (heat: 8)" [Undecided,Confirmed] https://launchpad.net/bugs/659084
[20:32] <cking> natty narwhal kills tux? http://www.mcphee.com/shop/product_images/c/906/11689__59447_zoom.jpg
[20:35] <manjo> cking, looks aaaaweful
[20:36] <cking> karmic koala gets impaled too if he's not careful
[20:36] <gilson585|> lol too funni
[20:48] <ogasawara> bjf: I notice you're monitoring patchworks for some of the kernel SRU's.  just curious what your process is ... do you re-delegate to sconklin once they're ready to be applied (ie have garnered 2 acks).
[20:49] <sconklin> don't assume that we have a process ;-o
[20:49] <ogasawara> heh
[20:49] <bjf> ogasawara, no, after two acks i apply them to my own tree, do test builds, push to public then ask sconklin to review
[20:49] <bjf> ogasawara, after sconklin and smb say "looks good" i push to master repo
[20:51] <ogasawara> bjf: and I assume you just nudge them directly if you need a 2nd ack for a patch
[20:53] <bjf> ogasawara, yup
[20:54] <bjf> ogasawara, depending on your meaning of "nudge them directly"
[20:54] <bjf> :-)
[20:59]  * ogasawara lunch
[21:01] <jjohansen> ivoks: nope didn't notice or else it would be fixed already
[21:02] <ivoks> jjohansen: ok
[21:03] <jjohansen> ivoks: thanks for bringing it up, will look into it
[21:03] <ivoks> jjohansen: it's enabled in config
[21:03] <ivoks> jjohansen: so i'm not really sure what's going on
[21:03] <jjohansen> ivoks: yep, its probably in the packaging phase
[21:32]  * tgardner bails for the day
[21:57] <bjf> ogasawara, mumble