[00:00] rcn-ee, null pointer patch -> http://marc.info/?l=linux-netdev&m=127490516731906&w=2 [00:00] going to try to run with that, and check if the memory leak was fixed elsewhere in 2.6.35 [02:38] rcn-ee, okay, that patch fixes the null pointer at least, just got it booting [02:39] currently 36 objects in slab size-2048 [02:39] ... and no increases yet [02:39] I'll ping back in an hour [02:41] rcn-ee, note that this is _with_ the micrel patches, plus an additional one which I'll email you [02:42] (er, it's actually the one from the link, so I'll only email you if you want a known-to-be-working copy of it :p) [02:57] cool cwillu, was playing with the patch.. http://marc.info/?l=linux-netdev&m=127490516731906&w=2 needed for 2.6.34 and 2.6.35 ? ;) [02:58] rcn-ee, haven't tested it under 2.6.34 [02:59] rcn-ee, I'm suspicious that the null-pointer was a resulting from freeing the memory (i.e., what wasn't happening in .34 and earlier) [02:59] you're referring to the 2 -> 4 line? [02:59] okay, will queue up for 2.6.35 and get a build out, will test 2.6.34 tomorrow too just for kicks.. [02:59] k [03:00] re, leak test, it's still holding at 36 objects [03:00] I've seen it go up to 100 or so, but it came back down [03:00] so, it seems to be working properly [03:00] yeah, it's more stablized then the previous version which shot up too fast.. [03:04] going for a walk for an hour [03:04] I might dance a little while I'm walking :p [03:05] (road trip to replace / upgrade a bunch of hardware with bb + zippy's, and that wasn't going to work out to well if the max uptime of a zippy is a day :p) [03:05] you should... too much stress from the ks8851 driver for you this weekend.. [03:05] now I can actually write features to pack in before I leave wednesday :) :D \o/ [03:05] yeah that would have sucked big time, nothing like hardware that refuses to stay up.. [03:07] yep [03:07] I knew I had this problem, but I thought I remembered that 2.6.33 didn't have it [03:07] as it turns out, I just never used the ethernet under 2.6.33 :) [03:08] I mean, I had a couple crappy workarounds, but I didn't want to have to explain their need to my boss :p [03:08] hardware that stays up is better [03:09] yeap... :) (crap replaced device 1 with 2, migrate to 2, shutdown 1, device 1 no longer repsonding..) [03:09] (device 2 no longer responding) [03:09] we get enough lightning strikes that I already have enough issues :p [03:10] had a customer call me up saying my system was rebooting every few seconds [03:10] he didn't feel the need to mention that his desktop was also doing the same [03:10] yeah, you need good ups in the summer.. (or two or three in line..) [03:13] in this case, if the power is out, they're not doing anything anyway [03:13] and I've gone through the sd testing routine and so forth [03:13] I'm actually considering reimplementing reboot as "sync; dontechodangerous b > /proc/sys-rq-trigger" [03:13] nice and quick :) === JaMa|Zz is now known as JaMa === lag is now known as Guest73840 === ericm|ubuntu is now known as ericm|prague === XorA|gone is now known as XorA === hrw|gone is now known as hrw [10:07] mornig [10:36] * cwillu_at_work dances with hrw [10:38] que? [10:38] my beagles are no longer leaking memory like little 2kb sieves === lag is now known as Guest96617 [13:26] hi to everybody... [13:26] I've the same problem... segmentation fault on line 282 in rootstock [13:27] now I'm using a physical ubuntu Lucid installation [13:27] any idea? [13:30] http://www.mail-archive.com/ubuntu-bugs@lists.ubuntu.com/msg2382346.html [13:30] furibondox: known issue [13:31] furibondox: what rootstock version are you using? [13:31] bug 604872 [13:31] Launchpad bug 604872 in qemu-kvm (Ubuntu) (and 1 other project) "qemu-system-arm segfaults emulating versatile machine after running debootstrap --second-stage inside vm (affects: 1) (heat: 8)" [Medium,Triaged] https://launchpad.net/bugs/604872 [13:31] depends on what you're installing [13:31] sometimes it just get stuck and sometimes you'll get the segfault [13:31] rsalveti: the latest from ubuntu repository [13:32] furibondox: you can try upstream version, I'm still fixing other bugs before releasing a new version [13:32] from svn? [13:32] but you're still going to have the seg fault, the only difference is that it's going to try qemu more than once [13:32] furibondox: bzr [13:32] ok [13:32] I will try [13:33] bzr branch lp:project-rootstock [13:34] I'm installing bzr [13:34] rootstock reworked to use a chroot works great :) [13:35] cwillu_at_work: using chroot instead of qemu???? [13:35] furibondox, chroot with qemu-static [13:35] chroot with qemu [13:35] ah ok [13:35] it actually works spectacularly well :p [13:36] furibondox: the problem is that the additional packages are installed with apt-get [13:36] as you can make use of as many cores as you have available, etc [13:36] with a full vm [13:36] rsalveti, I reworked it to not use the vm at all beyond the chroot itself [13:36] so, if you're still getting lots of segfault, try installing ubuntu-minimal and then installs the rest at your board [13:37] cwillu: yeah, with root this is the best way [13:37] still need to take a better look at that [13:37] cwillu_at_work: gota a patch? [13:37] not really; I've really had my way with the script [13:37] actually, I guess alot of it would be patchable [13:37] rsalveti: if I try to install ubuntu-minimal and then I create a script to install all the other packages I need and I call it with --script it should work? [13:38] yeah, don't worry, will take a better look at it later [13:38] it's pretty straightforward though [13:38] yep [13:38] it'll need some tweaks after the rootless changes.. ;) [13:38] rcn-ee: yep, but still somehow an easy change [13:39] furibondox: nops, because the script runs inside the vm [13:39] what you can do is to mount the filesystem, copy qemu static on it and chroot [13:39] then you are free to work on whatever you want [13:39] ok [13:39] https://wiki.ubuntu.com/ARM/RootfsFromScratch [13:40] furibondox: see sing qemu user mode emulation (with chroot) [13:40] *using [13:41] OK, however now I try with the latest bzr release [14:05] ogra: Can you send me the line to make boot.scr please? [14:05] mkimage *** [14:05] mkimage -A arm -T script -C none -n "Ubuntu boot script" -d [14:18] ogra: how many bytes does mkimage adds to initrd? [14:18] hrw, i think 64 ... one sec [14:19] hrw, 72 :) https://wiki.ubuntu.com/ARM/BeagleEditBootscr [14:19] * ogra knew he wrote that up somewhere [14:19] thx [14:21] ogra: ok, why does this not work?: dd if=/mnt/uInitrd skip=1 bs=72 | gunzip -c | cpio -t [14:21] ogra: Cheers [14:23] ogra: a vanilla mkimage only adds 64, no? [14:26] slangasek, probably because -T ramdisk adds different stuff [14:26] ukleinek, might be, i think it varies with the comment (-n option) [14:27] ogra: well, so how do I unpack it? :) [14:27] so the 72 might only be true if the comment is "Ubuntu boot script" [14:27] ogra: IIRC, no [14:27] slangasek, i never unpacked a uInitrd [14:28] the comment is "Ubuntu Initrd" [14:28] ukleinek, funny, then i wonder why 72 works [14:28] slangasek, you flipped bs and skip options ? [14:29] http://git.denx.de/?p=u-boot.git;a=blob;f=include/image.h;h=bcc08d1a73224bb715d15983adea4767ce0e85fc;hb=HEAD#l176, 7*4 + 4 + 32 [14:30] ogra: er, they're reversible [14:30] except that the way I've done it gives better performance :) [14:30] (and may spit a warning at the end due to a partial read) [14:58] ogra: And the uimage mkimage script? (my 'useful commands' file is at home) [15:05] lag_: mkimage -A arm -O linux -T kernel -C none -a 0x80008000 -e 0x80008000 -n "Ubuntu Kernel" -d zImage uImage [15:05] Thanks cooloney [15:08] cooloney: I'm looking at bug 566645, because I got the same thing here with latest lucid kernel [15:08] Launchpad bug 566645 in linux-ti-omap (Ubuntu Maverick) (and 2 other projects) "OTG configuration is broken on omap kernel (affects: 3) (heat: 49)" [High,Confirmed] https://launchpad.net/bugs/566645 [15:09] cooloney: if you want to test it here, or debug, I have the proper cable here [15:15] rsalveti: thanks, actually, i don't have the HW for testing, [15:16] rsalveti: can you test that lucid kernel? i did not prepare the maverick kernel [15:16] cooloney: I got it with lucid [15:16] didn't test maverick one yet [15:16] neither upstream [15:17] rsalveti: cool, how's the result of lucid testing kernel? [15:17] cooloney: if you're at prague we cat probably give you one beagleboard so you can reproduce it [15:18] cooloney: same issue with latest lucid kernel, 2.6.33-502-omap [15:18] rsalveti: awesome, i am in kernel room and love to test [15:19] robclark, https://code.edge.launchpad.net/~ogra/jasper-initramfs/trunk has the code in jasper_setup [15:19] * robclark looks [15:20] http://bazaar.launchpad.net/~ogra/jasper-initramfs/trunk/files rather [15:21] cooloney: can you get by the arm room later? just because there are lots of cables and devices to be moving around [15:21] GrueMaster, http://rcn-ee.net/deb/tools/UBOOT/u-boot-beagleboard-2010.03+r52+gitrca6e1c136ddb720c3bb2cc043b99f7f06bc46c55-r52.bin [15:21] rsalveti: no problem. i'd love to [15:21] cooloney: don't need to hurry, will be here for the whole week :-) [15:21] .oO(why did i just read "i love you" above ... ) === prpplague^2 is now known as prpplague [16:18] cooloney: now it doesn't work at all :D [16:18] was finally able to test it === lag is now known as Guest78932 [17:02] cooloney: mkimage -A arm -T script -C none -n "Ubuntu boot script" -d [17:04] Guest78932: sudo dd if=/media/4C43-C886/boot.scr of=boot.script skip=64 bs=1 [17:04] Guest78932: is this right? ^^ [17:05] Yep [17:12] bye === JaMa is now known as JaMa|FBT === fta_ is now known as fta === fta_ is now known as fta [19:27] Hello [19:28] I am looking to install Ubuntu on a Archos 5 IT, any pointers? [20:09] hi folks! [20:09] i have a little question [20:10] i'mm looking for a small system to begin with ubuntu/arm development [20:10] i would like to have some advice [20:11] which one you think is most suitable to begin?? [20:12] beagleboard? or tincantools' hammer? [20:12] loluengo, beagleboard [20:12] why? [20:12] i mean... why pcacjr? [20:13] any advantage? [20:13] hmm [20:13] it's simple to use [20:13] you could get the beagleboard C4 [20:13] it's a good hw [20:14] i think the tincantools' nail kit is also very easy [20:14] loluengo, well i've only been hacking on beagleboard lately [20:15] loluengo, http://beagleboard.org is a good start [20:15] and flyswatter for jtag progamming? [20:16] maybe :-), depends on you mate [20:16] heh [20:18] any other not-so-expensive jtag emulator recommendation? [20:19] What image do I use to install Ubuntu on an ARM device? [20:21] i looked at ti.com page and all of the emulator the recommend are VERY expensive! [20:23] loluengo: it all depends on what you want to do [20:24] loluengo: for alot of the basic operations of OMAP3 you don't really need a jtag [20:25] prpplague, what do you mean by basic operations? [20:25] loluengo: the OMAP3 has internal rom code that supports booting from SD card, uart, USB and nand flash [20:26] loluengo: so jtag isn't really needed for initial bootloader programming [20:26] prpplague, programming? debugging? tracing? [20:27] loluengo: basic programming debugging can be done via uart or other I/O, but if you really need jtag, you can use something like the flyswatter with openocd [20:27] hmmm [20:28] that sounds like a great PLUS for beagleboard [20:28] (over tincantools' hammer) [20:29] loluengo: beagle and hammer aren't exactly in the same ball park [20:29] loluengo: they are for different purposes [20:35] prpplague, why do you say that? [20:35] i see them similar [20:35] both are arm-based boards [20:35] both run linux [20:35] loluengo: the hammer was designed as a hardware developers platform with limited resources [20:36] loluengo: the beagle was designed as a software development platform with very little hardware expansion [20:36] loluengo: they are vastly different target audience [20:36] s/are/have [20:36] aaahhh ok [20:37] if i understood hammer is like a processor module - no peripherals added [20:38] and beagleboard has plenty of peripherals, intended to develop software [20:40] exactly [20:40] loluengo: the hammer is available with some peripherals, but those are mainly for testing and reference for the developer [20:43] good advice prpplague [20:43] i think hammer is for me... [20:44] my work is more hardware oriented than software oriented [20:49] loluengo: is there something specific you are planning to work on? [20:51] prpplague, yes... some kind of data logging device [20:51] loluengo: ahh [20:52] prpplague, not so interesting, but veeery useful === JaMa|FBT is now known as JaMa === fta_ is now known as fta [22:10] Hello [22:10] I'm trying to port Ubuntu to an armv6 device, that uses fbdev and am writing an xorg.conf [22:10] It uses a fbdev device [22:11] But I'm getting (ee) fbioblank Invalid argument error [22:11] Any ideas? [22:12] ogra_cmpc: Did you write rootstock by the way? === fta_ is now known as fta === XorA is now known as XorA|gone