[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAHQNsocKsMrfuiiknYve5UViBwm-i29J0274CTMSsWJOunWSxA@mail.gmail.com>
Date: Wed, 7 Dec 2016 13:44:51 -0500
From: Billy Shuman <wshuman3@...il.com>
To: Michael Chan <michael.chan@...adcom.com>
Cc: Netdev <netdev@...r.kernel.org>,
Siva Reddy Kallam <siva.kallam@...adcom.com>
Subject: Re: 4.9.0-rc8: tg3 dead after resume
On Wed, Dec 7, 2016 at 12:37 PM, Michael Chan <michael.chan@...adcom.com> wrote:
> On Wed, Dec 7, 2016 at 7:20 AM, Billy Shuman <wshuman3@...il.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
Powered by blists - more mailing lists