Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754106Ab2FKDiH (ORCPT ); Sun, 10 Jun 2012 23:38:07 -0400 Received: from mail-ob0-f174.google.com ([209.85.214.174]:47243 "EHLO mail-ob0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753877Ab2FKDhp (ORCPT ); Sun, 10 Jun 2012 23:37:45 -0400 MIME-Version: 1.0 In-Reply-To: References: <4FD39A7F.9020106@mvista.com> Date: Mon, 11 Jun 2012 09:07:44 +0530 Message-ID: Subject: Re: Break point not hit while debugging linux kernel with kgdb From: Anil Nair To: prasannatsmkumar Cc: Sergei Shtylyov , linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1732 Lines: 43 Hello Prasanna, On Sun, Jun 10, 2012 at 10:20 AM, prasannatsmkumar 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/