I resolved the file system error and now i am able to boot my machine with 3.4.9 Kernel. But still i am facing issues while setting up KGDB,below is the issues i am facing on both development and test machine:
1) Development machine (This machine have KERNEL to be debugged):
i have added below arguments in grub.cfg file for KGDB to wait for remote GDB connection establishment:
kgdbwait kgdboc=ttyUSB0,115200
Again I booted my machine, and now i am able to see below message on screen but for very few seconds , after that machine starts booting normally.Can we pass some time delay till GDB debugger get connected to the test machine ??
waiting for remote connection.........
2) Test Machine (where GDB is running for remote debugging):
I have copy vmlinux file to test machine and start GDB session by giving following below commands:
gdb ./vmlinux (after running this command i m getting below logs)
GNU gdb (Ubuntu/Linaro 7.2-1ubuntu11) 7.2
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /home/rohit/vmlinux...done.
set debug remote 1
target remote /dev/ttyUSB0 ( please see below logs after running command)
(gdb) target remote /dev/ttyUSB0
Remote debugging using /dev/ttyUSB0
Sending packet: $qSupported:xmlRegisters=i386;qRelocInsn+#25...Sending packet: $qSupported:xmlRegisters=i386;qRelocInsn+#25...Sending packet: $qSupported:xmlRegisters=i386;qRelocInsn+#25...Sending packet: $qSupported:xmlRegisters=i386;qRelocInsn+#25...Timed out.
Timed out.
Timed out.
Ignoring packet error, continuing...
Packet qSupported (supported-packets) is supported
warning: unrecognized item "timeout" in "qSupported" response
Sending packet: $Hg0#df...Sending packet: $Hg0#df...Sending packet: $Hg0#df...Sending packet: $Hg0#df...Timed out.
Timed out.
Timed out.
Ignoring packet error, continuing...
Sending packet: $?#3f...Sending packet: $?#3f...Sending packet: $?#3f...Sending packet: $?#3f...Timed out.
Timed out.
Timed out.
Ignoring packet error, continuing...
Sending packet: $Hc-1#09...Sending packet: $Hc-1#09...Sending packet: $Hc-1#09...^CQuit
Can you please help me out in this ?
Thanks for your support
Thanks
Vivek
On Wed, Oct 17, 2012 at 9:36 PM, Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx> wrote:
Hi....
> I did some googling and found one clue that i have to change file system inhm, since your root fs is ext4, well then I guess that is safe...
> menuconfig file for EXT4 , which support both EXT2 and EXT3 as well,
> so for that i have enable below features in file systems...
>
> # CONFIG_EXT2_FS=n
> # CONFIG_EXT3_FS=n
> CONFIG_EXT4_USE_FOR_EXT2 3=Y
not sure what this variable does. Are you sure it is safe?
anyway, are you sure that the ext4 support itself is already enabled?
either as built in (=Y) or module (=m). If you choose to make it as
module, don't forget to rebuild the initrd/initramfs. Usually "make
install" in the kernel source tree will take care of that.
not sure what to say here...but I guess that warning is normal because
> After these modifications i crossed earlier error but hit back with 2 new
> errors , below is the description:
>
> 1) EXT4-fs(sda2): could not mount as ext3 due to feature incompatibilities
> EXT4-fs(sda2): could not mount as ext2 due to feature incompatibilities
ext4 is not really backward compatible to ext3/2
--
regards,
Mulyadi Santosa
Freelance Linux trainer and consultant
blog: the-hydra.blogspot.com
training: mulyaditraining.blogspot.com
_______________________________________________ Kernelnewbies mailing list Kernelnewbies@xxxxxxxxxxxxxxxxx http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
