linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
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:36:40 +0200	[thread overview]
Message-ID: <200910290936.40397.dk-arm-linux@gmx.de> (raw)

Hi all,

I've got a strange problem with latest git kernel. If I connect a PCIe->PCI bridge (without any connected PCI device!)
to my openrd-base board the kernel freezes during bootup if PCI is enabled:
Filename 'uImage_openrd'.
Load address: 0x800000
Loading: #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         ############
done
Bytes transferred = 2390120 (247868 hex)
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-2.6.32-rc5-00081-g964fe08-
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2390056 Bytes =  2.3 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

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.

If I insert eg a PCIe Network card everything works fine.
With former marvell 2.6.22 stock kernel / u-boot kernel boots up and I can access PCI card connected after my bridge.

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 :(



Many thanks,
Dieter

             reply	other threads:[~2009-10-29  8:36 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-29  8:36 Dieter Kiermaier [this message]
2009-10-29  8:35 ` marvell kirkwood / openrd-base kernel freeze on bootup with PICe->PCI bridge Simon Kagstrom
2009-10-29  8:50   ` Dieter Kiermaier
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=200910290936.40397.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).