Re: Break point not hit while debugging linux kernel with kgdb

[Anil Nair]

Hello Prasanna,

On Sun, Jun 10, 2012 at 10:20 AM, prasannatsmkumar
<prasannatsmkumar@xxxxxxxxx> wrote:
> In one of the machines I am facing a scenario:
> I recompiled Ubuntu linux kernel (with the default config taken from
> /boot) and the newly compiled kernel does not boot. After detecting
> the hard disk (SCSI device) it panics.

Did you compile the kernel using standard step? Which Ubuntu version
you are trying to install your customized kernel? What is the kernel
version you are trying to compile? For ubuntu distribution standard
steps are given at their site for compiling customized kernel, i
followed those steps and was able to compile and install customized
kernel. Here is the link for it,

https://help.ubuntu.com/community/Kernel/Compile

>I am able to see only a part of
> the kernel stack trace due to low resolution so I am in a situation
> where I cannot do anything further. In this situation kgdb seems to be
> the only way.

Also, i think so the kernel is in panic due to the reason that it
couldn't find initial ram disk. Did you create an initial ram disk
while compiling and installing the kernel? I came through the same
situation that is why i am asking?
are you using mkinitramfs command for creating ramdisk? trying using
update-initrd command, google for it i forgot its usage.! :). After
creating ramdisk move it to the /boot directory and update the grub
using the update-grub command.


I hope this may solve you problem. :)

-- 
Regards,
Anil Nair
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/