/srv/irclogs.ubuntu.com/2012/07/30/#ubuntu-x.txt

tjaaltonRAOF: so, 1.13 is not in -proposed yet?05:11
RAOFtjaalton: No; I got part-way through and then stalled on fixing up -ati. I didn't want to upload until I'd tested that it at least brings up a server on -ati, -intel, and -nouveau.05:13
tjaaltonok, cool. I have -intel to test on05:14
tjaaltonthough I bet you do as well :)05:14
RAOFAnd this morning someone wanted help fixing up pointer barriers for Fedora! I couldn't possibly go past helping them out a bit so I don't have to :)05:14
tjaaltonmagcius?-)05:15
RAOFYeah05:15
RAOFAre you back from your holiday?05:16
tjaaltonyup :( :)05:16
tjaaltonjust when it got hot05:17
tjaalton(lowest during the night was 22C)05:18
RAOFOooh, urgh.05:18
RAOFThat is incorrect.05:18
RAOFYou should tell the weather to try again; this time, it failed.05:18
tjaaltonhehe, yeah05:19
tjaaltonwell, there are still the weekends fully packed with activities, so there's time to get some of the "lost weather" back05:19
tjaaltonit has been quite rainy and cool most of the july05:20
mlankhorstmorning07:42
mlankhorstoh new intel drivers08:08
mlankhorstRAOF: how's uploading going? I just pushed intel 20.2 update08:14
akheronhey08:14
akheronI'm trying to find out why my X server crashes every now and then when waking from suspend08:15
mlankhorstheya08:15
mlankhorstf08:15
mlankhorstoops08:15
akheronI've got one crash dump that shows it segfaults on free() in Xi/xiproperty.c, in function XIDeleteAllDeviceProperties08:16
mlankhorstthat usually means memory corruption, can you try running X with valgrind?08:16
akheronmlankhorst: sure, how?08:16
mlankhorstsec08:16
mlankhorstcreate a script /etc/X11/X2 with these contents08:17
mlankhorst#!/bin/bash08:17
mlankhorstexec /usr/bin/valgrind --track-origins=yes --leak-resolution=high --malloc-fill=ef --free-fill=df /usr/bin/Xorg "$@" -verbose 10 &>>/home/yourusername/xorg-valgrind.log08:17
mlankhorstmake it executable08:17
mlankhorstthen remake the /etc/X11/X symlink, point it to /etc/X11/X208:18
mlankhorstthen just restart lightdm :)08:18
mlankhorstto restore, sudo ln -sf /usr/bin/Xorg /etc/X11/X08:18
akheronok, let's try08:19
akheronyeah, now running in valgrind08:23
mlankhorstit's more useful if you install xserver-xorg-core-dbg and xserver-xorg-input-(evdev,synaptics)-dbgsym08:24
akheronwhat apt source I need for the -dbgsym packages?08:25
mlankhorsthttps://wiki.ubuntu.com/DebuggingProgramCrash/ see Debug Symbol Packages08:25
akheronah yeah, without those the stack traces show ???08:26
mlankhorstyeah for quantal I made -dbg packages so you would no longer need to enable that repo to debug most of X :)08:27
akheronheh08:27
akheronwill I need a dbgsym package for the intel driver too?08:28
akheronintel_drv.so08:28
mlankhorstif it shows up it would help08:28
mlankhorstsame for libdrm08:29
akheronyeah, both seem to show up08:29
akheronthis will take some time, as the crahs doesn't occur every time when waking from suspend08:30
akheronusually once every two days08:30
akheronor so08:30
tjaaltonwhat do you mean by a 'crash'?08:32
tjaaltonyou get the login screen?08:32
akherontjaalton: yes08:32
tjaaltonok08:32
akheronactually I'm not sure if it's always when waking from suspend08:33
akheronsometimes the machine won't suspend and I get a login screen, so it happens when going to suspend08:33
akheronhmm, I still get ???'s from intel_drv.so08:40
mlankhorstxserver-xorg-video-intel-dbg ?08:41
mlankhorstand maybe libdrm.*-dbg08:51
akheronmlankhorst: nope, I still get ???'s09:53
RAOFmlankhorst: I'm a bit confused by -ati and -evdev, but mostly evdev. What happened to 0005-fix-horiz-scrolling.patch  0006-axis-label-overrun.patch? They got added to a commit? And the git log is confusing; it's not a pre-sync to debian-experimental - there are still significant differences.10:41
mlankhorsthm you're right, i wanted to sync evdev but they didn't want the patches, so no longer valid10:42
RAOFYeah.10:44
RAOFIt's probably also worth dropping the explicit depends on xserver-xorg-core; we don't need them.10:44
mlankhorstRAOF: well I mesed up on evdev, first patch has to be manually unapplied with patch -Rp1, then you get the stable release again, to build against10:44
RAOFmlankhorst: Hm, ok.10:44
mlankhorstbuild system will reapply the patch10:44
mlankhorstati.. let me check10:44
RAOFYeah.10:45
RAOFati doesn't have an orig.tar.gz; there's no xf86-video-ati 6.99.99 release (right?), so it should have a ~git version so we can bump it if we want to grab a newer snapshot.10:46
mlankhorstyeah10:46
RAOFAlso, I was also confused by the rationale; you said you grabbed a newer snapshot for some UMS fixes, but this is a kms-only release?10:47
mlankhorsterm I meant it removes UMS, but there were some X server fixes after that that we need for building against x1.1310:48
RAOFAaah. Ok, that makes sense.10:48
mlankhorstbut yeah I didn't know yet if I wanted to do another pull or not so I just set version to a stub10:50
RAOFHEh.10:51
mlankhorsteverything more clear now? :)10:52
RAOFSo, another general comment - when pre-merging from Debian, it's nice if you include the (possibly incomplete) Debian changelog (complete with UNRELEASED), then add the Ubuntu changelog on top.10:53
RAOFYeah, everything more clear now. You could have committed the version number at the time you committed, though. There's no reason you can't change the version if you decide you need a newer pull ;)10:53
mlankhorstaye but at that time I still had to update 25-ish other drivers, decided it was more easier not to handle everything as special if I could10:54
RAOFFair enough.10:54
mlankhorstit's different if I just update -ati or -all10:55
mlankhorstbut I would rather have the new stack soon, I want to do a new push of the x-1.13 ppa, but for precise renamed, to test the mechanics I want to propose11:00
RAOFYeah. Now that's cleared up, I'll punch through it (tomorrow)11:03
mlankhorstgreat :)11:03
mlankhorstoh looks like new libXrandr landed too11:06
akheronmlankhorst: now it crashed11:45
akheronvalgrind: m_mallocfree.c:288 (get_bszB_as_is): Assertion 'bszB_lo == bszB_hi' failed.11:45
akheronvalgrind: Heap block lo/hi size mismatch: lo = 80, hi = 0.11:45
akheronThis is probably caused by your program erroneously writing past the11:45
akheronend of a heap block and corrupting heap metadata.  If you fix any11:45
akheroninvalid writes reported by Memcheck, this assertion failure will11:45
akheronprobably go away.  Please try that before reporting this as a bug.11:45
akheronthere are 52 invalid writes in the valgrind log :/11:46
mlankhorstWow, you managed to crash valgrind with invalid memory access? Amazing!11:55
mlankhorstI genuinely didn't know you could do that :011:55
akheron:)11:56
akheronthe crash always happens after this log line:11:57
akheron(--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found11:57
mlankhorstjust dump the full log somewhere11:57
akheronmlankhorst: https://gist.github.com/320642911:58
mlankhorstwhat version of synaptics are you using?11:59
akheronmlankhorst: xserver-xorg-input-synaptics      1.6.2-1ubuntu1~precise112:01
mlankhorstcnd: Arghhhhh synaptics is corrupting in that log again, updatetouchstate out of bounds, this time in the other direction12:02
akheronso this is a somewhat known prob?12:04
mlankhorstI don't know, I can silence some warnings12:04
mlankhorstone of the valgrind warnings there is known at least but I didn't isolate it to causing a crash, give me a sec12:06
akheronmlankhorst: ok, no hurry12:07
akheronI've had this issue for a long time12:07
akherononly now it started irritating me enough to look at it :)12:08
mlankhorstok how good are you with packaging? can send you a patch or updated package to test12:09
akherondpkg-buildpackage :)12:09
akheronso yes, I believe I can build and install a package12:10
akheronif you send a patch12:10
mlankhorstok sure12:10
mlankhorsthttp://people.canonical.com/~mlankhorst/229-strip-mode-pointer.patch this will shut up some warnings at least12:11
mlankhorstif I backported it correctly, but I suspect it will not fix things enough12:12
akheronI'll have a try12:16
akheronthanks12:16
mlankhorsthow long has this been happening though, new breakage or old?12:18
mlankhorstwell, before july or after?12:18
akheronmlankhorst: before12:44
akheronI got this machine on february, and first used debian with gnome 312:44
akheronit had odd bugs (with synaptics) so I decided to try ubuntu12:45
akheronand ubuntu crashes :)12:45
akheronI installed it maybe two months ago, and the problem has been there all the time12:45
mlankhorstok12:46
akheronthe package is building now, btw12:46
mlankhorstelse I was thinking the security update but I guess we could rule it out then12:46
akheronmlankhorst: yah, certainly not the last update12:52
akheron*yeah12:52
mlankhorstif it still crashes one more time, which is likely, please update synaptics http://people.canonical.com/~mlankhorst/synaptics-dbg.patch , but I want to rule this issue out first :)12:52
akheronmlankhorst: ok12:53
mlankhorsta lot of valgrind errors should be gone at least12:53
akherontoo bad the only way to reproduce seems to be to suspend and resume 20 times...12:53
mlankhorstyou're helping a lot of others, I can't seem to reproduce it :)12:54
akheronnow running 2:1.11.4-0ubuntu10.7~ppa :)13:04
mlankhorstwhat if you touch keypad during suspend, ?13:05
mlankhorstwell, during start or end of suspend13:05
akheronmlankhorst: that sometimes makes it crash13:20
akheronbut I'm not sure13:20
akheronthe last time, for example, it crashed about 5 sec after fully waking up13:20
mlankhorstakheron: can you give a valgrind log from that and then patch synaptics?13:21
akheronmlankhorst: that's the valgrind log I gave you13:22
mlankhorsterm I just want to see if other errors are gone now :)13:24
akheronmlankhorst: and now with the xserver-xorg patch, I still get the same invalid writes in UpdateTouchState13:24
akheronah13:24
akheronI'll post a new log, though i didn't crash yet13:25
akherona sec13:25
mlankhorstwell the nice thing about the Xorg valgrind hook is that it records all attempts previously13:25
mlankhorstso it doesn't wipe the log on X server restart13:26
cndmlankhorst: remember we reverted a patch in precise13:26
cndwithout those patches we will get touch update corruption I think13:26
mlankhorstok13:27
akheronmlankhorst: https://gist.github.com/320689113:27
akheronin this one, I suspended & resumed once13:27
mlankhorstsigh looks like I have to figure out that failure, then13:27
akheronthe errors are there but no crash yet13:27
akheronnow I'll gotta go13:28
akheronwill try the synaptics patch late today or tomorow13:28
mlankhorstcnd: Sigh so really the only way to fix it is to find out why the whole patch series crashes on the backported input stack?13:28
cndyeah13:28
mlankhorstit's a simple null pointer dereference, but how it gets there makes no sense to me13:28
cndhmm13:29
mlankhorstand upstream was unaffected, let me see if I can find the packages I was using again13:31
mlankhorstcnd: this was why it didn't make sense to me btw13:59
mlankhorst(0x009508d0 in ActivateKeyboardGrab (keybd=0x21d2fd10, grab=0x220cfd80, time=..., passive=0) at ../../dix/events.c:161613:59
mlankhorst(gdb) print *keybd13:59
mlankhorst$1 = {public = {devicePrivate = 0x21c918a8, processInputProc = 0xa4cda0 <ProcessKeyboardEvent>, realInputProc = 0xa4cda0 <ProcessKeyboardEvent>, 13:59
mlankhorst    enqueueInputProc = 0x947bf0 <EnqueueEvent>, on = 0}, next = 0x0, startup = 1, deviceProc = 0x649aa0, inited = 1, enabled = 0, coreEvents = 4, 13:59
mlankhorst  deviceGrab = {grabTime = {months = 0, milliseconds = 1328245}, fromPassiveGrab = 0, implicitGrab = 0, activeGrab = 0x21d28ad8, grab = 0x0, 13:59
mlankhorst    activatingKey = 0 '\000', ActivateGrab = 0x950750 <ActivateKeyboardGrab>, DeactivateGrab = 0x950570 <DeactivateKeyboardGrab>, sync = {frozen = 0, 13:59
mlankhorst      state = 0, other = 0x0, event = 0x21d30270}}, type = 3, xinput_type = 96, name = 0x21d304a8 "SynPS/2 Synaptics TouchPad", id = 14, key = 0x0, 13:59
mlankhorst  valuator = 0x21d30ad8, touch = 0x21d326c8, button = 0x21d30580, focus = 0x0, proximity = 0x0, kbdfeed = 0x0, ptrfeed = 0x21d32568, intfeed = 0x0, 13:59
mlankhorst  stringfeed = 0x0, bell = 0x0, leds = 0x0, xkb_interest = 0x0, config_info = 0x21d304c8 "udev:/sys/devices/platform/i8042/serio1/input/input7/event7", 13:59
mlankhorst  unused_classes = 0x0, saved_master_id = 0, devPrivates = 0x21d2ff78, unwrapProc = 0xa4ac50 <xkbUnwrapProc>, spriteInfo = 0x21d2ff5c, master = 0x21bbfed0, 13:59
mlankhorst  lastSlave = 0x0, last = {valuators = {683, 384, 0 <repeats 34 times>}, numValuators = 4, slave = 0x0, scroll = 0x21d30bf0, num_touches = 2, 14:00
mlankhorst    touches = 0x21d32c10}, properties = {properties = 0x21d34a10, handlers = 0x21d34a48}, transform = {m = {{0, 0, 0}, {0, 0, 0}, {0, 0, 0}}}, 14:00
mlankhorstwhy is it in processkeyboardevent for a touchpad?14:01
cnddon't know off the top of my head14:01
cndbut it may be correct14:01
cndas odd as that sounds14:01
mlankhorstok14:01
mlankhorstbut spriteinfo was freed at that point, so that seems to be what it's dereferencing14:03
mlankhorstare grabs supposed to be possible on disabled devices?14:05
cndseems odd14:24
cndI wish I could help out more, but I'm fighting a huge fire elsewhere right now :(14:27
mlankhorstyeah it's the gimp crash14:31
mlankhorstblindly looking through diff, isfloating seems to have added a check for !IsMaster(dev) upstream14:46
mlankhorstother than that, tons of code churn from c99 initializers :/14:50
mlankhorstok admitting defeat, I don't understand the input stack :)15:17
=== shadeslayer is now known as shadeslayer_
=== shadeslayer_ is now known as shadeslayer
akheronmlankhorst: so I have no hope? :)18:21
mlankhorstakheron: you do, you could go back to previous server-xorg 10.518:21
mlankhorstbut there's a crash you can trigger in that case18:21
akheronwhat crash?18:22
mlankhorstbug #102151718:22
ubottuLaunchpad bug 1021517 in xorg-server (Ubuntu Precise) "Xorg-server crashes reproducible with GIMP usage" [High,Fix released] https://launchpad.net/bugs/102151718:22
akheronuh18:24
mlankhorstakheron: the fun of having a weird stack :/18:25
akheronwell, if there's anything I can do... or should I switch to quantal? :)18:28
akheronwould it help if I patched synaptics now?18:29
mlankhorstit might :)18:34
mlankhorstwould at least enable more debug info18:34
akheronmlankhorst: 18:46
akheron../../src/synaptics.c: In function 'UpdateTouchState':18:47
akheron../../src/synaptics.c:3126:35: error: 'struct SynapticsHwState' has no member named 'num_slots'18:47
akheron../../src/synaptics.c:3127:69: error: 'struct SynapticsHwState' has no member named 'open_slots'18:47
mlankhorstprobably wrong member then, it should be clear from the code which one shouldbe used there but its end of workday and I have a headache :)18:48
akheronheh18:48
akheronmlankhorst: ok, got it to work18:53
akheronbut how to build the .ddeb now?18:54
mlankhorst-nc18:54
akheronnow it crashes19:00
akheron(--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found19:00
akheronBUG: triggered 'if (priv->num_active_touches >= hw->num_mt_mask)'19:00
akheronBUG: ../../src/synaptics.c:3120 in UpdateTouchState()19:00
mlankhorstthought BUG_WARN was meant to be non-fatal19:00
akheronand then a segfault without printing the "Dumping slot state" message or anything else19:00
mlankhorstah well just remove that line 19:01
akheronmlankhorst: 19:08
akheron(--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found19:08
akheron(EE) synaptics: SynPS/2 Synaptics TouchPad: Dumping slot state:19:08
akheronBacktrace:19:08
akheron==24744== 19:08
akheron==24744== Process terminating with default action of signal 11 (SIGSEGV)19:08
akheron==24744==  General Protection Fault19:08
akheron==24744==    at 0x67BD801: __fprintf_chk (fprintf_chk.c:28)19:08
akheron:>19:08
mlankhorst oh right19:08
mlankhorstvalgrind doesn't like that kind of thing19:09
mlankhorstright just leave it be for now, I'll get back to you :)19:09
akheronok19:09

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