From: Grant Likely <grant.likely@secretlab.ca>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>,
Ayman El-Khashab <ayman@elkhashab.com>
Subject: Re: problem PCIe LSI detected at 32 device addresses (ppc460ex)
Date: Sun, 3 Apr 2011 16:09:26 -0600 [thread overview]
Message-ID: <BANLkTikTeAgc2dg3-M7yM185pg7FAdbAGw@mail.gmail.com> (raw)
In-Reply-To: <1301867559.2549.32.camel@pasglop>
On Sun, Apr 3, 2011 at 3:52 PM, Benjamin Herrenschmidt
<benh@kernel.crashing.org> wrote:
>
>> Ok, I've narrowed the scope of the problem some. =A0I moved forward
>> to a more recent kernel (2.6.31 to 2.6.36) and that resolved the
>> problem of the controller showing up as every device on the bus.
>> However, from 2.6.37 to the current HEAD, I have not been able to
>> build a kernel to run on the 460EX. =A0I tried 2.6.37, 2.6.38, and
>> the HEAD and all result in the following kernel panic. =A0I am not
>> sure how to proceed here. =A0I suppose we can stick with 2.6.36 since
>> it works, but I'd like to understand what it might take to remedy
>> this.
>
> Smells like somebody changed something with the OF flash code... Josh,
> Grant, any idea what's up there ?
Not sure, more information would be helpful.
Ayman, if you do a 'git log v2.6.36.. drivers/mtd/maps/physmap_of.c',
then you'll see a list of commits touching the mtd driver. Would you
be able to do a 'git checkout <sha1-id>' on each of those are report
back on at what point things stop working? Actually, a full bisect
between 2.6.36 and 2.6.37 would be best, but this is a good start if
you're limited on time. Once you find the first commit where it
fails, do a 'git checkout <sha1>~1' to confirm that it is in fact the
commit that causes the breakage.
Can you also post your device tree please?
Thanks,
g.
next prev parent reply other threads:[~2011-04-03 22:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-01 16:26 problem PCIe LSI device detected at all 32 device addresses (ppc460ex) Ayman El-Khashab
2011-04-01 22:59 ` problem PCIe LSI detected at " Ayman El-Khashab
2011-04-03 21:52 ` Benjamin Herrenschmidt
2011-04-03 22:09 ` Grant Likely [this message]
2011-04-03 23:22 ` Ayman El-Khashab
2011-04-04 20:54 ` Grant Likely
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=BANLkTikTeAgc2dg3-M7yM185pg7FAdbAGw@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=ayman@elkhashab.com \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.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).