/srv/irclogs.ubuntu.com/2010/01/22/#ubuntu-arm.txt

=== bjf is now known as bjf-afk
=== asac_ is now known as asac
asacmoin moin08:10
ograyawn yawn08:38
cooloney_asac: ogra morning guys08:39
=== cooloney_ is now known as cooloney
ogracooloney, hey, thanks for poking the NIC issue :)08:40
asacdmart: there?08:40
asachi cooloney08:40
cooloneyogra: no problem, i got no clue about that, so asked for help. heh08:42
ogragah, seems i dont het uboot off my back today ...08:43
ogra*get08:43
ograasac, no go for the NIC fix09:34
asachuh?09:54
asacogra: thought you ignore that until we get input from fsl09:54
ograasac, FSL attached a patch to bug 507887#10:19
ubot4Launchpad bug 507887 in uboot-imx "NIC not properly initialized in uboot code" [High,Confirmed] https://launchpad.net/bugs/50788710:19
ograbut seems its only half the fix10:20
asacogra: cool. and not ;)10:26
ograright10:26
ograthere were 3 patches overall attached to three bugs10:26
ograsadly none for the MMC issue and all of them against 2009.0810:26
ograso nothing that helps us10:27
ograthe L2 fix looks intresting though10:27
asacthe NIC patch looks simple enough10:27
asacto check if it would work on .0110:27
asacwhere is the L2 patch attached?10:27
ogramail10:28
ograthe NIC patch doesnt work10:28
ograas i said above (and in teh bug), we seem to miss the actual patch that implements the function10:28
asacheh. can you reply in bug and to mail?10:29
ograi did10:29
ograwell, not by mail though10:29
asackk10:30
ograsee commants 3,4 and 5 on bug 50788710:30
ubot4Launchpad bug 507887 in uboot-imx "NIC not properly initialized in uboot code" [High,Confirmed] https://launchpad.net/bugs/50788710:30
=== dmart is now known as Guest46463
=== Guest46463 is now known as dmart
ografsck from util-linux-ng 2.1613:48
ograe2fsck 1.41.9 (22-Aug-2009)13:48
ogra/dev/sda6: clean, 146136/2321984 files, 948823/9277521 blocks (check deferred; on battery)13:48
* ogra pokes his babbage with a pointy stick ...13:49
ograyou got no battery you darn thing !!!13:49
ograogra@babbage2:~$ sudo cat /proc/apm13:51
ogra1.13 1.2 0x02 0xff 0xff 0xff -1% -1 ?13:51
ogramumble13:51
asacbug 45665914:24
ubot4Launchpad bug 456659 in linux-fsl-imx51 "suspend/resume failure on imx51" [High,In progress] https://launchpad.net/bugs/45665914:24
asacbug 48826714:25
ubot4Launchpad bug 488267 in ffmpeg "ffmpeg should be built with -marm for lucid on armel" [Low,Fix released] https://launchpad.net/bugs/48826714:25
=== bjf-afk is now known as bjf
ogracooloney, do you know if the FSL kernel patches change anything wrt /proc/apm output ?15:16
asachttps://wiki.ubuntu.com/MobileTeam/ReleaseStatus/Lucid15:28
asacogra: plars: GrueMaster: persia: dyfet: ^^15:28
ograasac, i think the fact that we have an outdated uboot is also RC (if RC means release critical :) )15:29
ograi.e. i doubt we'll ever get a fix for the MMC issues for 2009.01 ... so i think they should still be on release team radar15:30
ogra(which in turn enforces us to update to .08)15:30
asacogra: well. thats covered15:30
asacor do we have a bug for that?15:31
asacimo its well covered by the other two problems15:31
asacwhich reminds me that i should RC the other bug if its not yet15:31
ograwe have a bug for the MMC issue15:31
ogranot for "hey we chose an old version" :)15:31
asacogra: can you target for lucid + milestone alpha-315:31
asacand gimme bug id ;)15:31
* ogra digs15:31
ograBug 50676115:32
ubot4Launchpad bug 506761 in uboot-imx "lucid uboot hangs on fatload uImage on fsl TO2 TO2.5 and TO3" [Medium,Confirmed] https://launchpad.net/bugs/50676115:32
asacthx15:32
asacogra: why is that wontfix for lucid?15:33
asacthat demotes that to non-RC ;)15:33
ograuh15:33
* asac changes that15:33
asacalso its medium ;)15:33
asacthats overly polite -> critical now15:33
ograyou did set the Wontfix :P15:34
ograand the Medium :)15:34
asacreally?15:34
asacouch15:34
asacoh... maybe when i thought that the paritioning was good enough15:34
ograright15:34
ograright after the commant about partitioning15:34
asacogra: the version revision thing is not RC?15:35
ograbecause it "doesnt block release"15:35
ogranot for now imho15:35
asacdyfet: did busybox -marm work?15:35
ograas long as FSL stands to their promises and we get a fixed release15:35
asacyeah15:35
asacok15:35
dyfetasac: yes15:36
ograasac, i'm about to upload busybox15:36
dyfetasac: already posted for sponsor15:36
ograBug 51119715:36
ubot4Launchpad bug 511197 in busybox "fails to build on arm lucid (thumb2)" [Undecided,Confirmed] https://launchpad.net/bugs/51119715:36
asacdyfet: where?15:36
ogragot that in my queue ...15:36
asacah in the bug15:36
asacjust ping me here ;)15:36
ograjust didnt get to it yet15:36
asaci read bugmail at most twice a decade :-P15:36
asaclol15:36
ograasac, dont worry, i need some sponsoring points anyway ;)15:37
ograasac, did you talk with doko about Bug 417009 (shipping the jaunty libgcc_uno.so15:38
ogra)15:38
ubot4Launchpad bug 417009 in openoffice.org "all openoffice apps die in 'com::sun::star::ucb::InteractiveAugmentedIOException' on armel in karmic" [High,Confirmed] https://launchpad.net/bugs/41700915:38
ograits still "confirmed" so i assume we still ship the hack15:39
ograasac, if you want the hack gone that should be on our list15:40
asacogra: talked to doko about this today15:43
ograah, good15:43
ogradoes he see a chance to get that fixed ?15:43
asache said its not RC if we ensure that we build it again from fresh sources15:43
asacaka the lib15:43
ograwell, we still ship old crap :)15:44
asacnot RC because the fix is so unlikely, that it doesnt make sense to stirr up release team15:44
ograok15:44
asacplars: so after talking to doko about python dove killage, he mentioned that python wasnt even build in lucid yet, so maybe the python2.6 package that is building right now, will help15:44
ografsck from util-linux-ng 2.1615:50
ograe2fsck 1.41.9 (22-Aug-2009)15:50
ogra/dev/sda6 has been mounted 40 times without being checked, check forced.15:50
ograPass 1: Checking inodes, blocks, and sizes15:50
ograGEEZ !!!!15:50
ograi only added a printf !15:50
ograwhy the heck does it not think its on battery anymore °!15:50
* ogra reboots again15:51
asacogra: wrong negation? feels ok if it doesnt think its on battery ;)15:52
asacunless you have a battery :-P15:52
asacoh15:52
* asac should read more backlog15:52
asacgood15:52
ograwell, you saw the code before15:52
asacogra: do you get a warning during build?15:52
asaclike missing prototype?15:52
ograi just added a printf to print out the value of the ac15:52
ogranope15:52
asacso stdio is probably included ;)=15:52
asac?15:52
asacok15:52
ogralets see, probably it was actually an enforced check because 40 mounts were done15:53
asacdoes it build with all warnings?15:53
asacmaybe15:53
ogramountall: Could not connect to Plymouth15:53
ografsck from util-linux-ng 2.1615:53
ograe2fsck 1.41.9 (22-Aug-2009)15:53
ogra/dev/sda6: clean, 146112/2321984 files, 949695/9277521 blocks15:53
ograinit: plymouth-log main process (3168) terminated with status 11115:53
ograhmm, it really doesnt see the battery anymore15:53
ogranow thats weird15:53
ogra                if (fscanf(f, "%s %s %s %x", tmp, tmp, tmp, &acflag) != 4)15:55
ogra                        acflag = 1;15:55
ograis the original code15:55
ogra                if (fscanf(f, "%s %s %s %x", tmp, tmp, tmp, &acflag) != 4)15:56
ogra                        printf("acflag is: %x", acflag);15:56
ogra                        acflag = 1;15:56
ograis what i made out of it15:56
ograit doesnt exec the printf ... nor does it set acflag15:56
plarsasac: cool, will give it a try16:23
asacuff16:48
asacso next week i want a better meeting16:48
asac;)16:48
asacmore success to report16:48
asacplease make that happen :)16:48
ograheh16:48
ograat least you didnt have to report many disasters :)16:49
asacogra: when did pitti send that announce?16:56
asacwas that in a thread?16:56
asaci cant even find it ;)16:56
ograyou mean the moving of people from rookery to a new machine ?16:56
asacno. the moving of the work itesm from macaroni to people ;)16:56
asachttp://people.canonical.com/~pitti/workitems/canonical-mobile.html16:57
asacvs16:57
asachttp://macaroni.canonical.com/~pitti/workitems/canonical-mobile.html16:57
ograhmm16:57
ograasac, ubuntu-platform@16:58
asacogra: right. but was that standalone mail or a reply to an existing thread?16:58
ogra20.01.2010 14:25:0516:58
ograstandalone16:58
asaci have all that in my main inbox16:58
ograwith a big ANNOUNCE tag16:59
asacok i dont have it ;)16:59
ogralook for ANNOUNCE in the subject16:59
asacguess it was killed in a my eager zero inbox effort ;)16:59
ograheh16:59
ograhmm, so powertop seems to miss some kernel options on imx5117:01
=== fta_ is now known as fta
armin76asac: what about snapdragon? :)17:58
asacfta: i will demote the ffmpeg depends for this upload ... so its not rejected because depends arent fulfillable18:01
asacwe can put that back when its in18:01
ftaasac, /me sad. why not use !armel instead?18:02
asacfta: we have it on armel. just not in the archive18:02
asacits not because of armel ... just because of archive18:02
asaci dont want to block the chromium upload on first getting the other stuff up18:03
ftawhy is it rejected in the 1st place?18:03
asacif its not fulfillable18:03
asacthen it cant go in18:03
asacall depends need to be there18:03
asacso its recommends now.18:03
asacyou can drive the ffmpeg als in18:03
ftawhy not submit it first?18:03
asacits just licensing for that18:03
asacbecause i dont want to wait any longer18:03
fta*sigh* ok18:03
asacyou could have uploaded it ;)18:03
asacwould be great if you could do.18:04
armin76asac: chromium now fails for me :P18:19
armin76  export LD_LIBRARY_PATH=/var/tmp/portage/www-client/chromium-9999/work/chromium-9999/out/Release/lib.host:/var/tmp/portage/www-client/chromium-9999/work/chromium-9999/out/Release/lib.target:$LD_LIBRARY_PATH; cd v8/tools/gyp; mkdir -p /var/tmp/portage/www-client/chromium-9999/work/chromium-9999/out/Release/obj.target/geni; "/var/tmp/portage/www-client/chromium-9999/work/chromium-9999/out/Release/mksnapshot" "/var/tmp/portage/www-client/chrom18:19
armin76ium-9999/work/chromium-9999/out/Release/obj.target/geni/snapshot.cc"18:19
armin76pure virtual method called18:19
armin76terminate called without an active exception18:19
armin76what was that error about?18:22
armin76and i'm using gcc-4.318:23
asacthat was about -fno-strict-alias breakage for ggc 4.318:35
asacif you are really sure everything uses gcc 4.3 on your system now then i dont know18:35
asacbut i would expect it doesnt18:35
asacyou can try -fno-tree-sink18:35
asacgrab the patch from our packaging .head18:36
asacno_tree_sink_v8.patch18:36
* asac out18:36
armin76well, but the -fno-tree-sink is used only if gcc_version=4418:38
armin76and it worked before, i'm wondering if you now need gcc-4.4 :P18:38
plarsnew python didn't help btw19:32
asacdamn20:47
asacplars: there?20:47
asacplars: so you basically can go to console, and make the board hang by running import pybootchargui right?20:48
plarsasac: yes20:48
plarsasac: right, that one and uno both seem to do it so far.  Haven't found others yet20:48
asacplars: so idea is to run python -v20:48
asacthat should spit out the modules that get implicitly imported20:49
asacif you | tee that to a file you might be able to try each of those until you find which import causes this20:49
plarsah, neat, didn't know about that20:49
asacright20:49
plarsok, the last thing I see it trying to import was cStringIO20:50
plarsneed to reboot, sec20:50
asacyeah20:50
asacso check if that alone causes it ;)20:50
asacthen we can check what it does etc.20:50
asacalso ... did you find any module you could import without a hang?20:50
plarsasac: yes, plenty.  These had been the only two so far that I found that caused it to hang20:51
asac cat ./Modules/cStringIO.c  | pastebinit20:52
asachttp://pastebin.com/f51e45d2820:52
plarscStringIO imports ok, must be something after that20:52
asacplars: so we dont see the module that fails to import?20:53
asace.g. it hangs before the dump?20:54
plarsasac: correct20:54
asacplars: can you paste the current import list?20:54
plarsasac: I don't think it's an import from there...20:56
plarsasac: importing socket gives me the same impot list with python -v, and that's the last thing that this module imports20:56
asacfrom where?20:57
asaclet me check something20:58
plarsasac: I'm still looking at uno20:58
asacah20:59
asachttp://paste.ubuntu.com/360871/20:59
asacthats import uno on x8621:00
asac>>> import pybootchartgui21:00
asacimport pybootchartgui # directory /usr/lib/pymodules/python2.6/pybootchartgui21:00
asac# /usr/lib/pymodules/python2.6/pybootchartgui/__init__.pyc matches /usr/lib/pymodules/python2.6/pybootchartgui/__init__.py21:00
asacimport pybootchartgui # precompiled from /usr/lib/pymodules/python2.6/pybootchartgui/__init__.pyc21:00
asacthats the thing i get for bootchart21:00
asacso its not that easy :(21:00
asacplars: do you know about other modules that cause this hang?21:08
plarsasac: those are the only two I've found so far21:09
asac# pybootchartgui/__init__.pyc has bad magic21:10
asacwhat does that mean?21:10
asacplars: maybe removing the precompiled bits helps? sudo rm /usr/lib/pymodules/python2.6/pybootchartgui/*.pyc21:13
asacsorry...  just trying random things21:13
asac>>> import pybootchartgui21:18
asacimport pybootchartgui # directory pybootchartgui21:18
asac# pybootchartgui/__init__.pyc has bad magic21:18
asacimport pybootchartgui # from pybootchartgui/__init__.py21:18
asac# wrote pybootchartgui/__init__.pyc21:18
asacah ... now i see where its coming from.21:18
asacthe package ships an old __init__.pyc here:21:18
asac/usr/share/python-support/pybootchartgui/pybootchartgui/__init__.pyc21:18
asacremove that ;)21:18
plarsasac: interesting21:19
plarsI don't have that file21:19
plarsand I don't see any .pyc file in the dpkg -L list21:20
asacodd21:20
asacdpkg -L pybootchartgui  | grep pyc$21:20
asac/usr/share/python-support/pybootchartgui/pybootchartgui/__init__.pyc21:20
asacwell. its karmic21:20
plarshowever after the earlier rm, I seem to be able to run pybootchartgui21:20
asacso its probably clean ;)21:20
asaccool ;)21:20
plarsso maybe... but what about uno?21:20
plarsand where did some stray .pyc come from? this was a new install21:21
asacplars: have you tried to reinstall pybootchargui after python upgrade?21:21
asacmaybe give that a try21:21
plarsno21:21
asacmaybe it needs just fresh .pyc21:21
asacthe other directory i asked you to clean is generated during install21:21
asacby python-central or something21:21
asacnot sure if tere are triggers that recreate all .pyc if python is updated though21:22
asacto be sure check if reinstalling still keeps pybootchartgui working21:22
plarsalso...21:22
plarssudo rm /usr/lib/python2.6/dist-packages/uno.pyc21:22
plarsimport uno still hangs21:22
asacplars: uno is something different. thats ooo21:23
asacthats a different beast21:24
plarsasac: right, but symptom is the same21:24
asacyes21:24
asacplars: so does reinstalling pybootchartgui make keep it working?21:24
asac;)21:24
plarsasac: have to wait for the reboot21:24
plarsI hung it again trying uno21:24
asacah ok21:25
* asac checks something21:26
plarsasac: pybootchartgui seems to be working now21:27
asacvery good21:28
asacplars: have you tried to remove /usr/lib/python2.6/socket.pyc as well?21:30
plarsasac: no, but importing socket seemd ok21:30
plarsasac: no help21:30
asacok.21:30
asacso i somehow dont get rid of the thought that the uno issue has something to do with the21:31
asacuno thin we have in OOO21:31
asace.g. the bug that requires us to ship the jaunty so21:31
asaci am not sure if that is pyuno.so though21:31
asacdo you remember?21:31
plarsasac: no idea, sorry21:31
asacthe bug about this was https://bugs.edge.launchpad.net/ubuntu/+source/binutils/+bug/43661721:31
ubot4Launchpad bug 436617 in binutils "ARM unwind table linker processing broke OO's uno2cpp" [High,Confirmed]21:32
plarswill be interesting to boot the next livecd if it has the new python in it and see if it works21:32
asaclet me poke chris21:32
asacplars: so ... pyuno.so pulls in that ugly jaunty libgcc3_uno.so21:38
asacthrough libpyuno.so21:38
asacsomehow21:39
asacguess thats not build with thumb221:39
plarsI see21:39
plarsI'm afraid that all of this may be hit or miss until x021:39
plarsfrom the sounds of things, this all likely relates back to that21:40
asacthe gcc3_uno.so thing probably yes.21:40
asacplars: anyway, so with just removing pyuno we get a booting desktop now?21:44
asacplars: if thats the case thats all we can hope for ;)21:44
asacand we should consider to just do it to get working images until we get X0 to test21:44
plarsasac: oh, pyuno was never preventing it from booting, just happened to be another pythong module I noticed that caused trouble.  Previously I was able to get it booting by taking pybootchartgui out of the init21:44
plarsasac: so no reason to remove uno21:45
asacplars: cool. so basically with a reinstalled bootchart it works?21:45
plarsasac: seems to be, tomorrows image will be good to double-check with21:45
asacguess we have flaky but working images tomorrow with some luck then ;)21:45
asacplars: great. with that you can go and do more positive stuff until we get news on hardware/kernel front i guess. thanks a lot!!!21:46
plarsasac: thanks for all your help!21:46
asacno thanks to you ... at least i can somehow sleep again ;)21:48
asacthe good I get out of this is that if we have everything recompiled the Y1 boards might become more and more stable ;)21:48
plarsasac: I didn't think you ever slept!21:53
asacits those things i tell you :-P21:53
asacactually i skip the timezone lag for sprints this way21:54
asaci just keep my live going in central US time ;)21:54
asacanti-jetlag method its called21:54
plarsheh21:55
asacpersia: http://pastebin.com/f429b20ae ... anything else you would like to see there?23:19
persiaasac: From policy 4.1.4, missing bits include:23:23
persia1. how to generate the fully patched source, in a form ready for editing, that would be built to create Debian packages.23:24
persia(most people do this with debian/rules patch, which might work for your CDBS mess)23:24
persia3. Remove source modifications that are currently being applied when building the package23:25
persiaThis might just be telling someone to unroll the tarball, but I'm not sure.23:25
persiaYou've hit #2 and #4 well, and added lots of other interesting stuff :)23:26
asacpersia: 1. is covered in patching23:30
asacsection23:30
asacimo23:30
asacand 3. sounds odd ;)23:30
asacnot sure what that means23:30
asacsome patches are feature patches, some are needed to build (or at least there might be patches)23:30
asaci dont think anyone can ask for keeping those separately documented ;)23:31
asacfor me patching section also tells 3.23:31
persiaasac: You7re supposed to provide a step-by-step guide, not say "start a local build and break in" :)23:31
asacyeah. thats bad ;) but debian/rules patch is broken :-P23:31
asacthe joy of cdbs23:31
persiaI've always interpretedf "remove source modifications" as being both classes of packages.  Someone who does silly things gets to keep both parts.23:31
asacanyway, for a reasonably educated guy this shouldnt be a problem ;)23:32
persiaYou know, lots of people don't use CDBS anymore :)23:32
asacright. but kick off a local build is quite generic ;)23:32
asacyou can even use the instructions in the section above ;)23:32
asacgood. i think all is fine. thanks!23:32
persiaWell, but it's also a non-ideal way to do it, because you have to break it.23:32
asacthats a bug23:33
asacdebian/rules patch should just work, but last time i checked it didnt23:33
persiaThere's probably a CDBS rule like secret-internal-quilt-patched-but-not-built-but-you-don't-know-the-rule-name: rule that one could call.23:33
asacheh. we tried a bit23:33
asacits a bug in the tarball.mk i think23:33
persiaOh.  Ugh.23:33
asacwe have that in firefox etc.23:33
persiaDid I mention that tarball-in-tarball is ugly too :)23:34
asacbut let me assure oyu its not a practical problem23:34
asacyou want to edit and then usually continue build anyway ...23:34
asacyes, but without tarball in tarball you dont want to build the sources regularly23:34
persiaAnyway, your README.source is massively better than not having one at all, especially for such a confusing package using a strange special private CDBS derivative.23:34
asacheh23:34
persiaI understand the problem, I just think the solution is more RAM :)23:35
asacso with enough ram, even cdbs-edit-patch would be great experience ;)23:42
persiaWell, not as bad, assuming the content was fully cached or one is operating on a tmpfs23:43
persiaI'd probably still use quilt, but that's just because I've come to not like digging through CDBS when I wanted to figure out how to do something.  dh(1) makes my life easier.23:44
asacaha23:46

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