From mboxrd@z Thu Jan 1 00:00:00 1970 From: Billy Shuman Subject: Re: 4.9.0-rc8: tg3 dead after resume Date: Wed, 7 Dec 2016 13:44:51 -0500 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Cc: Netdev , Siva Reddy Kallam To: Michael Chan Return-path: Received: from mail-io0-f170.google.com ([209.85.223.170]:35158 "EHLO mail-io0-f170.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752435AbcLGSvj (ORCPT ); Wed, 7 Dec 2016 13:51:39 -0500 Received: by mail-io0-f170.google.com with SMTP id a124so727611254ioe.2 for ; Wed, 07 Dec 2016 10:51:38 -0800 (PST) In-Reply-To: Sender: netdev-owner@vger.kernel.org List-ID: On Wed, Dec 7, 2016 at 12:37 PM, Michael Chan wrote: > On Wed, Dec 7, 2016 at 7:20 AM, Billy Shuman wrote: >> After resume on 4.9.0-rc8 tg3 is dead. >> >> In logs I see: >> kernel: tg3 0000:44:00.0: phy probe failed, err -19 >> kernel: tg3 0000:44:00.0: Problem fetching invariants of chip, aborting > > -19 is -ENODEV which means tg3 cannot read the PHY ID. > > If it's a true suspend/resume operation, the driver does not have to > go through probe during resume. Please explain how you do > suspend/resume. > Sorry my previous message was accidentally sent to early. I used systemd (systemctl suspend) to suspend. > Did this work before? There has been very few changes to tg3 recently. > This is a new laptop for me, but the same behavior is seen on 4.4.36 and 4.8.12. >> >> rmmod and modprobe does not fix the problem only a reboot resolves the issue. >> >> Billy