On Mon, Jun 04, 2012 at 12:00:10PM +0100, Rob Allen wrote: > Ram Pai, > > I've found the change that introduced the failure I'm seeing, and it > seems you are the author. Please can you offer some help? > > commit 0a2daa1cf35004f5adbf4138555cc5669abf3a3e > Author: Ram Pai <linuxram@xxxxxxxxxx> > Date: Mon Jul 25 13:08:41 2011 -0700 > > PCI: make cardbus-bridge resources optional > > Allocate resources to cardbus bridge only after all other genuine > resources requests are satisfied. Dont retry if resource allocation > for cardbus-bridges fail. > > Signed-off-by: Ram Pai <linuxram@xxxxxxxxxx> > Signed-off-by: Jesse Barnes <jbarnes@xxxxxxxxxxxxxxxx> Yes looking into it. The resource assignment for one of the BARs of the firewire ohci device at 0a:09.4 has got reassigned a valid address AFAICT. I think that device does not like the OS to reassign any resources. We need to determine whether the ohci device behaves abnormally if it gets assigned a address other than what is assigned by the BIOS. To do that; as Yinghai suggested, lets see the contents of the register with and without the patch. output of the following command on a working kernel and a non-working kernel will shed some light. lspci -vvxxx -s 0a:09.4 also boot messages on a working kernel will also be helpful. RP -- 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
