Hi,
Further to my previous message, I've bisected the issue and landed up
pointing at this patch:
99935a7a59eaca0292c1a5880e10bae03f4a5e3d is first bad commit
commit 99935a7a59eaca0292c1a5880e10bae03f4a5e3d
Author: Yinghai Lu <yinghai@xxxxxxxxxx>
Date: Sun Oct 4 21:54:24 2009 -0700
x86/PCI: read root resources from IOH on Intel
For intel systems with multi IOH, we should read peer root resources
directly from PCI config space, and don't trust _CRS.
Signed-off-by: Yinghai Lu <yinghai.lu@xxxxxxx>
Signed-off-by: Jesse Barnes <jbarnes@xxxxxxxxxxxxxxxx>
I did try to revert this one patch from the current 2.6.33-rc2+ git
tree, but it wasn't straightforward. Hopefully this might be enough to
track down the issue. Let me know if you'd like any more info about my
system,
Steve.
-------- Forwarded Message --------
From: Steven Whitehouse <swhiteho@xxxxxxxxxx>
To: linux-pci@xxxxxxxxxxxxxxx
Subject: Problem booting Dell R710 with 2.6.33-rc1
Date: Wed, 23 Dec 2009 11:00:04 +0000
Hi,
I sent this yesterday but it looks like the list has eaten it. I assume
thats due to the atached .jpg, so here it it again without the .jpg and
if you'd like to see that, please send me a private email and I'll
forward it directly to you,
Steve.
-------- Forwarded Message --------
From: Steven Whitehouse <swhiteho@xxxxxxxxxx>
To: linux-pci@xxxxxxxxxxxxxxx
Subject: Problem booting Dell R710 with 2.6.33-rc1
Date: Tue, 22 Dec 2009 14:08:09 +0000
Hi,
The attached .jpg shows all I've been able to capture from a crash that
I've run into on trying to boot my R710 with the latest kernel. I know
that 2.6.32 works ok (with the same kernel config) so I'm fairly sure
that the issue is related to something at the last merge window.
I'm afraid that the machine is not on a serial console so I can't easily
capture any more than what is shown in the .jpg, which is mostly
messages of the form: "no compatible bridge window for..."
I'm assuming that for some reason the various drivers cannot allocate
the PCI resources they require.
Any ideas what is going wrong? I can send a kernel .config if required,
but I don't think its likely to be a config issue. Also I can test any
patches if that would be helpful.
I did try turning on PCI debugging, but the messages were no more
verbose. I also tried both with and without PCIe hotplug support turned
on and that made no difference either. I did look on google, but I
couldn't track down any useful information about the particular messages
that I'm seeing,
Steve.
--
To unsubscribe from this list: send the line "unsubscribe linux-pci" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
