/srv/irclogs.ubuntu.com/2010/03/09/#ubuntu-x.txt

Sarvattsudo tune2fs -C 200 /dev/sdax to force a fsck00:00
rye[fixing-x]Sarvatt, the initrd archive contains regular file, hm...00:01
* rye[fixing-x] has not enough knowledge about the boot process00:01
Sarvattlooks like it uses the ones in / by the time it tries to load the video driver from that bugs dmesg and it just packs all the modprobe.d confs in incase any of them are relevant early00:06
RAOFSo, just a regular reboot worked fine.00:06
RAOFI'll force a fsck.00:07
BUGabundogreat00:08
BUGabundogoing to a tty, closed my gdm and session :(00:08
BUGabundoany logs you guys might find useful ?00:09
Sarvattrye[fixing-x]: was that bug i linked earlier yours?00:10
* Sarvatt cant load launchpad00:10
rye[fixing-x]Sarvatt, erm... what bug? The one with backlight - yes, that was mine, bug 534469 is not mine, but I have the same symptom, I suppose00:12
ubottuLaunchpad bug 534469 in nvidia-graphics-drivers "Failed to load NVIDIA 195.36.08 kernel modules because nouveau is loading." [Undecided,New] https://launchpad.net/bugs/53446900:12
Sarvattah ok00:12
RAOFOk.  And booting with a fsck still works.00:12
rye[fixing-x]Sarvatt, subscribed to it...00:12
RAOFSo, it looks like this is only an issue for those with /usr on a separate partition?  In which case, I'm back to f-spot hacking.00:13
* rye[fixing-x] wants to drop separate partitions, since he has issues with mounted, ureadahead and now with X due to separating of /usr and /var...00:13
BUGabundoSarvatt: RAOF: you guys want my xorg logs? would be nice to see this not happen again :(00:15
RAOFBUGabundo: Feel free to file a bug with “ubuntu-bug xorg”; that'll attach everything we'd like, and I go through the nouveau bugs frequently.00:16
BUGabundoblob00:16
BUGabundo"Please wait while bug data is processed. This page will refresh every 10 seconds until processing is complete." ??00:18
rye[fixing-x]Sarvatt, should I as bug £534469 about separate /usr or you will do that?00:18
rye[fixing-x]awesome, GBr layout makes me mad00:18
rye[fixing-x]Sarvatt, bug #53446900:19
ubottuLaunchpad bug 534469 in nvidia-graphics-drivers "Failed to load NVIDIA 195.36.08 kernel modules because nouveau is loading." [Undecided,New] https://launchpad.net/bugs/53446900:19
BUGabundohttps://bugs.edge.launchpad.net/ubuntu/+source/xorg/+bug/53475500:20
ubottuLaunchpad bug 534755 in xorg "gdm/session killed when jumping to TTY" [Undecided,New]00:20
BUGabundoRAOF: ^^^00:21
=== rye[fixing-x] is now known as rye
ryeok, it is now 2:26 AM here, so I go offline. Will ask OP about separate /usr in case nobody else does in the morning00:26
ryegood luck and thanks for the help with troubleshooting00:27
Sarvattsorry, in the middle of a bunch of other troubleshooting at the moment, will take a look at it in a bit00:35
Sarvattgot an interesting crash resuming with the blob - http://pastebin.com/Ptqia4fi00:36
Sarvattno problem with the blob after 6 boots here, glad its not as bad as it could have been :)00:49
RAOFSarvatt: Yeah.00:51
RAOFI didn't particularly want to do any nvidia firefighting today :)00:51
Sarvattmaybe we need our systems to boot in 15 seconds like the bug reporter to reproduce :)00:53
Sarvatthmm looks like BUGabundo got the same X segfault resuming with the blob as I did in one of his old logs - http://launchpadlibrarian.net/40541663/GdmLog2.txt01:21
bjsnidernvidia released an update to the nv driver02:58
bjsniderthey added gem, gallium, dri2, vdpau, and full support for all hardware reaching back over 10 years02:59
superm1haha03:00
bjsniderok, maybe not03:01
bjsniderthey added ion support after their usual 5 minutes of work03:01
brycehtjaalton, btw notice some pending stuff for xorg in git; is there a reason this isn't uploaded yet?03:08
brycehtjaalton, and if not, shall I upload it? (I've a fix for apport I'd like to roll out)03:09
Sarvattapw: unfortunately the i915 powersave=0 module option is still needed on my netbook so dont be surprised if you hang after resume with -1603:16
Sarvattthe plus side is it no longer flickers constantly with powersave=1 after resume, but it still eventually hangs to a solid color until I suspend/resume again03:16
Sarvatti'm not sure what's up with xorg, tjaalton was pinging you a few days ago saying you needed to import an older release before uploading it I think?03:19
Sarvatt[14:40] <tjaalton> bryceh: expect a yet-another merge clash with xorg, since you didn't push the changes :)03:24
Sarvatt[14:41] <tjaalton> just the changelog though, as usual03:24
Sarvatt[15:46] <tjaalton> hm, need to merge xorg since xorg-dev is uninstallable03:24
brycehyeah pretty sure I fixed that03:24
brycehSarvatt, still unclear why the git tree isn't pushed... was there an issue with it?03:28
brycehs/pushed/uploaded/03:28
Sarvattchecking it out now, had a few problems03:42
Sarvatthmm03:59
Sarvattlooks like your failsafe translation stuff got zapped03:59
Sarvattthink thats what tjaalton was talking about04:00
Sarvattxgettext -f debian/po-failsafe/POTFILES.in -d failsafexinit -o debian/po-failsafe/failsafexinit.pot -L Shell04:01
Sarvattxgettext: error while opening "debian/po-failsafe/POTFILES.in" for reading: No such file or directory04:01
Sarvattbryceh: xorg git should be all fixed up now04:05
Sarvattforgot to git add the internationalization file before commiting04:07
Sarvattoops, would help if i remembered to enter my pass to push that last one :) now its fixed04:08
tjaaltonSarvatt: the Vcs* tags were removed from debian05:09
tjaaltonand Standards-Version is in the wrong place :)05:10
tjaaltonbryceh: other than that it's good to go, I was just waiting for other potential fixes05:11
tjaaltonhmm, it never had any Vcs tags in debian05:18
tjaaltonso if they were added by us, then ok05:18
tjaaltonoh yeah, 2009-11-05 Bryce Harrington Add Vcs tags05:20
Sarvattahh sorry, thanks for fixing it05:41
Sarvatt4 hour queue for the fixed up linux-backports-modules in edgers :(05:42
RAOF:(  There goes my quick PPA build of f-spot.05:53
Sarvattanyone else's trackpads get laggy today?05:55
RAOFNot mine.05:56
Sarvattugh, maybe it was the -intel update05:56
RAOFLet me flick the stupid switch on my nvidia/intel netbook and check :)05:57
RAOFMy (now intel) netbook doesn't know anything about laggy trackpads.06:03
RAOFBah!  Stupid IA32-only atom processors.  Who produces a chip that only supports such a register starved, ancient ISA anyway!06:08
tjaaltonsuperm1: before I file a bug, do you know why dkms fails to build nvidia when invoked via dpkg-reconfigure, but succeeds when I put the make command in a script?08:28
superm1tjaalton, did it fail on first install too?08:28
tjaaltonthe error is "make[1]: Makefile: No such file or directory"08:28
superm1and are you seeing this on lucid or karmic?08:28
tjaaltonboth actually, but now using only lucid08:29
superm1on karmic i'd expect it was caused by a permissions problem08:29
superm1but on lucid everything should be owned by root:root08:29
tjaaltonit succeeds when the package is installed via preseeding pkgsel/include08:29
tjaaltonor at least I think it does08:30
superm1well that sounds a bit bizarre then08:30
tjaaltonhum no, it wasn't installed like that08:30
tjaalton"make module" does create the Makefile when run by hand or via the script08:31
tjaaltonbut not the dkms way08:31
superm1so it sounds like something is wrong in the dkms.conf then for this nvidia driver08:31
superm1although i would expect to be hearing a lot more about this then08:32
superm1you don't already have a Makefile in /usr/src/nvidia-current-195.36.08$  ?08:33
tjaaltonyes, but it's cleaned away08:33
tjaaltonwhen the dir is copied to /var08:33
tjaaltonrunning make creates a symlink to Makefile.kbuild08:34
tjaaltonmake clean removes the file/symlink08:35
superm1why would Makefile be cleaned when the dir is copied over though?08:35
tjaaltonI'll pastebin the shell debug output08:36
tjaaltonadded 'set -x' to dkms08:36
tjaaltonit does run make clean there08:36
superm1but i dont see anything in the clean rule for the Makefile that deletes itself08:37
tjaaltonbut it's in makefile08:39
superm1oh i see08:39
tjaaltonhttp://pastebin.ubuntu.com/391587/08:39
tjaaltonso it copies the source and then cleans it :)08:40
tjaaltonlines 994-101208:41
superm1still sounds to me like a bug in the way the nvidia source is doing it08:41
superm1running clean should be safe08:41
superm1but i'm baffled still why this would work during the first install then08:42
tjaaltonyep08:42
tjaaltonwell it didn't, was wrong about that08:42
superm1i've got installs here that it has worked on first install and on upgrades though08:42
superm1speaking of which, i just did an install of the -16 kernel on a system with nvidia right now, and it DTRT08:44
superm1let apport file the bug for you on the failure and attach that set -x run to dkms to the bug too08:45
tjaaltonthis is a slightly modified environment, apport isn't useful there.08:49
superm1well then attach everything it would have attached08:51
tjaaltonok I will08:54
superm1http://paste.ubuntu.com/391604/ yeah, it def still WFM08:57
tjaaltonsuperm1: could you get the same output of it (set -x), so I could compare them?09:03
superm1tjaalton, in /usr/sbin/dkms?09:04
tjaaltonsuperm1: yep09:04
superm1http://pastebin.com/Mf6AC8iY tjaalton 09:06
tjaaltonhrm, I did a rollback of all the custom settings and reinstalled the package, and it built fine09:07
superm1oh dang, that didnt capture it09:07
tjaaltonI can't think of anything that would conflict with this though09:07
tjaaltonthere's only one make etc09:07
superm1what were you customizing?09:07
tjaaltonwell some shell settings might have something to do with it09:08
tjaaltonthere are lots of changed configs etc, for the uni environment09:08
tjaaltonor perhaps just that I logged in from the console, and not via sudo09:08
superm1its quite possible that some variables need to be unset for DKMS that aren't being unset then09:09
tjaaltonhmm I can get the output here09:09
superm1it wouldnt be the first bug that came up from an unsanitary environment at least09:09
tjaaltonok, I'll dig something out of this :)09:11
tjaaltonnoticed that there are a bunch of variables being unset in dkms09:11
superm1yeah, quite possible there needs to be more unset09:12
tjaaltonthough why does it succeed when run by hand, hmm..09:12
tjaaltonanyway, thanks so far09:12
tjaaltonsuperm1: found it, unsetting ARCH made it work10:58
tjaaltondon't know why we set that10:59
bdrunghas someone time to sponsor bug #534026?11:07
ubottuLaunchpad bug 534026 in xserver-xorg-video-ati "Please merge xserver-xorg-video-ati 1:6.12.191-1 (main) from Debian experimental (main)." [Undecided,Confirmed] https://launchpad.net/bugs/53402611:07
tjaaltonwe are past FF, so it probably needs an exception11:07
tjaaltonoh it's approved already11:08
tjaaltonhe11:08
tjaalton*eh11:08
tjaaltondon't change the packaging11:08
tjaaltoncheck how other packages enable the patchsystem11:10
tjaaltonsynaptics for instance, they all are basically the same11:10
jcristaudebian/README.source should have explanations how to enable the patch system11:11
tjaaltonright11:12
bdrungdebian/README.source is not very helpful. the debian maintainers remove all quilt invocation from their rule file.11:19
bdrungi know, that we shouldn't change the packaging, but in my opinion using 3.0 (quilt) is better than hacking debian/rules. the debian maintainers prefer quilt. So this is not the issue.11:21
bdrungtjaalton: ^11:21
tjaaltonbdrung: I don't understand... debian/rules already had everything set up for patching11:24
tjaaltonchanging the source package format is way bigger than keeping the rules diff11:25
bdrungtjaalton: http://launchpadlibrarian.net/40489726/xserver-xorg-video-ati_6.12.191-1ubuntu1-v2.patch11:25
tjaaltonwell, philosophically anyway :)11:26
bdrungyes11:28
bdrungtjaalton: i can convert the debdiff if you insist on not using 3.0 (quilt)11:28
jcristau3.0 (quilt) is unusable11:34
tjaaltonbdrung: perhaps wait until bryceh chimes in11:34
jcristaubdrung: enabling the patch system is not "hacking debian/rules", and it's 2 lines in the debdiff instead of a complete revamp of the package11:35
bdrung_tjaalton, jcristau: i updated the patch for bug #534026 to make you happy. ;)13:41
ubottuLaunchpad bug 534026 in xserver-xorg-video-ati "Please merge xserver-xorg-video-ati 1:6.12.191-1 (main) from Debian experimental (main)." [Undecided,Confirmed] https://launchpad.net/bugs/53402613:41
jcristaubdrung_: ta13:51
bdrung_jcristau: ta?13:52
jcristauthank you13:52
bdrung_jcristau: for what does the a stand in ta?13:55
jcristauhttp://www.urbandictionary.com/define.php?term=TA :)13:56
bdrung_interesting13:59
tjaaltonbdrung_: thanks, replied14:04
bdrung_tjaalton: thanks. what does the ACK mean? wouldn't uploading it instead of acknowledging it the right thing to do?14:07
tjaaltonbdrung_: I'd like to hear what bryceh thinks14:09
superm1tjaalton, okay file a DKMS bug to add it to the unset list too then15:04
tjaaltonsuperm1: done, bug 53498615:07
ubottuLaunchpad bug 534986 in dkms "please unset ARCH in /usr/sbin/dkms" [Undecided,New] https://launchpad.net/bugs/53498615:07
=== seb128_ is now known as seb128
apwbryceh, does switching away from and back to VT-7 work for you with an updated system?17:58
apwactually scratch that, bryceh does your X end up on VT-8 now?17:59
* apw has a drm:drm_mode_getfb error on VT-7, and X is on 8 ... oddness17:59
brycehapw, what's odd is I do have some systems on VT8, and others on VT718:01
brycehit's not consistent18:01
apwand now i have the feeling something odd happened during boot ... somethign i'd not twigged about18:02
brycehalso I do see a myriad number of issues related to vt switching18:02
brycehprobably all unrelated18:02
apwi got a modeset between plymouth and gdm which i shouldn't18:02
apwi suspect it started on 7 blew up, and restarted on 818:02
brycehI had a system where vt switching did not work at all, because plymouth was not installed; after installing it, it worked again18:02
apwwibble18:03
brycehapw, there seem to be a set of pretty severe interactions between plymouth and X18:03
brycehesp. related to vt switching - see the bugs filed in the plymouth bug tracker18:03
apwvery strange, i presume keybuk is looking at plymouth at the mo18:03
superm1and i assume it's those same interactions to blame for why enter is killing X sometimes?18:04
apwsuperm1, i am starting to feel its when you don't have KMS you get that behaviour18:04
apwthat always first return fecks you18:04
apwbut i've not done any sort of repeated test to confirm18:05
superm1apw, i've had it happen with KMS working18:05
superm1well "working"18:05
apwits perfect, wonderful, you cannot see any issues18:05
brycehsuperm1, that's right18:05
superm1i have problems where the second monitor doesn't work once X starts18:05
brycehsuperm1, bug 53204718:05
ubottuLaunchpad bug 532047 in plymouth "Plymouth text-mode splash causes X to crash on first run due to shared tty7" [High,In progress] https://launchpad.net/bugs/53204718:05
apwsuperm1, which version have you tested kernel wise18:05
superm1apw, -15 and the -16 that just hit the archive18:06
superm1i just updated hardy->lucid the other day18:06
apwso -16 is as bad, boo18:06
brycehsuperm1, basically, while X is showing the login screen plymouth is displaying some confirmation dialog behind the scenes and waiting for user input.  If the user hits enter or '2', plymouth sends X a SIGQUIT18:06
apwbryceh, yay for plymouth18:07
brycehyeah18:07
superm1I thought gdm requests plymouth to quit though?18:07
jcristausuperm1: seems to be full of races..18:07
brycehsuperm1, the bug had been believed fixed at one point but users are definitely still reproducing it on latest bits, so dunno18:08
=== radoe_ is now known as radoe
Sarvattthe problem is that plymouth is leaving the signal handler active on its console X is starting on and it just so happens that both the 2 or enter keycodes are quit key sequences, first time they are hit after it happens gdm restarts X on VT8 and its fine after that18:29
Sarvattyou should be able to add a stty -F /dev/tty7 -isig somewhere in the gdm startup scripts to work around it18:31
apwbryceh, do we yet have any known bad cards which need blacklisting.  i have preliminary blacklisting code which could do with a test18:50
apw(for kms)18:50
brycehapw, yeah jdstrand would be a good test case19:07
brycehhe's quite motivated to seeing the issue he saw resolved and has been quite active at helping do testing for us19:08
apwbryceh, sounds good ... i hear he is doing some testing for manjo right now, once he has those results i'll ask him for his ids19:08
Sarvattshoot, looks like a bunch of stuff I said got dropped19:24
Sarvatt<Sarvatt> bryceh, apw: any ideas on ways to add chipset detection logic to i915 to selectively set the default module options for certain cards? a way to set powersave=0 default for 945 and modeset=0 for 8xx would help a lot since 965+ doesn't need powersave=0 and such19:24
Sarvatt<Sarvatt> 8xx seems to be just as buggy with UMS as KMS from what I can see, just in different ways.. It's working with modeset=0 for a lot of people as a side effect of us explicitly disabling UMS support in intel so vesa is used19:24
Sarvatt<Sarvatt> and if we're sticking with --kms-only on 2.9.1 theres not much reason not to update to 2.10.x imo19:24
Sarvattbut sounds like you guys were already talking about it while i was disconnected :)19:25
apwSarvatt, i have patches which currently would allow a change of options, they currently only change modeset19:26
apwit would be no real difficulty to go one step further19:27
Sarvattchanging powersave=0 just for 945 would be nice, the 965+ bugs with it seem to be fixed19:27
jcristaumy 945gm seems happy enough with powersave now19:27
apwthe change of powersave sounds like somethign which should just be turned off for those cards in the driver itself19:28
Sarvatthave you suspended and used the machine more than 30 minutes after resuming?19:28
apwrahter than overriding the module parameters19:28
brycehSarvatt, I'm going to drop the --kms-only bit19:28
jcristauSarvatt: ah, no, i haven't used suspend19:28
apwyeah suspend is always a pig19:28
Sarvattthats where the problem is, it hangs to a black screen with 100% gpu usage in framebuffer compression after resume and another suspend/resume cycle fixes it until it happens again19:29
jcristauok19:29
apwyeah that one was a swine to find last time, is it back in the drm .33 backport they19:29
jcristaudo you know the fdo bug number for that off-hand?19:29
apwthen19:29
Sarvatti've been just dealing with it and suspending/resuming again to fix it for the power savings though :D19:30
apwheh that was a world of pain19:30
apwso Sarvatt i think the powersave thing may need doing a more sane way19:31
Sarvattjcristau: one sec, i'll dig some up but i'm in the middle of formatting a pixman patch to submit upstream for arm simd detection problems with our toolchain19:31
jcristauSarvatt: yeah no hurry, thanks19:31
apwusing the driver flags themselves so if you could email me with a list of the cards which are bust, i915 and !945+ or whatever it is and we'll see about fixing it properly19:31
apwSarvatt, actually lets file a bug on it a nice clean generic bug on the kernel asking for it disabled for them, and assign it to me19:32
Sarvattjcristau: https://bugs.freedesktop.org/show_bug.cgi?id=26594  (marked fixed but its only fixed by the reporter using powersave=0..) http://bugzilla.kernel.org/show_bug.cgi?id=14781 (lots of me-too's from 945 with the seperate issue from the original reporter..)19:36
ubottuFreedesktop bug 26594 in DRM/Intel "[945GM] Screen corruption and flickering" [Normal,New]19:36
Sarvattseems like those are the only two i have bookmarked, i subscribed to other ones and they are somewhere in my mailbox so they will take some digging19:37
jcristauhrm not much activity on that fdo bug19:38
Sarvattdarnit, I need to get my butt in gear and put in a resume to you guys so I can have time to do all of this stuff instead of doing it while sitting in traffic all day between jobs :)19:38
brycehheh19:40
Sarvattah hah19:48
Sarvattjcristau: https://bugs.freedesktop.org/show_bug.cgi?id=2626619:48
ubottuFreedesktop bug 26266 in Driver/intel "Screen lockup some time after wakeup from standby (to ram)" [Critical,Assigned]19:48
jcristauSarvatt: ah thanks, i'll ping this19:50
brycehmorning RAOF20:07
RAOFbryceh: Good morning.20:08
RAOFWhy don't I ever run into these bugs first? :/20:12
brycehRAOF, I know, I ask myself that a lot 20:13
brycehinsufficient time usually20:13
Sarvatthmm, with these new launchpad dialogues do debdiff's count as patches?20:21
SarvattThis file does not look like a patch.20:21
Sarvattah well I'll just say yes anyway :)20:22
brycehdebdiffs do count as patches20:26
brycehreally launchpad should distinguish between regular patches and debdiffs better, but it doesn't20:26
brycehtjaalton, I've uploaded xorg with the fix for the intel apport script.  Geir will probably appreciate it21:19
tjaaltonbryceh: ok good, don't forget to push :)21:22
brycehoh yeah21:22
tjaaltonbryceh: btw, did you see that bdrung merged -ati?21:28
tjaaltonwaiting for upload21:28
brycehyeah working on it next in fact21:28
tjaaltonok21:28
brycehit's fine by me, I've just been swamped with other stuff21:28
brycehthanks for reviewing and mentoring ben21:29
tjaaltonnp21:30
bryceh-ati uploaded21:44
RAOFbryceh: I'm cleaning up nouveau DDX; I'll have a package in git soon for you to sponsor, if you could.21:46
brycehRAOF, great, I'll be ready21:46
bdrungbryceh: debuild -S -sa21:47
brycehdah21:47
ibkanat>anyone have tips on getting a tablet to work with ubuntu 10.4? I followed https://help.ubuntu.com/community/AiptekTablet but didnt work21:50
bdrungbryceh: thanks for sponsoring21:52
brycehbdrung, thanks for doing the merge!  It xx'd out two items from my todo list :-)21:53
bdrung:)21:53
bryceh(technically I think we needed a FFe for updating -ati, but since we're still pre-beta I think we can handwave through it and beg forgiveness if anyone complains)21:54
bdrungbryceh: we have a FFe for it21:54
brycehbdrung, ah then excellent.  21:55
brycehbdrung, will that cover to upgrade to 6.13 when its out?21:55
bdrungbryceh: bug #534026 comment 521:55
ubottuLaunchpad bug 534026 in xserver-xorg-video-ati "Please merge xserver-xorg-video-ati 1:6.12.191-1 (main) from Debian experimental (main)." [High,Fix released] https://launchpad.net/bugs/53402621:55
bdrungbryceh: probably not, but i assume that an upgrade request will be granted21:56
brycehok21:59
Sarvatt\o/ https://wiki.ubuntu.com/X/Tagging -- I didn't know that existed and was just about to ask if you had a list bryce :)22:20
brycehSarvatt, :-)22:26
brycehSarvatt, ah didn't know it wasn't common knowledge, yes it's quite good22:26
brycehSarvatt, also if you don't know about this report, you might like it as it goes along with that page nicely:  http://www2.bryceharrington.org:8080/X/Reports/ubuntu-x-swat/symptoms_intel.html22:27
brycehSarvatt, that's a report showing the symptoms for bugs in a sortable column, limited to ones tagged 'lucid' (so you don't have to troll through ones against karmic that haven't been re-tested yet)22:28
brycehSarvatt, that report is a good way to spot dupes22:28
Sarvattmy bug work would be a *heck* of alot more productive if I could figure out how to mass search attached logs on bug reports. I usually spend most of my free time keeping up to date with mailing lists and git logs and every day I find myself trying to find errors strings that aren't in the bug reports so I have to resort to searching for symptoms and wasting time trying to see if its the one thats fixed22:40
Sarvattalmost wish you could get attachments sent in bug mails though i'd need 10 gmail accounts then :)22:41
Sarvatthttps://bugs.edge.launchpad.net/ubuntu/+source/xserver-xorg-video-intel?field.searchtext=GPU+lockup&orderby=-importance&search=Search&field.status:list=NEW&field.status:list=INCOMPLETE_WITH_RESPONSE&field.status:list=INCOMPLETE_WITHOUT_RESPONSE&field.status:list=CONFIRMED&field.status:list=TRIAGED&field.status:list=INPROGRESS&field.status:list=FIXCOMMITTED&field.assignee=&field.bug_reporter=&field.omit_dupes=on&field.has_patch=&field.has_no_pack22:44
Sarvattage=22:44
Sarvatt845 and 855 have major problems for sure22:44
BUGabundoSarvatt: ahaha22:45
Sarvattoops too long for one line22:45
Sarvattthats like not even a week's worth of bugs and 845/855 is dominating it22:46
Sarvatthttps://bugs.edge.launchpad.net/ubuntu/+source/xserver-xorg-video-intel?field.searchtext=GPU+lockup22:46
Sarvattthere we go22:46
brycehSarvatt, arsenal has some stuff to help do searches on attachments22:51
brycehSarvatt, if you grab the arsenal code I can help show you how to craft tools to search log files22:51
Sarvattmost of the 8xx bugs seem to be page table error hangs22:51
BUGabundofor a moment I though you meant the english team that beat my FCPorto tonight 22:52
Sarvattincluding the EIR: xxxxxxxxx line from i915_error_state in the bug description would be nice22:52
brycehSarvatt, I may be able to do that in the apport script22:55
brycehI need to look into what Geir's been doing with the reports; I think there's fair room for more automation22:56
Sarvattchecking out arsenal now, proposed a merge with a change to the README to point at the new Template-Python svn address23:07
brycehgreat23:08
RAOFbryceh: pkg-xorg git has xserver-xorg-video-nouveau update in it.23:09
brycehRAOF, ok on it23:09
Sarvattlooks pretty straight forward23:09
Sarvattyeah process-xorg-retargeting.py needs some fixing up for nvidia from what I see, it's retargetting nvidia-graphics-drivers bugs on lucid to nvidia-graphics-drivers-18023:15
brycehRAOF, uploaded23:15
RAOFbryceh: Danke.23:16
brycehSarvatt, true23:17
brycehSarvatt, bzr pull and check again23:17
Sarvatti'm going to need to set up a private launchpad instance to mess with these scripts I guess :)23:17
Sarvattoh dang, I was behind a few days23:18
brycehSarvatt, nah, many of the scripts include a dry_run bool you can set so you can run them without causing changes23:42
brycehthose that don't have that probably should23:43

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