Prev: oprofile, perf, x86: introduce new functions to reserve perfctrs by index
Next: Question about e06e7c615877026544ad7f8b309d1a3706410383 -- [IPV4]: The scheduled removal of multipath cached routing support.
From: Bjorn Helgaas on 25 Mar 2010 13:00
> It looks like the iomem_resource tree got wrecked. Has anyone been
> changing anything in there lately?

My pci=use_crs patches change the contents of the iomem_resource tree,
and it's possible they broke some assumptions PCMCIA was making, so
you might see if "pci=nocrs" makes any difference. If it does, please
attach an acpidump and the entire dmesg logs with and without that option.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Bjorn Helgaas on 30 Mar 2010 20:40
Rafael, this is a regression from 2.6.33, in case it's not on your
list yet.

Ozgur, thanks for attaching the logs. There's some interesting stuff
there that I don't understand yet, such as this from the pci=nocrs dmesg:

[ 1.577758] pci 0000:00:1e.0: PCI bridge to [bus 03-04]
[ 1.583031] pci 0000:00:1e.0: bridge window [io 0x5000-0x5fff]
[ 1.551889] pci 0000:03:01.0: CardBus bridge to [bus 04-07]
[ 1.557507] pci 0000:03:01.0: bridge window [io 0x5000-0x50ff]
[ 1.603303] PCI: No. 2 try to assign unassigned res
[ 1.688208] pci 0000:03:01.0: CardBus bridge to [bus 04-07]
[ 1.693826] pci 0000:03:01.0: bridge window [io 0x0000-0x00ff]

Apparently we moved that CardBus I/O window from [0x5000-0x5fff] to
[0x0-0xff]. I'm dubious about that because the upstream bridge at
00:1e.0 only positively decodes [0x5000-0x5fff] (though it *is* in
subtractive decode mode, so it will forward more). I wish we had
a little more debug output about when & why we moved that window.

I'm especially dubious because your /proc/ioports with pci=nocrs
from comment 8 (which is the case that's supposed to be working)
contains this:

5000-5fff : PCI Bus 0000:03
0000-00ff : PCI CardBus 0000:04
0000-00ff : PCI CardBus 0000:04

That looks completely broken in terms of the hierarchy. It looks
like you have a USB device in the CardBus slot (ohci_hcd 0000:04:00.0).
Maybe the broken hierarchy doesn't cause problems with this device
because it doesn't use I/O ports.

Anyway, I'd like to see the entire dmesg log when booted *without*
pci=nocrs, because that's the case that fails. Since the system doesn't
boot, you'll have to use a serial console or netconsole to collect the
whole thing. The serial console log in comment 7 is corrupted; it looks
like all the lines got truncated to 80 columns or something. And please
boot with "ignore_loglevel" so we see all the debug messages on the console.
Also, no need to tar up and compress your attachments -- I always figure
if bugzilla wants to compress stuff, it can do it internally without
bothering us.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Bjorn Helgaas on 1 Apr 2010 13:40
Using ignore_loglevel shouldn't affect the problem, so I'm confused.
Can you reproduce the original problem and attach the entire serial
console log?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
 | 
Pages: 1
Prev: oprofile, perf, x86: introduce new functions to reserve perfctrs by index
Next: Question about e06e7c615877026544ad7f8b309d1a3706410383 -- [IPV4]: The scheduled removal of multipath cached routing support.