[15:30] <Sarvatt> if anyone's using fglrx or nvidia with xorg-edgers let me know if you have any problems after 1.9.2.901+git20101129+server-1.9-branch.65f2ab20-0ubuntu0sarvatt2, finally got around to testing the autoconfiguration of nvidia and fglrx stuff so they work without an xorg.conf and haven't had any problems with it so I threw it in there
[15:46] <tseliot> nice
[15:47] <apw> Sarvatt, whats the correct package to file an X bug against the intel driver specifically ??
[15:47]  * apw discovers there are far too many for launchpad to tell me
[15:48] <tseliot> xserver-xorg-video-intel?
[15:48] <Sarvatt> apw: xorg or xserver-xorg-video-intel
[15:48] <tseliot> apw:  at least for the ddx driver
[15:48] <Sarvatt> tseliot: in case you're interested, http://sarvatt.com/downloads/patches/105_nvidia_fglrx_autodetect.patch
[15:49] <tseliot> Sarvatt: I was about to ask. Thanks
[15:52] <Sarvatt> http://pastebin.com/t0TSk2Lv
[15:54] <tseliot> Sarvatt: very good :)
[16:07] <apw> bryceh, that bug is getting worse it seems:  bug# 682712
[16:07] <apw> bug# 682712 even
[16:07] <apw> bug #682712 even
[16:08] <ubot4`> Launchpad bug 682712 in xserver-xorg-video-intel (Ubuntu) (and 1 other project) "x server crashes with: [drm:i915_gem_mmap_gtt_ioctl] *ERROR* Attempting to mmap a purgeable buffer (affects: 1) (heat: 8)" [Undecided,New] https://launchpad.net/bugs/682712
[16:09] <Sarvatt> i've been following that one for about a month now on the intel-gfx list but haven't seen any updates on a real fix
[16:15] <tseliot> Sarvatt: is there an upstream report about it?
[16:16] <Sarvatt> mentioned it in the bug, https://bugzilla.kernel.org/show_bug.cgi?id=22652
[16:16] <ubot4`> bugzilla.kernel.org bug 22652 in Video(DRI - Intel) "[drm:i915_gem_mmap_gtt_ioctl] *ERROR* Attempting to mmap a purgeable buffer" [Normal,New]
[16:16] <tseliot> refreshing the page helped ;)
[16:20] <tseliot> apw: can you bisect the DDX code?
[16:20] <apw> tseliot, i can't say i've ever done that so i have no idea how to build it
[16:20] <apw> tseliot, but i with proper instruction i am willing
[16:20] <Sarvatt> apw: this return anything intel related? sudo grep -r Assertion /var/log/gdm/
[16:20] <apw> its had me 3 times in the last 10 minutes
[16:20] <tseliot> it would be nice to be able to pin down the problem to a specific commit (or to a set of commits)
[16:21] <apw> though i think once it has happened once we are in looser space
[16:21] <apw> Sarvatt, nothing from that at all
[16:22] <tseliot> apw: https://wiki.ubuntu.com/X/Bisecting
[16:24] <tseliot> apw: I guess you can use the debian directory from the package in edgers if you're using -intel from git
[16:24] <tseliot> Sarvatt should know more about this since he runs edgers
[16:24] <apw> i have stock maverick on there userspace wise
[16:38] <tseliot> apw: right but I don't think the ubuntu package is maintained in a git repository
[16:39] <apw> oh hrm, not making it easy are they
[16:43] <Sarvatt> apw: if you don't want to start with the full xorg-edgers to see if it still happens I copied the important parts here https://launchpad.net/~sarvatt/+archive/apw (x-x-v-intel will take awhile to build, just uploaded)
[16:43] <Sarvatt> intel is maintained in git.. http://git.debian.org/?p=pkg-xorg/driver/xserver-xorg-video-intel.git;a=shortlog;h=refs/heads/ubuntu
[16:47] <Sarvatt> been trying my hardest to reproduce it but can't manage to
[16:57] <tseliot> Sarvatt: my bad, I relied on what's in the wiki
[16:58] <tseliot> apw: the ubuntu git branch ^^
[16:59] <apw> Sarvatt, was there a recent xorg update ?
[16:59] <apw> (for maverick)
[17:00] <apw> cause things just got a whole heap worse
[17:03] <apw> can anyone point me to the right source package name for the xserver, these binary packagenames seem to have no relation
[17:03] <jcristau> xorg-server
[17:03] <Sarvatt> yeah there was a xinerama fix but it shouldn't affect your single head intel setup, people are still having that crash you're getting on xserver 1.7.x
[17:04] <apw> this is going to be a pain in the ass
[22:14] <cnd> bryceh, RAOF: with the X server merge window about to close, do you have any thoughts on 1.9 or 1.10 for natty?
[22:14] <cnd> or is it still too soon to tell
[22:15] <RAOF> Nothing likely to cause the atmosphere to combust seems to have landed; I'm leaning 1.10
[22:52] <bryceh> I'm okay with doing 1.10
[22:52] <bryceh> 1.9 is proving to be a bit too stable
[22:53] <bryceh> ;-)
[22:55] <Sarvatt> if we aren't getting xinput 2.1 in 1.10 I think I'd prefer 1.9.x here
[22:55]  * Sarvatt ducks
[22:55] <bryceh> (well, aside from apw's bug)
[22:55] <Sarvatt> "the kernel doesn't break userspace" my butt
[22:56] <bryceh> heh
[22:57] <bryceh> Sarvatt, I notice the links you posted were from last month
[22:57] <Sarvatt> yeah saw that bug when it first started rolling in from drm-intel-next
[22:58] <Sarvatt> I can't for the life of my reproduce it with git x-x-v-intel libdrm and mesa
[22:58] <bryceh> Sarvatt, think it is an incompatibility between the natty kernel and maverick userspace?  Or think it'd still occur with natty userspace too?
[22:59] <Sarvatt> can't reproduce it with natty userspace either
[22:59] <bryceh> x86_64 specific maybe?
[23:02] <bryceh> 8086:2a42 is gm45 right?
[23:02] <RAOF> Yes.
[23:03] <RAOF> Good old 2a42 :)
[23:03] <Sarvatt> yeah, was reported on a 945GM too
[23:03] <bryceh> I dunno if it's good or bad that I recognize cards by pciids...  :-/
[23:03] <bryceh> was the other report also x86_64 by chance?
[23:04] <Sarvatt> for 2a42 it's not bad, so many bugs specific to that :)
[23:04] <Sarvatt> looked but can't tell from the logs posted
[23:09] <bryceh> Sarvatt, http://www.serverphorums.com/read.php?12,224683
[23:11] <Sarvatt> ohhh tricksy apw
[23:11] <Sarvatt> xorg-server 2:1.7.6-2ubuntu7.4 (For technical support please see http://www.ubuntu.com/support) 
[23:12] <Sarvatt> thats not maverick :)
[23:12] <Sarvatt> (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
[23:12] <Sarvatt> (II) Module intel: vendor="X.Org Foundation"
[23:12] <Sarvatt> 	compiled for 1.7.6, module version = 2.9.1
[23:12] <bryceh> ahh
[23:13] <bryceh> still... even that combination shouldn't be throwing this bug
[23:13] <bryceh> but yeah would be nice if apw could reproduce it on pure natty
[23:13] <Sarvatt> I went and made him a maverick ppa to test newer stuff, whoops
[23:17] <Sarvatt> that opens up a world of dupes, Failed to submit batchbuffer: Invalid argument was a common error with 2.9.1. was wondering why there was no apport crash report there but it being lucid would make sense
[23:18]  * bryceh nods