[00:01] <rcn-ee> i was just thinking of another possibilty, little out their..... omap core bug between revisions?
[00:02] <rcn-ee> overo: OMAP3525 ES2.1 beagle: OMAP3430/3530 ES3.0
[00:03] <rcn-ee> actuallly let me try btrfs on my old Bx board...
[00:03] <rcn-ee> it's ES2...
[00:06]  * rcn-ee quickly rebuilds a new rootfs, as it has the older 2.6.32.11 kernel...
[00:13] <rcn-ee> cwillu_at_work, this issue didnt' happen with 2.6.32.11 right?  I'm still rebuilding the new image, but this with 2.6.32.11 on my old beagle OMAP3430/3530 ES2.1 http://pastebin.com/5DhUsa27
[00:14] <rcn-ee> nm it would help to have btrfs tools isntalled...
[00:14] <cwillu_at_work> heh
[00:14] <cwillu_at_work> not fatal though
[00:14] <cwillu_at_work> I'd dying long before I get to btrfs-fsck
[00:14] <rcn-ee> ah okay...
[00:15] <cwillu_at_work> I'm going to retry with 2.6.32.1-x1.0 (i.e., the random uImage I have lying around :p)
[00:16] <rcn-ee> rootstock is almost done for me, just tarring...
[00:17] <cwillu_at_work> booting now
[00:18] <cwillu_at_work> init: procps main process (666) terminated with status 255
[00:18] <cwillu_at_work> [   40.506011] device fsid c24abdbd5df3226a-2ff6a72b00d09595 devid 1 transid 6466 /dev/root
[00:18] <cwillu_at_work> [   40.516143] btrfs: use spread ssd allocation scheme
[00:18] <cwillu_at_work> [   40.552825] VFS: Mounted root (btrfs filesystem) readonly on device 0:13.
[00:18] <cwillu_at_work> [   40.559814] Freeing init memory: 184K
[00:18] <cwillu_at_work> init: procps main process (666) terminated with status 255
[00:19] <cwillu_at_work> and then it dies waiting for rootfs
[00:19] <cwillu_at_work> init prompt comes up to bring up a maintenance shell, but the shell doesn't start
[00:21] <cwillu_at_work> and... there's the csum error
[00:21] <rcn-ee> part of the shell scripts are in the uinird now...
[00:21] <rcn-ee> but it should still run from the disk, like previously..
[00:21] <cwillu_at_work> be aware, I'm not using an initrd :p
[00:22] <rcn-ee> shouldn't matter.. just less random notuseful errors on bootup
[00:22] <rcn-ee> init: procps main process (666) terminated with status 255
[00:22] <cwillu_at_work> sounds familiar
[00:22] <rcn-ee> oh i was quoting you...  it's untaring to my mmc that refused to umount...
[00:22] <cwillu_at_work> ah, k
[00:22] <cwillu_at_work> heh
[00:23] <cwillu_at_work> refusing to umount generally means it's still writing everything out :p
[00:23] <cwillu_at_work> umount is the thing that takes 10-15 minutes on my mkcard script :)
[00:23] <rcn-ee> exactly what i was seeing...
[00:23] <persia> The easy way to avoid that is to have much less RAM :)
[00:23] <cwillu_at_work> heh
[00:24] <cwillu_at_work> csum error in /sbin/mountall this time
[00:24] <cwillu_at_work> race condition!
[00:24] <cwillu_at_work> or, what happens on 2.6.32 instead of 2.6.33
[00:26] <cwillu_at_work> persia, not really avoiding anything, it's the same wait time :p
[00:26] <cwillu_at_work> but don't you worry, my zippy2 will be here monday, and then I can make my root images from the ram constrained heaven of a beagle!
[00:26] <rcn-ee> man it really want's the btrfs tools... but otherwise no csum error.. http://pastebin.com/Fya99DmH
[00:27] <rcn-ee> btw, check your zippy2, some have the zippy1 id, forum post in the beagleboard forum about it...
[00:27] <cwillu_at_work> k
[00:28] <cwillu_at_work> btrfs.fsck both doesn't do anything, and doesn't take the same options as normal fsck
[00:28] <cwillu_at_work> can you hack up /etc/init/mount to not do the fsck?
[00:29] <rcn-ee> your mouting ro from the bootargs?
[00:29] <rcn-ee> rw shoudl by pass the fsck pass..
[00:29] <rcn-ee> or modify /etc/fstab... ;)
[00:29] <cwillu_at_work> was referring to your paste
[00:29] <rcn-ee> umounts...
[00:30] <cwillu_at_work> I mount rw generally, doesn't make any difference when I tried it the other day though
[00:31] <cwillu_at_work> (no difference to getting the overo to boot, that is)
[00:31]  * cwillu_at_work considers ordering a pizza
[00:33] <rcn-ee> and i get login... http://pastebin.com/KLUUqKVB  so probally not a ES2.1 to ES3 bug...
[00:34] <cwillu_at_work> yep
[00:36] <rcn-ee> would btrfs file check show us anything?
[00:37] <cwillu_at_work> just reading a file is sufficient
[00:37] <cwillu_at_work> it would show a csum error if the file contents changed, and a tree csum error if the metadata was changed (and there's automatically duplication of metadata pages)
[00:37] <cwillu_at_work> part of the joke is that it doesn't leave much for fsck to do :)
[00:38] <rcn-ee> yeah, cause it takes care of alot of it...
[00:43]  * cwillu_at_work runs badblocks against the mmc reader, and orders a pizza
[01:56] <NCommander> lool: you around?
[11:31] <playya> moin
[11:31] <playya> anyone has some documentation about ARM OABI?
[11:36] <hrw> oabi?
[11:38] <hrw> playya: http://www.chiark.greenend.org.uk/~theom/riscos/docs/CodeStds/APCS.txt
[11:40] <playya> ok. reading. thx
[11:41] <playya> there're a lot of ARM docs about EABI, but no OABI :/
[12:03] <hrw> oabi has to die
[12:09] <ogra> i thought it is dead
[12:09] <ogra> (at least it smells like)
[13:09] <vaibahv> ..
[13:42] <NC|Out> lool: you around? not sure if you saw my earlier ping w.r.t. to ARM subarch detection
[17:23] <lool> NCommander: 02:56 < NCommander> lool: you around?
[17:23] <lool> NCommander: 3 am is not going to work
[17:23] <lool> NCommander: FYI:
[17:23] <lool> 13:11 < lool> asac: Any input on the improved-subarch detection spec?
[17:23] <lool> 13:12 < lool> asac: I'm going to prepapprove it, we can decide to schedule or  not
[17:25] <ogra> 3am is a safe time to be sure you are not in meetings !
[17:25] <ogra> :)
[21:03] <prpplague> ogra: ping