hi, zhangfx,
thank you for your reply, I added printf to the init.c file of
android file system code (system/core/init/init.c), and found that the
kernel panic after the "open_devnull_stdio" is called, so I think the
kernle panic in that function, I will check the exact point the error
arise.
as you said " For illegal instructions,you can add printk in arch/
mips/kernal/traps do_ri entrance", did you mean whenever illegal
instructions executed, the do_ri function will be called?
andy
On 12月2日, 上午7时59分, zhangfx <zhan...@lemote.com> wrote:
> For illegal instructions,you can add printk in arch/mips/kernal/traps do_ri
> entrance
> zhangfx <zhan...@lemote.com>编写：
> The kill init message means your init process exit(it should never),it is not
> kernal fault, try add prints in init source code to find out reason,probably
> due to illegal instruction,or wrong init.rc
> 李晖 <lihui205...@gmail.com>编写：
> Hi, all I am porting android to loongson2f, the android file system(froyo)
> and android linux kernel(2.6.35) was compiled succeed, then I put them to two
> separate partition of u-disk which was partitioned to ext3, then I start the
> loongson machine and step into the pmon environment and I typed: load
> /dev/fs/ext2@usb0/vmlinux.32 g console=tty root=/dev/sda2 rw init=/init
> rootwait androidboot.console=ttyS0 after which, the penguin logo appeared,
> and the following info was printed: ...... ...... ...... EXT3-fs (sda2):
> using internal journal EXT3-fs (sda2): recovery complete EXT3-fs (sda2):
> mounted filesystem with writeback data mode VFS: Mounted root (ext3
> filesystem) on device 8:2. Freeing unused kernel memory: 240k freed Kernel
> panic - not syncing: Attempted to kill init! By insight into the linux kernel
> source code, I found that it was the time the kernel mount the filesystem
> that the kernel panic, but I don't know the exact place the kernel panic. So,
> in order to find exact point the kernel panic, I want to debug the kernel, I
> found that a tool called kgdb can debug linux source in source code, but
> there is not tool corresponding to 2.6.35 or higher linux kernel exist in the
> official size, so I want to know how did you debug the loongson linux kernel?
> any suggestion or tips well be greatly appreciated!!! andy -- You received
> this message because you are subscribed to the Google Groups "loongson-dev"
> group. To post to this group, send email to loongson-dev@googlegroups.com. To
> unsubscribe from this group, send email to
> loongson-dev+unsubscr...@googlegroups.com. For more options, visit this group
> at http://groups.google.com/group/loongson-dev?hl=en.
>
> --
> You received this message because you are subscribed to the Google Groups
> "loongson-dev" group.
> To post to this group, send email to loongson-dev@googlegroups.com.
> To unsubscribe from this group, send email to
> loongson-dev+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/loongson-dev?hl=en.
--
You received this message because you are subscribed to the Google Groups
"loongson-dev" group.
To post to this group, send email to loongson-dev@googlegroups.com.
To unsubscribe from this group, send email to
loongson-dev+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/loongson-dev?hl=en.
