From: Kumar Gala <galak@kernel.crashing.org>
To: avorontsov@ru.mvista.com
Cc: linuxppc-dev@ozlabs.org
Subject: Re: mpc8568e-mds: pci-e is broken
Date: Wed, 23 Jan 2008 13:42:56 -0600 [thread overview]
Message-ID: <6785FDE5-FEBA-4FE2-A94C-85FCE299D1CC@kernel.crashing.org> (raw)
In-Reply-To: <20080123193712.GA12037@localhost.localdomain>
On Jan 23, 2008, at 1:37 PM, Anton Vorontsov wrote:
> Hello Benjamin, Kumar,
>
> Using galak/powerpc.git's e4a0d8a1f7e6a9741ec46 head, MPC8568E-MDS
> is oopsing during PCI-E probe, like this:
>
> - - - -
> Found FSL PCI host bridge at 0x00000000e0008000. Firmware bus
> number: 0->255
> PCI host bridge /pci@e0008000 (primary) ranges:
> MEM 0x0000000080000000..0x000000009fffffff -> 0x0000000080000000
> IO 0x00000000e2000000..0x00000000e27fffff -> 0x0000000000000000
> Found FSL PCI host bridge at 0x00000000e000a000. Firmware bus
> number: 0->255
> PCI host bridge /pcie@e000a000 ranges:
> MEM 0x00000000a0000000..0x00000000afffffff -> 0x00000000a0000000
> IO 0x00000000e2800000..0x00000000e2ffffff -> 0x0000000000000000
>
> [...]
>
> PCI: Probing PCI hardware
> PCI: 0001:01:00.0: class b20 doesn't match header type 01. Ignoring
> class.
> PCI: Closing bogus Apple Firmware region 1 on bus 0x02
> PCI: Closing bogus Apple Firmware region 2 on bus 0x02
odd, you shouldn't see these anymore w/my git tree.
>
> Unable to handle kernel paging request for data at address 0x00000000
> Faulting instruction address: 0xc0142760
> Oops: Kernel access of bad area, sig: 11 [#1]
> MPC85xx MDS
> Modules linked in:
> NIP: c0142760 LR: c01427a8 CTR: 00000000
> REGS: df823dc0 TRAP: 0300 Not tainted (2.6.24-rc8-g146f2dc2-dirty)
> MSR: 00029000 <EE,ME> CR: 42044082 XER: 00000000
> DEAR: 00000000, ESR: 00000000
> TASK = df820000[1] 'swapper' THREAD: df822000
> GPR00: 00000000 df823e70 df820000 df800380 000000d0 00000200
> 00000004 c028aa6c
> GPR08: df81c200 00000007 00000000 df809a44 22044024 48fdafc9
> 1fff4e00 c02276ec
> GPR16: c0227760 df823f98 c0227748 c0284efc c0227774 c0227788
> c023e5b0 c02a9200
> GPR24: df8098d8 df823eac df809800 b6db6db7 00000000 00000008
> 00000000 df8098e0
> Call Trace:
> [df823e70] [c01427a8] (unreliable)
> [df823ea0] [c0143c9c]
> [df823f00] [c027a338]
> [df823f20] [c026e38c]
> [df823f30] [c026df08]
> [df823f60] [c02641ec]
> [df823ff0] [c000dc08]
> Instruction dump:
> 39290001 2f9d0006 7d4a4f5e 7f3ccb78 48000020 812b0004 800b0000
> 39290001
> 7c004850 7f805040 419c0044 7fdcf378 <83dc0000> 38000000 2f9e0000
> 41beffe8
> ---[ end trace 8640abe69a316dee ]---
> Kernel panic - not syncing: Attempted to kill init!
> Rebooting in 180 seconds..
> - - - -
>
>
> It seems like be8cbcd8896670a01ead7a29e33ff is at "fault".
>
> static void __devinit __pcibios_fixup_bus(struct pci_bus *bus)
> {
> ...
> if (i >= 3 && bus->self->transparent)
> continue;
> ...
> }
>
> That new check doesn't work, here bus->self->transparent == 0.
> Could it be that the message below is the root cause?
>
> PCI: 0001:01:00.0: class b20 doesn't match header type 01. Ignoring
> class.
this is expected but of how FSL hw reports itself.
> I.e. drivers/pci/probe.c just don't setting transparent flag.
> I wonder if we need use quirk_transparent_bridge() here or
> we can fix it other way?
>
> Just in case, I'm observing that message for a long long time, and
> it didn't tell upon any functionality till now.
Is this with the 8568 MDS in standalone or plugged into the back pane?
- k
next prev parent reply other threads:[~2008-01-23 19:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-23 19:37 mpc8568e-mds: pci-e is broken Anton Vorontsov
2008-01-23 19:42 ` Kumar Gala [this message]
2008-01-23 19:50 ` Anton Vorontsov
2008-01-23 22:04 ` Kumar Gala
2008-01-23 23:02 ` Kumar Gala
2008-01-24 14:00 ` Anton Vorontsov
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=6785FDE5-FEBA-4FE2-A94C-85FCE299D1CC@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=avorontsov@ru.mvista.com \
--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).