From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Yuri Tikhonov <yur@emcraft.com>
Cc: Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>,
Linux/PPC Development <linuxppc-dev@ozlabs.org>,
Roland Dreier <rdreier@cisco.com>,
Sean MacLennan <smaclennan@pikatech.com>
Subject: Re: Re[2]: mal_probe crash
Date: Tue, 13 Jan 2009 13:52:21 +1100 [thread overview]
Message-ID: <1231815141.22571.35.camel@pasglop> (raw)
In-Reply-To: <1515542773.20090113015150@emcraft.com>
On Tue, 2009-01-13 at 01:51 +0300, Yuri Tikhonov wrote:
> On Tuesday, January 13, 2009 you wrote:
>
> > On Mon, 2009-01-12 at 14:37 +0100, Geert Uytterhoeven wrote:
> >> On Fri, 9 Jan 2009, Roland Dreier wrote:
> >> > > Can you double check that the e1000 isn't copying the PCI resources into
> >> > > a unsigned long before ioremap'ing the result, thus cropping the top
> >> > > bits ?
> >> >
> >> > as far as I can see, e1000 is using pci_ioremap_bar(), which should do
> >> > the right thing as long as resource_size_t is the right type (which it
> >> > looks like it is on PowerPC 44x).
> >>
> >> Indeed, the full 36-bit address is passed to __ioremap() via pci_ioremap_bar(),
> >> as evidenced from the additional debug output below (see [1]).
> >>
> >> As I don't have any other 3.3V PCI Ethernet cards, I plugged in a 3.3V PCI USB
> >> 2.0 card in the second PCI slot, and got a similar crash (see [2]).
> >>
> >> Are the PCI slots on the Sequoia known broken under recent Linux kernels? I've
> >> never used them before...
>
> > Hrm, something is indeed wrong, hard to say what tho. My canyonlands
> > works fine (460EPx) and I can try a Taishan one of these days (440GX
> > iirc). What is in sequoia ? I think it's a GX no ?
>
> Sequoia is equipped with 440EPx.
>
> I observe the 'mal_probe' crash on the Katmai board too (based on
> 440SPe):
Yes, EMAC is currently busted. We'll fix it asap.
Cheers,
Ben.
next prev parent reply other threads:[~2009-01-13 2:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-07 20:44 mal_probe crash Sean MacLennan
2009-01-08 20:46 ` Josh Boyer
2009-01-07 22:50 ` Benjamin Herrenschmidt
2009-01-09 14:42 ` Geert Uytterhoeven
2009-01-09 22:34 ` Herbert Xu
2009-01-09 23:13 ` Benjamin Herrenschmidt
2009-01-09 14:49 ` Matthias Fuchs
2009-01-09 15:02 ` Matthias Fuchs
2009-01-09 15:24 ` Geert Uytterhoeven
2009-01-09 21:30 ` Benjamin Herrenschmidt
2009-01-09 22:01 ` Roland Dreier
2009-01-12 13:37 ` Geert Uytterhoeven
2009-01-12 21:36 ` Benjamin Herrenschmidt
2009-01-12 22:48 ` Josh Boyer
2009-01-12 22:51 ` Re[2]: " Yuri Tikhonov
2009-01-13 2:52 ` Benjamin Herrenschmidt [this message]
2009-01-13 16:19 ` Geert Uytterhoeven
2009-01-09 21:09 ` Benjamin Herrenschmidt
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=1231815141.22571.35.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=Geert.Uytterhoeven@sonycom.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=rdreier@cisco.com \
--cc=smaclennan@pikatech.com \
--cc=yur@emcraft.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.