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

=== jcristau_ is now known as jcristau
=== tseliot1 is now known as tseliot
=== mac__v is now known as mac_v
johnf1911a friend of mine is having a problem with the intel X driver on karmic16:04
johnf1911sometimes, after suspend and resume, his display doesn't come back16:04
johnf1911like it stays suspended16:04
johnf1911this is on a lenovo X200s16:05
johnf1911in dmesg, we get this lovely output16:05
johnf1911http://paste2.org/p/50066416:05
johnf1911this is where the fun starts: INFO: task i915/0:358 blocked for more than 120 seconds.16:05
johnf1911we can ssh into the system after the failure16:06
johnf1911though killing X still doesn't appear to solve the problem, it doesn't successfully restart16:06
johnf1911bryce: ^ jcastro suggested you might be able to help16:08
johnf1911one final item of note, the machine has two displays, and internal one as well as a second connected via "HDMI" (actually displayport in the ultrabase to a DVI converter to a panel)16:14
johnf1911both displays blank when we have the issue16:14
tseliotjohnf1911: can you reproduce the problem when the external screen is not connected?16:21
johnf1911hmm16:22
johnf1911I'll ask him to remove the screen and test16:22
tseliotit looks like it's failing to read EDID16:22
tselioti2c-adapter i2c-2: unable to read EDID block.16:22
tselioti915 0000:00:02.0: HDMI Type A-1: no EDID data16:22
johnf1911I take it there are known problems like this one?16:22
johnf1911those messages are a long time before the error16:22
johnf19113840seconds after boot versus 4016:23
johnf1911I don't believe that's related, it's probably at gdm/X startup16:23
tseliotif you want to get modes you usually try to get EDID first16:24
tseliotalso your /var/log/Xorg.0.log should have interesting information (after reproducing the problem)16:25
johnf1911there's nothing in Xorg.0.log16:45
johnf1911when he runs the machine at home, without the second display, he's never seen the issue16:46
johnf1911he's going to explicitly test it tonight to be sure though16:46
johnf1911so it may be related to dual head16:46
tseliotok16:58
tseliotjohnf1911: also it would help if he could follow these instructions: https://wiki.ubuntu.com/X/Backtracing#Using Screen to get backtraces for Suspend/Resume crashes17:03
johnf1911ok17:05
johnf1911if it crashes again today (seems to be once every 2 days, though it may relate to how often he's away from his machine) we'll do that17:06
johnf1911I think he's disabled display suspending17:06
johnf1911so if it's related to that we won't have a crash, but we will know that it may be related17:06
johnf1911thanks for your help17:06
tseliotnp17:15
=== marjomercado is now known as marjo
tormodjcristau, what are the rules (or best way) when upstream ships no configure, run autoreconf in debian/rules and/or add the generated files to orig.tar.gz?18:52
brycetormod, autoreconf is likely better19:02
tormodbryce, ok but I see sometimes generated stuff added to the tarball, and googled up some comments about being able to build the package on a less equipped system and so on19:04
tormodyou know it's Debian when they talk about end-users running configure :)19:04
bryceheh19:05
brycewell, the autoreconf stuff would be run on the build system, not on the user's system (if I'm understanding the issue right)19:06
bryceyeah I've been known to just redo the tarball with the config stuff in it myself, however I consider that pretty kludgy19:06
hyperairtormod: autoreconf in debian/rules prior to configure, make maintainer-clean afterwards in the clean rule of debian/rules19:07
hyperairi think that's the general approach19:07
hyperairor rm -rf Makefile.in after make distclean19:07
brycethe debian way is to ship the tarball as distributed by upstream, with no changes19:07
tormodbryce, that's what I have heard also, but not what I have seen19:07
tormodjcristau, if you have time to review, it is about http://git.debian.org/?p=collab-maint/intel-gpu-tools.git;a=summary19:34
tormodRAOF, are your nouveau packages just upstream git + last ubuntu packaging?21:25
tormodRAOF, ddx I mean21:25
RAOFtormod: Yes they are.22:30
RAOFActually...  let me check the changelog. :)22:30
RAOFtormod: Yes, yes it is.  The DRM component isn't, but the DDX is.22:31
tormodRAOF, then I can just add it to my auto-xorg-git/update-ppa job22:35
tormodthe only catch is the version, you used git+2009, auto-xorg-git uses git2009 :)22:36
tormodI can add a tweak for that to my nightly script and drop it when we have 0.1122:36
hyperairtormod: you've got a nightly git building script?22:37
hyperairmay i see?22:37
hyperairi might be able to use a few parts for my banshee daily script22:37
hyperair(which doesn't handle anything other than karmic atm)22:38
RAOFtormod: Sweet.  I was meaning to automate the nouveau uploads at some point, I just haven't got around to it.22:38
tormodhyperair, it uses the auto-xorg-git so it will probably not help much for banshee22:39
tormodand I still have to run it and type in my gpg key22:39
hyperairah22:39
hyperairi've solved my gpg problems ;-)22:39
hyperairwith a little help from seahorse and alarm-clock-applet22:39
tormodwell since I use my personal gpg key it is not a problem but a feature that I have to enter it :)22:40
* hyperair pulls out the auto-xorg-git script from bzr22:40
tormodbut I would use a more loose key for some autobuilder thingy22:41
hyperairtormod: well yes, i have to enter my passphrase as well. i just got it automated in the sense that it'll automatically run and prompt me22:41
hyperairalarm-clock-applet inherits the GPG_AGENT_INFO from my gnome-session and runs the script at midnight, then seahorse bugs me for the passphrase22:41
tormodhyperair, sure,  I have all that set up, and I use the seahorse(?) caching so I only type it once22:42
hyperairah. haha22:42
tormodfor anyone curious this is the script I run (almost) every night to keep xorg-edgers up to date: http://ubuntu.pastebin.com/m64eaaf6922:43
hyperairah auto-xorg-git manually creates the tarball eh22:43
tormodI guess I will push it to the bzr repo as well22:44
hyperairhmm interesting22:44
* hyperair uses git-buildpackage to build tarballs22:45
tormodI got quite a bit of things automated there that took hours in the early xorg-edgers days22:45
hyperairthat's cool22:46
tormodhyperair, we could maybe use git-buildpackage here also, but it works as it is22:46
hyperairyeah22:46
pwnguineventually, you guys are gonna reinvent gentoo22:47
hyperair?22:47
hyperairwhy so?22:47
hyperairhttp://pastebin.com/f660a0a8 <-- this is my banshee building script22:47
tormodpwnguin, we publish binaries...22:47
hyperairpwnguin: by building we really mean preparing source packages to upload22:48
pwnguinbuild everything from git head source22:48
pwnguini know22:48
hyperairthe difference is that we have our binaries all built in one place22:48
pwnguinthats how it starts22:48
hyperairso users don't have to go about wasting the world's precious energy compiling22:48
pwnguinthen one day someone decides they want to override the C FLAGS env var22:48
hyperairunlike gentoo users >_>22:48
tormodpwnguin, we stay close to the normal distro packaging, no CFLAGS tweaking etc22:50
hyperairthat's when they switch to gentoo. ubuntu will never become a source-based distro.22:50
brycehyperair, I think we lack sufficient drama to reinvent gentoo22:50
hyperairbryce: strongly agree. =P22:50
tormodhyperair, some nice use of git log in your script, instead of my sed/awk hackery22:51
hyperairtormod: hahah thanks.22:51
hyperairwell i've no idea how to use awk =p22:52
hyperairso i kinda make do with sed22:52
pwnguinthat never stops anyone22:52
hyperairwell yes, there are great possibilities with sed.22:52
* hyperair has never needed to learn awk22:52
pwnguinSome people, when confronted with a problem, think22:53
pwnguin“I know, I'll use regular expressions.”   Now they have two problems. 22:53
tormodRE rulez22:53
hyperairxD22:54
hyperairthat's a nice quote.22:54
pwnguin    “If you have a problem and you think awk(1) is the solution,22:54
tormodit's the cellular automata of information processing22:54
pwnguin    then you have two problems.” 22:54
hyperairbut yeah, RE rules.22:54
hyperairpwnguin: then it's the same, isn't it? =p22:54
tormodok enough fanboying22:54
pwnguinhyperair: predates RE22:55
pwnguin"      make(1) is employed sparingly for very simple scripts. sed(1) only required to deal with yacc(1) defi-"22:55
pwnguinciency, namely eliminating name clashes. awk is used once in the bootstrap to perform a relatively simple task22:55
pwnguinthat should probably be done using ed(1), since: ‘‘If you have a problem and you think awk(1) is the solution,22:55
pwnguinthen you have two problems.’’ - David Tilbrook22:55
pwnguindoh22:55
pwnguini'll stop22:55
hyperairheheh22:55
hyperairhmm i should probably make better use of set -e in my script22:59
hyperairrather than those kludgy || return 1s22:59
tormodhyperair, or at least chain them with &&23:01
tormodbryce, I was thinking I would help out with bringing mesa git up to date23:13
tormodI looked at bzr-fast-export and git-fast-import but could not really get it working so I scripting up something else23:13
brycetormod, that would be great23:14
brycefwiw, I probably won't be much help with xorg-edgers this cycle; I suspect for the LTS our eyes are going to be too far behind bleeding edge23:15
tormodbryce, won't be done today, but I hope to get it done over the weekend23:16
brycekewl23:16
tormodbryce, ok but please try to push radeon KMS23:16
bryceyep that's the plan23:16
tormodalthough not officially EOL'ing it, upstream seems to care less about non-KMS issues23:16
* bryce nods23:16
tormodbut you are aiming for mesa 7.7 at least?23:17
brycenot decided yet23:17
bryceif it makes it by the end of the year, quite possibly23:19
bryceif it's late into next year, though, we may have to pass23:19
tormodxorg 7.5 (and xserver 1.7) I guess since it's already in Debian23:19
bryceyeah I think we'll be looking very strongly at what is in Debian Testing at chrismastime23:20
tormodso you are not gonna sync everything in experimental at this point?23:21
tormodI mean if there are things there which might not make it for Testing before Xmas23:21
brycedunno yet, I'm still kind of consumed by karmic stuff at the moment23:26
brycebut I definitely intend to be more conservative this time through23:26
brycethere's trade offs though23:27
brycethe goal of LTS is not to have ancient stuff but rather to have stable stuff that can be supported well going forward23:27
brycein some cases the bleeding edge stuff *is* the best choice as it's gotten the most debugging and is more likely to be relevant upstream23:27
brycein other cases where a lot of development work has gone on compared with the level of testing, it may be safer to hold back a bit23:28
bryceat this point I'm not sure where the line needs drawn, component by component, and I hope folks can help give good advice so we can make smart decisions on all of this23:28

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