On Sun, May 13, 2012 at 11:32 PM, Clemens Ladisch <clemens@xxxxxxxxxx> wrote: > Stefan Richter wrote: >> On May 13 bugzilla-daemon@xxxxxxxxxxxxxxxxxxx wrote: >>> https://bugzilla.kernel.org/show_bug.cgi?id=43244 >>> >>> firewire_ohci: Failed to set Link Power Status >>> >>> Afterwards, the machine is completely dead (ignoring Magic SysRq), requiring >>> holding the power button to get anywhere. >>> >>> Blacklisting firewire_ohci allows the kernel to boot okay. >>> >>> Having experimented with Ubuntu's mainline kernel builds, it seem to have been >>> introduced between 3.1.0-rc2 (working) and 3.1.0-rc3. >> >> 0a:09.0 CardBus bridge: O2 Micro, Inc. OZ711MP1/MS1 MemoryCardBus Controller (rev 21) >> 0a:09.1 CardBus bridge: O2 Micro, Inc. OZ711MP1/MS1 MemoryCardBus Controller (rev 21) >> 0a:09.4 FireWire (IEEE 1394): O2 Micro, Inc. Firewire (IEEE 1394) (rev 02) (prog-if 10 [OHCI]) >> >> $ git shortlog v3.1-rc2..v3.1-rc3 drivers/firewire/ >> >> Stefan Richter (3): >> firewire: cdev: fix 32 bit userland on 64 bit kernel compat corner cases >> firewire: ohci: fix DMA unmapping in an error path >> firewire: core: handle ack_busy when fetching the Config ROM >> >> None of that code is in the path that is taken up to and after "failed to >> set Link Power Status". Hence the bug was most certainly not introduced >> by these but >> - either outside v3.1-rc2..v3.1-rc3, and the bisection went wrong >> due to a false negative, >> - or inside v3.1-rc2..v3.1-rc3 but due to some changes to the kernel >> or to the kernel configuration that are not directly related to >> firewire. > > These integrated chips tend to have incestuous relationships between their > PCI functions; it's possible that some CardBus change broke things. > > And indeed: > > $ git shortlog v3.1-rc2..v3.1-rc3 drivers/pci/ > ... > Ram Pai (3): > PCI : ability to relocate assigned pci-resources > PCI: make cardbus-bridge resources optional > PCI: code and comments cleanup > > Yinghai Lu (2): > PCI: honor child buses add_size in hot plug configuration > PCI: make SRIOV resources optional > > > I'm not sure how resource-related changes can result in something that looks > like a power management issue, but maybe the chip doesn't allow register > accesses after its resources are moved, or something like that. Any ideas? > can you post full log with pci debug enabled with lastest upsteam kernel? Thanks Yinghai -- 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
