| 00:01.46 | kergoth | rwhitby-away: want to mention the nslu2 stuff on the oe success stories page in the wiki? |
| 00:03.30 | *** join/#nslu2-linux Christopher (~Christoph@128-193-247-9.resnet.oregonstate.edu) |
| 00:06.22 | Tiersten | ka6sox: No |
| 00:09.36 | ka6sox | I was just curious... |
| 00:09.49 | ka6sox | especially the upper address bits. |
| 00:10.01 | Tiersten | Somebody said they were connected |
| 00:10.33 | ka6sox | okay. |
| 00:10.38 | ka6sox | trust but verify |
| 00:11.21 | Tiersten | trying to find it in the logs now |
| 00:11.28 | ka6sox | ty |
| 00:12.16 | Tiersten | rwhitby said so |
| 00:12.21 | Tiersten | Around August 13th |
| 00:13.23 | ka6sox | good |
| 00:13.41 | Tiersten | That's when the post was |
| 00:13.44 | Tiersten | Trying to find it at the moment |
| 00:22.28 | Tiersten | http://groups.yahoo.com/group/nslu2-linux/message/540 |
| 00:22.32 | Tiersten | Took ages to find that |
| 00:22.47 | Tiersten | The search archive feature in Yahoogroups is terrible |
| 00:23.14 | ka6sox | it is |
| 00:23.47 | Tiersten | Allan has traced it out so it should be okay |
| 00:25.05 | ka6sox | ya..I see that. |
| 00:25.08 | CodeWhacker | Important Safety Tip: initrd=0x01000000,16M does not work very well at all |
| 00:25.41 | Tiersten | 0x1000000 = 16777216 |
| 00:26.03 | Tiersten | You'll hit the end of RAM by doing that and that's a bad thing |
| 00:26.39 | CodeWhacker | rats! well, the 10M setting appears a bit small for the ramdisk contents |
| 00:26.53 | Tiersten | Try something in between |
| 00:27.36 | Tiersten | You can't change the 0x01000000 as that is where redboot loads the ramdisk |
| 00:27.44 | Tiersten | If you want to change it then you must change redboot |
| 00:28.09 | CodeWhacker | not trying to change the base address |
| 00:43.08 | ka6sox | Tiersten: anything else before I reflash to uNLSUng? |
| 00:43.18 | Tiersten | Nope |
| 00:43.30 | ka6sox | k |
| 00:43.57 | ka6sox | I'll install 1.92 again unless you want me to test 1.94. |
| 00:45.05 | Tiersten | 1.94 is still broken. I've not had any time in the last few days to look at it. Been busy with real work |
| 00:46.22 | ka6sox | real life sometimes is like that :P |
| 00:46.50 | Tiersten | Yeah. Sucks :) |
| 00:47.02 | Tiersten | I have to document the process to build redboot as well |
| 00:47.05 | Tiersten | Not that it's hard |
| 00:50.07 | ka6sox | ah |
| 00:53.41 | CodeWhacker | doubleplusungood results |
| 00:53.50 | Tiersten | ? |
| 00:54.01 | CodeWhacker | initrd=0x01000000,13M fails as well |
| 00:54.18 | Tiersten | Let me have another look at the redboot code |
| 00:54.38 | CodeWhacker | you want to see the error? |
| 00:55.55 | Tiersten | The redboot code should load anything that fits |
| 00:56.15 | Tiersten | It doesn't have any limits on how big it is apart from size of flash and size of RAM |
| 00:56.16 | CodeWhacker | checking if image is initramfs...it isn't (no cpio magic); looks like an initrd |
| 00:56.16 | CodeWhacker | Division by zero in kernel. |
| 00:56.16 | CodeWhacker | [<c0054bc4>] ($a+0x0/0xfa4) from [<c0055ef4>] (try_to_free_pages+0x100/0x1f0) |
| 00:56.16 | CodeWhacker | [<c0055df4>] (try_to_free_pages+0x0/0x1f0) from [<c004da38>] ($a+0x208/0x304) |
| 00:56.16 | CodeWhacker | [<c004d830>] ($a+0x0/0x304) from [<c004b8b4>] (generic_file_aio_write_nolock+0x5e4/0xa7c) |
| 00:56.17 | CodeWhacker | [<c004b2d0>] (generic_file_aio_write_nolock+0x0/0xa7c) from [<c004be84>] ($a+0x58/0x80) |
| 00:56.19 | CodeWhacker | [<c004be2c>] ($a+0x0/0x80) from [<c004bf68>] (generic_file_write+0x54/0x80) |
| 00:56.21 | CodeWhacker | <PROTECTED> |
| 00:56.23 | CodeWhacker | [<c004bf14>] (generic_file_write+0x0/0x80) from [<c0066e74>] (vfs_write+0xe4/0x11c) |
| 00:56.25 | CodeWhacker | <PROTECTED> |
| 00:56.27 | CodeWhacker | [<c0066d90>] (vfs_write+0x0/0x11c) from [<c0066f44>] (sys_write+0x3c/0x58) |
| 00:56.29 | CodeWhacker | [<c0066f08>] (sys_write+0x0/0x58) from [<c000bc6c>] ($a+0xb4/0xd0) |
| 00:56.31 | CodeWhacker | <PROTECTED> |
| 00:56.33 | CodeWhacker | [<c000bbb8>] ($a+0x0/0xd0) from [<c001a1ac>] ($a+0x34/0x174) |
| 00:56.35 | CodeWhacker | <PROTECTED> |
| 00:56.37 | CodeWhacker | [<c001a178>] ($a+0x0/0x174) from [<c00333d0>] (do_exit+0x0/0xa04) |
| 00:56.39 | CodeWhacker | <PROTECTED> |
| 00:56.43 | CodeWhacker | and that repeats forever |
| 00:56.47 | Tiersten | You really don't need to paste the entire stacktrace |
| 00:56.52 | CodeWhacker | sorry |
| 00:56.58 | Tiersten | There is probably something you hitting at the end of memory |
| 00:57.02 | CodeWhacker | wasn't sure how much was relevant |
| 00:58.01 | CodeWhacker | well, the old value was 10M, and the current ramdisk unpacks to just over 12M |
| 00:58.38 | Tiersten | You're probably overwriting something at the end |
| 01:03.54 | ka6sox | catch you on the other side. |
| 01:04.43 | Tiersten | ? |
| 01:05.23 | CodeWhacker | something doesn't make sense here |
| 01:06.16 | CodeWhacker | when I unpack and mount the ramdisk, it only shows 4.4M used up, vs 4.0M from the Sunday build |
| 01:07.24 | CodeWhacker | so why is the unpacked size so much larger? |
| 01:07.29 | ka6sox | (headed home) |
| 01:08.13 | Tiersten | You got lots of little files? |
| 01:08.30 | Tiersten | http://shop4.outpost.com/product/3321502/ if anybody is interested |
| 01:10.46 | CodeWhacker | Tiersten: doesn't look like it, and the larger version only has 11 more files than the smaller one |
| 01:11.08 | Tiersten | How did you create the ramdisk? |
| 01:11.19 | CodeWhacker | oemake bootstrap-image |
| 01:11.27 | CodeWhacker | looking for the creation command now |
| 01:12.11 | dyoung-web2 | whats your CONFIG_DEV_BLK_RAM_SIZE set to? |
| 01:14.08 | CodeWhacker | dyoung: where's that? |
| 01:14.45 | dyoung-web2 | Kernel Config. |
| 01:15.19 | CodeWhacker | CONFIG_BLK_DEV_RAM_SIZE=10240 |
| 01:16.28 | CodeWhacker | df says: |
| 01:16.41 | CodeWhacker | oops |
| 01:17.07 | CodeWhacker | home/roy/workspace/NSLU2/oe/build-nslu2-openslug/tmp/deploy/images/ramdisk |
| 01:17.07 | CodeWhacker | <PROTECTED> |
| 01:17.07 | CodeWhacker | /tftproot/tmp/ramdisk |
| 01:17.07 | CodeWhacker | <PROTECTED> |
| 01:17.40 | CodeWhacker | really just looks like the ramdisk was arbitrarily created larger |
| 01:19.30 | dyoung-web2 | Well, the 12M ramdisk wont fit because of that CONFIG_BLK_DEV_RAM_SIZE paramater is set to exactly 10M. I dunno about the smaller one though. |
| 01:20.07 | CodeWhacker | ok, that makes sense |
| 01:21.24 | Tiersten | It's set to 10? |
| 01:21.31 | Tiersten | The stock one is 16MB |
| 01:25.21 | CodeWhacker | adjusted and rebuilding |