From: Billy Shuman <wshuman3@gmail.com>
To: Michael Chan <michael.chan@broadcom.com>
Cc: Netdev <netdev@vger.kernel.org>,
Siva Reddy Kallam <siva.kallam@broadcom.com>
Subject: Re: 4.9.0-rc8: tg3 dead after resume
Date: Wed, 7 Dec 2016 13:44:51 -0500 [thread overview]
Message-ID: <CAHQNsocKsMrfuiiknYve5UViBwm-i29J0274CTMSsWJOunWSxA@mail.gmail.com> (raw)
In-Reply-To: <CACKFLinTBokAXnOri9_sxuFby0y4VxxrhEOh1aayPsyPWwDahw@mail.gmail.com>
On Wed, Dec 7, 2016 at 12:37 PM, Michael Chan <michael.chan@broadcom.com> wrote:
> On Wed, Dec 7, 2016 at 7:20 AM, Billy Shuman <wshuman3@gmail.com> 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
next prev parent reply other threads:[~2016-12-07 18:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-07 15:20 4.9.0-rc8: tg3 dead after resume Billy Shuman
2016-12-07 17:37 ` Michael Chan
2016-12-07 18:39 ` Billy Shuman
2016-12-07 18:44 ` Billy Shuman [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-12-08 9:03 Siva Reddy Kallam
2016-12-09 14:29 ` Billy Shuman
2016-12-12 10:23 Siva Reddy Kallam
2016-12-26 6:27 Siva Reddy Kallam
[not found] ` <CAHQNsocHhcb5RyXk5ywMhUAo=Ef4-_1y=9w_tmKEK1bsTf4kgA@mail.gmail.com>
[not found] ` <9ac07689abefd319a2baae2860fd8247@mail.gmail.com>
2017-01-16 14:59 ` Billy Shuman
2017-01-24 9:55 Siva Reddy Kallam
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAHQNsocKsMrfuiiknYve5UViBwm-i29J0274CTMSsWJOunWSxA@mail.gmail.com \
--to=wshuman3@gmail.com \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=siva.kallam@broadcom.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).