[08:25] <superm1> apw, if you get that kernel that jbarnes was looking for yesterday built some time this morning, can you ping me?  I'd like to see that it fixes the problems that we found yesterday
[08:25] <apw> superm1, eep.  remind me what he was looking for
[08:27] <apw> i am building so many things for so many people ...
 10:44:46> -http://git.kernel.org/?p=linux/kernel/git/anholt/drm-intel.git;a=commit;h=07f4f3e8a24138ca2f3650723d670df25687cd05
 10:45:06> -apw: can we get a kernel with that patch (actually a drm-intel based kernel would be even better)
[08:44] <apw> jbarnes, about?
[08:56]  * Ng shakes fist at X. Stop crashing!
[08:59] <Ng> I don't sem to get any log indication that it's doing it though, I would have expected a segfault syslog
[09:02] <apw> superm1, 32 or 64 better for you?
[09:29] <superm1> apw, 32 
[09:29] <superm1> apw, i dont think atom's do 64..
[11:11] <bryce_> jbarnes_BCN: http://tinyurl.com/l7zw8u
[11:38] <apw> jbarnes_BCN, superm1, latest karmic kernel with the patch you requested up: http://people.ubuntu.com/~apw/jbarnes-karmic/
[11:40] <superm1> thanks apw, grabbing right now
[11:55] <superm1> jbarnes, apw unfortunately that kernel still does have the resume problem wrg to random corruption when KMS is enabled
[11:58] <superm1> adding on xorg-edgers right now to pair with it
[13:26] <jbarnes_BCN> commit 13f4c435ebf2a7c150ffa714f3b23b8e4e8cb42f
[13:26] <jbarnes_BCN> Author: Eric Anholt <eric@anholt.net>
[13:26] <jbarnes_BCN> Date:   Tue May 12 15:27:36 2009 -0700
[13:26] <jbarnes_BCN>     drm/i915: Don't allow binding objects into the last page of the aperture.
[14:06] <superm1> jbarnes_BCN, did you see my ping before, I sent it to jbarnes. not sure if that's a local session back in californida
[14:06] <superm1> california even
[14:06] <jbarnes_BCN> heh
[14:06] <jbarnes_BCN> no I missed it
[14:06] <superm1> 29-05-2009 05:55:37 > superm1: jbarnes, apw unfortunately that kernel still does have the resume problem wrg to random corruption when KMS is enabled
[14:06] <superm1> 29-05-2009 05:58:22 > superm1: adding on xorg-edgers right now to pair with it
[14:06] <jbarnes_BCN> been off & on... had to completely reschedule my travel for the next couple of weeks
[14:06] <superm1> ah
[14:06] <jbarnes_BCN> superm1: arg ok
[14:06] <superm1> i added xorg-edgers as well, same thing
[14:07] <superm1> so i'm on a fully updated karmic + whatever is currently on edgers for karmic's ppa
[14:08] <jbarnes_BCN> I think we need a gpu dump (did we get one yet?) and a copy of the rest of the contents of debug/dri/0
[14:08] <superm1> i dont think we got a gpu dump yet
[14:11] <superm1> can you grab it from wifi again since i've not got console access while it's in crazy state?
[14:11] <superm1> although i wonder if my wifi comes up at that point post resume
[14:12] <jbarnes_BCN> yeah we can get it from ssh
[14:12] <superm1> where ya at?  i'll come to you
[14:12] <jbarnes_BCN> the couch by sala b3
[14:13] <jbarnes_BCN> at the end of the hall
[14:13] <superm1> k, ill come in a few min, just need to send an email
[14:16] <bryce__> jbarnes_BCN: http://tinyurl.com/l3netq
[14:49] <bryce__> 100 papercuts:  https://wiki.ubuntu.com/LittleDetails
[14:58] <seb128> bryce__: isn't that session starting in 16 minutes ?
[15:56] <tseliot2> jbarnes: ping
[15:56] <tseliot2> or bryce
[18:03] <Spec> Heya...if I want to rebuild (with pbuilder) the xserver-xorg-core package without a specific patch, can I just apt-get source the package, delete the patch, and build it?
[18:05] <Sarvatt> comment it out from debian/patches/series
[18:05] <Spec> i hope i'm not shooting myself in the foot :), thanks.
[18:06] <Sarvatt> which patch?
[18:09] <Spec> Sarvatt: 169_mipointer_nullptr_checks.patch
[18:09] <Spec> I'm wondering if the patch caused an issue I'm seeing now, or if it's just logging the issue and the "workaround" implemented with it doesn't actually solve the problem
[18:10] <Spec> (but it does solve a moar important problem....i just wanna test.)
[18:11] <Spec> I might also remove 166_nullptr_xinerama_keyrepeat.patch
[18:13] <jcristau> what's the problem?
[18:14] <Spec> BUG #324465
[18:14] <Spec> err, no bot?
[18:14] <Spec> wait, sorry, that's a different bug that got fixed
[18:14] <Spec> current bug is BUG #363375
[18:15] <Spec> the mouse "loops" on my fourth monitor sometimes, and I get a lot of error messages in X.org's logfile
[18:43] <Spec> so...the results of the pbuilder are a bunch of .deb files (xdmx, xdmx-tools, xnest, xserver-stuff, xvfb, etc), should I install all of them?
[18:43] <Spec> and to revert dpkg --purge/reinstall w/ apt-get?
[18:44] <jcristau> Spec: just xserver-xorg-core (and -dbg if you want to debug)
[18:45] <Spec> don't know how to debug ;)
[18:45] <Spec> i'll do this later tough, thanks for the help.
[19:53] <Sarvatt> Spec easiest way is to add all your debs to a folder, cd to it and run sudo dpkg-scanpackages . /dev/null | gzip -9c > Packages.gz  and add deb file:/opt/debs/ / to your /etc/apt/sources/list replacing /opt/debs/ with what you picked
[19:53] <Sarvatt> err sorry ignore the >/dev/null, i pasted from my crontab :D
[19:54] <maxb> That is overkill for a single source-package build
[19:54] <maxb> Merely use "sudo debi --upgrade"
[20:13] <Spec> what's wrong with dpkg -i? :p
[20:44] <Ng> hrm, starting to see some rendering corruption after a day or so of the KMS kernel on jaunty with 2.7.1
[20:47] <Ng> now starting to see quite a lot of corruption on widgets
[20:49] <bryce_> hrm
[20:50] <bryce_> Spec: dpkg -i is fine, that's what I always use :-)
[20:50] <bryce_> Ng: hrm
[20:51] <bryce_> Ng: well, 2.7.99.1* is in xorg-edgers and a lot of people are having success running that
[20:51] <bryce_> Ng: is this with compiz?
[20:51] <Ng> yeah
[20:51] <Ng> I'll switch up to edgers I guess :)
[20:58] <Sarvatt> need a kernel upgrade Ng :)
[20:59] <Sarvatt> http://people.ubuntu.com/~apw/jbarnes-karmic/
[21:00] <Sarvatt> was just merged today but that fixes the swap related corruption
[21:01] <Sarvatt> http://anholt.livejournal.com/41132.html
[21:01] <hyperair> ooh cool
[21:03] <Ng> nice
[21:03] <Sarvatt> didnt help theres a big memory leak with 3d compositing enabled making you swap more either
[21:07] <Ng> I have 3GB, I didn't notice any swapping
[21:11] <hyperair> Sarvatt: i noticed that it reduced when i turned on KMS
[21:11] <hyperair> strange eh..
[21:11] <hyperair> i've been able to last up to ~12 hours now without having to restart X
[21:13] <Sarvatt> oh  ya couldn't before? i havent done UXA without KMS in a long time, it was taking about 24 hours before i had to restart when i had compiz on with 1.5gb ram but I guess it all depends on how much you actually do during that time :D
[21:14] <Sarvatt> i just switched to metacity compositing for now till its fixed
[21:14] <hyperair> Sarvatt: not that i couldn't, more like i didn't know how to.
[21:14] <hyperair> then  the email came in the other day to -devel
[21:14] <Sarvatt> 241MB gem obect bytes 241MB gtt bytes right now after 3 days uptime
[21:15] <hyperair> eh that's pretty awesome.
[21:15] <hyperair> so metacity's compositing is better than compiz's huh
[21:15] <hyperair> as in it doesn't leak like crazy
[21:15] <Sarvatt> anholt was saying it was GL compositing doing it in that blog post i linked
[21:16] <hyperair> 833M gem object bytes here, 794M gtt bytes
[21:16] <hyperair> no wait
[21:16] <hyperair> 79M gtt bytes
[21:16] <Sarvatt> your aperture is that big?!
[21:16] <hyperair> 1323610112 object bytes
[21:16] <Sarvatt> ahh
[21:16] <hyperair> 79474688 gtt bytes
[21:21]  * Ng reboots into the new kernel and the various -edgers bits
[21:23] <Sarvatt> hyperair, did you try earlier drivers out to see if theres a problem there too? to  be honest i didn't notice the leak until around may 15th (i have 1.5gb ram and dont use swap so it hit hard) and i havent tried earlier drivers out yet since its easier to disable compiz instead of losing all of the bug fixes in the newer drivers
[21:32] <Sarvatt> hyperair: by oh ya couldnt before I meant I didnt know it was worse without KMS, sorry
[21:39] <hyperair> Sarvatt: -2.4 doesn't have it.
[21:39] <hyperair> Sarvatt: i'm pretty sure i didn't see it with 2.5
[21:39] <Sarvatt> wonder if i should up mesa on jaunty in xorg-edgers to 7.6, the fix for 3d rendering on 8xx is only in master
[21:39] <hyperair> though i may be wrong
[21:39] <Sarvatt> oh i meant 2.7 or newer
[21:39] <hyperair> i used that very briefly
[21:40] <hyperair> oh
[21:40] <Sarvatt> 2.7 or 2.7.1
[21:40] <hyperair> everything 2.7 and up has it
[21:40] <hyperair> 2.7.0 had it
[21:40] <hyperair> definitely
[21:40] <hyperair> and 2.7.1
[21:40] <hyperair> and the current master
[21:40] <hyperair> all without KMS
[21:40] <Sarvatt> gotcha, i only used EXA on 2.7.0 and 2.7.1 because its so much faster
[21:40] <hyperair> by current master i meant xorg-edgers' one
[21:40] <hyperair> EXA is faster?
[21:40] <hyperair> O_o
[21:41] <Sarvatt> http://global.phoronix-test-suite.com/index.php?k=profile&u=robert-15508-6884-16319
[21:41] <hyperair> i didn't really experiment with EXA on those, but i'm pretty sure that EXA had the memory leak too
[21:41] <Sarvatt> the 05-09 ones are with driver 2.7.1 even though it says 2.7.0
[21:42] <hyperair> i see.
[21:43] <hyperair> anholt seemed willing to fix it, but only if we can find a minimal test case
[21:43] <hyperair> =\
[21:43] <Sarvatt> someone posted one that works for me, the loop opening and killing firefox
[21:43] <hyperair> is it?
[21:43] <hyperair> hmm
[21:43] <Sarvatt> on the bug report, he saw it
[21:43] <hyperair> i see
[21:44] <hyperair> i actually have a patched drm which disables BO caching
[21:44] <hyperair> took the one from your PPA and patched the figure from 14 to 0
[21:44] <hyperair> some #define there
[21:44] <hyperair> that one lets the memory drop a little if you close firefox