Bjorn Helgaas wrote: > On Tue, Nov 26, 2013 at 02:06:03AM +0100, Martin Mokrejs wrote: Bjorn, thanks for all you clarifications, they are helpful. > >> [ 174.623769] pciehp 0000:00:1c.7:pcie04: pcie_isr: intr_loc 108 >> [ 174.623781] pciehp 0000:00:1c.7:pcie04: Presence/Notify input change >> [ 174.623784] pciehp 0000:00:1c.7:pcie04: Card present on Slot(7) >> [ 174.623798] pciehp 0000:00:1c.7:pcie04: Data Link Layer State change >> [ 174.623801] pciehp 0000:00:1c.7:pcie04: pciehp_check_link_active: lnk_status = 7011 >> [ 174.623802] pciehp 0000:00:1c.7:pcie04: slot(7): Link Up event >> [ 174.624040] pciehp 0000:00:1c.7:pcie04: Surprise Removal >> [ 174.624075] pciehp 0000:00:1c.7:pcie04: Link Up event ignored on slot(7): already powering on >> [ 174.625660] pciehp 0000:00:1c.7:pcie04: Enabling domain:bus:device=0000:11:00 >> [ 174.625690] pciehp 0000:00:1c.7:pcie04: pciehp_check_link_active: lnk_status = 7011 >> [ 174.726003] pciehp 0000:00:1c.7:pcie04: pciehp_check_link_status: lnk_status = 7011 > > These messages are more verbose and possibly more alarming than necessary. > We should clean this up somehow. Some of it is probably debug stuff that > is no longer relevant. But I guess you're booting with "pciehp_debug=1", > so maybe the normal messages aren't so verbose. Yes, I have debug enabled (kernel config line should be in dmesg somewhere), I am glad debug output says more, it helps when there is a problem popping up in future. ;-) Martin -- 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
