From mboxrd@z Thu Jan  1 00:00:00 1970
From: chris@basementcode.com (Christopher Harvey)
Date: Thu, 30 Jun 2011 08:12:21 -0500
Subject: Debugging a custom kernel
In-Reply-To: <20110629212741.GG5604@hermes>
References: <20110629201441.GF5604@hermes>
	<4E0B55BE.7040906@basementcode.com> <20110629212741.GG5604@hermes>
Message-ID: <9010b514b542a9cbf4352593059f25cd@basementcode.com>
To: kernelnewbies@lists.kernelnewbies.org
List-Id: kernelnewbies.lists.kernelnewbies.org

On Wed, 29 Jun 2011 23:27:41 +0200, Apelete Seketeli wrote:
> On 29-Jun-11, Christopher Harvey wrote:
>> On 06/29/11 16:14, Apelete Seketeli wrote:
>>  > I still can't
>> > figure where the boot process is getting stuck with step-by-step
>> > execution, but it seems that the last function called is 
>> "delay_loop"
>> > from arch/x86/lib/delay.c.
>> Have you run the backtrace (bt) command from the gdb shell? That 
>> should
>> tell you what function is calling the __delay.
>
> I didn't, will try that and see if it helps.

That command is your bread and butter. If you type "up" into gdb it 
will take you to the line that called __delay. Keep typing up to see 
exactly what series of functions were called to get to the __delay.