Message-ID: <488877C8.9020706@jp.fujitsu.com>
Date: Thu, 24 Jul 2008 21:38:32 +0900
From: Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>
User-Agent: Thunderbird 2.0.0.16 (Windows/20080708)
MIME-Version: 1.0
To: Pierre Ossman <drzeus-list@drzeus.cx>
CC: LKML <linux-kernel@vger.kernel.org>, linux-pci@vger.kernel.org
Subject: Re: post 2.6.26 requires pciehp_slot_with_bus
References: <20080724134737.4b91f30d@mjolnir.drzeus.cx>
In-Reply-To: <20080724134737.4b91f30d@mjolnir.drzeus.cx>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 987
Lines: 27

Hi Pierre,
(Added linux-pci to CC)

Pierre Ossman wrote:
> Somewhere post 2.6.26, pciehp started whining about not being able to
> claim the slot and error code -17. It suggested adding
> "pciehp_slot_with_bus", which actually helped. Still, having a kernel
> parameter should just be a temporary fix.

The "pciehp_slot_with_bus" option is a workaround for the platforms
that assign the same physical slot number to multiple slots. If your
system has PCI chassis and it supports Chassis Number registers,
maybe one of the solution is using chassis number + slot number as a
slot name. But I don't have any idea other than "pciehp_slot_with_bus"
if your system doesn't support chassis number.

Do you have any idea?

Thanks,
Kenji Kaneshige


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/