kklimondaany idea why I'm not seeing splash with nouveau? I get a scrambled screen - mostly black, with some random colors00:12
kklimondaas soon X loads everything works fine00:13
kklimondaah, it's bug 72347700:14
ubot4`Launchpad bug 723477 in xserver-xorg-video-nouveau (Ubuntu) "screen corruption instead of pylmouth on boot with nouveau (affects: 1) (heat: 159)" [Undecided,New] https://launchpad.net/bugs/72347700:14
RAOFbryceh: Ok.  So, I too see a (smaller) memory delta (on amd64); my steady-state numbers change from ~500MiB to ~645MiB.00:40
RAOFHm.  And it looks like the mere act of loading nvidia's libGL dirties in excess of 4MiB of memory, doubling the dirty memory of my gnome-terminal.01:06
RAOFbryceh: Looks like the mere act of linking to nvidia's libGL is going to increase the memory of the process by ~5MiB.  If cairo links to libGL, that's a lot of memory.01:38
bjsniderwhy shouldn't it? it's not using the mesa libgl at all.01:40
brycehRAOF, could we prevent that from occurring with nvidia?  wayland won't work with nvidia anyway01:42
RAOFbjsnider: You don't understand; that's 5MiB of *unsharable* memory.  If you have 30 processes linking to GTK you've uselessly eaten 150MiB of memory.01:43
RAOFbryceh: We could get cairo-gl to dynamically load libGL when first constructing a GL context, I guess.01:44
bjsniderRAOF, have you talked to nvidia about that?01:44
brycehanyway, need to get off the computer, bbl01:44
RAOFbjsnider: No, I've only just noticed it.01:44
RAOFbryceh: It's probably pretty easy to dynamically load libgl; I'll check it out.01:44
bjsniderRAOF, surely that's not how nvidia _wants_ things to work01:47
RAOFI can imagine reasons why nvidia would do that.01:47
bjsniderRAOF, you're more qualified to imagine that kind of thing than i are01:48
RAOFSpecifically, runtime patching of code will cause that, and it's not unreasonable to do that in libGL (mesa did on i386, until I stopped it).01:48
bjsniderRAOF, i'm sure if you notify aplattner he can either do something about it or explain why it works that way01:50
kklimondaRAOF: hmm.. in my case it was more than 5MB I think.. I do remember that some basic Qt app I wrote used 45MB of ram, and 20MB came from one of nvidia libraries..01:53
kklimondabut I've assumed I don't know how to read /proc/pid/smaps01:54
RAOFkklimonda: Was that dirtied memory or a sharable library text?  nvidia's libGL is pretty big, and will show up as such, but should be sharable across all the processes linking to it.01:55
kklimondaRAOF: right, I can't really remember right now - I'll check it out when I go back to nvidia.01:55
RAOFUnless they've done something crazy like make a non-PIC libGL on i386.01:55
kklimondabtw, is there something wrong with nvidia drivers that makes unity so slow on it?01:56
kklimondarunning dmesg takes seconds for example01:56
kklimondapretty much everything I do in terminal gets slowed down considerably the moment I start looking at it (it works fine when terminal is hidden)01:57
RAOFI'd guess you're hitting a font-rendering fallbakc.02:00
kklimondayeah, it's quite possible - at some point changing to "Best shape" gave me a lot of performance boost02:02
kklimondabut when I tried doing that in natty it didn't help.. at least I don't remember the same boost :)02:02
RAOFIt's possible that switching your fonts will do somethnig, too.02:07
kklimondaRAOF: http://paste.ubuntu.com/583614/ 02:40
kklimondaPrivate Dirty: 16396 kB02:40
RAOFOwch.  What process was that?02:44
wgrantRAOF: Hi.02:46
RAOFwgrant: Howdie.03:14
RAOFwgrant: After somethnig?03:14
RAOFOther than a chat after a long period of no chatting? :)03:15
RAOFBah.  Dear Telstra: unless you're willing to buy out my existing phone contract you *definitely* won't be able to offer me a ‘fantastic deal on my mobile phone’.04:49
wgrantRAOF: Sorry, back.06:09
wgrantRAOF: Your 113_tls.diff in mesa has made it into xorg-edgers, and it breaks unity pretty badly (at least on r600g).06:09
wgrantIs it meant to do that?06:09
RAOFIt is not.06:09
RAOFWhat does it do?06:09
wgrantWell, Unity basically doesn't render. It occasionally flickers up a very corrupt version of itself when hovered.06:10
wgrantNormal compiz mostly works, except that some shadows are broken.06:10
RAOFAnd you're sure this is a tls problem?06:11
wgrant(at least in the 20110318 xorg-edgers mesa build... I reverted the patch from that and it's all good again)06:11
RAOFOh.  Curses.06:12
wgrantI might try building it with the patch locally, just in case. But the 20110316-20110318 diff is pretty minimal, apart from that patch, some 965 stuff, and some tiny refactorings.06:13
RAOFwgrant: Are you on i386 or x86-64?06:16
wgrantRAOF: x86-6406:16
RAOFThat makes it easier.  I *have* an x86-64 r600g system :)06:16
RAOFAlthough I guess I could also break open the esprimo and throw in the radeon card.06:17
wgrantIt's a Radeon 5700 of some variety, FWIW.06:17
RAOFWhich, conveniently, is also what I have.06:18
RAOFOh, balls.  Something's broke in my monitor, and it's now sending invalid EDIDs.06:55
wgrantSure it's not just X being really broken?06:58
RAOFNah; the kenel's throwing “checksum invaliD!” into dmesg all the time.07:01
mvoI get some really odd artifacts on my intel notebook with natty, looks like redraw problems, oddly enough with the unaccelerated desktop. 14:26
=== JanC_ is now known as JanC
mvobryceh: are there any report on redraw artifacts on intel and noveau with the classic desktop? it happens for me on natty a lot when e.g. minimizing a window16:34
brycehmvo, 622068 725333 737967 are visual corruption bugs reported on -intel.17:38
mdeslaurmvo: I see it, and kees sees it also18:26
mdeslaurbryceh: ^18:26
mdeslaurmvo: are you using metacity?18:27
brycehmdeslaur, hmm, didn't that get identified as a kernel bug and sorted out a couple weeks ago?18:31
mdeslaurbryceh: I don't know...but I'm up-to-date18:32
mdeslaurbryceh: it only happens with metacity, but it happened with my nvidia laptop and it happens with my new intel laptop this week18:32
brycehbug 71711418:32
ubot4`Launchpad bug 717114 in xserver-xorg-video-intel (Ubuntu Natty) (and 4 other projects) "[i945gm] Screen Corruption with new Xorg stack with terminal programs (affects: 20) (dups: 3) (heat: 104)" [Medium,Triaged] https://launchpad.net/bugs/71711418:32
brycehset to fixed for linux on 3/1818:33
mdeslaurbryceh: that's not the same issue18:33
mdeslaurbryceh: I'll try and get a couple of screenshots...but am not sure under what to file the bug18:34
brycehmdeslaur, ok, mind digging up the bug report #?18:34
mdeslaurbryceh: can I just file it under xorg until someone figures out what's causing it?18:35
brycehgiven this other one was a kernel issue, wouldn't you think yours is kernel too?18:36
mdeslaurbryceh: you're just trying to get rid of me :)18:38
brycehmdeslaur, but no, if you feel there is value to having me involved in looking at it, go ahead and file against X, but I'm like 90% certain it's going to end up being another kernel issue18:39
brycehmdeslaur, I posted a list of other graphical corruption bugs to mvo up above, I'm going to forward them all upstream today, so if you file yours against xorg I'll send that one up too18:43
bryceheven if it ends up being a kernel bug, when I upstream them they often will point out the patch for us18:43
mdeslaurbryceh: does binary nvidia use the kernel?18:43
mdeslaurbryceh: ok, let me reproduce and get a couple of screenshots, and I'll file it18:43
brycehit uses a lot less of the kernel than the foss drivers do18:46
mdeslaurbryceh: bug 74038718:49
ubot4`Launchpad bug 740387 in xorg (Ubuntu) "graphical corruption with multiple drivers and classic desktop (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/74038718:49
brycehmdeslaur, ah yeah that is quite different (and I think different from what mvo is mentioning)18:52
brycehmdeslaur, I would guess even if it looks similar, the issue on -nvidia and -intel could have different root causes.  Mind filing a second bug for the other machine?18:53
mdeslaurbryceh: sure18:53
mdeslaurbryceh: bug 740422 for issue on nvidia with nvidia screenshots19:26
ubot4`Launchpad bug 740422 in xorg (Ubuntu) "graphical corruption with classic desktop (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/74042219:26
mvomdeslaur: yeah, I use metacity19:55
mdeslaurmvo: are 740387 and 740422 what you are seeing?19:55
mvohold on a sec, let me check19:55
mvomine looks like this: http://people.canonical.com/~mvo/tmp/Screenshot.png19:55
mvoexcept for the blur, I added that :)19:56
mdeslaurmvo: looks similar19:56
mvoI have it on intel and noveau19:57
mvonouveau is not stable enough for me to run unity19:58
mvobut that is a different matter19:58
mvomdz: thanks, I have a look at 74037220:00
brycehmdeslaur, mvo, do you recall about when you started seeing this regression?20:23
brycehtrying to get a feeling for what kernel (or X) version brought the issue20:23
mdeslaurbryceh: honestly, I'm investigating metacity now...I think it's a DX patch20:23
mvomy gut feeling is the 1.9 - > 1.10 switch, but I may be wrong20:24
mvomdeslaur: interessting idea!20:25
tjaaltonis it the same corruption we discussed the other day?20:25
tjaaltoni'm seeing it with savage20:25
tjaaltonwhen opening menus etc20:25
brycehfwiw, I've seen something similar on -ati but it only shows up when launching URLs from xchat to firefox so dunno if it's the same issue.  Similar effect though (invalidly drawn areas of the region)20:25
brycehtjaalton, don't think so20:26
mvobryceh: this is what triggers it most reliable for me as well20:26
brycehthat menu corruption was particular to -ati it seems (upstream has pointed to a kernel patch to revert)20:26
tjaaltonah, looked at the screenshot, and it's not20:26
brycehI had been thinking perhaps the damage issue was a subset of the menu drawing issue since I started seeing both at the same time20:27
brycehbut now I'm pretty sure they're distinct bugs20:27
brycehmdeslaur, should I hold off on upstreaming this bug?  (about to pull the trigger on it to go to -intel)20:28
mdeslaurbryceh: yeah, you should probably wait a bit20:29
mdeslaurbryceh: I can't seem to reproduce it at the moment with the DX patches ripped out20:29
brycehmdeslaur, 06_Add_UXD_shadows_and_borders.patch ?20:34
mdeslaurbryceh: maybe, I'm trying to figure out which one now20:35
mdeslaurbut that,s the one that I suspect20:35
brycehhmm, some of these metacity patches sound like they could have some performance implications20:36
AlanBellwondering if someone could help me get a little further with bug 73833020:57
ubot4`Launchpad bug 738330 in virtualbox-ose (Ubuntu) (and 1 other project) "Today's Natty update means no guest additions in virtualbox (affects: 9) (heat: 58)" [Undecided,Invalid] https://launchpad.net/bugs/73833020:57
AlanBellthis is the oracle virtualbox drivers, not the Free Software OSE ones - however the source is available and gets compiled with dkms I think20:58
AlanBellthe problem is an ABI issue with the new Natty xorg ABI 10 and the drivers20:59
jcristaudkms is for kernel module, not X drivers21:02
tjaaltonso the guest-additions are opensource?21:02
tjaaltonif not, there's nothing we can do other than wait for oracle to fix it21:03
jcristautjaalton: virtualbox-guest-additions is in non-free in debian, so i guess not21:03
AlanBellinteresting point about dkms, I was just reading up on that21:04
AlanBellso it does build a video related driver, but I think that is the kernel part, so the xorg driver itself would be separate21:05
tjaaltonX.Org guests: support X.Org Server 1.10 pre-release and Ubuntu 11.04 Alpha. 21:05
tjaaltonfrom 4.0.4 changelog21:05
tjaaltonwhich means abi 9, so they just need to fix it21:05
jcristauso they have both a closed and an open X driver?21:08
AlanBellhttp://www.virtualbox.org/changeset/36301 does that look like the crucial change to you?21:08
AlanBelljcristau: the source is all available21:08
AlanBellthe latest version comes prebuilt, the OSE version in Ubuntu lags behind21:09
jcristauthis stuff is so fucking broken..21:09
AlanBelland unity only runs on the bleeding edge prebuilt version21:09
AlanBellor did until recently :)21:09
tjaaltonAlanBell: so where is the vboxvideo_drv_110rc.so built?21:11
tjaaltonum, 110.so21:11
jcristauAlanBell: "comes prebuilt" means without source then?21:11
AlanBelljcristau: no, the stable release version is available built - just like anything else21:13
AlanBellthey don't have daily builds from SVN21:13
AlanBelland the version in Ubuntu is older than the upstream stable release21:13
AlanBellit really isn't much more insane than anything else out there tbh21:14
tjaaltondon't see anything newer upstream21:14
tjaalton4.0.4 is the latest release21:14
AlanBellah, ok sorry, the latest is in Natty, but I am using a Maverick host21:15
tjaaltonvirtualbox-ose-guest-x11 should depend on the correct abi21:19
tjaaltonwhat it supports21:19
tjaaltonnot what it happens to be "built" against21:20
AlanBellso for instant gratification I guess I compile from SVN and install those drivers in the guest Natty21:29
tjaaltonsomething like that21:29
speakmanHi folks. Is there any tools to trace what's causing X to be extremely CPU intensive?21:53
speakmanI'm on a w3680 (6-core @ 3.33GHz) but I'm getting flashbacks from the mid -90.21:53
tjaaltonkill apps one by one, when it stops you have your culprit :)21:55
speakmanI've tried (of course) but it's still laggy no matter which apps are running21:56
speakmanI'm on two GPUs with four monitors if it may have anything to do with it. Both are Nvidia with the propretary drivers instaleld.21:56
tjaaltonlikely does21:57
speakmanBut anyway; is there a way to trace what's causing the X processes the CPU hogging?21:57
tjaaltontry a profiler21:58
speakmanThere's no way to attach to the running X process?21:58
tjaaltonyes, but nvidia..21:58
tjaaltonbesides, what would you benefit by hooking gdb to it?21:59
speakmanI've not mentioned gdb. But I thought there might be tools for profiling X.22:00
speakmanThis can't be the only computer with X hogging the CPU?22:00
tjaaltoni said try a profiler22:00
tjaaltonthere are tools22:00
tjaaltoni just don't have any docs handy22:00
speakmanis there any X profilers available?22:01
tjaaltonor try with a single gpu & monitor first22:01
tjaaltonwhy would x need a profiler of it's own?22:02
AlanBellwell virtualbox is now compiling away on my natty VM22:08
tjaaltonAlanBell: could you tell felix geyer about the issue?22:16
AlanBelltjaalton: where do I find him?22:18
speakmanI just ran sysprof and it seems like nvidia_drv.so is the trouble22:20
AlanBellnvm, devfx22:20
tjaaltonspeakman: surprise :)22:20
tjaaltonit's also an unusual setup22:21
tjaaltoni guess22:21
speakmantjaalton: not really... but now how to fix it :/22:22
brycehmdeslaur, good work narrowing down to patch 16; are you or someone you know going to disable that patch?22:22
brycehmdeslaur, if not I can take care of doing it22:23
brycehmdeslaur, have you also verified this was the cause of the -nvidia issue as well?22:25
mdeslaurbryceh: I've pinged the author of the patch, let's see what he says22:26
mdeslaurbryceh: I only tested it on -nvidia22:26
mdeslaurbryceh: but will change the gconf key on my -intel laptop tomorrow22:27
AlanBellyay, I have unity in 3d again, the virtualbox-ose-guest-x11 package in natty works just fine22:41
=== Amaranth_ is now known as Amaranth

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