/srv/irclogs.ubuntu.com/2010/10/12/#ubuntu-kernel.txt

vishwa_tiHi folks08:00
amitkGuys, is this cpu to old to support acpi-cpufreq ? http://pastebin.com/nti2sKSZ08:00
amitkvishwa_ti has this problem08:00
amitkapw: lag: ^08:01
=== diwic is now known as diwic_afk
slangasekso would anyone here like to have the mini-PCIe card to blame for bug #654937?  iwlagn replacement card is now on order :)08:03
ubot2Launchpad bug 654937 in linux (Ubuntu) "r8192se_pci: rtl8191SEVA2 fails to transmit certain mumble packets (affects: 1) (heat: 497)" [Undecided,New] https://launchpad.net/bugs/65493708:03
slangasek(also, bug #655769)08:03
ubot2Launchpad 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/65576908:03
amitkvishwa_ti: btw, do you have speedstep settings in your bios enabled (if any?)08:04
vishwa_tiamitk: I have done any settings explicitly..is it disabled by default?08:06
amitkvishwa_ti: depending on how old the machine is, it might be08:06
vishwa_tiamitk: let me check that08:07
lagamitk: WGT http://pastebin.com/nti2sKSZ - you need to speak with cking08:07
lagHe shouldn't be too long08:07
amitklag: true, thanks08:08
lagamitk: vishwa_ti: http://wiki.archlinux.org/index.php/Cpufrequtils#Intel08:09
lagSeems to answer your question 08:09
amitklag: 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 supported08:12
lagamitk: This may well be true08:14
* smb yawns08:14
lagamitk: But as a debugging exercise vishwa_ti could at least give it a go08:14
lagamitk: So I'm guessing that the module isn't being loaded automatically then?08:15
lagMorning smb08:15
smbmorning 08:15
vishwa_tiI enabled speedstep settings in bios..still I do not see acpi-cpufreq08:16
amitklag: 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
amitkvishwa_ti: you won't see anything in lsmod. Check /sys/devices/system/cpu/cpu0/cpufreq/scaling_driver08:17
lagamitk: Let me have a look08:17
vishwa_tiya now I see acpi-cpufreq when I cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_driver08:17
amitkvishwa_ti: \o/ you're set! You should also see ondemand now08:18
vishwa_tiyep..08:18
* amitk packs up08:18
lag:)08:18
amitkthanks lag08:19
lagamitk: np08:19
vishwa_tithanks a lot amitk, lag08:19
lagvishwa_ti: You're very welcome08:20
apwslangasek, i am sure tim will want it08:27
lucentI'm the guy posting about firewire device and data corruption on the mail list :)08:29
lucenteager to test patches I heard mentioned08:30
TeTeTapw: 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 while08:30
ubot2Launchpad 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/58632508:30
=== diwic_afk is now known as diwic
smblucent, I believe it was manjo saying he had patches. Though his day begins later08:31
lucentsmb: thanks! good to know08:32
apwTeTeT, looking08:37
laglucent: I believe he's going to update bug 657081 when he has a kernel ready08:53
ubot2Launchpad 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/65708108:53
lucentI'm excited :)08:54
apwsmb, launchpad working [sic] for you ?09:09
apwseems more broken than usual for me09:10
smbapw, It works for me as much as I use it currently (which is not at all)09:10
JFoit is failing for me more than normal09:11
diwicapw, I think we need to report these things to Marjo so he'll get feedback from more than my (limited) experience of LP09:11
JFomarjo isn't able to help this09:11
JFothis needs to be reported to Francis I imagine09:11
smbapw, Hm, it seems to bring up bug reports I had been looking at in the past, but this is not a very conclusive teste09:11
apwnot getting timeouts even so i assume its in a HEAP09:12
* JFo tries something09:12
smbapw, I assume you stopped going to edge09:12
diwicJFo, if Marjo is our representative, it'll be good for him with more than the one example I gave him of LP failure09:12
JFoah yes, that bit is true09:13
apwwell the link i was using was a raw link so to 'non-edge' in the first instant09:13
apwit has now switched over to edge, so its make progress, at a glacial pace09:13
smbapw, At the moment at least for the bug report I tried the reload time seemed reasonable09:13
smbapw, whicht link do you try09:14
apwhttps://launchpad.net/bugs/65708109:14
ubot2Launchpad bug 657081 in linux (Ubuntu) "New firewire stack unreliable with Texas Instruments TSB82AA2 IEEE-1394b (affects: 1) (heat: 6)" [Undecided,New]09:14
smbreport is up here09:14
apwok that one works09:14
apwhttps://launchpad.net/bugs/58632509:14
ubot2Launchpad 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
apwand that one doesn't seem to ... wtf09:14
smbapw, done09:15
diwicnever underestimate Murphy's law09:15
apwdouble wtf09:15
smbapw, I can even see the last of the 118 comments09:15
smbapw, One would not believe that I am farther away from it09:16
apwfinally got the content... what is up with this thing09:16
smbapw, Maybe you looked at too many bugs and now got bandwith controlled because clearly you are a bot. :-P09:18
apwheh nothing would supprise me anymore09:18
TeTeTlol09:19
lagsmb: bug 2207009:29
ubot2Launchpad 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/2207009:29
lagIgnore the 2.6.2009:30
lagThis is a current Lucid bug09:30
boapw: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/65878909:49
ubot2Launchpad 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:49
apwbo to09:50
apwta09:50
bo?09:52
apwTeTeT, do you have kit to test this resolution bug ?09:54
apwthe patch does not backport trivially and so will require testing before we can SRU it09:54
TeTeTapw: yes, I do have an Esprimo E here09:55
TeTeTapw: 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 this09:56
apwsmb, you have a backport of that resolution patch already ?09:57
smbTeTeT, Hm, was that when I just made something compile for you or picked in the patch myself...? I fail to remember now09:58
smbapw, I would need to check, seems like an awfully long time ago09:59
lucent...in a galaxy far far away09:59
TeTeTsmb: not sure what you did, I know I failed with the kernel due to the abi bump09:59
apwthere is no mention of your involvement in the bug09:59
TeTeTapw: he just setup the kernel for me so it would compile in a PPA09:59
smbTeTeT, 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 it10:00
TeTeTapw: this is the PPA: https://edge.launchpad.net/~tspindler/+archive/ubuntu-kernel-lvm10:00
apwTeTeT, do you have a source tree for that somewhere?  so i can see what version of the patch was tested ?10:01
TeTeTapw: 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 patch10:13
apwTeTeT, 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 old10:14
TeTeTapw: ok, but testing should not be a problem. The customer has a test lab with T61, x61 and the Esprimo E setup to check10:16
apwTeTeT, i am somewhat supprised this is something they hit often10:17
TeTeTapw: 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 there10:18
apwTeTeT, and you said you had the affected machine too?  so you could pre-test it before sending a test to the customer ?10:18
TeTeTapw: yes, I can test it on a T61 to make sure it's not breaking anything else and on the Esprimo E10:19
apwok cool.  i'll get you some test kernels shortly10:19
TeTeTapw: this is the patch I sent to smb: https://pastebin.canonical.com/38506/10:20
TeTeTapw: can resend the email if you want10:20
apwTeTeT, its close to the current version, and we want that latest one tested anyhow as that is the official upstream solution10:23
* apw feels all sneezy ... damn that steve10:33
smbNothing as annoying as catching the cold from your colleagues...10:34
apwindeed10:34
apwsmb are we aware of any issues mounting root, with lsi h/w ?10:50
apw(for lucid)10:50
apwpossibly with a udev segfault ?10:51
smbapw, I am aware of certain newer controllers not being supported at all and potential multipath issues. But failing to moint root, not yet10:51
apwclaims of 'changes to sysfs layout breaking udev' ... no evidence as such tho.10:51
smbapw, any hinting to changing sysfs between what and lucid?10:52
smbnot aware of a change that would change the sysfs layout whithin the stable release10:52
apwme either, i suspect its utter conjecture ... asking them to file a bug10:53
apwTeTeT, ok i've put a link to the kernels in the bug11:05
TeTeTapw: thanks, I'll try these today11:09
apwsmb, 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.patch11:10
smbapw, Ok, thanks. I will add it to the next round of proposals for drm33 stable updates11:11
JFoback on after a while, I must sleep a bit.12:07
=== _LibertyZero is now known as LibertyZero
=== bladernr is now known as bladernr_
=== ogra_ is now known as ogra
=== yofel_ is now known as yofel
=== cmagina is now known as cmagina-afk
apwsmb, you need to mark your blueprints as a 'series goal' of natty14:40
apw(now that natty exists :))14:41
smbapw, Ok, will do so in a minute or two. Thanks. :)14:41
=== cmagina-afk is now known as cmagina
=== bjf[afk] is now known as bjf
tgardnerapw, do we need CONFIG_INIT_PASS_ALL_PARAMS=y in the natty enforcer?15:16
apwtgardner, i recon so yes15:17
apwtgardner, shall i shove that in before i close hthis puppy15:18
tgardnerapw, sure15:19
tgardnerjust so we don't forget15:19
=== diwic is now known as diwic_afk
tgardnerapw, am also thinking we should drop armel from natty for now15:21
tgardnernatty master, that is15:22
apwtgardner, ok can do15:22
apwwill that render the ISOs unbuildable, ie. do we need to move those out to a new branch in short order15:22
tgardnerapw, hmm, how do we get a linux-libc-dev in place though?15:22
apwwell there is one now, from the previous version15:22
apwwe'll use that to build ourselves15:23
apwas much as we rely on it, which is basically not at all15:23
apwor did you mean for arm15:23
tgardnerapw, right. I'm not too worried about ISO building just yet. lets sort which branches we're gonna carry going forward.15:23
apwiirc we carried just the linux-libc-dev for armel in master, ie. it built from there15:24
tgardnerapw, thats my recollection as well15:24
apwPackage: SRCPKGNAME-libc-dev15:25
apwArchitecture: i386 amd64 lpia ia64 powerpc sparc armel15:25
apwfrom lucid15:25
tgardnerapw, I was thinking more about dropping the development arm flavours for now. leave versatile for qemu.15:26
apwthat sounds acceptable, and easy to test15:26
apwi guess most of them will come in in at least some form from linaro anyhow15:27
tgardnerapw, yep, I'm gonna try to get Rigby to do all the work15:27
tgardnerfor the master kernel version at least15:27
apwdo we need to be having a session/part of a session on arm or do we assume others will cover that15:28
apwand we can just rock up and say no :)15:28
tgardnerI suppose we should talk to them about it, huh?15:28
ckingapw, here's a graph of the write rate as the head moves across the disc: http://zinc.canonical.com/~cking/write-rates.png15:28
apwi guess we can add it to our agenda for the 'flavours' one15:29
apwcking, those regular up-ticks are unexpected15:29
bjftgardner, are you expecting the stable team to pick up the linaro pull requests now?15:29
tgardnerbjf, I was just test building it. but for the future I've no strong preference. Guess we should decide.15:30
tgardnerI've sorta been covering the arm bases15:30
ckingapw, why? it's a mechanical, surely you can expect perfect linear I/O transfer rate15:31
apwi assume you mean 'can't'15:31
apwnot expecting perfection, by my brain says there is a periodic uptick15:32
apwthree showing on there, and wondering whether they are real15:32
apwor just noise15:32
apw3 maybe 415:32
ckingapw, I've got finer grained data to work on, I could shove it into a fft and see if there are any underlying harmonics15:32
apw:)15:33
ckingcould be because somebody walked passed the machine and this disturbed the heads slightly ;-)15:33
ckingurgh, nearly time for tooth extraction.15:34
smbapw, Are you still on the specs document. Clicked on edit to change a link and saw you have a lock there15:37
apwsmb, hrm not sure i think i have15:38
smbapw, OK, I aborted. Just to let you know, stable process is clearly hardware and not devprocess ;-)15:39
apwsmb, nope when i dit the Specs page it says i don't have a lock15:39
apwsmb, what they moved it _again_ ?15:39
apwsomeone needs to fix the system so we don't have to rename the damn things every time someone changes their mind15:39
smbIf it worked before then yes. Or was a typo there15:39
=== cking is now known as cking-afk
=== ivoks-afk is now known as ivoks
=== diwic_afk is now known as diwic
apwtgardner, are we calling the first upload -1 or -016:01
tgardnerapw, don't care. the current ABI number is fine.16:01
apwtgardner, ack16:02
hermesFellow 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:23
bjfhermes, http://wiki.ubuntu.com/Kernel16:25
=== cking-afk is now known as cking
hermesbjf: 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 evaluation16:26
hermesbjf: Or like a team who work on something, and I could get involved to contribute with them16:27
apwall of our bugs are public, as is our mailing list, and all contributions are welcome16:27
hermesapw: great16:28
bjfhermes, JFo can help you get going on looking at bugs16:29
hermesbjf: thats is great, I would want a little help initially to get set myself up16:31
bjfogasawara, you have some stable release patches queued for maverick somewhere? you planning on pushing those today?16:39
ogasawarabjf: yep, I've got them ready to push.  just wanted to double check with you guys first that it's ok16:40
ogasawarabjf: I've also already build and boot tested16:40
ogasawarabjf: then I think I can officially hand off the Maverick git repo to you guys16:40
bjfogasawara, good for me, i think it's cool with sconklin and smb16:40
* smb is cool 8he thinks)16:40
tgardnerogasawara, aren't you officially on stable duty for the next while?16:40
ogasawaratgardner: yep, but will go through sconklin for that16:41
tgardnerack16:41
AndChat|I kno u guys r busy but I've got an issue in the kernel i'd like to shine some light on16:43
apwAndChat|, you'd need to elucidate16:44
AndChat|http://ubuntuforums.org/showthread.php?t=159369516:44
AndChat|Basicly myth hangs when using dvb module cx23885 to tune channels causing kernel oops16:49
ogasawarabjf, smb, sconklin: pushed 2.6.35.5, 2.6.35.6, and 2.6.35.7 patch sets to Maverick tip16:50
bjfogasawara, cool, thanks16:50
smbogasawara, I am probably throwing myself behind the train but did those have tracking bugs?16:51
hermesbjf: Should I ask JFo personally or shud I ask him here16:51
ogasawarasmb: yep, lemme find them real quick16:51
ogasawarabug 64552216:52
ubot2Launchpad 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/64552216:52
ogasawarabug 64920816:52
ubot2Launchpad 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/64920816:52
ogasawarabug 65142516:52
ubot2Launchpad 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/65142516:52
sconklin1Cable company is here to install my faster network. It shouldn't cause an outage . . . . but if I drop away that's why16:52
bjfhermes, here is good a good start16:52
tgardnersmb, behind the the train ?16:52
ogasawaratgardner: heh, I guess that's better than in front of it :)16:53
smbogasawara, cool, just wanted to make sure we got them to add to the changelog16:53
hermesbjf: alright16:53
ogasawarasmb: I added them as BugLinks to the commits which update the version16:53
smbtgardner, ogasawara, right but if the purpose is to stop it... well probably as useless to throw one before than after. :)16:54
tgardnerah, I get it.16:54
hermesI am fairly new to the kernel programming, but I have a keen inclination towards systems programming. 16:55
hermesCould anyone suggest me what shoud I start looking at 16:55
hermesJFo: if you could help me get started I would appreciate than man16:55
sconklin1hermes: a good first set of tasks are just to pull the kernel source from the distribution git repositories and build it locally17:02
=== sconklin1 is now known as sconklin
bjfapw, tgardner do we have a start of an agenda for the mini-sprint in boston after uds?17:08
=== diwic is now known as diwic_afk
apwbjf, i've not put anything anywhere yet, though we did have something ...17:28
apwi think there is a spot for the agenda on the wiki page though17:28
apwtgardner, 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.list17:29
apwspecifically for armel17:29
tgardnerapw, which chroot flavour?17:29
apwarmel for maverick17:30
apwas made by a make_release17:30
tgardnersdhould be 'sudo ./make_chroot maverick armel'17:30
apwwhere does POCKETS get set ?17:30
=== ivoks is now known as ivoks-afk
tgardnerit tries to figure out if you are me, pete, then defaults to the regular mirror17:31
apwi'm running it with my own on the command line17:31
tgardnerkteam-tools/chroot-setup/scripts/chroot-defs.conf17:31
tgardnerfunction get_pockets ()17:31
apwtgardner, yeah gets passed that17:32
apwyet behaves as if it does nto contain 'release'17:32
tgardnerapw, hmm, etc/sources.list is trashed?17:32
apwtgardner, yeah its empty, present but empty17:33
tgardneruh, thats not cool17:34
apwtgardner, i guess i get to debug it :/17:34
tgardnerwrite_mirror is where that gets updated17:34
ckingis there a k-t meeting today?17:34
bjfcking, nope, done until post uds17:35
bjfcking, you can quit for the day :-)17:35
ckingin which case, I will be slipping off "early" today17:35
* smb suddenly feels very gone17:36
manjoany idea when the natty tree will be open ? 17:38
* tgardner wonders if manjo has been living in a cave17:38
ckingliving a cave is what trolls like me do17:39
apwmanjo, i'd not say for a couple of months yet17:39
apwelse how can we have a holiday17:39
manjoapw, yep got that.. was wondering if we know what month etc ? I wanted to answer a partner on the time frame17:40
ckingdidn't we agree to keep it the same as maverick?17:41
* apw *blink*17:41
ckingapw, http://zinc.canonical.com/~cking/iotest-4k-writes.png - more graphs17:42
apwcking, i was rather partial to hardy's kernel ...17:42
ckingyeah, we should revisit it I think for natty 17:42
apwmanjo, have you looked for the tree ?17:44
manjoyep I have it cloned on tangerine17:47
tgardnermanjo, in that case you shold know the tree has been open for 6 weeks or more17:47
apwand if you meant the archive, it'll be open as soon as the toolchain is in17:48
manjocan you guys hear me on mumble?17:51
smbmanjo, no17:51
manjocrap17:51
manjois it mumble or you guys fscking with me ? :) 17:52
tgardnermanjo, eh? I can't hear you.17:53
ckingmanjo, cannot hear you17:54
manjofack I give up 17:57
bjfmanjo, we can barely hear you17:57
ckingmanjo, how's that HDD testing progressing?17:57
* cking thinks a mumble plug in to android is required17:58
manjocking, I ran stress for 3 days, sat, sun, monday, I had to kill it this morning.17:58
manjocking, I am going to try your test kit you point us to17:58
manjoso far it looks good, I too try dding 2.5T worth of data into the disk and that works17:59
manjoI have brian from AMI testing the latest maverick on their bios 17:59
ckingmanjo, collect the output and send it to me, I can analyse the throughput with some gnuplot magic17:59
manjothey have started to integrate maverick iso into their test bed17:59
manjoI 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
ckingis this firmware BIOS+ACPI or UEFI+ACPI?18:00
manjocking, they are testing a few different BIOS versions to make sure the patches they put in for different distros are holding up 18:01
manjocking, UEFI 18:01
ckingin which case, it's not BIOS, it's UEFI :-)18:01
manjoyeah :) 18:01
manjoUEFI BIOS18:02
manjoeasy to type bios18:02
ckingnooooo. UEFI is not BIOS18:02
manjomy fingers type bios more easily than UEFI18:02
ckingheh, easy to do. BIOS has been around for donkeys18:02
manjoso. we have quiet a bit a testing going on with Maverick in AMI18:03
lagNo meeting today?18:03
ckinglag, nope18:03
lag'cos Maverick has been released?18:03
manjolag, usually not until after uds18:03
lagWoooooooooooooooo18:04
manjoprobably after November 6, bjf ?18:04
manjocking, I poked the guy at Seagate to send us some disks18:04
cking manjo, what spec are these?18:05
manjocking, 3T disks18:05
ckingsweet18:05
lagmanjo: Can you poke the guy as Seagate to send me some of those disks?18:05
manjonot sure if they are 4K or not 18:05
bjfmanjo, lag, the topic seems to indicate Nov. 9 :-)18:05
manjolag, this is for testing ?18:05
ckingbjf, you expect us to read?18:05
manjotgardner, tangerine is in boston ?18:06
tgardnermanjo, yep18:06
manjotgardner, I have an extra 2.5T disk ... do you want to add it to tangerine ?18:06
tgardnermanjo, tangerine only supports 2.5" disks18:07
manjobummer18:07
manjocking, if the seagate disks arrive before UDS I will bring you one 18:09
manjoI have not heard back from them as yet18:09
ckingI'm not wetting myself waiting for them18:11
lagmanjo: Of course18:11
manjolag, :) ok 18:17
maxbHrm. The fact that the kernel no longer lets you attach a debugger to your own processes didn't make the release notes18:44
maxbAnyone point me to have to turn it off, given that omission? :-)18:44
=== smb` is now known as smb
tgardnermaxb, kees should be able to remember how. its a sysfs flag somewhere.18:46
jjohansenmaxb: change /proc/sys/kernel/yama/ptrace_scope 18:46
maxbyama?18:47
jjohansenset it to 0 for no extra ptrace control18:47
jjohansenit is a collection of security restrictions that have been floating around for years18:47
keesmaxb: why did it not make the release notes? it's been in the notes for like 5 months18:47
jjohansenptrace restrictions, symlink, hardlink18:47
maxbhttps://wiki.ubuntu.com/MaverickMeerkat/ReleaseNotes <-- am I in the wrong place?18:47
bo_apw: I filed a bug with kernel drm information as you asked to do.18:59
keesmaxb: hm, here it is https://wiki.ubuntu.com/MaverickMeerkat/TechnicalOverview19:00
keesmaxb: gah, but it vanished from there too19:01
keesmaxb: https://wiki.ubuntu.com/MaverickMeerkat/TechnicalOverview?action=recall&rev=38  <- search for "ptrace" there19:03
keesmaxb: I'll try to get the releasenotes updated19:03
* tgardner lunches19:22
jjohansenbjf: when is the Lucid EC2 update going to get pushed?19:26
bjfjjohansen, should be in -proposed now, checking19:27
=== ivoks-afk is now known as ivoks
bjfjjohansen, -309.17 is in proposed, that was uploaded after your rebase19:30
bjfjjohansen, are you asking when will it be promoted to -updates?19:30
jjohansenbjf: ah yeah an estimate19:31
bjfjjohansen, at least another week19:32
jjohansenokay, thanks19:32
gilson585Can someone assist me on bug 65934819:34
ubot2Launchpad bug 659348 in linux (Ubuntu) "dvb module cx23885 hangs mythtv-setup (affects: 2) (dups: 1) (heat: 14)" [Undecided,New] https://launchpad.net/bugs/65934819:34
jjohansenbjf: thanks, it came up in the server team meeting19:34
bjfjjohansen, that's what i figured19:35
=== sconklin1 is now known as sconklin
* jjohansen -> lunch19:58
ivokshi20:14
ivoksdid you notice that -virtual is missinf nfs modules?20:14
ivoks(in maverick)20:14
ivoksthat's bug 65908420:19
ubot2Launchpad 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/65908420:19
ckingnatty narwhal kills tux? http://www.mcphee.com/shop/product_images/c/906/11689__59447_zoom.jpg20:32
manjocking, looks aaaaweful20:35
ckingkarmic koala gets impaled too if he's not careful20:36
gilson585|lol too funni20:36
ogasawarabjf: 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:48
sconklindon't assume that we have a process ;-o20:49
ogasawaraheh20:49
bjfogasawara, no, after two acks i apply them to my own tree, do test builds, push to public then ask sconklin to review20:49
bjfogasawara, after sconklin and smb say "looks good" i push to master repo20:49
ogasawarabjf: and I assume you just nudge them directly if you need a 2nd ack for a patch20:51
bjfogasawara, yup20:53
bjfogasawara, depending on your meaning of "nudge them directly"20:54
bjf:-)20:54
* ogasawara lunch20:59
jjohansenivoks: nope didn't notice or else it would be fixed already21:01
ivoksjjohansen: ok21:02
jjohansenivoks: thanks for bringing it up, will look into it21:03
ivoksjjohansen: it's enabled in config21:03
ivoksjjohansen: so i'm not really sure what's going on21:03
jjohansenivoks: yep, its probably in the packaging phase21:03
* tgardner bails for the day21:32
=== ivoks is now known as ivoks-afk
bjfogasawara, mumble21:57
=== bjf is now known as bjf[afk]

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!