From: Marco Schramel <Schramel.Linux@go.bartec.de>
To: Wolfgang Denk <wd@denx.de>
Cc: "PPC_LINUX" <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: BDI kernel debug
Date: Wed, 7 Jul 2004 07:01:16 +0200 [thread overview]
Message-ID: <200407070701.16632.Schramel.Linux@go.bartec.de> (raw)
In-Reply-To: <20040706181831.52416C109F@atlas.denx.de>
Hello,
>
> > Are there some options in the kernel or in the gdb to set ?
>
> Did you enable CONFIG_DEBUG_KERNEL in your kernel configuration?
Yes it is enabled, furthermore the "Include BDI-2000 user context switcher" is set and compiler options "Additional compile arguments: "-g -ggdb -fno-schedule-insns -fno-schedule-insns2" are set
> Did you read the FAQ section of the DULG, especially
> http://www.denx.de/twiki/bin/view/DULG/HowToDebugLinuxExceptions
> and
> http://www.denx.de/twiki/bin/view/DULG/HowToSingleStepThroughRFIInstruction
In my case i try to step through m8260_setup_arch() function to debug m8260_find_bridges() for pci support. Is there the MMU already on ?
I think it is.
When the bdi runs through the code the most time it comes to the __delay() function. Then i try "step" or "next" and it often hangs forever.
> Best regards,
>
> Wolfgang Denk
Thank you for your reply.
Best regards,
Marco
---------
Marco Schramel
R&D
Bartec GmbH
Schulstr. 30
94239 Gotteszell, Germany
www.bartec.de
Marco.Schramel@go.bartec.de
Phone: +49 (0)9929/301332
Fax: +49 (0)9929/301112
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-07-07 5:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-06 11:31 BDI kernel debug Marco Schramel
2004-07-06 18:18 ` Wolfgang Denk
2004-07-07 5:01 ` Marco Schramel [this message]
2004-07-07 11:42 ` Fahd Abidi
2004-07-07 11:52 ` Marco Schramel
[not found] <81C69D96BDD30640952C7A404004AA250C2CA8@h0007e95d9fa7.ne.client2.attbi.com>
2004-07-07 13:07 ` Fahd Abidi
2004-07-08 14:03 ` Marco Schramel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200407070701.16632.Schramel.Linux@go.bartec.de \
--to=schramel.linux@go.bartec.de \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=wd@denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.