superm1 | oh i should look at what i was reverting ;) it was a comment. so it must be a commit near there then, and the comment threw bisect off | 00:34 |
---|---|---|
=== maxb_ is now known as maxb | ||
=== albert231 is now known as albert24 | ||
=== albert24 is now known as albert23 | ||
tjaalton | bryce: assign me to the bugs, and I'll have a look | 16:45 |
tjaalton | it's really unfortunate that these regressions happened, but maybe the 7.4 branch has fixes for them already | 16:46 |
tjaalton | s/me to the bugs/the bugs to me/ | 16:47 |
tjaalton | I'll make sure upstream knows about these if they're not fixed already | 16:52 |
tjaalton | it's high on my list since i've been so vocal to follow upstream on this :) | 16:54 |
bryce | tjaalton: 359392 is the master bug for this | 19:40 |
bryce | tjaalton: other possibly related bugs are at https://wiki.ubuntu.com/X/Bugs/IntelDriver | 19:41 |
bryce | notice all the i965-specific freezes starting from early april | 19:41 |
tjaalton | ok, I'll hunt them once I get back home | 19:48 |
bryce | d805c820: fix potential recursive locking deadlock in _mesa_HashWalk() maybe? | 19:49 |
bryce | thanks, we're heading out for easter brunch. bbiab | 19:49 |
knome | hello. | 19:52 |
tjaalton | yeah if it's 965 related I should be able to reproduce and test potential fixes | 19:52 |
knome | on hardware drivers, nvidia-180 says first that another version of the driver is in use | 19:53 |
knome | and when i activate it, it says that it is disabled, but still in use | 19:53 |
knome | what can i do to activate it? | 19:53 |
tjaalton | knome: upgraded from intrepid? | 19:58 |
knome | tjaalton, yes. | 19:58 |
tjaalton | so is 180 installed now? | 19:58 |
knome | it is | 19:58 |
tjaalton | is it used? (look at the logfile) | 20:02 |
knome | which logfile? | 20:02 |
tjaalton | Xorg.0.log | 20:02 |
tjaalton | dmesg should tell as well | 20:02 |
superm1 | checking dpkg -l | grep nvidia would probably be useful too to make sure none of the 177 bits are still installed | 20:03 |
knome | tjaalton, LoadModule: "nvidia" | 20:05 |
knome | superm1, there is even some 96-bits | 20:05 |
tjaalton | knome: the version string would tell which version is used | 20:05 |
knome | tjaalton, 180.44 | 20:06 |
knome | after boot jockey insists that 180 isn't used. | 20:07 |
knome | and can't activate | 20:07 |
tjaalton | so it's lying | 20:07 |
knome | supposedly | 20:07 |
knome | 3d is working fine, though. | 20:07 |
knome | just wondering | 20:07 |
tjaalton | dunno why | 20:07 |
knome | should i file a bug? | 20:08 |
tjaalton | not sure | 20:09 |
tjaalton | maybe :s | 20:09 |
tjaalton | s/s/)/ | 20:09 |
knome | which files should i include? | 20:10 |
knome | and against which package? | 20:10 |
tjaalton | use ubuntu-bug | 20:14 |
tjaalton | jockey I suppose | 20:15 |
knome | filed bug #360161 | 20:23 |
ubottu | Launchpad bug 360161 in jockey "Jockey can't activate a driver even if Xorg.0.log tells it used" [Undecided,New] https://launchpad.net/bugs/360161 | 20:23 |
knome | my screen also goes partly black now and then | 20:26 |
knome | eg. if browsing web with firefox, part of the window background might become black. | 20:26 |
knome | is this known? | 20:27 |
knome | there is no exact steps to reproduce. | 20:27 |
knome | this *might* have something to do with my gtk theme, but i'm very sceptical about that. | 20:28 |
tjaalton | haven't seen it myself | 20:28 |
knome | right | 20:28 |
knome | i'll try to get a screenshot of it once it happens again | 20:29 |
knome | or a photograph | 20:29 |
=== james_w` is now known as james_w | ||
andresmujica | bryce: please check bug #360193, i was able to reproduce the freeze using mesa 7.3 and the application alarm-clock | 21:45 |
ubottu | Launchpad bug 360193 in ubuntu "x server freezes consistently" [Undecided,New] https://launchpad.net/bugs/360193 | 21:45 |
bryce | andresmujica: interesting. My gut suggests it may be a separate freeze issue | 23:31 |
bryce | after all, we already have about 20 known freezes before we even got to april 3rd. ;-) | 23:32 |
bryce | from what I've gathered, the april-3rd freeze is not triggerable by a specific user action, it just comes on "randomly" (gods I hate that term!) | 23:33 |
bryce | which is why my gut thinks that freezes that are reproducible easily with a specific application, and that aren't resolved by going 7.4->7.3, really sound like a separate issue | 23:34 |
andresmujica | hi bryce | 23:34 |
andresmujica | well | 23:34 |
andresmujica | i'm testing a lot | 23:34 |
bryce | good! :-) | 23:34 |
bryce | yeah I will try reproducing on my laptop too | 23:34 |
andresmujica | and found 2 freeze actions | 23:34 |
andresmujica | and 1 "natural" freeze with mesa 7.3 | 23:34 |
andresmujica | sudo apt-get install alarm-clock | 23:34 |
andresmujica | and then start alarm-clock | 23:35 |
bryce | oh, also keep in mind there are issues that 7.4 actually fixes, it's not all just new bugs ;-) | 23:35 |
andresmujica | your laptop is frozen | 23:35 |
andresmujica | ssh from a remote machine and kill the alarm-clock | 23:35 |
bryce | ok | 23:35 |
andresmujica | and get your system back | 23:35 |
bryce | hmm | 23:35 |
andresmujica | aslo with strace gcalctool or strace firefox | 23:35 |
bryce | ok that sounds like a very different issue, that's not a classic X freeze | 23:35 |
andresmujica | yeap | 23:35 |
andresmujica | i believe a focus thing | 23:35 |
bryce | if you can freeze on strace glxinfo, there's a known bug on that | 23:36 |
andresmujica | i' m waiting to get another "natural" freeze to kill app per app | 23:36 |
bryce | cool | 23:36 |
bryce | ok, switching computers | 23:36 |
andresmujica | hmm nop freeze with strace glxinfo | 23:36 |
andresmujica1 | just got the freeze again, and effectively is not the same as the alarm-clock one, as i cannot recover the system by killing apps... | 23:54 |
andresmujica1 | the bad thing is i'm using mesa 7.3 | 23:54 |
andresmujica1 | and xserver-xorg-core/xserver-common 1.6.0-0ubuntu1 | 23:55 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!