=== ericm-Zzz is now known as ericm|ubuntu === asac_ is now known as asac [02:25] Daviey: I'll start looking at them this week. Just returning from holiday/vacation. Need a vacation just to relax from the vacation. === Jack87|Away is now known as Jack87 === Jack87 is now known as Jack87|Away === Jack87|Away is now known as Jack87 === panda is now known as Guest64421 === jcrigby_ is now known as jcrigby === Jack87 is now known as Jack87|Away [09:45] ogra_: Do you have a minute? [09:45] ogra_: I was hoping you could help me with qemu-system-arm? :) [11:42] Daviey, whats up ? [11:45] ogra_: I'm really sucking in trying to get either the server cloudimg's or the core images running in qemu-system-arm [11:45] They don't seem to output to tty.. and i couldn't get data over serial. [11:45] So i'm not convinced i'm doing it right. [11:46] I've been trying versatile(a|p)b [11:46] on what host ? [11:46] amd64 [11:46] versatile is rather dead [11:46] no, which release i mean :) [11:46] (on the host) [11:46] Oh, oneiric [11:46] ah, better use vexpress [11:47] vexpress is the favoured machine? [11:47] right, omap should also work i think [11:48] I am having issues installing libscrollkeeper0 from karmic/lucid repos. all i get is 404... what can i do? [11:48] ogra_: Could i ask you to try, http://cloud-images.ubuntu.com/oneiric/20110821-armel/oneiric-server-cloudimg-armel.tar.gz (tarball contains a disk img and kernel)) [11:49] phew, sure, let me install the qemu stuff, i havent used that since a year or so [11:49] hmm, though i have no oneiric x86 machine [11:50] ogra_: I can give you ssh access to a virtual machine if that helps? [11:50] but no graphical interface if you want that [11:50] nah, let me roll an oeniric chroot quickly [11:50] ogra_: expect beer. [12:01] Daviey, oh, btw, http://cdimage.ubuntu.com/ubuntu-server/daily-preinstalled/20110822/ ac100 images ... (they dont work yet, but are close) [12:01] ogra_: Oh awesome! [12:02] ogra_: although, for bare metal arm - i care more about the images working through D-I. :/ [12:03] indeed [12:03] we dont use them yet untl we have real arm server HW ... [12:03] .. unless someone writes a pxe enabled dd script :) [12:03] thats trivial === zyga is now known as zyga-siesta [12:32] Daviey, so how is your image expected to work ? for the beagle emulation you need a full disk image with boot partitions [12:32] *partition [12:33] (containing x-loader and u-boot etc) [12:39] ogra_: We don't have much idea :) [12:39] well, you should produce something similar to what we build on the imagebuilders [12:39] a two partition image with the boot bits in the first (vfat) partition [12:40] and then go from here https://wiki.linaro.org/Resources/HowTo/Qemu-beagleboard [12:40] ogra_: I'm loathed to try and replicate what your team is doing. [12:41] well, probably vexpress can boot more similar to what versatile was [12:41] that would make it easier [12:41] ogra_: Does it have isa-serial per chance? :) [12:41] no idea [12:41] i never used it :) [12:42] yeah, libvirt seems to think everyone wants it :) [12:42] https://wiki.linaro.org/PeterMaydell/QemuVersatileExpress [12:42] that looks more backwards compatible to versatile than qemu [12:42] and it seems to be able to emulate 1G [12:43] heh, ..."If you want you can add "-smp 4" to make it boot as a 4-core SMP model." [12:44] heh [12:44] ogra_: Who would be the best person for utlemming to work with to fix our build process? [12:45] utlemming is our cloud image master. :) [12:45] well, lets find a proper concept first :) [12:46] hummmm.... [12:46] ogra_: Well use case is two fold: 1) Emulated ARM hardware using qemu-system-arm.. 2) Some manipulation to get it running on bare metal (probably pandaboard) via LXC. [12:46] we dont seem to build vexpress netinst images anymore [12:47] so there is no vmlinuz :( [12:47] argh [12:48] i wonder if linaro has something like that [13:09] Daviey, so using vexpress it cant determine the filesystem of the img it seems [13:09] argh [13:10] what fs is it ? [13:10] $ file oneiric-server-cloudimg-armel.img [13:10] oneiric-server-cloudimg-armel.img: Linux rev 1.0 ext4 filesystem data, UUID=87915972-5866-47e0-af76-306c3a1143b4, volume name "cloudimg-rootfs" (extents) (large files) (huge files) [13:10] oh [13:10] it doesnt try ext4 at all [13:11] ah, ok - what should it be? [13:11] it checks ext2/3 above the mount error [13:11] [ 1.231251] No filesystem could mount root, tried: ext3 ext2 cramfs vfat btrfs [13:12] Odd that it supports btrfs but not ext4 :/ [13:12] Daviey, so here is what i did ... [13:12] pulling the latest vexpress hwpack from http://snapshots.linaro.org/oneiric/vexpress-oneiric/20110822/0/images/hwpack/ [13:13] (there is sadly no "current" link and the hwpacks have version numbers in their filename) [13:13] unpack it, dpkg -x pkgs/linux-image-3.0.0-1001-linaro-vexpress_3.0.0-1001.1~ppa~natty_armel.deb . [13:14] qemu-system-arm -kernel boot/vmlinuz-3.0.0-1001-linaro-vexpress -M vexpress-a9 -cpu cortex-a9 -m 1024 -append 'root=/dev/mmcblk0 rw mem=1024M raid=noautodetect console=ttyAMA0,38400n8 rootwait vmalloc=256MB devtmpfs.mount=0' -sd oneiric-server-cloudimg-armel.img -nographic [13:17] ... [13:17] heh [13:17] root@osiris:/root/tmp# grep EXT4 boot/config-3.0.0-1001-linaro-vexpress [13:17] # CONFIG_EXT4_FS is not set [13:17] intresting, not even a module [13:18] ogra_: that is great! What do we need to do, to get the hwpack into Oneiric? [13:18] the vexpress package might be in the archive somewhere actually [13:18] Ah ok, does vexpress max out at 512MB of RAM like versatile? [13:19] there you go http://ports.ubuntu.com/pool/main/l/linux-linaro-vexpress/ [13:19] it should apparently support 1G [13:20] groovy. [13:22] Daviey, if you download the kernel-image udeb (you can also extract that with dpkg -x), that only contains vmlinuz and System.map [13:23] ah, worth knowing [13:24] ogra_: So, is there a reason it shouldn't support ext4? Ie, should i raise a bug - or is there a logical reason? [13:24] are your instrances supposed to survive reboots ? or is it some throw away thing ? [13:25] i dotn see a reason to not support ext4 [13:25] if its throw-away i would actually go without journal, that speeds up I/O (and if you dont need reboot-recovery the journal is rather moot anyway) [13:31] ogra_: should be persistent across reboots [13:31] ah, k, then better keep a journal ;) [13:32] although perf is probably more importiant than reliability at this stage IMO :) [13:32] well, talk to linaor if you need config chaneges in the kernel [13:32] *linaro [13:33] linaro being on a different release cycle to us kind of concerns me to rely upon their kernel TBH. [13:34] the packages in the ubuntu archive fall under the ubuntu release schedule [13:34] (not more QA than other universe packages indeed) [13:35] but indeed you can use omap instead, but with less ram and more complex image creation [13:36] (since the vm behaves exactly like a beagle you also need a matching image) [13:37] Yeah, i want to be able to allocate as much memory as possible. [13:37] Ieally up to 16GB :) [13:38] lol [13:38] Ideally* [13:38] so you should go into qemu hacking and invent a VM that can do that [13:38] i think the vexpress is the biggest we have up to now [13:39] also dont expect great performance of qemu in general [14:40] I'm trying to do "sudo -s" in console, but all i get is "sudo: must be setuid root" - what can I do? [14:41] The system I use (Ubuntu inside maemo on N900) arrived with that glitch. I did nothing to provoke that, I can't reinstall to fix it. [14:52] help [15:52] utlemming: Hello! [15:52] howdy Daviey [15:53] utlemming: meet ogra_ and NCommander.. they are your new best friends, which we will have to buy lots of beer for at UDS> [15:53] hello ogra_ and NCommander [15:55] utlemming: So ogra_ managed to get your images working by doing, http://pb.daviey.com/nINF/ [15:56] ext4 isn't supported by the kernel at this stage, which is why you've changed it to ext3. [15:56] I just pulled ext4 out of the recipe [15:56] and I was working on the in-image kernel [15:57] looking at your pastebin, do we not have a working Ubuntu-provided kernel? [15:57] You should be able to use, http://ports.ubuntu.com/pool/main/l/linux-linaro-vexpress/ [15:58] utlemming: I got a proof of concept with openstack starting the instance, but i lucked out with the options.. If you are able to ack that process works.. we should be able to land that soon. [15:59] yeah, the change shouldn't be too difficult. I should have confirmation shortly. [16:04] do we not have a 3.0.0.x kernel for arm images in the ports pool? [16:06] utlemming: apparently, https://launchpad.net/ubuntu/+source/linux/3.0.0-9.12/+build/2733971 [16:07] ah...okay, so I was using the right kernel :) [16:08] pass. someone from the arm team is best placed to answer that. [16:09] utlemming: We do for omap/omap4, not sure why there isn't one for vexpress. [16:10] I was building the cloud images with the omap kernel simply because it was the only one current for the 3.0.0.x kernel tree. [16:11] Might be a question for ppisati. [16:14] ppisati: can you chime in on the building of vexpress arm kernels? === zyga-siesta is now known as zyga [16:24] Daviey: why am I buying utlemming beer? [16:27] NCommander: Awesome! You can buy me one aswell. [16:27] NCommander: I think you didn't parse it correctly, beer is being provided for you, not by you. [16:27] Daviey: er,I just asked why you are buying me beer [16:27] oh, awesome [16:27] yay [16:28] * NCommander got wired crashed and might be semi-sleep deprieved [16:28] Can I get one too? [16:29] charlie-tca: no. [16:29] oh, well. Worth asking, anyway :) [16:30] charlie-tca: heh, sure you can - utlemming is buying. [16:31] * GrueMaster sighs. Everyone always ignores the QA guy when beer is involved. [16:33] +1 GrueMaster [16:35] Hi, ogra_ [16:35] this is regarding USB OTG [16:36] last tuesday u had mentioned that u will update the status on USB OTG === chuck_ is now known as zul [17:30] How can I generate a new .Xauthority file? [18:42] has anyone had success with the vexpress kernel and networking? [18:42] I'm seeing "qemu: hardware error: lan9118: Unimplemented MAC register write: 9 = 0x8100" [19:56] utlemming: lool experienced that a while ago [19:56] Daviey: thanks [19:57] utlemming: we need to cherry pick, http://lists.gnu.org/archive/html/qemu-devel/2011-03/msg02900.html [19:58] Or with a better comment, http://git.linaro.org/gitweb?p=qemu/qemu-linaro.git;a=commitdiff;h=a0313c00fc [20:01] * utlemming looks to test patch [20:10] utlemming: If that resolves it, lets get a debdiff / branch together to upload. [20:11] Daviey: sure thing [20:22] Daviey: patch confirmed [20:27] utlemming: rocking, show me the money^D debdiff [20:33] Daviey: http://uec-images.ubuntu.com/oneiric/20110822-armel.2 (new images) [20:33] utlemming: ROCKING.. can you throw me the qemu-system-arm command line you tested it with? === davidm` is now known as davidm [20:37] Daviey: give me a minute...the image isn't pinging so I think my network setup needs some work [20:38] bah, who needs network access. [20:43] utlemming: vexpress networking only half works sadly; I get some packet drops when doing a netinst :-/ [20:43] utlemming: but I didn't get your failure [20:43] https://bugs.launchpad.net/qemu-linaro/+bug/799757 [20:43] Ubuntu bug 799757 in qemu-linaro "Network unstable with vexpress model" [Undecided,New] [20:44] lool: well then, whats your qemu invocation? [20:44] I'm using: qemu-system-arm -kernel boot/vmlinuz-3.0.0-1001-linaro-vexpress -M vexpress-a9 -cpu cortex-a9 -m 1024 -append 'root=/dev/mmcblk0 rw mem=1024M raid=noautodetect console=ttyAMA0 ip=10.1.6.2::10.1.6.1:255.255.255.0 rootwait vmalloc=256MB devtmpfs.mount=0' -sd oneiric-server-cloudimg-armel.img -net nic,vlan=0 -net tap,vlan=0 --nographic [20:47] utlemming: I'm not passing any -net, not sure what raid=noautodetect does and the one thing which is bad here is your -sd which should be -drive file=sd.img,if=sd,cache=writeback [20:47] you don't actually need -cpu [20:48] I believe you want console=ttyAMA0,115200 [20:48] I don't know why you pass vmalloc=256MB devtmpfs.mount=0 either [20:49] both those were feed to me by http://pb.daviey.com/nINF/ [20:50] lool: well, that worked better [20:52] Daviey: use qemu-system-arm -kernel boot/vmlinuz-3.0.0-1001-linaro-vexpress -M vexpress-a9 -cpu cortex-a9 -m 1024 -append 'root=/dev/mmcblk0 rw mem=1024M console=ttyAMA0,115200 rootwait ' -drive file=oneiric-server-cloudimg-armel.img,if=sd,cache=writeback --nographic [20:52] utlemming: is this on oneiric? [20:52] I'm using natty. Firing up oneiric now [20:53] utlemming: --nographic should be -nographic [20:53] yup, it should. But qemu didn't spawn an SDL window [20:55] utlemming: Argh! That explains why it's not fixed for you :) [20:55] .. and why i started ranting :( [20:55] My pleasure to increase your stress level a bit [20:59] utlemming: I live for stress, yeah baby! [20:59] Asside from being _dog_ slow, I can confirm the image boots [21:00] utlemming: drop -nographic if you want the SDL window [21:00] lool: is SDL faster? [21:00] no [21:00] but it gives more features [21:00] you can switch between qemu console, serial console and fb [21:01] I usually disable graphics and use -serial stdio to get the output of ttyAMA0 on my terminal [21:02] lool: do you have any suggestion for making it run any faster? [21:03] utlemming: only use one CPU, not SMP (1 x cortex-a9 is fine); disable safe writes (-drive above); put the -sd in tmpfs; run on a fast intel box :-) [21:03] utlemming: it will be slow though [21:04] utlemming: some useful things can be run under qemu-arm-static instead; you will be using your intel kernel and hosts' files [21:04] depends what you're doing, and some things also fail utterly in that mode [21:05] the images are being installed under qemu-system-arm -- it takes about an hour to generate the images, but works well for debootstrap === zyga is now known as zyga-w510 === Jack87|Away is now known as Jack87 === NekoXP is now known as Neko [23:20] Anyone about? I'm seeing a 20 % drop in performance after updating my PandaBoard kernel to 3.0. Looking for some kernel hackers... [23:21] michaelh1: Describe your test method. [23:22] GrueMaster: CoreMark, which is a CPU bound benchmark. First noticed on my own NEON benchmark which shows the same results. [23:23] GrueMaster: NFS root. Build CoreMark. Boot into a random 2.6.35. Run CoreMark. Boot into linux-linaro 3.0. Run same binary. Compare. [23:23] GrueMaster: The bogomips in /proc/cpuinfo is also at ~80 % [23:24] LP: #831683 [23:24] michaelh1: I'd have to check, but I believe there was an issue with the cpu speed above 900mhz in the kernel (may have been beagleXM). [23:24] lp 831683 [23:24] Launchpad bug 831683 in linux-linaro "Performance regression between 2.6.35 and 3.0" [Undecided,New] https://launchpad.net/bugs/831683 [23:25] thanks, ubot2. [23:26] Ah, that's the incantation! [23:26] GrueMaster: the board is stable with a .35 kernel (it's used in a build farm and works quite hard) [23:28] It is highly possible that this may be related to bug 709245 [23:28] Launchpad bug 709245 in linux-ti-omap4 "ARM SMP scheduler performance bug" [High,Confirmed] https://launchpad.net/bugs/709245 [23:29] Try running with nosmp on the kernel cmdline and see if that helps performance. Or, try ping -f to the machine while it is busy. [23:32] GrueMaster: will do [23:33] GrueMaster: note that the machine is idle and this is a single threaded benchmark [23:34] Well, the benchmarks we ran earlier were mainly hdparm and discovered a 10x boost with nosmp. [23:38] GrueMaster: nope, nosmp has no effect. Noted on the bug. [23:39] Ok. Worth a shot though. [23:40] GrueMaster: is there a debug flag I can set to show the clocks/frequencies that have been set? [23:41] It should be in the dmesg output or /var/log/syslog. [23:45] GrueMaster: no, nothing. We'll see what people think of the bug...