From: dk-arm-linux@gmx.de (Dieter Kiermaier)
To: linux-arm-kernel@lists.infradead.org
Subject: marvell kirkwood / openrd-base kernel freeze on bootup with PICe->PCI bridge
Date: Thu, 29 Oct 2009 10:50:34 +0200 [thread overview]
Message-ID: <200910290950.34825.dk-arm-linux@gmx.de> (raw)
In-Reply-To: <20091029093510.4e9a8dde@marrow.netinsight.se>
Am Donnerstag 29 Oktober 2009 09:35:10 schrieb Simon Kagstrom:
Hi Simon,
> On Thu, 29 Oct 2009 10:36:40 +0200
> Dieter Kiermaier <dk-arm-linux@gmx.de> wrote:
>
> > Uncompressing Linux............................................................................................................................................................ done.
> >
> > The PCIe->PCI bridge is a Marvell 88SB2211 evaluation board and I expect it works well - at least it does in all other environments I've tested so far.
>
> > Please can someone help me to track this down?
> > Some tips how to debug such a problem using openocd are very welcome, too!
> > I'm completely lost in space :(
>
> Try attaching gdb to it, i.e.,
>
> arm-unknown-linux-gnu-gdb vmlinux
>
> and then connecting to openocd's GDB remote with
>
> target remote localhost:3333
>
> After that you can backtrace and examine stuff as you normally do with
> GDB. Remeber to start with nohlt when you use GDB, but I guess you're
> already doing that.
Yes I do.
Ok, sometimes things are more easy than one could think off :)
I've done what you told me:
(gdb) target remote localhost:3333
Remote debugging using localhost:3333
warning: shared library handler failed to enable breakpoint
__delay () at arch/arm/lib/delay.S:44
44 subs r0, r0, #1
Current language: auto; currently asm
(gdb) bt
#0 __delay () at arch/arm/lib/delay.S:44
#1 0xc003b1f4 in panic (fmt=0xdf834000 "\002") at kernel/panic.c:138
#2 0xc003e0fc in do_exit (code=-545054720) at kernel/exit.c:902
#3 0xc002a054 in die (str=0xc042fb58 "", regs=0xdf835e10, err=40)
at arch/arm/kernel/traps.c:274
#4 0xc002a11c in arm_notify_die (str=0xc040dc94 "Attempted to kill init!",
regs=0xdf835bbc, info=0xdf835d78, err=3221397788, trap=0)
at arch/arm/kernel/traps.c:286
#5 0xc002634c in do_DataAbort (addr=4276361468, fsr=40, regs=0xdf835e10)
at arch/arm/mm/fault.c:524
#6 0xc037440c in __dabt_svc ()
Backtrace stopped: frame did not save the PC
(gdb)
Could someone see the cause of my freeze?
Dieter
>
> // Simon
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
>
next prev parent reply other threads:[~2009-10-29 8:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-29 8:36 marvell kirkwood / openrd-base kernel freeze on bootup with PICe->PCI bridge Dieter Kiermaier
2009-10-29 8:35 ` Simon Kagstrom
2009-10-29 8:50 ` Dieter Kiermaier [this message]
2009-10-29 8:52 ` Daniel Mack
2009-10-29 8:59 ` Simon Kagstrom
2009-10-29 9:14 ` Dieter Kiermaier
2009-10-29 9:36 ` Dieter Kiermaier
2009-10-29 10:33 ` Ronen Shitrit
2009-10-29 10:57 ` Dieter Kiermaier
2009-10-29 11:33 ` Ronen Shitrit
2009-10-29 15:11 ` Dieter Kiermaier
2009-10-29 15:16 ` Russell King - ARM Linux
2009-10-29 22:47 ` saeed bishara
2009-10-30 8:55 ` Dieter Kiermaier
2009-11-03 14:36 ` Dieter Kiermaier
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=200910290950.34825.dk-arm-linux@gmx.de \
--to=dk-arm-linux@gmx.de \
--cc=linux-arm-kernel@lists.infradead.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).