/srv/irclogs.ubuntu.com/2009/09/01/#ubuntu-arm.txt

=== cbrake is now known as cbrake_away
ali1234does console-kit-daemon really need to use all spare cpu time or is it a bug?07:37
=== ericm is now known as ericm-afk
loolali1234: it's a bug08:49
loolali1234: What environment do you see this in?08:49
ali1234lool: i'm running on omap850 after using the "root from scratch" script with --seed=lxde,gdm08:50
loolali1234: Could it be an option missing from your kernel?08:51
ali1234yes, it certainly could. but which one?08:51
loolali1234: I would strace consolekit to see whether it's failing a syscall or something like that08:51
loologra: Did you ever see 100% used with CK?08:52
loolI didnt ever see this08:52
ogranope08:52
ograbut i remember the desktop team had a bug about it early in jaunty ... though that was fixed for release08:53
ograCK did spawn threads endlessly iirc08:53
ali1234i saw that bug on launch pad, it seems to be a memory leak issue with lots of ssh connections. i only have one08:53
ali1234strace just says: restart_syscall(<... resuming interrupted call ...>08:55
ali1234then nothing08:55
ograhmm, why dont we have a dove image today08:57
ali1234it almost is a kernel issue since i'm using 2.6.25 and no particular config08:58
ali1234*almost certainly08:58
ogralool, Couldn't open .flint/dbw/postlist.baseA: Too many open files09:02
ograCouldn't open .flint/dbw/postlist.baseB: Too many open files09:02
ogra)09:02
ogrado you think it's worth trying to giv that back ?09:02
ogra(thats xapian-core)09:03
ograseems like a buildd issue09:03
loolhmm09:13
loolAny other build like this?09:13
ogranope09:13
ograxapian seems to hammer the disk during its test phase09:14
loolI guess you could give it back09:14
ograwe have two idling buildds, i'll just try09:14
loologra: livefs failed to build09:14
loolhttp://people.canonical.com/~ubuntu-archive/livefs-build-logs/karmic/ubuntu-dove/latest/livecd-20090901-armel.out09:14
lool  empathy: Depends: libmissioncontrol-client0 (>= 4.37) but it is not installable09:15
ograah, yeah, empathy09:15
loolevolution and others09:15
lool  evolution: Depends: evolution-common (= 2.27.90-0ubuntu2) but it is not going to be installed09:15
ograi just gave back evo, it always needs handholing09:15
ograseb never waqits until the "all" packages are published09:15
ograhmm, xapian has the same issue on ia6409:16
ograand on sparc09:16
ogralool, i dont get why dove wouldnt use an older livefs as all other arches do though09:18
* ogra pbuilds xapian-core locally09:19
loolOh that's unrelated, I actually broke the build but I fixed it now09:24
loolWell I think, I'm test building09:24
loolpoumpoudoum09:28
ograpoumpoudoum ?09:30
loollalala if you wish09:31
loolok it built09:31
loolhmm that's bad09:31
lool/home/lool/cdimage/debian-cd/tools/pi-makelist-vfat: Couldn't list any drive09:31
ograoh09:31
ograi thought you were talking about xapian and wondered whn you secretly pushed that to the buildds :)09:32
ograETOOMANYTOPICSATONCE09:32
loolOh09:35
loolWe never actually cared to support partition=1 in pi-makelist-vfat09:35
loolonly no partition or part 209:35
ograwhich didnt fail since we never used partition 1 yet09:35
loolHmm oddly it doesnt work with partition=1 either09:36
loolOk found another bug in that script which went unnoticed09:37
loolOh no it was just local to my edit, some typo during copy-paste caused a lowercase or something09:39
looland it worked, cool09:40
loolall deployed, just waiting to confirm I can kick a rebuild09:40
loolSure enough http://cdimage.ubuntu.com/ports/daily-live/20090831/karmic-desktop-armel+dove.list was empty09:42
rabeehlool: which machine are you using for that build?09:42
rabeehlool: are dove machines already part of the buildd cloud?09:43
ograrabeeh, nope09:48
loolrabeeh: No, imx51 based09:48
ograwe hope to add dove soon though09:48
loolrabeeh: I dont think we can get z0 stable enough and we dont have enough yX09:48
rabeehisn't that incremental work? meaning if you have 1 yx then you can add to buildd, and if you have 2 then you can add 2?09:49
loolMy main worry is silent breakage: it might be ok if a buildd goes completely missing and has to be remote rebooted but it's not ok if it breaks in the middle of a build: it could either cause a subtle breakage to go unnoticed and if it actually fails the build we cant distinguish hardware errors from software ones which we need to fix  :-/09:50
rabeehi mean you can start with what you have, and get more soon.09:50
ograbut we dont have a single one we can spare yet09:50
loolrabeeh: I think we could start like that, but we have no facility to schedule builds on this or that buildd09:50
rabeehso, what is the yx board allocation o buildd/developer?09:53
rabeehbtw - is it possible to set a board remotely part of a buildd?09:54
rabeehfor example i have my own y0 board; that is free at nights and weekends; can i set it (behind a firewall) to be part of the buildd cloud?09:55
rabeeh(i know; this is intermediate solution until you get the amount of boards you have requested)09:55
ograwe have 7 armel buildds atm ... https://launchpad.net/builders09:56
rabeehfor example, you can never ssh to the board; but the board can poll and pull build requests from the web09:56
ograand as you can see currently two are idle, one is in maintenance09:56
ograhaving more doesnt really help, having faster ones will ...09:57
ograwhich is why we look forward to add doves09:57
rabeehhmm. why?09:57
ograbecause one package is built on one buildd09:57
ograif you take openoffice it takes about 36h to build09:58
rabeehbut they are idle :)09:58
rabeehdon't they have queues for karmic builds?09:58
ograhaving it building in 24h would improve ... having one more buildd wouldnt help speeding it up09:58
ograits not a cluster where adding more power would improve anything for the single build09:59
ograadding more machines just lets the qeue get empty faster10:00
ograbutu the queue as you can see is empty most of the time ... it might indeed help at high times where you have tons and tons of uploads10:00
ograthe amount of 7 machines is quite ok ... replacing them incrementally with doves will help a lot but we currently need the few doves we have for development and QA of the dove image we build10:02
rabeehwhich machines you have here are running on discovery 78100?10:02
rabeehi recall canonical had few of those machines for jaunty armv5 armel distro10:03
rabeehmy point is can we use armv5+vfp machines for armv6+vfp?10:03
ograright, but after the alpha5 release (thursday) we will default to only build for v610:04
ograno, you cant use v5 machines for that10:04
rabeeh(implementing software instruction abort handlers for the armv6 part)10:04
ograthats why we currently are stuck with imx51 machines10:04
ograhow stable would such a software layer be ... how much slowdown would you get through such an additional layer10:05
rabeehwell. it's hard to guess; but armv6 has big SIMD addition; which is never used in integer/floating based application10:06
loolsorry had an UPS delivery10:06
rabeehit is used in packages like ffmpeg; and might only break if the debian/rules calls some test to use that10:06
looland it's broken so I need to deal with it10:06
rabeehlool: hope it's not Dove :)10:06
loolIt's not  :)10:06
ogramy assumption is that if you develop such a layer to run on v5 buildds you invest a lot of time to make sure its stable enough, do QA on it etc10:07
ograand i bet once you are done the amopunt of y0 we want is available :)10:07
ograso using imx51 until that point serves as well without risking stability10:08
rabeehright. and i'm looking at the instruction set addition; and seems lots of instructions being added10:09
ograright10:09
rabeehwill take lots of time to implement those exception handlers10:10
rabeehogra: what i can promise is that y1 boards will come with 1GB of DDR :)10:10
ograeffectively you would end up with something like qemu-arm inbetween the CPU and userspace10:10
ograWOW !10:10
rabeehright10:10
ograthat will make a huge improvement !10:10
ograthe diskspeed already is a huge improvement on the dove vs imx10:11
ograadding more ram will make the builders fly :)10:11
rabeehpersonally i think we should have buildd version of dove10:12
rabeehoverclocked and even more DDR10:12
rabeehlunch time :) ttysw10:14
ogra:)10:14
loolrabeeh: It's common for packages to call binaries from others; not frequent but common enough that it needs to work well; for instances all GStreamer apps call the equivalent of gst-inspect on startup which will cause all plugins to be loaded10:37
loolIncluding ffmpeg10:37
lool(Now Gst is a special case because it actually traps sigill but still :)10:37
rabeehogra: back to the original question; is it possible that put my board part of the buildd cloud? (inside a firewall)11:08
rabeehlool: got it.11:08
ograrabeeh, nope, our IS team wouldnt allow that i guess11:15
=== cbrake_away is now known as cbrake
=== bjf-afk is now known as bjf
=== ericm-afk is now known as ericm-Zzz
=== bjf is now known as bjf-afk
tleeHas karmic's arm build system move to vfp yet?17:38
ograafter alpha5 we'll move immediately17:54
tleeThanks Ogra.  How many days (weeks) is that from now?    Also how long you think it would take to rebuild all the packages?17:58
ograalpha5 images will be released on thursday17:59
ogra(including a dove live image btw)17:59
ogratesting appreciated :)17:59
ograno idea how long it will take to rebuild the whole archive ... i'd guess a week or two18:00
ogralool, any idea ?18:00
loologra: we moved already18:04
loolto vfp18:04
looltlee: we're using v6+vfp at the moment18:04
ograoh !18:04
loolWe wont rebuild the archive18:04
ogradont we do a complete rebuild anyway during the process ?18:05
loolWhat do you mean?18:05
tleewow.18:05
ogralool, on the std arches we usually do a complete archive rebuild before final18:06
ograhttps://wiki.ubuntu.com/KarmicReleaseSchedule spt24th18:06
ogra*sept18:06
ograand oct 15th18:06
loologra: That's out of archive18:09
loolWe dont keep the results18:09
ograoh, i thought we did18:09
loologra: So did you get like thousands of packages to download on the week before release?   :)18:09
ograwhy would i if the versions dont change18:10
loologra: Because the binaries arent identical18:14
loologra: It would be a terrible idea to have two .debs with different md5 and contents named the same thing and using the same version; we never do that18:14
ograoh, indeed18:15
loolAnd it's also why we wont rebuild the whole archive just for armel18:15
ograyeah, understood18:15
ograthast a bit sad though18:15
loolNot too much18:16
loolBut it's why the lack of buildd was such a big deal18:16
ograindeed18:16
loolBut given the number of uploads before release it's not that bad18:16
ogratrue18:16
ograproblematic is that we wont see fallout caused by the setting for packages that werent uploaded18:16
ograwe'll likely hit the ftbfs'es for these in karmic+1 only18:17
=== bjf-afk is now known as bjf
tleeHave any of you seen this "BUG: soft lockup - CPU#0 stuck for 61s!"?18:55
ogranope, not on armel yet18:56
tleeGoogle it and it seems to happen a lot of times in kernel.18:56
ograi have seen it on via eden18:56
ograand other thin clients i worked with (geode etc)18:56
tleeorga:  turn on nullmailer and see if you can see what I seen on karmic.18:56
ograoh, wait, looking at my dmesg ...18:57
ograhttp://paste.ubuntu.com/263307/18:57
tleeI believe I have 400+ email Q to send out and nullmailer is trying to run every few minutes.  Seems to trigger that erorrs for me.18:57
ograit's currently doing a heavy duty build18:57
tleeon Karmic.  Quite offer.18:58
ograNCommander, http://paste.ubuntu.com/263307/18:58
tleeOn Jaunty, I see the bash has issue.18:58
ograNCommander, watch your dmesg on the dove under load, appears to be a kernel bug18:58
tleeOn Karmic, seems only the nullmailer.18:58
ograwell, i'm building a package here18:59
ograand it seems to have been triggered by bash18:59
tleeDo you know any method to help track this bug down?19:01
ograi pinged bjf in #ubuntu-kernel19:01
bjforga, I can *sigh* here just as easily19:02
ograheh19:03
ogranote that i use the -201 build still19:04
bjfogra, oh! well that's obviously your problem :-)19:04
ogranot sure if 202 or 203 fix it, but i guess tlee runs something newer19:04
ograi cant replace the kernel before webkit isnt finished, i need the log19:05
ograand that might go on for the rest of the nigh ...19:05
ogra+t19:05
bjfogra, I'll boot mine up and see what I see19:05
ograi didnt see it before19:05
ograseems to be load related19:05
tleeorga: what do you mean by 201, 202, 203?19:14
ograthe kernel builds19:15
ograits the ABI version of the packaged kernels we use19:15
bjftlee, you will see the version as 2.6.31-203.8, the 203 is the API versions19:16
ograhttp://ports.ubuntu.com/pool/main/l/linux-mvl-dove/19:16
tleeI am still back in 2.6.30.  I built 2.6.31 last week, have not try it yet.19:16
ogralinux-image-2.6.31-203-dove_2.6.31-203.7_armel.deb is the current package19:17
ogra(i think there is one pending in the queue though)19:17
bjfogra, yes there is one "in the queue", it has some of the latest mvl changes and we are building zImages instaed of uImages19:18
ograyeah, i saw the thread on the ML19:18
tleeOk, I will try to sync it up tomorrow. Have some demo to do today. Don't want to mess with the demo god for now.19:18
ograheh19:19
bjftlee, I hear that!19:19
tleeI am in trouble now.  Lighting is stiking from above..... run ..... :-)19:20
ograhaha19:21
NCommanderogra, yeah, I've seen that. Thought it was an issue with the old kernel I was using19:30
NCommanderIt didn't reappear since I updated to a 202 kernel, although I haven't been using that as extensively19:30
NCommanderactually19:31
ograok, i'll see what 203 does for me then19:31
NCommanderer19:31
NCommander20319:31
NCommanderer, 202 or 20319:31
NCommanderI used to get it trying to spin livecd-rootfs's19:31
NCommanderthen it went away when I updated the kernel19:31
tleeThere is no uImage in the linux-image-2.6.31-203-dove_2.6.31-203.7_armel.deb.  How do I make the uboot to load vmlinuz?22:45
=== bjf is now known as bjf-afk

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