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