From: Rojhalat Ibrahim <imr@rtschenk.de>
To: Scott Wood <scottwood@freescale.com>,
Michael Guntsche <michael.guntsche@it-loops.com>
Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [BUG] PCI related panic on powerpc based board with 3.10-rcX
Date: Tue, 11 Jun 2013 09:24:28 +0200 [thread overview]
Message-ID: <10631172.HfDeIDHqX3@pcimr> (raw)
In-Reply-To: <1370904753.18413.19@snotra>
On Monday 10 June 2013 17:52:33 Scott Wood wrote:
> On 06/10/2013 12:07:43 PM, Michael Guntsche wrote:
> > Good evening,
> >
> > On Mon, Jun 10, 2013 at 1:41 PM, Rojhalat Ibrahim <imr@rtschenk.de>
> >
> > wrote:
> > > Hi Mike,
> > >
> > > could you please try this patch:
> > > https://lists.ozlabs.org/pipermail/linuxppc-dev/2013-May/106624.html
> > > http://patchwork.ozlabs.org/patch/244515/
> > >
> > > Rojhalat
> > >
> > > On Saturday 08 June 2013 21:39:37 Michael Guntsche wrote:
> > >> After bisecting I found the responsible commit.
> > >>
> > >> 50d8f87d2b3: powerpc/fsl-pci Make PCIe hotplug work with Freescale
> > >> PCIe controllers
> > >>
> > >> Reverting this commit allowed my board to boot again.
> > >>
> > >> @Rojhalat: Please have a look at
> > >> http://marc.info/?l=linux-kernel&m=137071294204858&w=2
> > >> for my initial bugreport.
> > >>
> > >> What I do not understand at all is why this is affecting my
> >
> > platform.
> >
> > >> AFAIK there is no PCIe hardware on it AND I completely disabled
> >
> > PCIe
> >
> > >> support in config.
> > >>
> > >> Kind regards,
> > >> Mike
> >
> > This patch does not fix the problem, during boot the kernel still
> > panics. I had a closer look at the commit and the following patch
> > fixes it for me....
> >
> > diff --git a/arch/powerpc/sysdev/fsl_pci.c
> > b/arch/powerpc/sysdev/fsl_pci.c
> > index 028ac1f..21b687f 100644
> > --- a/arch/powerpc/sysdev/fsl_pci.c
> > +++ b/arch/powerpc/sysdev/fsl_pci.c
> > @@ -814,7 +814,7 @@ int __init mpc83xx_add_bridge(struct device_node
> > *dev)
> >
> > if (ret)
> >
> > goto err0;
> >
> > } else {
> >
> > - fsl_setup_indirect_pci(hose, rsrc_cfg.start,
> > + setup_indirect_pci(hose, rsrc_cfg.start,
> >
> > rsrc_cfg.start + 4, 0);
> >
> > }
>
> The only difference here is that you're not setting hose->ops to
> fsl_indirect_pci_ops. Do you know why that is helping, and what
> hose->ops is set to instead?
>
> -Scott
The difference is only the read function in hose->ops, which is set to
indirect_read_config instead of fsl_indirect_read_config.
fsl_indirect_read_config calls fsl_pcie_check_link, which is where the Oops
occurs.
Mike, can you find out where exactly in fsl_pcie_check_link the bad access
happens? Enabling CONFIG_DEBUG_BUGVERBOSE might help.
Rojhalat
next prev parent reply other threads:[~2013-06-11 7:24 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-08 19:39 [BUG] PCI related panic on powerpc based board with 3.10-rcX Michael Guntsche
2013-06-08 19:39 ` Michael Guntsche
2013-06-10 11:41 ` Rojhalat Ibrahim
2013-06-10 11:41 ` Rojhalat Ibrahim
2013-06-10 17:07 ` Michael Guntsche
2013-06-10 17:07 ` Michael Guntsche
2013-06-10 22:52 ` Scott Wood
2013-06-10 22:52 ` Scott Wood
2013-06-11 7:24 ` Rojhalat Ibrahim [this message]
2013-06-11 17:00 ` Scott Wood
2013-06-11 17:00 ` Scott Wood
2013-06-11 17:09 ` Michael Guntsche
2013-06-11 17:09 ` Michael Guntsche
2013-06-11 17:28 ` Scott Wood
2013-06-11 17:28 ` Scott Wood
2013-06-12 8:19 ` Rojhalat Ibrahim
2013-06-12 8:19 ` Rojhalat Ibrahim
2013-06-12 21:50 ` Scott Wood
2013-06-12 21:50 ` Scott Wood
2013-06-13 7:21 ` Rojhalat Ibrahim
2013-06-13 7:21 ` Rojhalat Ibrahim
2013-06-13 16:49 ` Scott Wood
2013-06-13 16:49 ` Scott Wood
2013-06-14 7:55 ` Rojhalat Ibrahim
2013-06-14 7:55 ` Rojhalat Ibrahim
-- strict thread matches above, loose matches on Subject: below --
2013-06-08 17:35 Michael Guntsche
2013-06-08 17:30 Michael Guntsche
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=10631172.HfDeIDHqX3@pcimr \
--to=imr@rtschenk.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=michael.guntsche@it-loops.com \
--cc=scottwood@freescale.com \
/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.