=== yofel_ is now known as yofel
tjaaltonmesa 7.10.2, go/no-go ?08:26
RAOFtjaalton: The diffstat is (somewhat surprisingly) not too scary.  Everything seems to work, too.10:28
tjaaltonRAOF: oh, you've tested it already?10:28
RAOFA bit today.10:28
tjaaltonok, nice10:28
tjaaltonnext week the kernel will be frozen, so if we want to disable nouveau acceleration by default we should make it now10:30
tjaaltonOTOH fedora doesn't do it anymore10:30
tjaaltonso maybe it would be too invasive a change at this point10:30
RAOFAnd we don't seem to have users screaming about it, either.10:31
tjaaltonlet's keep status quo then10:31
RAOFI've got a nouveau upload that supposedly fixes an EXA crash, but, again, people don't seem to be hitting it.10:32
tjaaltongot a link to a bug?10:32
RAOFNo; it was just talking with darktama.\10:32
tjaaltongreat, can't install maverick on a spare machine because of ati kms fail12:01
tjaaltonhave to use a dvi-dsub dongle, and it doesn't seem to recognize it12:02
tjaaltonradeon.modeset=0 to the rescue, of course..12:08
tjaaltonexcept X still doesn't work12:20
tseliotis it a new card?12:22
tjaaltonno, an ancient X80012:24
tjaaltonhum no, some firegl device actually, but from the same era12:24
tjaaltonI'll try natty next12:24
tjaaltonx starts, just no picture to prove it12:26
tjaaltonlogfile looks innocent as well12:26
tjaaltonsame with natty12:57
tjaaltonworks with the dvi cable13:03
tseliottjaalton: what cable was the one that didn't work?13:41
tjaaltontseliot: d-sub, with a dvi dongle13:52
tseliotah, ok13:52
=== seb128_ is now known as seb128
kklimondahey, any chance that one of you, X people have seen something like that on nouveau: http://people.ubuntu.com/~kklimonda/wtf.png ?16:55
bryceh_heya sarvatt21:35
Sarvatt_heyo! sorry, swapping between 4 different machines and missed IRC21:44
Sarvatt_Error:  Failure creating backup file for /etc/default/grub.  Changes not applied.21:45
Sarvatt_[Errno 13] Permission denied: '/etc/default/grub.bak'21:45
Sarvatt_bryceh_: doesn't look like this runs update-grub after?21:46
Sarvatt_bryceh_: hrm, second run thinks "disable bootloader graphics" isn't applied 100% of the time21:48
Sarvatt_but its there21:48
bryceh_Sarvatt, yeah I just added update-grub yesterday21:56
bryceh_Sarvatt, those errors are because it has to run as sudo 21:56
bryceh_need to figure out gksudo or some such to request privs21:56
bryceh_Sarvatt, yeah sorted the disable bootloader graphics issue out yesterday too; that was kind of a hard one21:57
bryceh_Sarvatt, fixes pushed to bzr21:59
Sarvatt_bryceh_: cool, everything working now22:00
bryceh_I also got the packaging squared away.  Just need to test it on a virgin machine then I think I can upload.22:01
bryceh_ok, X blueprints filed22:53
bryceh_I made 3, one for stakeholders, one for discussing tools/processes/debugging/etc., one team huddle one22:53
bryceh_RAOF, ^ please review and see if I missed anything22:55
tjaaltonsubscribed to them22:57
bryceh_tjaalton, I'm looking forward to having so many X folks at one UDS :-)22:59
tjaaltonbryceh_: yeah, there might even be <gasp> discussions :)23:02
tjaaltonthe previous planning session I attended took maybe 15min :)23:02
Sarvatt_hopefully they dont overlap private sessions I have to go to this time around :)23:03
bryceh_tjaalton, Sarvatt_, yeah make sure you're subbed as essential to these so you don't get too cross-scheduled23:03
bryceh_tjaalton, Sarvatt, also if you guys think we need additional topics just shout.23:04
bryceh_although it seems from past uds's that 3 X sessions was about right23:04
bryceh_but now that there's more of us we could probably handle more if we see the need23:06
bryceh_tjaalton, sarvatt: I'm kind of disappointed -intel is still proving quite buggy - http://tinyurl.com/3jrqgat23:10
bryceh_I have been pumping bug reports upstream but the patches we've been getting have been more miss than hit lately23:11
tjaaltonbtw, was the apport-collect script broken for a while?23:12
bryceh_I'm kinda stuck on what else to do... any ideas?23:12
bryceh_tjaalton, yeah, a couple typos23:12
tjaaltonok, that's why ubuntu-bug reported ~empty bugs23:12
bryceh_sorry about that; have them run apport-collect <bug-nr> and that should fix them up23:13
tjaaltonso are these intel bugs without the trigger-happy apport script?23:15
tjaaltonie. nothing we can turn off?-)23:15
bryceh_the GPU lockup ones are from the gpu lockup hook, and are mostly legit bugs23:15
bryceh_I think I got the script a lot less trigger-happy now, although the vesafb conflict or whatever that causes the false positives is still  there23:16
bryceh_bugs with ESR 0x00000010 are often that issue23:16
tjaaltonok, so unless we educate ourselves as gpu programmers there's not much to do than report them upstream and be nice to ickle :)23:17
bryceh_bug #2 is whatever causes freezes on 915/945, we get tons of those, and upstream tends to dupe them all together, point to a patch, and close as fixed.  Then we have to pull that fix in, and wait for another series of 915/945 bugs to get reported.  Rinse, lather, repeat.23:18
ubot4`bryceh_: Bug 2 on http://launchpad.net/bugs/2 is private23:18
bryceh_there's a third class which is arrandale specific23:18
bryceh_I had thought the new ia32-libs would resolve that since it seems to only affect x86_64, but we're still getting bugs reported23:19
bryceh_so like "[arrandale] GPU lockup (ESR: 0x00000001 IPEHR: 0x02000024)" is typical error codes on that23:19
bryceh_fourth class is 965-specific, bug #68638823:20
ubot4`Launchpad bug 686388 in xserver-xorg-video-intel (Ubuntu Natty) (and 4 other projects) "[i965gm] GPU lockup - Invalid GTT entry during Display B Fetch (affects: 11) (dups: 8) (heat: 80)" [High,Incomplete] https://launchpad.net/bugs/68638823:20
bryceh_I think that covers the common classes for the gpu lockups23:20
bryceh_then there's a whole bunch of other random assorted bugs23:20
bryceh_oh, and various 865 lockups, but we just wontfix those23:21
bryceh_tjaalton, yeah I think you're right regarding needing gpu programming education ;-)23:22
tjaaltoni'll probably buy a second hand fujitsu laptop (v5535) with sis 671 on it, and see how the damn driver works first :)23:23
tjaaltonor, rather, doesn't23:23
bryceh_well, like one thing I'm wondering is it'd be nice if when Intel posts a patch that "fixes" it, that we have some easy way to roll a kernel with that patch so reporter can easily verify that no, it doesn't23:24
tjaaltondon't the kernel team do that, provide a ppa with a kernel that has a proposed patch23:25
bryceh_we have daily builds of intel-drm-next, but I think they're being stricter about putting untested patches into that23:25
bryceh_tjaalton, yeah they do, but I wonder if bugging them each time there is a patch needing packaged is the right solution?23:25
bryceh_and maybe it is; technically they are kernel bugs after all...23:26
tjaaltonbryceh_: no, but can't we make use of the infrastructure directly?23:26
Sarvatt_tjaalton: do you have an account on tangerine? its so friggin fast for building kernels, I can walk ya through it tomorrow if you want23:26
bryceh_right, that's what I'm wondering23:26
tjaaltonSarvatt_: t.c.c?23:27
tjaaltondoesn't seem like I do23:27
tjaalton"Permission denied (publickey)."23:28
Sarvatt_gotta pivot in from chinstrap23:28
tjaaltonthat's where i tried from23:29
Sarvatt_you'd know if you had an account, lets see23:29
Sarvatt_its a 64 core 64gb ram machine in one of the datacenters for kernel building, takes <10 minutes for a kernel build23:30
tjaaltonhmm, at my previous job I built mesa in 8min on a shell server, which had 12cores + hyperthreading, and 96GB RAM23:32
tjaaltoncan't remember the time it took, but it was fast23:32
tjaaltoncould've been less than 8min23:32
bryceh_it would be totally awesome if we could go from a) patch posted in upstream bug tracker, to b) built kernel (or mesa) .debs for reporter to test, in under 10 min23:36
bryceh_heck, even 30 min would be nice23:37
bryceh_currently it seems the turnaround is >5 hrs for such a case23:37
JanCtjaalton: I once talked with somebody who builds a kernel in < 1 min at his job  ;)23:38
tjaaltonyep, it should be doable. like create a branch, pull the fix, push the package to the builder (with some script, lp# as an argument) and then the bug would get the link23:39
tjaaltonJanC: ok, that's quick :)23:39
JanChe works/worked at http://sara.nl/ though  :P23:39
Sarvatt_thats a really freaking good idea23:40
tjaaltoni got a couple of friends at http://csc.fi23:40
tjaaltonthey have all the toys :,I23:40
Sarvatt_bryceh_: https://wiki.canonical.com/KernelTeam/BuildResources23:44

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