public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Felix Radensky <felix@embedded-sol.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] PCI-E problems on Kilauea board
Date: Tue, 17 Feb 2009 19:18:07 +0200	[thread overview]
Message-ID: <499AF14F.8060400@embedded-sol.com> (raw)
In-Reply-To: <200902171516.08780.sr@denx.de>

Stefan Roese wrote:
> Hi Felix,
>
> On Monday 16 February 2009, Felix Radensky wrote:
>   
>> I have several PCI-E related  problems on Kilauea board Rev 1.2
>>
>> 1. With u-boot v2009.01 and latest git I'm getting machine check
>>     exception when PCI-E card is plugged into slot 0. There's no
>>     problem if the same card is plugged into slot 1.
>>
>>     This seems to be a regression introduced after
>> 2008.10-rc2-02699-g725c8dd
>>     (version shipped on AMCC resource CD), as with this version both slots
>>     function properly.
>>
>>     Any hints what could be the problem with latest u-boots ?
>>     
>
> I just checked on my Kilauea and reproduced the problem. No, I don't have any 
> clue right now where this problem is generated. I can't remember any issues 
> with PCIe slot 1 on Kilauea.
>
> Perhaps you could try to find the git commit introducing this issue by 
> using "git bisect"?
>
> <snip>
>
>   
According to "git bisect" the problem was introduced by this commit:

30e76d5e3bc4c5208ee63585fe12b409d9308cd8 is first bad commit
commit 30e76d5e3bc4c5208ee63585fe12b409d9308cd8
Author: Kumar Gala <galak@kernel.crashing.org>
Date:   Tue Oct 21 08:36:08 2008 -0500

    pci: Allow for PCI addresses to be 64-bit

    PCI bus is inherently 64-bit.  While not all system require access to
    the full 64-bit PCI address range some do.  This allows those systems
    to enable the full PCI address width via CONFIG_SYS_PCI_64BIT.

Felix.

      parent reply	other threads:[~2009-02-17 17:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-16 16:44 [U-Boot] PCI-E problems on Kilauea board Felix Radensky
2009-02-17 14:16 ` Stefan Roese
2009-02-17 14:35   ` Felix Radensky
2009-02-17 14:44     ` Stefan Roese
2009-03-01 15:00       ` Felix Radensky
2009-03-02  8:37         ` Felix Radensky
2009-03-02  9:03           ` Stefan Roese
2009-03-02  9:32             ` Felix Radensky
2009-03-11 12:22               ` Stefan Roese
2009-03-11 13:40                 ` Felix Radensky
2009-03-11 14:05                   ` Stefan Roese
2009-03-11 14:42                     ` Felix Radensky
2009-02-17 17:18   ` Felix Radensky [this message]

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=499AF14F.8060400@embedded-sol.com \
    --to=felix@embedded-sol.com \
    --cc=u-boot@lists.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox