From: Siva Reddy Kallam <siva.kallam@broadcom.com>
To: Billy Shuman <wshuman3@gmail.com>
Cc: Michael Chan <michael.chan@broadcom.com>,
Netdev <netdev@vger.kernel.org>
Subject: Re: 4.9.0-rc8: tg3 dead after resume
Date: Mon, 12 Dec 2016 15:53:06 +0530 [thread overview]
Message-ID: <CAMet4B57_jXNVw35yZmU_asG_vc8jOmCCEXq0xn=0ot39RY52A@mail.gmail.com> (raw)
On Fri, Dec 9, 2016 at 7:59 PM, Billy Shuman <wshuman3@gmail.com> wrote:
> On Thu, Dec 8, 2016 at 4:03 AM, Siva Reddy Kallam
> <siva.kallam@broadcom.com> wrote:
>> On Thu, Dec 8, 2016 at 12:14 AM, Billy Shuman <wshuman3@gmail.com> wrote:
>>> 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.
>>>
>> We need more information to proceed further.
>> Without suspend, Are you able to use the tg3 port?
>
> Yes the port works fine without suspend.
OK
>
>> Which Broadcom card are you having in laptop?
>
> The nic is a NetXtreme BCM57762 Gigabit Ethernet PCIe in a thunderbolt3 dock.
>
OK
>> Please provide complete tg3 specific logs in dmesg.
>>
>
> [ 32.084010] tg3.c:v3.137 (May 11, 2014)
> [ 32.124695] tg3 0000:44:00.0 eth0: Tigon3 [partno(BCM957762) rev
> 57766001] (PCI Express) MAC address 98:e7:f4:8b:13:19
> [ 32.124698] tg3 0000:44:00.0 eth0: attached PHY is 57765
> (10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[1])
> [ 32.124699] tg3 0000:44:00.0 eth0: RXcsums[1] LinkChgREG[0]
> MIirq[0] ASF[0] TSOcap[1]
> [ 32.124700] tg3 0000:44:00.0 eth0: dma_rwctrl[00000001] dma_mask[64-bit]
> [ 32.219764] tg3 0000:44:00.0 enp68s0: renamed from eth0
> [ 36.219245] tg3 0000:44:00.0 enp68s0: Link is up at 1000 Mbps, full duplex
> [ 36.219250] tg3 0000:44:00.0 enp68s0: Flow control is on for TX and on for RX
> [ 36.219251] tg3 0000:44:00.0 enp68s0: EEE is disabled
>
> after resume
> [ 92.292838] tg3 0000:44:00.0 enp68s0: No firmware running
> [ 93.521744] tg3 0000:44:00.0: tg3_abort_hw timed out,
> TX_MODE_ENABLE will not clear MAC_TX_MODE=ffffffff
> [ 106.704655] tg3 0000:44:00.0 enp68s0: Link is down
> [ 108.370356] tg3 0000:44:00.0: tg3_abort_hw timed out,
> TX_MODE_ENABLE will not clear MAC_TX_MODE=ffffffff
>
> after rmmod, modprobe
> [ 570.933636] tg3 0000:44:00.0: tg3_abort_hw timed out,
> TX_MODE_ENABLE will not clear MAC_TX_MODE=ffffffff
> [ 604.847215] tg3.c:v3.137 (May 11, 2014)
> [ 605.010075] tg3 0000:44:00.0: phy probe failed, err -19
> [ 605.010077] tg3 0000:44:00.0: Problem fetching invariants of chip, aborting
>
>
>
>
We will try to reproduce and update you on this.
>>>> 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 reply other threads:[~2016-12-12 10:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-12 10:23 Siva Reddy Kallam [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-01-24 9:55 4.9.0-rc8: tg3 dead after resume 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
2016-12-08 9:03 Siva Reddy Kallam
2016-12-09 14:29 ` Billy Shuman
2016-12-07 15:20 Billy Shuman
2016-12-07 17:37 ` Michael Chan
2016-12-07 18:39 ` Billy Shuman
2016-12-07 18:44 ` Billy Shuman
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='CAMet4B57_jXNVw35yZmU_asG_vc8jOmCCEXq0xn=0ot39RY52A@mail.gmail.com' \
--to=siva.kallam@broadcom.com \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=wshuman3@gmail.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).