=== dyfet` is now known as dyfet === DanaG1 is now known as DanaG [09:37] hi === ramana-away is now known as ramana [11:44] persia: Hmm I don't think qemu-debootstrap works in pbuilder-dist -- it needs an arch arg [11:45] persia: And I doubt it works in mk-sbuild either [11:45] Eh I see the same biarch stuff in there :) [11:47] I tested both before I shipped, and successfully built armel and powerpc chroots on an amd64 machine. [11:48] So, unless something else changed since I pushed, it works, even if it's not supposed to work. [11:48] mk-sbuild is my primary workspace, with pbuilder-dist attempting to keep up out of courtesy for pbuilder users. [11:48] With the latest mk-sbuild, I consider pbuilder obsolete. [11:49] (because of support for type=file chroots). [11:50] plars: for the suspend/resume regression, which kernel works on your side? [11:50] plars: i failed to find any kernel on my side. [11:53] persia: Ah I'm wrong indeed; pbuilder and sbuild pass --arch to debootstrap [11:53] So it just works [11:54] I was expecting one had to care for --arch to be passed as well, but that's already the case [11:56] mk-sbuild has always passed --arch. It was added to pbuilder-dist some time ago (gutsy or hardy, I think). [11:56] One does have to care for --arch, but not quite so carefully. [11:57] Note that neither of these tools are capable of correctly building chroots for unsupported Ubuntu distributions right now. I'm not sure how much that matters, but figure it's worth mentioning. [12:08] persia: Would you have some time to review some early documentation? [12:09] lool: What sort of documentation? [12:09] persia: https://wiki.ubuntu.com/UbuntuDevelopment/Ports [12:09] persia: On development with qemu / for armel [12:10] Ah, cool. I definitely have time to review that :) [12:10] persia: This is very much tools focused rather than tasks-focused; I wish I'd document "How to build an armel package" stories [12:10] Also, on a related note, I'd like to get your input on how we should adjust pbuilder-dist and mk-sbuild to work in Debian. I know you've done a lot to bring nomenclature in line, but I'm not that familiar with the names in Debian. [12:11] persia: I'm afk for most of today, but I wish you go straight to making fixes or mention what should be fixed to me [12:11] lool: For straightforward stuff, I'll just edit. For discussion / debateable items, I'll send you email. [12:11] persia: pbuilder-dist > I think this functionality should be merged in pbuilder itself; I have some strict views on how it would be done, but didn't finish the (large) task of cleaning things up to make this possible [12:12] mk-sbuild > I'm not a heavy sbuild user, but I wish to change that; the sbuild team is quite active upstream touhg [12:12] lool: You'll merge *all* of pbuilder-dist into pbulder? [12:12] persia: Pretty much [12:12] persia: In fact, I think I already cover most of it [12:12] Fo mk-sbuild, I mostly just need some pointers to how to invoke qemu-debootstrap in Debian. [12:13] Was qemu-debootstrap merged already? [12:13] To where would it be merged? [12:13] The package in which it lives in Ubuntu doesn't exist in Debian, nor does anything obviously similar. [12:15] I think I sent it to qemu [12:15] Because it basically requires qemu and the binfmt stuff [12:15] Which is in qemu-user-static in Debian [12:15] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=572952 [12:15] Debian bug 572952 in qemu "qemu-debootstrap wrapper" [Wishlist,Open] [12:16] lool: that only works on armel [12:17] that is why i wanted to test newer release 0.12 [12:17] zumbi_: What only works on armel? [12:18] to see how that works for mips, pcc, etc... *re Bug3572952 [12:18] sorry, i have another keyboard layout bug 572952 [12:18] zumbi_: Error: Bug #572952 not found. [12:18] lool: Thanks. I'll tack that. [12:18] zumbi_: I created a powerpc chroot using qemu-ppc when writing qemu-debootstrap [12:18] So I think it works with our qemu-ppc static binary at least [12:18] zumbi_: I've also tested it with powerpc successfully. [12:19] zumbi_: Please test with arbitrary architectures, and let us know how it doesn't work. [12:19] uhm.. i should then test again, we tried it a couple weeks ago [12:19] Alternately, if you ran into an older version of mk-sbuild or pbuilder-dist that has the "only supported for armel" warning, please upgrade. [12:19] uhm.. note that i use debian stuff [12:22] Ah. I haven't ported my stuff to work on debian yet, and lool's work is pending the recently mentioned bug. [12:25] But if 572952 lands for squeeze, the necessary ubuntu-dev-tools stuff will as well. [12:27] yes, i would love to see it applied, also working for all arches, not only armel, but that is qemu lack of enough support for emulate other arches [12:32] I thought powerpc worked in Debian as well. [12:32] Or, rather, powerpc guests. [12:32] I'm less sure about other stuff. [13:13] ericm_: ping [13:13] saeed, pong [13:14] ericm_: regarding kexec patches [13:14] I send the patches to mailing list, but has been rejected [13:15] do you know if both patches were needed also for imx? [13:16] saeed, I guess the one for L2 is needed as well - according to cooloney's test result [13:16] it's really annoying I know, I didn't look too much into L2 on ARMv7, but it's totally different than ARMv5, guess we need some neater solution for the outer cache [13:17] ericm_: can you please check with cooloney's regarding the other patch? [13:17] saeed, sure [13:18] ericm_: now I'm debugging the highmem issue (crash when booting from sata) [13:18] saeed, cool [13:19] ericm_: can you please also check if this issue happens on imx? [13:21] saeed, called him [13:21] NCommander: you awake yet? [13:21] saeed, he tried kexec with both patches, not individually tested, so the first question is not sure which one is mandatory [13:21] or both are [13:22] and babbage with imx51 has only 512MB, so actually HIGHMEM wasn't actually even used [13:24] ericm_: you can pass kernel vmalloc=256M, that will make some dram as highmem [13:24] dmart, do you know if Catalin has an IRC name here on freenode? I guess Saeed and I can talk a little bit about some L2 issus we met during kexec debugging [13:24] saeed, indeed - I'll see if he has time to test this later [13:25] ericm_: thanks [13:25] saeed, no problem [13:25] ericm_: not sure whether he's usually online [13:26] OK, I think he will join - he's cmarinas [13:27] dmart, thanks [13:33] dmart: yes [13:40] NCommander: hi, dunno if you saw my post on the OOo bug, but it looks like the fix we had has a problem: privateSnippetExecutor pushes some arguments on the stack, but they never get removed after cpp_vtable_call returns [13:43] NCommander: this is a more complete attempt http://pastebin.ubuntu.com/395620/ [13:44] Since I have a OOo build tree now, I rebuilt libgcc3_uno.so and clobbered the installed version in lucid with it--- OOo seems to start up and "work"; is there anything else I should look for? [13:47] dmart: no, that was our usual test since we never got past start up :-) [13:48] dmart: who caught the arguments on the stack problem? (I didn't have an OOo crash, but I didn't abuse it hard) [13:48] dmart: actually, there IS an OOo test suite believe it or not. Might be worth trying to run it if you cna spare a few weeks [13:49] Nah. The test suite should only take 100-150 hours to run. [13:49] One of the other guys on my side, by inspection (it was a dumb mistake, we push some stuff which is never popped) [13:50] It means exception unwind annotations are needed after all, to clean up the stack if an exception happens, but it seems reasonably straightforward now we understand what the code is doing. [13:50] persia: is the testsuite part of the OOo source package? [13:51] * persia checks [14:27] dmart: My apologies: I don't appear to be able to answer the question. Attempting to download the ooo source from my local mirror (~50cm away) will apparently take 9 hours, and trying to unpack it directly on the mirror seems to break either with the version of dpkg on that server or with the amount of available RAM [14:27] * persia looks forward to more hardware exceeding the 512M boundary [14:28] NCommander: Maybe you could share? [14:30] dmart: no, its an addon, and OOo has to be built in a special way [14:30] argh, so, 4-5 days + x [14:31] Can I suggest that you verify what's suggested in http://pastebin.ubuntu.com/395620/ works for you and push that (assuming it does work, of course) [14:32] I did some standalone testing on this, checking that the normal and exception return paths do the right thing: it appears to behave well. [14:35] NCommander: scrollback the last few posts (forgot to ping you) [14:36] dmart: sure [14:37] NCommander: should I assign the lp bug back to you in the meantime? [14:37] dmart: [14:37] yeah [14:38] ok [14:38] done [15:50] davidm: greetings === amitk is now known as amitk-afk === NCommander is now known as Guest5889 === NCommand1r is now known as NCommander [20:08] asac: is chromium on ARM known to be broken? [21:14] can someone who has Ubuntu on ARM running on something beside dove or imx51 test something for me? [21:15] NCommander: depends on what you need [21:15] NCommander: i'm running a beagle [21:23] prpplague: can you download and install chromium-browser from the archive (in lucid) and see if it works properly [21:23] NCommander: sorry, i am not able to do that at the momment, sorry [21:24] NCommander: no display running atm [21:24] prpplague: X11 forwarding over SSH? [21:25] NCommander: only uart console [21:25] prpplague: ouch [21:25] prpplague: thanks anyway [21:25] NCommander: i should have something up and running towards the end of the week, but i suspect that is too far down the road for you [21:26] prpplague: yeah :-/