From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Christian Kujau <lists@nerdbynature.de>, linville@tuxdriver.com
Cc: zajec5@gmail.com, linux ppc dev <linuxppc-dev@lists.ozlabs.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: 3.0-rc1: powerpc hangs at Kernel virtual memory layout
Date: Thu, 02 Jun 2011 12:57:47 +1000 [thread overview]
Message-ID: <1306983467.29297.51.camel@pasglop> (raw)
In-Reply-To: <alpine.DEB.2.01.1106011712270.21697@trent.utfs.org>
On Wed, 2011-06-01 at 17:16 -0700, Christian Kujau wrote:
> On Tue, 31 May 2011 at 16:50, Christian Kujau wrote:
> > trying to boot 3.0-rc1 on powerpc32 only progresses until:
> >
> > > Kernel virtual memory layout:
> > > * 0xfffcf000..0xfffff000 : fixmap
>
> After hours (and hours!) of git-bisecting, it said:
>
> -----------------------
> ccc7c28af205888798b51b6cbc0b557ac1170a49 is the first bad commit
> commit ccc7c28af205888798b51b6cbc0b557ac1170a49
> Author: Rafał Miłecki <zajec5@gmail.com>
> Date: Fri Apr 1 13:26:52 2011 +0200
>
> ssb: pci: implement serdes workaround
>
> Signed-off-by: Rafał Miłecki <zajec5@gmail.com>
> Signed-off-by: John W. Linville <linville@tuxdriver.com>
> -----------------------
Ok, thanks a lot, It looks rather trivial actually: That new workaround
is PCIe specific but is called unconditionally, and will do bad things
non-PCIe implementations.
John, care to send the patch below to Linus ASAP ? I could reproduce and
verify it fixes it. Thanks !
ssb: pci: Don't call PCIe specific workarounds on PCI cores
Otherwise it can/will crash....
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
---
diff --git a/drivers/ssb/driver_pcicore.c b/drivers/ssb/driver_pcicore.c
index 82feb34..eddf1b9 100644
--- a/drivers/ssb/driver_pcicore.c
+++ b/drivers/ssb/driver_pcicore.c
@@ -540,7 +540,8 @@ void ssb_pcicore_init(struct ssb_pcicore *pc)
ssb_pcicore_init_clientmode(pc);
/* Additional always once-executed workarounds */
- ssb_pcicore_serdes_workaround(pc);
+ if (dev->id.coreid == SSB_DEV_PCIE)
+ ssb_pcicore_serdes_workaround(pc);
/* TODO: ASPM */
/* TODO: Clock Request Update */
}
next prev parent reply other threads:[~2011-06-02 2:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-31 23:50 3.0-rc1: powerpc hangs at Kernel virtual memory layout Christian Kujau
2011-06-01 0:25 ` Benjamin Herrenschmidt
2011-06-01 0:48 ` Christian Kujau
2011-06-01 1:08 ` Christian Kujau
2011-06-01 3:02 ` Christian Kujau
2011-06-01 3:49 ` Benjamin Herrenschmidt
2011-06-02 0:16 ` Christian Kujau
2011-06-02 0:47 ` Benjamin Herrenschmidt
2011-06-02 2:57 ` Benjamin Herrenschmidt [this message]
2011-06-02 3:06 ` Christian Kujau
2011-06-02 4:27 ` Christian Kujau
2011-06-02 7:33 ` Benjamin Herrenschmidt
2011-06-06 2:11 ` Christian Kujau
2011-06-06 3:46 ` Benjamin Herrenschmidt
2011-06-10 22:54 ` Christian Kujau
2011-06-10 22:59 ` Rafał Miłecki
2011-06-02 6:00 ` Rafał Miłecki
2011-06-02 6:07 ` Rafał Miłecki
2011-06-02 6:16 ` Christian Kujau
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=1306983467.29297.51.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=linville@tuxdriver.com \
--cc=lists@nerdbynature.de \
--cc=zajec5@gmail.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 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).