psusijjohansen, so let's figure out how to handle it ;)00:46
psusithe kernel needs some way of notifying the clients ( fs, md, dm, blockdev ) of the block device that it either wants to be , or already has been ( requested or surprise ) removed so they can release the bdev pointer.  that seems a wee bit problematic by the fact that multiple clients can have references...00:51
jjohansenpsusi: yes its problematic00:58
=== emma is now known as em
=== _LibertyZero is now known as LibertyZero
apwmjg59, the original was pulled as it was generic, that one is restricted to two models of dell where the touchpad doesn't work at all with alps, thats my memory anyhow ... causing issues ?07:08
jk-hey smb & apw07:26
smbhey jk- 07:26
apwcking, morning09:12
ckingapw, hiya09:14
apwcking, hows it going ...09:14
=== _ruben_ is now known as _ruben
mjg59apw: Well, it still doesn't work at all with alps in any real way12:36
mjg59apw: You're still just changing one non-configurable setup for another12:36
apwmjg59, the patch as commited only applies to those specific models but yes its crap12:37
apwmjg59, i am told that alps refuse to disclose how to enable the touchpad correctly as a touchpad12:38
mjg59You end up with something where you can't turn off tap to click, which may or may not be preferable to the original state12:39
apwmjg59, yeah i get you, cause its not a touchpad that option doesn't exist, sigh12:40
mjg59ALPS seem to believe that their multitouch protocol is a massive trade secret12:40
mjg59And it's annoyingly inconvenient to trace PS/212:40
apwi can only call the whole mess, well a mess12:40
apwyeah ... we are pushing vendors to use something else for their linux enabled stuff, they are just too painful to talk to12:41
mjg59But Dell aren't willing to push ALPS because that patch exists and is carried by Ubuntu12:41
apwmjg59, great indeed12:44
mjg59So kind of an awkward situation for everyone12:45
mjg59I should look into whether I can work out the init sequence using qemu, really12:46
apwif you have the kit yeah that would be a good plan me thinks12:48
ogasawarahrm, anyone recall if bjf had a script which closed a bugs task that has a nomination which is EOL13:26
ogasawaraI'm particularly looking at https://bugs.launchpad.net/ubuntu/karmic/+source/linux13:27
tgardnerogasawara, seems like he's been running something lately since I've seen a bunch of those kind of closures.13:27
apwogasawara, if not it should be a trivial one to write13:29
ogasawaraapw: indeed, was just hoping to save myself the 10min since I'm lazy13:29
ogasawaraI'll just wait till he comes online13:30
ogasawaraI'm thinking that whatever creates the CVE bugs should also drop adding karmic as a target, if it's not already fixed that is13:31
apwogasawara, ok i've finally rememberd to add that section to the config review, with the modulular things which are not modular13:32
apwogasawara, i believe we already have stopped adding karmic for cves13:32
apwogasawara, and my script should be closing them out, do you have an example of a non-won't-fix one ?13:32
ogasawaraapw: I actually meant to say if the script wasn't already fixed, it should be13:33
apwogasawara, i believe it is suppressed by the karmic being mark Supported: false13:34
apwogasawara, https://wiki.ubuntu.com/KernelTeam/Specs/KernelOneiricConfigReview#Non-modular_modules is the full list which needs review.  not sure how we should handle the review part, prolly needs a wi13:36
ogasawaraapw: cool.  I'll add myself a work item to start sifting through them.13:38
apwogasawara, last week we found a page which had your report on it for the bugs for the meeting, since then the link seems to have gone dead in th13:52
apwthe readme, did it move ?13:52
ogasawaraapw: can you point me to which README?13:53
ogasawaraapw: hrm, I'd been using http://reports.qa.ubuntu.com/reports/ogasawara/kt-meeting.txt but I do recall I should have move it from my own personal directory to the kernel-ppa/reports13:56
apwogasawara, would it run on people? as most of the reports are there13:57
ogasawaraapw: I don't see why know, I'll move it there for consistency and update the README13:57
ogasawarawow, s/know/not/13:57
bjfogasawara, we talked about adding it to the Makefile that generates all the reports14:01
ogasawarabjf: yep, makes sense14:01
ogasawarabjf: also before I forget, didn't you say you had a script which closes out a bug task for a nomination that is not EOL14:02
bjfogasawara, if that did/does happen, I'll need to update the copy of kteam-tools in people/~kernel14:02
ogasawarabjf: i was looking at https://bugs.launchpad.net/ubuntu/karmic/+source/linux14:02
bjfogasawara, i was "won't fix"ing bugs last night that were filed against dapper, feisty, and intrepid14:03
bjfogasawara, i don't have one that changes nominations for tasks that are EOL (but I should)14:04
apwogasawara, let me know when you are done fiddling with kernel i have something to add too14:04
ogasawarabjf: ok no worries, I'll whip up a script to close out EOL nominations14:04
ogasawaraapw: ack14:04
apwbjf, i assume the "plan" is to check everything into team-tools, and then rsync it over the one in ~kernel ?14:04
ogasawarabjf: I assume I can edit the Makefile the same as I did when I added my CVE report14:04
hggdhbjf: just confirming, the only other kernel for us (QA) to test now is Hardy, correct?14:04
bjfapw, yes, that's how I do it14:05
bjfogasawara, yes14:05
apwbjf ok cool14:05
bdmurrayapw, ogasawara: I've uploaded a new version of kerneloops which should *not* report WARNINGs.  I'm working on the driver tagging today.14:05
ogasawaraapw: go ahead and add whatever you need to kernel, I have to tweak my script I think14:06
bjfogasawara, look at mark-unsupported-wont-fix in kteam-tools/bugs 14:06
bdmurrayapw, ogasawara: so if you happen to see any Oopses with warnings in them let me know.14:06
bjfhggdh, you have to ask sconklin 14:06
ogasawarabdmurray: awesome, thanks14:06
bjfbdmurray, are you prefixing the driver tags with "kernel-" or anything, or is it just the driver name?14:07
bdmurraybjf: just the driver name14:07
bdmurrayI gave ogasawara a list of the existing oopses I tagged14:08
bjfbdmurray, if ogasawara and apw agree, I think it should be prefixed with "kernel-driver-"14:08
ogasawarabjf: that's fine with me, I just had bdmurray originally tag by driver name just for simplicity14:08
bjfogasawara, since we are prefixing all our other tags with "kernel-" and since I think it makes it more clear what that tag is for, it would be nice to have the prefix14:10
ogasawarabjf: makes sense14:10
bjfogasawara, i can also put together a report based on just "kernel-driver-*" bugs at some point14:12
bdmurrayI guess it would be easier to find new ones too14:12
ogasawarabjf: that would be nice14:12
bdmurrayrather than if something just got tagged e100014:12
hertonhggdh: not only hardy, including it these bugs are waiting for QA: 801636 806586 80893414:12
bdmurraybjf: I'll try and find whatever I wrote to tag the existing Oopses and retag them with kernel-driver-fglrx (or whatever)14:13
bjfbdmurray, that would be great, thanks14:14
bjfbdmurray, maybe after whatever changes you make this time and after this run of it, we should take it into our tools repo and maintain it ?14:15
hggdhherton: thanks. I was not aware we were doing backporting tests also14:16
hertonhggdh: I'm not sure what is done about lts-bakckport packages also regarding QA14:16
bdmurraybjf: so the plan is to modify apport so that oops are tagged kernel-driver-drivername when the oops is being submitted.  This is just cleaning up the already reported stuff so really should be a one time thing.  Additionally, its a mess of parsing Oops reports that I've downloaded14:16
bjfbdmurray, ah! ok, that makes sense14:17
bjfbdmurray, disregard my earlier comment, still waking up14:17
hertonhggdh: steve mentioned that for backport packages teams have to sign-off on them also, so I guess it is up to you, but better confirm with him later14:17
hggdhherton: I just wish I got to be informed of things that affect QA14:18
apwhggdh, don't the tasks in launchpad tell you things you need to be concerned with ?14:19
hggdhapw: not enough of a warning, if you add in unplanned-for work14:19
apwhggdh, so what sort of warning are you looking for14:20
hggdhapw: something like 'hey QA, we are going to add backporting tests to your expected work load, how about getting ready to it?' <- in advance14:21
apwhggdh, are we talking about lts-backport-foo here ?14:22
hggdhapw: bugs 806586 80893414:22
ubot2Launchpad bug 806586 in kernel-sru-workflow/security-signoff "linux-lts-backport-natty: 2.6.38-10.46~lucid1 -proposed tracker" [Undecided,In progress] https://launchpad.net/bugs/80658614:22
ogasawarabjf: do by chance know if lplib has a way of retrieving a list of current supported releases, so I don't have to maintain a hardcoded list like "releases = ['oneiric', 'natty', 'maverick', 'lucid', 'hardy']"14:23
bjfogasawara, in kteam-tools look at ktl/ubuntu, also look at the script i mentioned earlier, it calls a method to determine "support"14:24
ogasawarabjf: cool14:24
bjfogasawara, basically, we already maintain a master list and it's in ktl/ubuntu.py14:25
apwhggdh, ahh my understanding of why we are passing those your way, is cause you were signed up to do them14:30
* herton -> lunch14:32
* ogasawara back in 2015:07
apwogasawara, where can i find your current report, want to look at the format15:11
paultagHey kernel-ers. I've been testing btrfs for the cycle, and it's gotten to the point of horrid IO times, to the point where bootup is taking much longer then it should (2.6.38-8-generic-pae) -- has anyone heard anything about IO speeds on the +1 kernel, or upstream?15:18
paultagIt feels like I'm back in 2004 :)15:19
apwpaultag, nothing specific other than a general feeling that as they fix consistancy issues in btrfs it is losing its performance edge15:19
tgardnerpaultag, have you tried oneiric? a lot of work has gone into btrfs this cycle15:19
paultagtgardner: I have not, I'm still on natty. Should I consider it?15:20
paultagapw: well that's good anyway :)15:20
paultagIs there any way I can dump some sort of profile or set of statistics that might help development upstream?15:21
tgardnerpaultag, absolutely. you can run the oneiric kernel without having to change your user space.15:21
paultagtgardner: sure, sure :)15:21
paultagAlso, I do have one other, perhaps related, issue. Once in a while, after the screensaver's been on and DPMS shuts off the screen, the kernel locks up (not sure if btrfs blocks or fails a read, and it's stuck waiting for IO, or if it's kernel it's self, but I don't recall this with ext4), and will only respond to a REISUB. Does anyone have advice on how to debug this, and put together a sane report?15:25
paultagit's fairly reproducable, and it always happens when I need my machine in a bad way :)15:26
paultag(then I have to put up with a horrid boot time, welcome to my hell)15:26
apwpaultag, is it always when DPMS has triggered, there was/is a problem with vsync not restarting and breaking compiz15:27
ogasawaraapw: http://people.canonical.com/~kernel/reports/kt-meeting.txt15:28
paultagapw: I seem to recall one time seeing the screensaver frozen, but that could have been some sort of race condition. I also have two monitors if that helps debug anything15:28
paultagapw: should I upgrade a package or two and test if it is vsync?15:29
apwpaultag, i guess i'd wnat to know if you can login remotly, that'd be the first test15:29
paultagapw: good point. I'll install ssh and wait for it to happen, then let ya'll know. Since I REISUB, I'm guessing the kernel's online, and it does not look like a panic, so it *should* work15:30
paultagapw: cheers, thanks!15:30
ogasawarabjf: how often does the cron on lillypilly run for the kernel reports?15:59
ogasawarabjf: nm, every 3016:00
apwbjf, is this in a tabalable form for the irc converter: http://people.canonical.com/~apw/cve/pkg/CVE-linux.txt16:16
bjfapw, yes, any "moin table" format can be handled16:18
apwat rally we talked about reporting something in the weekly meeting on CVEs and that seems like the sort of thing, what you think16:19
bjfapw, that looks good to me16:20
apwok will get that into the readme while i am at it, if you could add to the agenda16:20
apwprobabally belongs in the 'stable' section16:20
bjfapw, ack16:21
bjfapw, who should i put as the reporter? you for now?16:21
apwbjf sure16:21
ogasawarawhat are the devel and mainline branches of kteam-tools?16:23
bjfogasawara, ignore "devel", i think sconklin created it16:23
apwogasawara, yeah i work against the master always ... ps i just updated the README for irc so we are likely to collide16:24
apwbjf, i've added moveing the CVE stats and the CVE report over to ~kernel for my 'next week' todo list16:24
ogasawaraapw: ack, I'll rebase and push16:24
bjfapw, ack, added agenda item to wiki page and to the runes16:25
ogasawaraapw: did you push your bits up yet?16:26
apwogasawara, yep16:26
apwfeel free to just merge it and fix the README16:26
apwwe are used to a mergetastic history16:27
ogasawaraapw: I'm not seeing your bits on kteam-tools master16:27
apwogasawara, brad found them, merged with them and pushed again16:28
apwso i assume they are up there16:28
ogasawaraapw: ah that makes sense then, I was looking for you as the author16:29
hertonogasawara: devel is some experimental things we have been playing with (changes to sru workflow), just ignore it for now16:29
apwbjf, ubuntu.supported_serieses ?? really, is not the plural of series series ?16:55
bjfapw, yes, thanks for pointing out i can't spell16:55
apwbjf, heh its bad if i spell better than thou16:56
bjfapw, i blame being drunk but I know you wouldn't believe that16:56
ogasawarahehe, I saw that too and chuckled16:56
* smb decides to end the day17:04
* apw cracks a cold one in sympathy17:10
* tgardner yanks the power to a noisy fan17:15
* apw calls it a day ... see your all next week17:43
jjohansenhave a good weekend apw17:44
tgardnerapw, what is the derby thing ?17:45
* tgardner --> lunch17:53
vanhoofhey guys -- quick question :)17:55
vanhooflatest oneiric kernel brought in the isci driver for newer intel sas controllers17:56
apwtgardner, fun is all17:57
vanhoofis there a process i should follow to request they be pulled into the initrd for installs?17:57
apwtgardner, updated it ... better ?17:58
vanhoofdisregard my question :)18:18
bdmurraybjf: I'm to lazy to remove the existing tag so I'll just add kernel-driver-ipaq and leave ipqa18:46
bdmurrayer ipqa18:46
bdmurraywtf ipaq18:47
bjfbdmurray, ok18:47
bjfapw, did you pick a usb drive? i just picked up a Patriot Rage XT (8G). Avg. read rate: 31.6MB/s Avg write rate: 5.8 MB/s   19:05
=== Quintasan_ is now known as Quintasan
=== yofel_ is now known as yofel
ohsixdid natty stop logging to /var/log/messages? :O my confings didn't change but theres no messages in there since march21:58
=== kentb is now known as kentb-out

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