[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130617182811.GA12442@d2.synalogic.ca>
Date: Mon, 17 Jun 2013 14:28:11 -0400
From: Benjamin Poirier <benjamin.poirier@...il.com>
To: Nithin Nayak Sujir <nsujir@...adcom.com>
Cc: davem@...emloft.net, netdev@...r.kernel.org,
Michael Chan <mchan@...adcom.com>
Subject: Re: [PATCH net-next] tg3: Prevent system hang during repeated EEH
errors.
On 2013/06/14 14:15, Nithin Nayak Sujir wrote:
[...]
> @@ -17796,6 +17799,10 @@ static pci_ers_result_t tg3_io_slot_reset(struct pci_dev *pdev)
> rc = PCI_ERS_RESULT_RECOVERED;
>
> done:
> + if (rc != PCI_ERS_RESULT_RECOVERED && netif_running(netdev)) {
> + tg3_napi_enable(tp);
> + dev_close(netdev);
> + }
> rtnl_unlock();
>
> return rc;
> @@ -17826,6 +17833,8 @@ static void tg3_io_resume(struct pci_dev *pdev)
> if (err) {
> tg3_full_unlock(tp);
> netdev_err(netdev, "Cannot restart hardware after reset.\n");
> + tg3_napi_enable(tp);
> + dev_close(netdev);
> goto done;
> }
Are these two hunks needed?
1) These functions do not call tg3_netif_stop() or tg3_napi_disable()
2) an error in tg3_io_resume() does not trigger device removal in
handle_eeh_events(). In fact the ->resume callback has no return value.
>
> --
> 1.8.1.4
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists