[01:40] <bryce> https://wiki.ubuntu.com/X/Troubleshooting/IntelPerformance
[06:01] <bryce_> heya cwillu
[06:01] <cwillu> poke poek
[06:01] <bryce_> cwillu: with -intel bug triaging, the name of the game for us is getting bugs upstreamed to Intel
[06:02] <bryce_> we fix _some_ bugs in Ubuntu but the vast bulk are fixed upstream, and we cherrypick the patches into Ubuntu
[06:03] <bryce_> of course, hardly anyone reports bugs to us in a form that we can upstream, so it usually takes some work on our part to massage them into shape, getting the requisite info, etc.
[06:04] <bryce_> cwillu: the page to bookmark is http://intellinuxgraphics.org/how_to_report_bug.html
[06:05] <cwillu> got it
[06:06] <bryce_> I've been developing some automated scripts that help in gathering or requesting the info, but some reporters really need human help
[06:06]  * cwillu is composing notes in the background, please keep the info dump going :)
[06:06] <bryce_> ah ok :-)
[06:07] <bryce_> what else...
[06:07] <bryce_> you may want to join the ubuntu-x@ mailing list as well; quite low traffic but I try to announce stuff there and we sometimes have useful discussions
[06:08] <bryce_> https://lists.ubuntu.com/mailman/listinfo/Ubuntu-x
[06:08] <cwillu> if I start adding tags to bugs in a private namespace, are they likely to remain there, at least for a week or so?
[06:08] <bryce_> we also have a team set up in launchpad - https://edge.launchpad.net/~ubuntu-x-swat
[06:09] <bryce_> private namespace?
[06:09] <cwillu> (cwillu-foo, cwillu-bar)
[06:09] <bryce_> ahh, yeah feel free to add tags
[06:09] <cwillu> mainly so I don't trip on other stuff by accident
[06:10] <cwillu> I was planning on opening umbrella bugs per-chipset, linked to newly opened bugs for each unique symptom that I can see.  
[06:10] <bryce_> btw, if you join the ubuntu-x-swat list, one important caveat is that it subscribes you to the bug mail - roughly 100 mails per day
[06:11] <bryce_> so if you do that make sure you have procmail or something to filter those out.  I'd be happy to share my procmail rules if you use it
[06:11] <cwillu> I think a good portion of the deluge comes from people posting to the first bug they find with a similar symptom, so "intel video hangs" gets all the traffic even if it's an 810 bug
[06:11] <bryce_> being a member of the team enables you to set states Triaged and Wontfix, set priorities, etc.
[06:11] <cwillu> bryce, I'm addicted to gmail :p
[06:11] <bryce_> hehe
[06:12] <bryce_> indeed, you're absolutely right.  "driver performance regression" would be another good subjectline if you wanted to cause a me-too storm ;-)
[06:12] <bryce_> I try to always update bug titles when I see ones that just describe a generic symptom
[06:13] <bryce_> it helps head off confirmation hell
[06:14] <bryce_> regarding tagging of chipsets, one thing I've been doing is prepending bug titles with chipset names, [i845], etc.
[06:14] <cwillu> yep, that was my inspiration actually :)
[06:14] <bryce_> I think people used to use tags for the same purpose, but an advantage to the subject lines is that it helps mitigate me-too'ing
[06:15] <cwillu> Umbrella bug per chipset, and then nice fresh bugs with the chipset in the title, a list of similar but different bugs in the summary, exhortations to verify the chipset and simple instructions to do so
[06:15] <bryce_> as well, even mroe importantly, it's the format upstream likes to have when we upstream the bugs
[06:15] <cwillu> basically, a couple hundred words of boilerplate, to make it easy on the lazy bug reporters
[06:15] <bryce_> sounds interesting
[06:15] <cwillu> is that counterproductive re: upstreaming those bugs?  (I'm imaging that the boiler plate can be stripped easily enough)
[06:16] <bryce_> dunno, I'd need to see it in action.  Willing to give anything a shot that helps us get more organized
[06:16] <cwillu> I guess if I get a start on this over the weekend, I probably won't be tripping over too much concurrent activity on launchpad
[06:17] <cwillu> I'll avoid marking any of the old bugs as duplicates until it's clear if it's a win or not
[06:18] <cwillu> (are duplicated bugs hidden from searching-by-tag by default as well?)
[06:18] <bryce_> yes
[06:23] <cwillu> this would also be one of those days I regret not having my wiki up and running
[06:23] <cwillu> my schemes -> http://pastebin.com/f5600578c
[06:27] <bryce_> nice
[06:28] <cwillu> is there any need to drill down to the particular revision, or is the general chipset enough?
[06:29] <bryce_> when you go through bugs you'll note the format I've been trying to use, basically separating standard sections via [lspci], [testcase], etc.
[06:29] <cwillu> yep
[06:30] <cwillu> god I hope they get that ext4 mess sorted out quick
[06:30] <bryce_> especially when upstreaming bugs I like to have the top of the bug report be a very brief [problem] statement, no more than 1-3 sentences, so people can quickly skim it
[06:31] <cwillu> okay
[06:31] <cwillu> Time for bed now, I should be getting started in ~10 hours or so
[06:31] <cwillu> Thanks for the info :)
[06:31] <bryce_> regarding the particular revision...  in the subjectline I tend to keep it just to the family, but in the [lspci] section it is good to be more specific
[06:32] <cwillu> okay
[06:32] <bryce_> sure, cya later :-)
[06:33] <cwillu> don't know if you want to mention anything on the mailing list, I probably won't be bothering to subscribe to it until I'm thoroughly sick of sifting through launchpad sometime tomorrow :p
[06:36] <bryce_> ok, I'll wait 'til you make introductions
[07:00] <tjaalton> bryce_: looks like the glxinfo crashers all had nvidia in NonfreeKernelModules, so -> nvidia-glx-180 :)
[07:01] <bryce_> aha
[07:01] <tjaalton> moving them right now
[07:01] <bryce_> tjaalton: odd, I was just looking at nvidia bug replies
[07:01] <tjaalton> also, there are a couple of intel regressions, suggesting that the most recent version doesn't work for everyone
[07:01] <tjaalton> filed against xorg
[07:01] <bryce_> looks like a handful of people followed through on my request to test + close -180 bugs.  Was hoping to see more, but at least it's something
[07:02]  * bryce_ looks
[07:02] <tjaalton> these were filed against mesa
[07:04] <bryce_> which bug #'s?
[07:05] <bryce_> none of the new bugs in xorg look due to today's updates...
[07:05] <tjaalton> 354735
[07:08] <tjaalton> ok that was the only one I guess
[07:09] <bryce_> ok
[07:09] <bryce_> nx6110 sounds familiar...
[07:11] <bryce_> hmm, well if he truly has narrowed it to 2:2.6.3-0ubuntu4 or ubuntu3, the only change in those that looks reasonably questionable is 118_drop_legacy3d.patch
[07:12] <bryce_> ./debian/changelog:  * 25_quirks_nx6110.patch:
[07:13] <tjaalton> hmm bug 354889 looks related
[07:16] <tjaalton> found a dupe for steve's bug
[07:24] <bryce_> how related?
[07:25] <tjaalton> same error message
[07:25] <bryce_> I've run across a bunch of "crash on playing video" bugs.  We need to report those upstream
[07:25] <tjaalton> http://dl.getdropbox.com/u/256410/IMG_0479.JPG
[07:26] <tjaalton> duped them already
[07:26] <bryce_> hehe
[07:26] <bryce_> man, that bit of code to put the error into the dialog has turned out way more useful than I'd anticipated :-)
[07:27] <tjaalton> heh
[07:30] <Alexia_Death> bryce: that was a truly inspired idea.
[07:30] <bryce_> grep ftw
[07:31]  * Alexia_Death hates having to do that manually when something fails
[07:32] <Alexia_Death> Now, if crash log would not get overwritten if you log in again for random crashes...
[07:32] <bryce_> Alexia_Death: it should not get overwritten
[07:32] <bryce_> Alexia_Death: I made sure the failsafe log gets written to Xorg.failsafe.log instead
[07:32] <Alexia_Death> failsafe yes
[07:32] <bryce_> Alexia_Death: also the Xorg.0.log.old should still contain the prior crash
[07:33] <Alexia_Death> but say my X crashes but theres no need or failsafe
[07:33] <Alexia_Death> X can start normally
[07:33] <bryce_> right
[07:33] <Alexia_Death> greeter loads just fine and I log in
[07:33] <bryce_> crash should still be in the Xorg.0.log.old
[07:33] <Alexia_Death> After I log in the crash log is gone.
[07:34] <Alexia_Death> no. its gone.
[07:34] <bryce_> are you sure?
[07:34] <Alexia_Death> the greeter log is in the .old
[07:34] <bryce_> it's been there for me...
[07:34] <bryce_> hm
[07:35] <Alexia_Death> I havent needed it in  the past few months but before that when tablet still crashed X I needed to keep a console session to coppy the log before it was lost
[07:36] <Alexia_Death> its a sort of thing you only need when things go wrong  with X configured right...
[07:36] <bryce_> Alexia_Death: ok, well 274870 covers this situation
[07:37] <Alexia_Death> ?
[07:37] <bryce_> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=503251 - forwarded to debian, but no response so far afaik
[07:37] <tjaalton> Alexia_Death: the wacom hotplug patches are now upstream :)
[07:38] <tjaalton> in 0.8.3-2
[07:38] <bryce_> (and I'm open to alternate ideas || patches)
[07:38] <tjaalton> and builtin serial devices should work OOTB
[07:38] <Alexia_Death> tjaalton: Indeed:D
[07:38] <Alexia_Death> bryce: yes, that covers it:)
[07:39] <Alexia_Death> tjaalton: how was that done?
[07:40] <Alexia_Death> My daemon has serial devices description file. I use an usb Serial tablet
[07:40] <Alexia_Death> laterz
[07:40] <tjaalton> Alexia_Death: with a hal callout program that feeds the parameters to the xserver/driver
[07:41] <Alexia_Death> tjaalton: sounds sensible:)
[07:41] <tjaalton> "usb serial tablet"
[07:41] <tjaalton> how's that possible :)
[07:42] <Alexia_Death> usb->serail adapter+ serial tablet:)
[07:42] <tjaalton> ah
[07:50] <tjaalton> how the hll is lp karma counted these days? yesterday or the day before mine was around 16k and now it's over 50k..
[07:51] <RAOF> Hm.  We may need to pull in a patch to update libdrm-nouveau.  Let's see...
[07:52] <bryce_> tjaalton: I heard there was some inflation in translation karma
[07:52] <tjaalton> i wonder if there's a "my sister runs ubuntu" team..
[07:52] <tjaalton> bryce_: haven't done those ;)
[07:52] <tjaalton> oh, soyuz
[07:52] <tjaalton> 35k from there
[07:55] <bryce_> tjaalton: btw, cwillu suggested some of these random unexplained lockups might be due to the ext4 fallout
[07:56] <bryce_> (bug #330824)
[07:56] <tjaalton> oh?
[07:56] <RAOF> Ow.  Everyone's favourite not-quite-stable filesystem!
[07:58] <tjaalton> I'll switch to btrfs once karmic opens ;)
[07:59] <tjaalton> who cares if it can't handle full disks
[07:59] <tjaalton> disks are cheap
[08:00] <bryce_> I wonder if there's any way we can easily determine what filesystem they have installed?
[08:04] <sbeattie> installed or mounted? cat /proc/mounts will tell you what fs types are mounted
[08:04] <tjaalton> the problem is (reliably) determining where $HOME is
[08:05] <tjaalton> under / or /home or linked somewhere
[08:05] <bryce_> I'll add /proc/mounts to our apport
[08:06] <sbeattie> ooh, mount -t ext4 will tell you if any of the fielsystems are ext4.
[08:09] <sbeattie> hrm, what does stat -f /path say on an ext4 system? 
[08:10]  * sbeattie wiped all his test ext4 partitions after getting bit by data loss.
[08:11] <bryce_>     try:
[08:11] <bryce_>         script = subprocess.Popen(['mount', '-t', 'ext4'], stdout=subprocess.PIPE)
[08:11] <bryce_>         matches = script.communicate()[0]
[08:11] <bryce_>         if (matches):
[08:11] <bryce_>             report['ext4'] = matches
[08:11] <bryce_>     except OSError:
[08:11] <bryce_>         pass
[08:11] <bryce_> look good?
[08:11] <tjaalton> sbeattie: Type: ext2/ext3
[08:11] <sbeattie> ah, bummer. time to file a bug on stat
[08:12] <tjaalton> yeah
[08:13] <tjaalton> jcristau: should the rgb.txt-file be revived? there seem to be a number of client apps that still want it
[08:14] <tjaalton> some of them proprietary
[08:17] <bryce_> committed
[08:31] <bryce_> I ought to write an automatic script to reply to bugs with "randomly" in the subject ;-)
[08:35] <RAOF> Hm.  I think we should pull in the recent changes to libdrm/nouveau.  Does anyone have any particular comments or questions about this?
[08:37] <bryce_> RAOF, yes what are the recent changes?  Are they feature additions or bug fixes?  How well tested are the changes?  Are there specific bugs in launchpad that they are likely to resolve?
[08:41] <RAOF> So, it's difficult to say whether the changes are bugfix or new features.  There are things which certainly are bugfixes.  Fixing a memory leak, cleaning up typos.
[08:42] <bryce_> given that we're a week away from release, how comfortable are you with that uncertainty?
[08:43] <bryce_> (fwiw, I am struggling with -intel fixes that are *definitely* bug fixes, yet apparently cause regressions... aargh!)
[08:43]  * wgrant makes it 2.5 weeks, not 1.
[08:45] <RAOF> I'm not entirely sure; this depends on precisely what xserver-xorg-video-nouveau is doing in Jaunty.  If it's predominantly for testing, then I'd be uncomfortable with not shipping the changes; their lack definitely generates an error in the driver, but I'm not sure whether anything actually _hits_ that path.
[08:45] <bryce_> wgrant: well, post April 9th we shouldn't be making any changes
[08:45] <wgrant> bryce_: That's true.
[08:46]  * bryce_ s/release/end of development/
[08:47] <bryce_> wtf is up with wiki.ubuntu.com tonight?
[08:47] <wgrant> It's not very up.
[08:47] <bryce_> indeed
[08:47] <RAOF> Well, actually, I am sure that something hits that path; mesa.  DRI is definitely broken because we don't have the changes in libdrm-nouveau, but that's really neither here nor there.  I'm not sure whether anything _else_ hits it.
[08:48] <bryce_> RAOF: personally I consider it predominantly for testing, and will back you up 100% on that.
[08:49] <bryce_> RAOF: but ultimately it's up to you -- if the changes cause regressions you'll want to have a plan on if, and how to deal with them.  
[08:51] <RAOF> Worst case we can simply disable the patch.  That'll take things back to their current, apparently working fine, state.
[08:51]  * bryce_ nods
[08:51] <bryce_> make sure to solicit testing feedback in that case
[08:52] <bryce_> disabling patches pre-release is not too difficult, but post release can require a lot of annoying paperwork
[08:52] <RAOF> Right.
[08:54] <bryce_> fwiw, I'm really happy with -nouveau's state in jaunty, it is exceeding where I'd expected of it to be development-wise
[08:55] <bryce_> similarly with -ati.  I think our open source story on both nvidia and ati hardware is notable
[08:55] <RAOF> It's very nice that 2D is quite drama-free.
[08:55] <bryce_> Intel, however, is not meeting what I had anticipated in jaunty.
[08:56] <bryce_> but still there's time
[08:56] <RAOF> Intel has been somewhat of a problem child this release, hasn't it.
[08:56] <RAOF> Although that might also be due to lack of testing; we've only had... 6 bugs reported against the nouveau stack in total?
[08:56] <bryce_> could be
[08:56] <bryce_> certainly no shortage of bug reports against nvidia -180
[08:57] <bryce_> RAOF: I'd put a "we're not accepting bug reports against -nouveau" statement in the bug tracker for -nouvea at the start of jaunty
[08:57] <bryce_> that may be cutting down on bug reports a bit.  I should probably pull that out (assuming you're interested in bug reports)
[08:58] <RAOF> I'm moderately interested, but the bugs will be less and less interesting the older Jaunty's snapshot gets.
[08:59] <RAOF> I know that Jaunty's nouveau package has so far resulted in at least one bug being filed upstream and fixed, though.  So that's good :)
[09:00] <bryce_> ok
[09:00] <bryce_> my plan has been to pull that out once karmic opens, which is just a few weeks, so unless you're anxious for bug reports I'll stick to that plan
[09:00] <RAOF> I think that's a fine plan.
[09:01] <bryce_> ok kewl.  let me know if there's any specialized info beyond the norm you'd like included in nouveau bug reports
[09:01] <bryce_> most people don't read directions, but for those who do, we can tell them what to include
[09:02] <RAOF> Xorg.0.log, as always.  Also, and slightly more difficultly, dmesg with the drm module loaded with 'debug=1'.
[09:02] <bryce_> interesting; how do you load the drm module with debug=1 ?
[09:03] <RAOF> "modprobe drm debug=1"
[09:03] <RAOF> But you obviously have to do that outside of X, and preferably you want to do that before nouveau.ko has been loaded at all.
[09:03] <bryce_> right, hm
[09:04] <RAOF> So I tend to start in recovery mode, drop to a root terminal, modprobe, then continue the boot sequence.
[09:04] <bryce_> usually by the time they've gotten to the directions, they've already got their bug.  I'll need to think on where best to put that direction.
[09:05] <RAOF> That's obviously only useful if you can easily reproduce the bug; running with debug=1 results in everything being a bit slower, and dmesg being big :)
[09:05] <bryce_> are there disadvantages to running with debug=1 ? 
[09:05] <bryce_> oh okay
[09:05] <bryce_> maybe we need a 'how to debug nouveau' wiki page with this on it
[09:07] <RAOF> That's a fine idea.
[09:07]  * bryce_ switching machines...
[09:11] <bryce> mm
[09:11] <bryce> ^%$ broken wiki
[09:12] <bryce> ok, well, some day we should make a troubleshooting page for nouveau.  ;-)
[09:12] <RAOF> Once the wiki is up!
[09:29] <RAOF> OK.  libdrm is pushed to git.  I'll craft a call for testing.
[09:48] <tjaalton> bryce: a random stock reply for such bugs?-)
[09:53] <bryce> tjaalton: couldn't hurt
[10:48] <bryce> heya albert23
[10:49] <albert23> hi bryce
[10:51] <bryce> albert23: what's new
[10:55] <bryce> +?
[10:56] <albert23> bryce: not much yet. Weekend has started and going to do some performance testing on Kubuntu
[10:56] <albert23> That's a bit slow on 965
[10:56] <bryce> yes
[10:56] <bryce> everything is slow on all intel chipsets
[10:57] <bryce> (my fault I think)
[10:57] <jcristau> tjaalton: yes, possibly (re: rgb.txt)
[11:01] <albert23> bryce: actually, Gnome is doing fine on the 965
[11:02] <albert23> and the 945 is fine without gem as well
[11:03] <albert23> So I guess it's the whole gem newness that's hurting at the moment
[11:03] <mnemo> albert23: try open a fullscreen firefox window on each side of the cube in gnome and then spin the cube
[11:03] <mnemo> I think it
[11:03] <mnemo> s about how big the bitmaps are or something
[11:04]  * bryce waves to jcristau
[11:05] <mnemo> if I spin the cube with no programs active, it's really fast even in EXA but if I create lots of firefox windows then in becomes very slow.. so maybe kubuntu just uses the intel driver differently and thus runs straight into the perf problems
[11:08] <albert23> mnemo: indeed, 3 times firefox makes the spin slow
[11:08] <albert23> but Kubuntu already seems to be slower with just moving windows around
[11:08]  * bryce <-- passing out
[11:08] <bryce> night everyone.
[11:09] <albert23> good night
[11:12] <mnemo> night
[13:42] <Kano> hi, was it needed to change the order of the entries in the xorg.conf
[13:51] <cwillu> oooo, uxa is fast again on the latest kernel on 945
[13:53] <albert23> bug 349314
[13:54] <albert23> Fixes tiling issues and slowdown on i915 chipsets
[13:58] <cwillu> got the impression that was supposed to help exa though
[14:01] <cwillu> albert23, was that supposed to be fixing uxa or exa?  Uxa has good performance again, exa still has noticeably slower rendering on larger windows
[14:03] <albert23> cwillu: the change is in i915_gem_tiling, and gem is used by both exa and uxa
[14:03] <cwillu> ineffective on exa then
[14:05] <albert23> cwillu: with exa, do you still see tiling error messages in X log?
[14:05] <cwillu> yes
[14:05] <cwillu> http://pastebin.com/f4b9a0722 is uxa
[14:05] <cwillu> http://pastebin.com/f779fadfc is exa
[14:06] <cwillu> Failed to set tiling on front/back/depth buffer under exa
[14:07] <cwillu> There's also a warning:  (WW) intel(0): DRI2 requires EXA
[14:07] <cwillu> bah, UXA
[14:07] <albert23> uxa also fails on the front buffer
[14:07] <cwillu> yes
[14:08] <cwillu> uxa is fast for any size of window though
[14:08] <cwillu> like, night and day difference
[14:08] <albert23> good, so far it was only fast fro small windows for me
[14:08] <Kano> cwillu: rejected by kernel usually means that the drm from kernel is wrong, 11.40 is patched
[14:08] <cwillu> Kano, I'm running 11.40
[14:10] <Kano> well maybe the fix was only for another chipset
[14:10] <albert23> Jesse mentions he only tested on i915...
[14:52]  * albert23 has no luck with the new kernel. GLBlur full-screen and sauerbraten are still slow (amd64)
[14:57] <cwillu> I've never had blur be fast on a 945
[14:58] <albert23> It's fast for me with gem disabled
[15:00] <cwillu> wow, turning it on and off again just put performance through the floor, I'm getting .2 fps now
[15:00] <mnemo> how can I make an LP bug be open against both python2.6 and mesa? if I select "also affects project" I only see upstream mesa project
[15:00] <cwillu> even with blur redisabled
[15:00] <mnemo> its for this bug --> https://bugs.launchpad.net/ubuntu/+source/python2.6/+bug/355137
[15:00] <cwillu> mnemo, also affects distribution
[15:00] <mnemo> aah ok
[15:21] <cwillu> bryce, the boilerplate for "we need xorg.0.log and lspci" should probably include a note to remark the bug as confirmed or new
[15:34] <cwillu> ooo, ubuntu wiki is back up
[20:35] <bryce_> cwillu: in fact what I've been doing lately, is tag bugs "needs-lspci-vvnn" when asking for those files.  I'm working on a script that automatically reviews bugs with those tags, that have had the files subsequently provided by the original reporter, and then it moves the bug to Confirmed automatically
[20:36] <bryce_> cwillu: using a script to do it ensures some level of consistency, and simplifies things for the reporter a bit, since they can then just reply via email or whatever
[20:37] <bryce_> oh btw, I've got a processing script that runs against all bugs in New, and asks the user to attach stuff, etc.
[20:37] <bryce_> so take care not to put bugs into New state unless they do need to be re-processed by the script.  
[20:38] <bryce_> I've seen situations where the reporter kept putting the bug back to New, and getting a new automated response, repeat etc.
[20:40] <cwillu> yep, I've been marking them back to confirmed
[20:40] <cwillu> the first script re: needs-lspci-vvnn, is that running now?
[20:41] <cwillu> I've removed that tag from about 5-6 bugs that had the relevant details attached
[20:41] <bryce> cool
[20:41] <bryce> I run the scripts manually usually on Mondays
[20:41] <cwillu> you remember anything about 865's dri being disabled offhand?
[20:42] <bryce> I like to keep them supervised since I've been known to make coding goofs ;-)
[20:42] <cwillu> heh
[20:42] <bryce> yes, in fact it is intentionally disabled
[20:42] <cwillu> is there a particular api for scripting lauchpad, or are you just making normal http requests?
[20:42] <bryce> yes, the api is provided by 'launchpadlib'
[20:42] <cwillu> is there any hope for it being enabled?
[20:43] <cwillu> thanks, I'll look into that
[20:43] <bryce> https://help.launchpad.net/API/launchpadlib
[20:43] <bryce> yes, the original problem was that with DRI enabled, 865 would freeze during boot
[20:43] <cwillu> 845 et al?
[20:44] <bryce> we tried a number of different things to get it working but no dice, so ended up disabiling it
[20:44] <bryce> no, I disabled it only on 865
[20:44] <cwillu> hmm, xorg claims 845 and 865 have it disables
[20:44] <cwillu> s/disables/disabled/
[20:45] <cwillu> https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/355258
[20:45] <bryce> oh right
[20:46] <bryce> hmm, I think we don't need to disable it on 845; I could take that bit out of the patch
[20:46] <bryce> this is bug 304871 btw
[20:48] <cwillu> yes, I pulled one guy away from that report back to his on report on 865 on the same issue, marked it as fix released, and got him to file a new bug for the dri issue
[20:49] <cwillu> 343690 I believe
[20:50] <bryce> good
[20:50] <cwillu> http://pastebin.com/ff2e4278 is where I'm at
[20:51] <cwillu> Internally flagging each bug as either a hang/crash, display corruption/anomaly, or performace
[20:51] <bryce> nice
[20:51] <cwillu> I'm just working down the list of incomplete bugs from the bug day page
[20:52] <cwillu> once I've finished that pass, I'll make umbrella bugs for each class, link them all up, etc
[20:52] <bryce> yeah I've thought we could fix titles to include keywords (like I did with "(UXA bug)") to make them easier to group
[20:52] <bryce> excellent
[20:52] <cwillu> I've just been doing [i865] [UXA], etc
[20:52] <cwillu> plus tags, but ya
[20:53] <cwillu> wonder how easy it would be to have seperate 'packages' per chipset to report against
[20:53] <cwillu> I mean, I know they're all in theory -intel, but...
[20:54] <bryce> btw, there's some triaging graphs here - http://people.ubuntu.com/~bryce/Plots/
[20:54] <bryce> click on X, then -intel on the left
[20:55]  * cwillu looks at the dip in incomplete bugs at 12:00->20:00, and shouts "hey, that was me!" :)
[20:58] <cwillu> is there a magic syntax to write bug numbers in launchpad description so that they get linked up automatically?  If there is, I haven't tripped over it yet
[20:59] <bryce> :-)
[20:59] <bryce> "linked up"?  do you mean duped?
[20:59] <cwillu> no, just referenced
[21:00] <bryce> ah, yes if you say "bug NNNNN" it'll autolink them
[21:00] <bryce> "bug #NNNN" may work too
[21:01] <cwillu> I knew that.  Except for the last 4 hours
[21:01] <cwillu> anyways :p
[21:01] <bryce> I don't think creating separate packages for each chipset would be very feasible, but I've thought it would be nice to create a launchpadlib report that allows ordering and/or filtering by chipset (or tags in general)
[21:01] <bryce> hehe
[21:26] <cwillu> If I can get a few machines with 845/855/865 chipsets, would some sort of remote access test farm be useful?
[21:35] <mnemo> cwillu: I think the most useful resource would be a a server that everyone can PXE boot from into various configs for super easy bisection
[21:35] <mnemo> it would be like grub booting over network where you can choose like 2.6.28kernel+intel2.6.3+mesa7.4 etc
[21:36] <mnemo> using such a tool we could easily and conveniently bisect issues
[21:36] <mnemo> and find the patches we need to cherry pick
[21:36] <cwillu> kexec would make short work of that
[21:36] <mnemo> if one has to compile mesa,kernel,libdrm and intel ddx it's soo much work to bisect issues (also many people, like me, is not that good at fixing issues when stuff doesnt compile)
[21:37] <mnemo> ive not really been able to test upstream versions at all until I found xorg-edgers
[21:37] <mnemo> but know I've been able to file several good upstream bugs using xorg-edgers + mainline kernel
[21:38] <mnemo> and easy bisection is probably the _one_ thing I can imagine that could help us quickly backport cherry picks
[21:38] <mnemo> the idea is basically xorg-edgers but with history and bootable directly from network
[21:39] <mnemo> that would rock imo, heh
[21:39] <mnemo> but probably hard to build
[21:39]  * cwillu ponders
[21:39] <cwillu> I'd need a power supply that I can power-cycle over the network
[21:39] <cwillu> and maybe a webcam :p
[21:40] <mnemo> yeah
[21:40] <mnemo> also... then it would also be easy for us to ask bug reporters to "hey, go boot this blah blah versions and see when it broke plx"
[21:40] <mnemo> i mean if its really easy we can get help from more people
[21:40] <cwillu> but beyond that, it doesn't look completely infeasible
[21:40] <cwillu> biggest problem would be how to handle access to it
[21:40] <cwillu> I don't need to be providing an open proxy :p
[21:41] <cwillu> I'm intruiged :
[21:41] <cwillu> not intruiged enough to jump on it right now, but that's probably something useful that I can poke at post jaunty release
[21:42] <mnemo> yeah
[21:42]  * cwillu idly wonders how you spell intruiged anyway
[21:42] <cwillu> intrigued
[21:42] <cwillu> that's it
[21:49] <bryce> hehe
[21:50] <bryce> a test farm is a good idea. With X testing, there's a bit of a limitation in that a lot of bugs require you to sit in front of a real physical screen
[21:51] <bryce> also, for bugs where X locks up, if you're using the machine remotely, how do you restart it?  You'd need some sort of IPC or something
[21:51] <bryce> but... if we had a good plan, I'd totally be on board with it.
[21:51] <tjaalton> hmm, people on the bibblelabs forums claim that our nvidia packages are broken because they link libGL.so.1 against the nvidia library, when it should be the mesa version..
[21:52] <tjaalton> resulting that bibble5 doesn't start
[21:52] <tjaalton> "works on fedora"
[21:53] <bryce> mne|afk: in fact I've been working on a bisection page thingee (for just -intel and -ati, not mesa, xserver, etc. yet)
[21:53] <bryce> I've just had so much regular bug work to do, my progress has been slow.  But it's probably about a man-week from being usable
[21:55] <bryce> cwillu: fwiw, before I started working at Canonical, in my previous job I set up exactly such a remote, automated test harness, for doing NFS testing, called 'Crucible'
[21:56] <bryce> http://markmail.org/message/yii6s3okfiyqlx57
[21:58] <cwillu> biggest sticking point is how do you monitor the video:  I mean, one could just get a good big kvm with a monitor and a webcam, but that's pricy
[21:58] <bryce> yep
[21:58] <cwillu> otherwise you're stuck with only really being able to test crashers
[21:59] <bryce> I was actually fortunate in snapping up a kvm when my previoous company went belly up and auctioned everythign off :-)
[21:59] <cwillu> intels aren't discrete, so you can't just plop a bunch of them into one machine and select them via pci address or whatever
[21:59] <cwillu> (thinking out loud)
[21:59] <bryce> right
[21:59] <bryce> even with discrete cards, there's often only one slot on the mboard to stick them
[22:00] <bryce> and having >1 vidcard in a system can sometimes cause other kinds of problems... (something I've been testing actually...)
[22:00] <cwillu> well, that can be addressed with a good choice of machine to use in the first place
[22:00] <cwillu> although that still doesn't help with the 'capturing the output' problem
[22:00]  * bryce nods
[22:00] <cwillu> I miss my multiseats :)
[22:03] <cwillu> afk for a bit
[22:05] <mnemo> "With X testing, there's a bit of a limitation"
[22:06] <mnemo> thats the reason why I was thinking about PXE network booting
[22:06] <mnemo> so you get different versions of stuff but you can still only test _your_ hardware
[22:07] <mnemo> "With X testing, there's a bit of a limitation in that a lot of bugs require you to sit in front of a real physical screen"
[22:07] <mnemo> even
[22:11] <mnemo> hmm, now still is pretty aburd actually... http://portableubuntu.sourceforge.net/index.php?section=screenshots
[22:11] <mnemo> ubuntu for Windows ?
[22:44] <bryce> mnemo: ahh, gotcha, thought you meant pxe booting within a testing environment
[22:45] <bryce> er, _remote_ testing environment I mean
[23:10] <tjaalton> lp is quite responsive today..
[23:12]  * bryce waves
[23:12] <tjaalton> filing a FFe for wacom-tools
[23:12] <tjaalton> howdy
[23:16] <RAOF> tjaalton: Which LP are you using, and how can I get at it? :)
[23:16] <tjaalton> RAOF: edge, trying to be sarcastic ;)
[23:20] <RAOF> Oh.  Dissappointing!  I'd quite like to actually access my bugs, damnit!
[23:21] <maxb> edge is functional, if slow, which is more than can be said for release right now :-)
[23:30] <bryce> maxb?
[23:33] <maxb> main lp.net is completely down
[23:35] <bryce> ah
[23:36] <bryce> bugger, wonder what happened.  wiki was down last night too
[23:40] <tjaalton> seems to work now
[23:47] <RAOF> Bah!  People should restart their computers more often.
[23:49] <RAOF> Or at least not report bugs when they're running the 2.6.28-7 kernel but only have the 2.6.28-11 headers installed, and then install nouveau-kernel-source.
[23:54] <tjaalton> yeah, like my vdr box which has intrepid and 2.6.27-2, and dist-upgrade pulled in -11 which fails to boot :)
[23:55] <tjaalton> I should upgrade it to jaunty now that I have a keyboard which works on it
[23:56] <tjaalton> plugging the hd to another machine just to edit menu.lst isn't much fun