/srv/irclogs.ubuntu.com/2009/05/01/#ubuntu-x.txt

lesshastehi.. my X restarted again spontaneously with this log http://pastebin.com/f4d283a9214:39
lesshasteI thought i  had installed debug symbols.. what can I do to get a better backtrace for next time?14:39
lesshasteI have installed xserver-xorg-core-dbg  for example so I am mystified14:45
mnemothere are certain types of bugs where the stack itself gets corrupted (buffer overflows etc) and in those cases you might not be able to reconstruct a backtrace because essentially what you think is return addresses are just random pointers14:53
mnemoi have no idea if that's the case for you though14:53
mnemolesshaste: there is a better wat to get backtraces, but its a bit more work14:54
lesshastemnemo: that's very interesting... I am not very good at interpreting backtraces like this one14:54
lesshastemnemo: what is that14:54
lesshaste?14:54
mnemoits kind of complicated but basically whenever you run into a CALL instruction in machine code, the CPU will push the address in memory where it is supposed to continue running once that CALL is done14:55
lesshasteoh I see. this involves patching X?14:55
mnemoso basically what gdb does is that it walks through the raw stack memory and then it just figures out which locations hold the actual returns addresses14:55
mnemono you can get a backtrace much easier14:55
lesshasteok14:56
mnemowith normal gdb actually14:56
lesshasteso run X in gdb?14:56
mnemobasically you need to attach gdb to X while its running and then keep gdb running in a ssh shell14:56
mnemoyea just start up X normally14:56
lesshasteok.. how do I do that please :)14:56
mnemoconnect to ssh from another computer14:56
mnemoand then you do "sudo gdb -p $(pidof X)"14:56
lesshasteoh I see... a little like a serial console14:56
mnemothis will temporarily freeze your X on that machine14:56
mnemoyea sort of like that14:57
mnemoanyway, once you type "c" inside gdb you will be able to use X again14:57
mnemoand then you just wait until you can trigger the crash again14:57
mnemoat that point gdb will stop again and break into a prompt mode from where you can do all kinds of neat analysis14:57
lesshastethat can't be done from a VT on the same machine?14:58
mnemono unfortunately not14:58
mnemoif you really want to do it from a single machine I think you can14:58
mnemoi've never done that though14:59
lesshastewhy won't it work from a VT?  That should be affected by an X crash should it?14:59
lesshasteshouldn't14:59
lesshaste(for the first should :) )14:59
mnemothe thing is that if you shutdown X and then start like "gdb X" then X won't unset its graphical mode when you break into the SEGV prompt in gdb so I dont think that would work14:59
mnemohmm im not sure why it won't work on a VT15:00
mnemoi mean try it I guess :) but I suspect it won't work15:00
mnemoheh I tried it now, it didnt work.. I can attach gdb fine but I can get back to X from there15:04
lesshastemnemo: which xserver-xorg-video-<name> do I need for the fglrx driver? Could it be ati?15:04
lesshastemnemo: :) thanks15:04
mnemonah15:04
mnemofglrx is none of those15:04
lesshasteah ok15:05
mnemofglrx is closed source crap15:05
mnemobut xserver-xorg-video-ati usually works pretty well for the same cards15:05
lesshastebut 3d right?15:06
mnemoyeah the open source -ati version has 3d with direct rendering etc15:06
mnemocompiz runs great on it etc15:07
lesshasteoh.. this sounds newish :)15:07
lesshasteI should change to that15:07
mnemohonestly, the best thing with the open source driver is that you can actually analyze the failures, file good bug reports and get stuff to improve15:07
lesshastesure but I didn't know 3d worked these days :)15:08
mnemotry it and see if it's good enough for you15:08
mnemoand file bugs if it doesnt work15:08
lesshastethanks15:14
lesshastewill do15:14
alex_mayorgahello, can anyone take a look at Bug #213171 and tell me if is actually the same bug or should I file a new one for my video issues?15:15
ubottuError: Could not parse data returned by Launchpad: The read operation timed out (https://launchpad.net/bugs/213171/+text)15:15
alex_mayorgaups!15:17
alex_mayorgahttps://bugs.edge.launchpad.net/bugs/21317115:21
ubottuLaunchpad bug 213171 in xorg "[i830] Unable to install with GUI on Fujitsu Lifebook C7651" [Unknown,In progress]15:21
alex_mayorgaanyone aware of i830 isues on the intel driver for 9.04?15:47
=== jbarnes_ is now known as jbarnes
alex_mayorgabryce, you around?18:56
bryceyes18:56
alex_mayorgaI'd like to volunteer to get https://bugs.edge.launchpad.net/ubuntu/+bug/213171 fixed18:56
ubottuError: Could not parse data returned by Launchpad: The read operation timed out (https://launchpad.net/bugs/213171/+text)18:56
alex_mayorgaI'll need heaps of guidance though :)18:56
bryceok, well first step is to test against -intel 2.718:57
alex_mayorgais that on the repos?18:57
bryceif you can reproduce the issue on that, then the next step is to file the bug upstream18:57
bryceyou can get it from the x-updates ppa18:57
alex_mayorgaOK, will start there, thanks18:58
brycehere is a link for filing it upstream - https://bugs.freedesktop.org/enter_bug.cgi?product=xorg18:59
brycehowever note that upstream generally does not give much priority to 8xx hardware... still it is worth a try just in case18:59
brycesome additional guidance on analyzing bugs can be found via http://wiki.ubuntu.com/X/19:00
alex_mayorgais there a way to use the intrepid driver?19:00
bryceyes, someone set up a PPA for that - it's linked to from the IntelPerformance troubleshooting page19:04
alex_mayorgaOK thanks that should at least give me my video back19:06
tjaaltonhowdy ho19:07
bryceheya tjaalton19:31
tjaaltonhi bryce19:34
brycehow's the move been going?19:34
tjaaltonalmost over :)19:35
tjaaltononly some stuff left in the old storage room19:36
tjaaltonand the final cleanup of the old place19:36
tjaaltonhow's karmic so far?-)19:42
tjaaltonabout the intel virtual hack; I think Mirv had it set to 2k*2k, and he was immune to these hangs, so it's looking pretty much like a solved case imho19:46
tjaaltonbbl, sauna ->19:47
alex_mayorgabryce, the intel driver at https://edge.launchpad.net/~ubuntu-x-swat/+archive/x-updates didn't help19:50
brycetjaalton: karmic is ok so far; I've set up my pbuilder and switched tools over to it, and done a few merges, but nothing major yet19:51
alex_mayorgayou were saying the intrepid driver is available somewhere, right?19:51
brycetjaalton: I think before I get into it too much I'm going to work on getting the UXA bugs upstreamed19:52
brycealex_mayorga: what was your experience with the 2.7 driver exactly?19:52
brycealex_mayorga: yeah see above19:52
alex_mayorgasame thing, the four quarters of the screen are overlaid in the top-left most quearter19:53
alex_mayorgaand the whole LCD "shakes" a bit to the left and right, really unusable, want a picture?19:53
bryceput the picture on the bug report, yes19:54
bryceit sounds a lot like a modeline issue19:54
alex_mayorgabryce, sorry my pidgin crashed before I could catch the other PPA19:54
bryceif you connect a different monitor to it, does the issue go away?19:54
alex_mayorgahadn't really tried a secondary monitor19:55
brycethe link is on the IntelPerformance page in wiki19:55
brycetest that next19:55
bryceif it is a modeline issue, switching drivers won't make any difference19:55
alex_mayorgajust plug a monitor, that's it?19:55
bryceyeah, plus maybe reboot19:55
alex_mayorgaonly clue I have is that video was perfect on intrepid19:56
alex_mayorgaI seem to have every single one of the WONT work at all video cards19:56
brycewell, go ahead and try the driver if you want, but modelines are calculated in the xserver19:56
alex_mayorgado you remember my geforce go19:56
brycefwiw, there are ways you can manually program modelines19:57
brycebut try attaching a different monitor first19:57
bryceif that doesn't make the issue go away, then no use bothering with modeline stuff19:58
alex_mayorgaOK, let me try to get a monitor from a friend see if that works19:58
brycealternately, you can try switching to a different resolution19:58
bryceeach resolution has a different modeline, so often if you have a modeline bug, it's particular to that one resolution19:58
alex_mayorgaI have to edit xorg.conf for that right?19:59
brycehowever if it is being caused by the display's edid or ddc data, all the resolutions could be borked19:59
bryceto switch resolutions just use xrandr19:59
alex_mayorgaFWIW tty2 is just merry :)20:01
alex_mayorgaxrandr: can't open display20:02
=== Adam is now known as aportier
aportieri was wondering if this is the correct place to come with issues with my intel graphics card20:09
alex_mayorgaaportier, I feel your pain :)20:10
alex_mayorgabut so far I think I'm better of staying on intrepid20:10
alex_mayorgaaportier: what card you've got?20:10
aportieri have an intel aspire one with an intel 945 GME20:11
aportieri have gotten the 2.7 drivers off your ppa and still have slowdown in video playback20:12
aportieri have tried exa and uxa modes on the x11.conf20:12
aportierand migrationheuristic greedy20:12
aportierno success so far20:12
bryceaportier: bug id#?20:12
aportierone sec its on the other pc20:13
aportier31492820:13
aportieri read something about piping a value into the /proc/mtrr but i couldn't understand the information well enough to apply it20:14
brycewhat else have you tried?  newer kernel?20:15
aportierhavn't messed with the kernel20:16
brycehmm, don't see 'aportier' on the lp bug, do you go by a different name there?20:16
aportieri think i subscribed to it, maybe not20:16
aportierits effecting all aspire one users afaik20:16
bryceok, next try 2.6.30-rc3.  It has a number of performance fixes, esp. for issues that still occur when uxa is enabled.20:16
bryceyou can also see the IntelPerformance troubleshooting guide in wiki20:17
aportieris there a ppa where i can get pre compiled kernels20:17
bryceyeah the kernel team's ppa20:17
aportieri will give that a shot, thank you20:18
bryceno prob, good luck20:21
tormodbryce, there is rc4 out now (both in mainline and karmic) with a bunch of intel fixes20:27
mnemodrm for g41 was fixed in rc4 for example20:27
brycegreat20:29
bryceis that now the default kernel?  I set up a chroot but it still though 2.6.28 was the default20:30
alex_mayorgabryce, thanks xserver-xorg-video-intel-2.4 gave my LCD back20:30
tormodbryce: I guess the meta packages are not updated yet. I downloaded the deb.20:31
brycealex_mayorga: wow interesting20:31
alex_mayorgaI'm installing flash to check video performance, but looks as good as it was on intrepid20:31
brycealex_mayorga: if you're still keen on chasing down the fix, now that you have isolated the bug to the video driver, it is possible to do a 'git bisect' to find the exact patch causing the problem20:32
bryceif you do that, then we may be able to get the issue solved in the current version of -intel20:32
bryceotherwise, it's likely that the issue will still be there if you ever want to upgrade20:32
brycetormod: gotcha20:33
brycetormod: I've been accumulating a list of -intel bugs we can close once the kernel updates :-)20:33
alex_mayorgabryce, I'll look into it, sounds like a very educational thing to do :)20:33
brycealex_mayorga: there's a document on how to do it available on wiki.ubuntu.com/X20:34
bryceindeed, it's quite educational ;-)20:34
brycebut with a little stubbornness it's quite effective at isolating problems to their fixes20:35
aportier@bryce: sorry to bother you again, but where would you recommend i get this test kernel? i can't locate it on launchpad20:43
bryce  http://kernel.ubuntu.com/~kernel-ppa/mainline20:44
alex_mayorgabryce, video it's a bit slow, but I'm not complaining, it's a really old laptop20:46
tjaaltonbryce: ok, sounds like a plan21:19
aportierok, back, kernel update did not fix the problem21:19
bryceaportier: ok, have you tried the 2.7.0 -intel driver?21:21
bryceavailable from https://edge.launchpad.net/~ubuntu-x-swat/+archive/x-updates/21:21
aportierrunning it right now21:21
aportierone of the first things i tried21:21
bryceoh right21:21
brycehmm21:21
aportieris there any validity to this /proc/mtrr issue? something you could help me understand a bit better?21:22
bryceok, now can you file a new bug report with this configuration, using the command 'ubuntu-bug xserver-xorg-video-intel', describe what you're experiencing, and give me the bug ID?21:22
bryceyes there is validity to that, did you try making those changes?21:22
aportiermy lspci -vvnn doesn't produce hex addresses for the registers21:22
aportieri get whole numbers21:23
aportierso i don't know what register to update21:23
aportieri tried a-e, no change21:23
bryceok, file a new bug, and describe what you've attempted with mtrr, and I can forward it upstream21:24
bryceI don't know a lot of particulars about mtrr stuff... it's a bit more of a kernel level thing21:25
aportierok, i will open a new bug. should i revert the kernel first, and what log files should i post21:25
mnemoi think basically mtrr's describe the characteristics of a set of memory ranges.. for example they can say "for all RAM memory starting at X up Y the CPU cache must never be used" and similar things21:28
bryceaportier: do it on the 2.6.30 kernel (actually probably won't matter).  If you file via ubuntu-bug it will attach everything needed for now21:29
bryceupstream may ask for more info later on21:30
aportierubuntu-bug is a package?21:30
mnemono its a command21:30
bryceit's a command you run on the command line21:30
mnemoa script that opens launchpad bugs21:30
aportierok cool never used it before21:30
aportierill go ahead and do that21:30
aportierthanks for the help21:31
aportierbug 37055221:57
ubottuLaunchpad bug 370552 in xserver-xorg-video-intel "Slow flash video playback on Intel 945gm" [Undecided,New] https://launchpad.net/bugs/37055221:57
aportierok im going to continue to pick through this on my own, if you guys see something glaring in there, please let me know21:58
aportierthanks again for the help21:58
tjaaltonbryce: so, rtg said that enabling kms "truly wrecks your experience".. do you know what me meant by that?22:00
brycenope22:01
brycesomeone else had tested it and found it doesn't do the plymouth thing but otherwise works22:01
bryceI was going to give it a shot myself and put together a paint-by-numbers guide22:01
tjaaltonjaunty is boring, maybe I should just upgrade..22:01
bryceneed to get a handful of UXA bugs upstreamed first22:02
brycetjaalton: thoughts on updating to newer mesa?22:03
* tormod is bored not having -intel hw to crash22:03
tjaaltonbryce: you mean 7.4.1?22:04
tjaaltonthere should be a 7.5rc next week22:04
brycetormod, tjaalton: ok well feel free to update us to latest whatever you want22:05
brycethe direction we've got for karmic is to go ultra-bleeding edge this time, to get best support for KMS and boottime prettiness22:06
tjaalton7.5 it is then?-)22:06
bryceyep22:06
mnemotjaalton: that reminds me, is it worth for me to prepare a debdiff for this one --> https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/368049   (dänzer already pushed that one to 7.4 stable branch)22:06
ubottuLaunchpad bug 368049 in mesa "compiz crashes gnome desktop using default ati driver (radeon X600)" [Undecided,Confirmed]22:06
tjaaltonnot that it's directly kms related, but22:06
brycetjaalton: we'll have driver dependencies on it22:07
tjaaltonmnemo: guess so22:07
mnemotjaalton: so you wont push 7.4.1 to jaunty then? is that too big/risky maybe?22:07
tjaaltonmnemo: it's not my call22:07
mnemobryce: what do you think?22:08
tormodthey already started mesa 7.6-dev, I guess it will have radeon-rewrite soon. 22:08
brycemnemo: if you put together a debdiff, I'll review and sponsor if it looks sane (as I suspect it will)22:09
mnemook I will do that then22:09
Sarvattglad I waited on -intel tormod, they're pushing some big bug fixes right now :D22:09
tjaaltonmnemo: we haven't done dot-releases-as-sru's before, so it'd need some discussiong before22:10
tjaalton..we do it22:10
tormodSarvatt: nice, hopes it fixes your card22:10
brycemnemo, tjaalton: oh, right, make sure to pull the specific patch that fixes it, not a point release22:10
mnemook22:10
brycethe SRU team never seems to allow putting point releases through22:10
tjaaltonright22:11
mnemowe might still look at the git log in 7.4 stable branch and see if fedora escalated some nice fixes from their releases and then we just package those one by one22:11
tormodthe SRU team won't accept a line of code that doesn't fix a serious bug on launchpad22:11
mnemomakes sense, _especially_ for mesa/xorg stuff22:12
bryceyeah cherrypicking patches that fix issues that we can reproduce in ubuntu or have a bug reporter who can test it to verify the bug exists, is a requirement of the sru team22:12
brycehmm, not sure that's a coherent sentence22:13
tjaalton:)22:13
bryceoh also with mesa, I'm especially cautious in considering patches that affect intel, since it seems to be so fragile - too often a fix seems to cause issues elsewhere22:14
bryceati seems more robust though, so I'm less worried there about mesa patches22:14
tjaaltonafter reading the blog post by keithp I guess that's going to change22:15
mnemoi hope we can get past all this frailty and be rock solid on UXA for the LTS22:17
tormodtjaalton: before you start on mesa 7.5, you might have a look at Sarvatt's upload to xorg-edgers, egl craps out on amd64 but that's maybe an old issue that was taken care of by a Ubuntu patch22:17
brycetjaalton: I've got a bunch of sessions planned for UDS to talk on intel issues22:17
Sarvattahhh shoot, I missed aportier'squestion22:18
SarvattI have an aspire one and you absolutely have to boot with mtrr cleanup and 1 spare reg22:18
bryce(assuming Europe lets us swine-flu-y Usians in)22:18
Sarvatti have to boot with enable_mtrr_cleanup mtrr_spare_reg_nr=1, aspire one has buggy mtrr's by default22:19
bryceSarvatt: ah cool - could you mind giving him some guidance on his bug #?22:19
brycealso, is that something we can sort out on the X side of things, or does it require kernel changes to solve properly?22:19
Sarvatt[    0.000000] original variable MTRRs22:19
Sarvatt[    0.000000] reg 0, base: 4194176KB, range: 128KB, type WP22:19
Sarvatt[    0.000000] reg 1, base: 4194048KB, range: 128KB, type UC22:19
Sarvatt[    0.000000] reg 2, base: 0GB, range: 1GB, type WB22:19
Sarvatt[    0.000000] reg 3, base: 1GB, range: 512MB, type WB22:19
Sarvatt[    0.000000] reg 4, base: 1528MB, range: 8MB, type UC22:19
Sarvatt[    0.000000] reg 5, base: 1526MB, range: 2MB, type UC22:19
Sarvatt[    0.000000] reg 6, base: 1525MB, range: 1MB, type UC22:19
Sarvatt[    0.000000] reg 7, base: 0GB, range: 128KB, type UC22:19
Sarvatt[    0.000000] WARNING: BIOS bug: VAR MTRR 7 contains strange UC entry under 1M, check with your system vendor!22:19
tjaaltonbryce: hehe, it would be a pretty lame uds if they wouldn't22:19
tormodbryce: you will have to wear masks :) revenge for taking all our fingerprints22:20
Sarvattkernel, when I build my kernels I enabled mtrr cleanup and 1 spare to fix it but the command line stuff works22:20
Sarvattreg00: base=0x000000000 (    0MB), size= 1024MB, count=1: write-back22:20
Sarvattreg01: base=0x040000000 ( 1024MB), size=  512MB, count=1: write-back22:20
Sarvattreg02: base=0x05f500000 ( 1525MB), size=    1MB, count=1: uncachable22:20
Sarvattreg03: base=0x05f600000 ( 1526MB), size=    2MB, count=1: uncachable22:20
Sarvattreg04: base=0x05f800000 ( 1528MB), size=    8MB, count=1: uncachable22:20
Sarvattreg05: base=0x060000000 ( 1536MB), size=  256MB, count=1: write-combining22:20
Sarvattthats what i get with 1 spare22:20
tjaaltontormod: hmm, pointer?22:21
tormodtjaalton: to what?22:22
tjaaltontormod: to the bug that xorg-edgers would fix22:22
Sarvattwhat i was just talking a bout with -intel? it's a big compiz fix if so22:23
brycetormod, tjaalton: :-)22:23
tormodtjaalton: it is not fixing something in particular, I was just warning about potential amd64 issue, but as I added, it might be fixed in some ubuntu patch22:24
tjaaltontormod: the vblank one? there aren't any other ones that would matter22:26
tjaaltonand it's not amd64-only22:26
tjaaltonbut with uxa/dri2 we don't have vblank anyway22:26
tormodwe are talking about different things, sorry :)22:26
tjaaltonmaybe22:27
tormodtjaalton: maybe you addressed me by mistake to start with :)22:27
tjaaltontormod: dunno, I'm confused regardless :)22:28
tjaaltonbeen away for "too long" (some weeks..)22:29
tormodbut now that I read your questions again: Sarvatt dropped a vblank patch in -intel, and the same can be done in mesa I guess.22:29
tormodSarvatt: right?22:29
SarvattI readded it22:29
tormodaha22:29
Sarvatt2 people had a problem with it22:29
tjaaltongrr, I hate these 1pix wide window borders22:30
Sarvattwas just mesa I dropped it from, no vblank patch in -intel22:31
tormodSarvatt: re your report 21512, you can get an unoptimized build (and see more variables in the backtrace) with: DEBUILD_BUILD_OPTIONS="noopt debug nostrip" debuild -b -us -uc22:31
SarvattI was going to do that but anholt said the backtraces were useless with the situation I was having22:32
tormodSarvatt: ok I mix up things or remember wrong regarding those patches...22:32
Sarvattlucky because it woulda taken either 2 hours to build locally or 24 hours to build on a ppa to do it :D22:32
tormodSarvatt: 2 hours to build the -intel driver?22:33
Sarvattoh sorry was thinking mesa there since we were just talking about it, now both of us are confused :D22:34
tjaaltonso what bug is it that using vblank would fix?22:34
* tormod goes to bed rather than stir up more confusion22:34
Sarvattthey're talking about it in intel-gfx right now actually22:35
Sarvattbig paste so I'll PM it22:35
tjaaltonpastebin works22:36
Sarvattit's on G45 though which explains why I had no problems without it22:36
tormodSarvatt: the mesa amd64 failure: the log shows some files are built with -fPIC and some not, I don't see why when looking at the Makefile, e.g. eglapi.c vs egllog.c22:50
Sarvattwould uploading it with DH_VERBOSE=1 help figure it out?22:53
Sarvattor is it in the mesa configs22:53
Sarvattweird, every other one isnt using -fPIC22:59
Sarvatttheres a bunch of new egl stuff in configure.ac, could always disable egl couldn't we?23:10
tormodSarvatt: yeah just disable it in confflags-common in debian/rules. I don't think it is even shipped in the debian packaging23:21
Sarvattnope it isnt, nowhere to be found23:22
tormodbut I am curious to that fPIC thing...23:22
Sarvatt/bin/bash ../../../bin/mklib -o EGL -linker 'gcc' -ldflags '' \23:23
Sarvatt-major 1 -minor 0 \23:23
Sarvatt-install ../../../lib \23:23
Sarvatt -lX11   -ldl eglapi.o eglconfig.o eglconfigutil.o eglcontext.o egldisplay.o egldriver.o eglglobals.o egllog.o eglhash.o eglmisc.o eglmode.o eglscreen.o eglstring.o eglsurface.o eglx.o23:23
Sarvattmklib: Making Linux shared library:  libEGL.so.1.023:23
Sarvattneed to add it to the static lib list in the configs maybe?23:24
tormodbut you don't see libEGL in the debian/*.install files23:24
Sarvattits auto detecting that we have egl and enabling it in the configure stage it looks like23:24
Sarvattdnl23:28
SarvattAC_ARG_ENABLE([egl],23:28
Sarvatt    [AS_HELP_STRING([--disable-egl],23:28
Sarvatt        [disable EGL library @<:@default=enabled@:>@])],23:28
Sarvatt    [enable_egl="$enableval"],23:28
Sarvatt    [enable_egl=yes])23:28
Sarvattif test "x$enable_egl" = xyes; then23:28
Sarvatt    SRC_DIRS="$SRC_DIRS egl"23:28
tormodsrc/egl/main/Makefile treats all those files the same, the CFLAGS should be the same, yet some have fPIC and some not.23:29
tormodthat snippet checks for your --disable-egl in confflags-common23:29

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