**** BEGIN LOGGING AT Tue Mar 05 02:59:58 2013 Mar 05 11:28:57 Hi! Yesterday I recompiled https://github.com/radekp/linux-2.6/tree/v2.6.34-gta02-qtmoko-v48. I get kernel panic when I booted it. May it be due to cross compiler I used? Mar 05 11:29:51 txor: hi, hmm hard to tell :) Mar 05 11:30:16 txor: if you are using qi as bootloader try hold POWER during boot - it will make it verbose Mar 05 11:31:28 txor: btw did you use your own config or changed anything? Mar 05 11:31:47 Y don't changed anything, .config from git. Mar 05 11:32:22 I used cross-tools from eCos, they compiled without errors... Mar 05 11:32:42 the config in arch/arm/configs/gta02_defconfig? Mar 05 11:33:05 Maybe the method of booting? I made two partitions, one with the uImage.bin and the other with the rootfs. Mar 05 11:33:28 radekp, No, a .config that appeared on linux-2.6 folder. Mar 05 11:33:53 if you use qi bootloader one ext3 partition is enough - qi will load the uImage-GTA02.bin from /boot dir on that ext3 Mar 05 11:35:45 I am interested on u-boot as it seems to be capable of booting eCos images (another RTOS). Mar 05 11:36:04 Could u-boot be the problem? Mar 05 11:36:09 txor: ahh oki, i think i have removed the .config in later versions and it's now in arch/arm/config location.. Mar 05 11:36:18 txor: yes Mar 05 11:36:38 txor: if you use uboot from NOR it cant load the image, because it's > 2MB Mar 05 11:37:47 txor: btw is AUX led blink when the boot fails? that should indicate kernel panic Mar 05 11:39:47 radekp, I see the kernel panic on the screen. Mar 05 11:40:03 oki, any useful message? Mar 05 11:40:17 radekp, Let me see! Mar 05 11:41:51 Kernel panic - not syncing: No init found. Try passing init= optiont to the kernel. See Doc blah blah. Mar 05 11:42:10 Hehe, wrong boot directive? Mar 05 11:42:40 Maybe I forgot to modify u-boot options!? Mar 05 11:42:42 wrong partitioning or root filesystem Mar 05 11:42:48 Ah! ok. Mar 05 11:42:56 imo it failed to mount rootfs Mar 05 11:43:08 * radekp has to go for lunch Mar 05 11:43:29 Bon appetit! Mar 05 12:06:04 txor: so, what is that before the kernel panic? Mar 05 12:06:22 txor: what partition was mounted as rootfs? Mar 05 12:06:38 txor: have you modified root= accordingly to your setup? Mar 05 12:06:51 txor: just pastebin the serial output for your whole boot Mar 05 12:07:25 Ok, give me a minute! Mar 05 12:14:14 Ok now the message is a little different, with a panic also. Mar 05 12:17:18 PaulFertser, How I can read the serial output? Using USB and connecting to ttyACM0? Mar 05 12:17:57 PaulFertser, I need to enter the u-boot prompt, right? Mar 05 12:19:11 txor: you've the debugboard, so simply connect to its ttyUSB0 with a terminal emulator, how else?.. Mar 05 12:20:44 PaulFertser, Oh yes! But now I am at u-boot promt, I see the boot_m line and it says ext2. As I have ext3 on my second partition, I need to change it right? Mar 05 12:24:51 txor: eh, too little info to say anything, you're talking riddles atm Mar 05 12:27:42 Hehe, sorry. Let me connect debug board! Mar 05 12:35:24 PaulFertser, at last! Here is my boot pastebin http://pastebin.com/AHTVSJXy Mar 05 12:35:56 The second part is formatted as ext3 partition Mar 05 12:36:09 Maybe that is one of the problems... Mar 05 12:38:06 txor: in you command remove the loglevel (or use loglevel=7) and rerun and repaste. Mar 05 12:38:50 txor: i mean in kernel arguments Mar 05 12:41:09 PaulFertser, You want me to change bootargs_base env varible? Mar 05 12:41:47 PaulFertser, How can I do it? Using setenv command? Mar 05 12:42:01 txor: sure Mar 05 12:42:07 txor: feel free to read the u-boot manual ;) Mar 05 12:43:52 PaulFertser, You're right, I need to read it! :D Mar 05 12:48:15 PaulFertser, Wow! Now a lot of output is going through the screen but not on to serial... Mar 05 12:50:56 I see a suspicious error message: Please append a correct "root=" boot option... Mar 05 12:51:57 It shows two options: Mar 05 12:51:59 if00 2048 mtdblock0 Mar 05 12:52:12 if01 262144 mtdblock1 Mar 05 12:52:13 txor: to get them on serial, use console=/dev/ttyS0 Mar 05 12:52:31 PaulFertser, Thanks I'll pastebin it. Mar 05 12:53:15 txor: sounds like you get no sd card detected. You might need "rootwait" option for that. Mar 05 12:57:53 PaulFertser, It won't write to minicom... :_ I used bootargs_base=rootfstype=jffs2 root=/dev/mtdblock6 console=ttySAC2,115200 console=ttyS0 loglevel=7 regular_boot Mar 05 12:58:23 and also console=/dev/ttyS0 Mar 05 13:00:13 a random question, does openmoko work with an android kernel? *because i'm not sure about the modules for the wireless, and that stuff* Mar 05 13:02:40 txor: yes, ttyS0 is meaningless on gta02, you need to use ttySAC2,115200 indeed Mar 05 13:02:57 Exio: there's some android port to gta02 Mar 05 13:03:11 i meant openmoko the "distro" Mar 05 13:03:21 txor: i guess your final bootargs have different console Mar 05 13:04:58 i would like to try to compile some distro to my lg p350, just for checking if it works Mar 05 13:13:00 PaulFertser, Maybe this is a clue: http://pastebin.com/GifkYLpC at u-boot prompt Mar 05 13:13:31 txor: nah, it's ok for that uboot version Mar 05 13:14:37 PaulFertser, Should I be able to list the ext3 filesystem from u-boot? Mar 05 13:14:54 PaulFertser, Maybe it would be easy If I format with ext2 xD! Mar 05 13:39:49 txor: it doesn't matter, your kernel boots and it doesn't care if you your uboot can see some partition or not. Mar 05 13:39:54 txor: just do what i suggested Mar 05 14:22:14 I could hack the uboot commands, saveenv does not have any effect and then I executed the commands on uboot prompt: rootwait seems to let kernel to detect the partitions. I still can't get the kernel log on the serial console... Mar 05 14:23:56 I gonna try more to get the log on the serial console. Mar 05 14:24:16 Interesting complaint are: Mar 05 14:24:37 JDB: no valid journal superblock found Mar 05 14:25:26 EXT3-fs (mmcblk0p2): error loading journal Mar 05 14:25:56 Arg... How ugly looks here! :S Mar 05 15:09:20 txor: mmcblk0 means your sd is visible Mar 05 15:09:32 txor: and that it'll work now if the journal is good Mar 05 15:30:38 PaulFertser, I still can't get the log on the serial console... Now the system did not complaint but it stops at message "Waiting for root device..." Mar 05 16:42:03 txor: but was it able to find SD card this time? Mar 05 16:42:11 txor: i hope you're not using nor u-boot, are you? Mar 05 17:28:16 PaulFertser, It foun the SD card and I think I am using nor u-boot, which uboot should I use? Mar 05 17:28:56 txor: you should flash u-boot to nand Mar 05 17:29:05 txor: you can't save env changes in nor u-boot. Mar 05 17:29:14 Thats it! xD Mar 05 17:29:37 txor: were you trying to boot qtmoko from NAND? Mar 05 17:29:48 PaulFertser, Can I brick my Freerunner doing such thing? Mar 05 17:29:58 txor: no, you have a debugboard Mar 05 17:30:10 PaulFertser, I thing i trying to boot from SD Mar 05 17:30:26 txor: ok, so you should use nand uboot and configure the kernel command line appropriately. Mar 05 17:32:20 PaulFertser, In the last try I booted the system using my own u-boot commands line by line, I think that they can be enough for now. Do you? Mar 05 17:32:32 I'll pastebin my commands: Mar 05 17:33:14 txor: i think that's not funny to boot every time manually adjusting the command line. Also NOR u-boot has known issues with power-saving etc. It doesn't make any sense to use it apart from some recovery. Mar 05 17:34:24 I prefer to test it this way first until it works, then I can put u-boot on nand, here are the commands: http://pastebin.com/s30wKuSe Mar 05 17:34:49 txor: how would having uboot in nand harm testing? :) Mar 05 17:35:03 PaulFertser, But if you really recommend mi to use nand I'll do it! Mar 05 17:35:22 txor: well, you'll have persistent u-boot env, i'd say worth it :) Mar 05 17:35:57 txor: how exactly are you using your debug board for the serial? Mar 05 17:36:05 txor: that command line looks like it should do the thing. Mar 05 17:36:14 PaulFertser, I understand that nand is not harming the tests, It's only for save some time! Mar 05 17:38:05 PaulFertser, log is still resistng to go to the serial port.... Mar 05 17:39:20 txor: how exactly are you using your debug board for the serial? Mar 05 17:40:53 txor: are you using ttyUSB0 or ttyUSB1? Should be USB1! Mar 05 17:41:07 txor: do you not enable flow control of any kind? Mar 05 17:41:26 PaulFertser, It's connected with JTAG, and I have 4 termials, one with minicom listening on /dev/ttyUSB0, one with openocd running, one with a telnet on localhost 4444 to use JTAG commands from openocd serve, and one with neocon listening to /dev/ttyACM0... Mar 05 17:41:47 PaulFertser, minicom recives the first messages from u-boot Mar 05 17:42:03 txor: ah, so it does use the right port, ok. Mar 05 17:42:06 PaulFertser, I didn't ever see a /dev/ttyUSB1 Mar 05 17:42:11 Ok Mar 05 17:42:31 But minicom not recives the kernel buffer output Mar 05 17:42:40 I see, the debugboard is using an additional eeprom, i guess that's why it works like it should. Mar 05 17:42:48 (with USB0 and not USB1) Mar 05 17:43:30 PaulFertser, How can I confirm that? Mar 05 17:44:02 txor: should the command be console=ttySAC2,115200n8 (and not simply 115200?) Mar 05 17:44:11 PaulFertser, I can send you a photo of the board! :D Mar 05 17:44:17 PaulFertser, I'll try! Mar 05 17:44:25 txor: no, i do not need a photo, i have schematics. Mar 05 17:44:33 txor: i just didn't pay attention to that eeprom. Mar 05 17:45:16 PaulFertser, Ok I go to try the 115200n8 line. Mar 05 17:55:09 txor: chances are something is wrong in your kernel Mar 05 17:55:20 txor: and that would be the reason it doesn't say anything on serial. Mar 05 17:55:29 txor: pastebin your dmesg Mar 05 17:55:37 (i mean on device) Mar 05 17:57:33 PaulFertser, something is wron on my device? Mar 05 17:57:38 wrong** Mar 05 17:58:23 A friend lend it to me, It is possible that he configured someting tricky! Mar 05 17:58:59 txor: no, since uboot is outputting all right, it means both your device hardware and your host's hardware and software works fine. It might be some odd kernel config on compilation that's preventing the output, pastebin its dmesg please. Mar 05 18:00:15 PaulFertser, Ok but I need the serial working first right? Mar 05 18:02:17 txor: you say it's working already because you see uboot's output. Mar 05 18:03:02 yes but dmesg output didn't appear, it stops printing at "Uncompressing Linux... done, booting the kernel." Mar 05 18:04:27 txor: you can obtain dmesg over usb networking Mar 05 18:04:30 Or wifi Mar 05 18:11:15 PaulFertser, the rootfs boot folder has to be empty? Mar 05 18:11:56 PaulFertser, Do the net will be running? I can't see if the system is! Mar 05 18:13:51 txor: the rootfs boot folder is irrelevant for you way of booting. Mar 05 18:13:55 txor: try different kernel Mar 05 18:19:22 PaulFertser, console=ttySAC2,115200n8 worked! Now I have the dmesg output on minicom!! :D Mar 05 18:19:53 txor: yay :) Mar 05 18:20:30 PaulFertser, http://pastebin.com/whyxzDkk at last :))) Mar 05 18:21:25 txor: congrats! Mar 05 18:21:36 txor: looks like it can't mount the partition, can you do e2fsck on your host? Mar 05 18:21:54 txor: and are you sure it's ext3 and not ext2 now? Mar 05 18:22:06 txor: better omit rootfstype altogether Mar 05 18:22:50 PaulFertser, I formated it woth mkfs.ext3 command on my host... Mar 05 18:23:14 txor: e2fsck it now Mar 05 18:23:25 PaulFertser, Ok Mar 05 18:23:39 txor: ah, one other thing Mar 05 18:24:26 txor: try glamo_mci.sd_max_clk=10000000 Mar 05 18:24:39 txor: some cards can't work on full speed for whatever reason, so try 10MHz instead Mar 05 18:25:19 PaulFertser, e2fsck reports that is clean. Mar 05 18:25:35 txor: ok, sd_max_clk that is then Mar 05 18:25:59 Now Ok Mar 05 18:33:17 txor: when are you going to actually start hacking on eCos? ;) Mar 05 18:34:44 PaulFertser, Ops! System down... xD Mar 05 18:35:18 txor: what do you mean? Were you able to boot? Mar 05 18:35:45 PaulFertser, I first need a kernel source reference code, that's why I want a working recompiled kernel. Also I compiled it with eCos cross-tools :) Mar 05 18:36:24 PaulFertser, My host crashed, I changed USB and my kernel entered on a buggy state lol! Mar 05 18:37:00 I'll restart the tests... Ah yes the sd_max_clk... Mar 05 18:46:16 PaulFertser, I tried "setenv bootargs rootfstype=ext3 root=/dev/mmcblk0p2 console=ttySAC2,115200n8 console=tty0 loglevel=7 glamo_mci.sd_max_clk=10000000 regular_boot rootwait rootdelay=5 \${mtdparts}" with the same results as before... Mar 05 18:46:38 PaulFertser, Now I'll try different kernels... Mar 05 18:47:11 PaulFertser, Maybe the best one will be the official uImage? Mar 05 18:48:31 txor: i suggested you omit rootfstype altogether Mar 05 18:51:03 PaulFertser, Yes right! Mar 05 18:51:46 txor: btw, rootwait is enough, you do not need rootdelay i think. Mar 05 18:56:52 PaulFertser, I am testing now with the kernel on http://sourceforge.net/projects/qtmoko/files/GTA02/uImage.bin-2.6.34-qtmoko-v48/download Mar 05 18:57:09 txor: i suggest you try ext2 rootfs for a change Mar 05 18:57:17 I used "setenv bootargs root=/dev/mmcblk0p2 console=ttySAC2,115200n8 console=tty0 loglevel=7 regular_boot rootwait \${mtdparts}" Mar 05 18:57:31 txor: gotta go to sleep, man, see you later Mar 05 18:57:38 And new dmesg output: http://pastebin.com/ZyKNULad Mar 05 18:57:53 PaulFertser, Ok Paul!! Tahnks you very much for your help Mar 05 18:58:13 PaulFertser, See you another day! Mar 05 18:58:29 PaulFertser, Really much thanks! Mar 05 18:58:54 Thanks all, you helped me much!! :D Mar 05 18:59:36 txor: your glamo_mci.sd_max_clk=10000000 Mar 05 18:59:45 txor: missing in the last paste Mar 05 19:00:07 txor: never hurt to lower the speed to be safe Mar 05 19:00:35 txor: also, check you have proper /sbin/init on the second partition of that card Mar 05 19:01:42 PaulFertser, Thanks Paul and good night! Mar 05 19:02:21 txor: and untar using sudo and "-p" to preserve the ownership (and other flags) Mar 05 19:02:25 txor: bye Mar 05 19:02:30 PaulFertser, cu **** ENDING LOGGING AT Wed Mar 06 02:59:58 2013