[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1385930359.6988.7.camel@LTIRV-MCHAN1.corp.ad.broadcom.com>
Date: Sun, 1 Dec 2013 12:39:19 -0800
From: "Michael Chan" <mchan@...adcom.com>
To: "Rafael J. Wysocki" <rjw@...ysocki.net>
cc: netdev@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
"Linux PM list" <linux-pm@...r.kernel.org>,
"Linux PCI" <linux-pci@...r.kernel.org>,
"Bjorn Helgaas" <bhelgaas@...gle.com>,
"Nithin Nayak Sujir" <nsujir@...adcom.com>,
"David Miller" <davem@...emloft.net>
Subject: Re: [PATCH] PCI / tg3: Give up chip reset and carrier loss
handling if PCI device is not present
On Sun, 2013-12-01 at 02:34 +0100, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki <rafael.j.wysocki@...el.com>
>
> Modify tg3_chip_reset() and tg3_close() to check if the PCI network
> adapter device is accessible at all in order to skip poking it or
> trying to handle a carrier loss in vain when that's not the case.
> Introduce a special PCI helper function pci_device_is_present()
> for this purpose.
>
> Of course, this uncovers the lack of the appropriate RTNL locking
> in tg3_suspend() and tg3_resume(), so add that locking in there
> too.
>
> These changes prevent tg3 from burning a CPU at 100% load level for
> solid several seconds after the Thunderbolt link is disconnected from
> a Matrox DS1 docking station.
I'm not familiar with the DS1. Does the tg3 device get removed through
tg3_remove_one() in this case? What happens when you reconnect the DS1?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists