lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date:   Thu, 8 Dec 2016 14:33:49 +0530
From:   Siva Reddy Kallam <>
To:     Billy Shuman <>
Cc:     Michael Chan <>,
        Netdev <>
Subject: Re: 4.9.0-rc8: tg3 dead after resume

On Thu, Dec 8, 2016 at 12:14 AM, Billy Shuman <> wrote:
> 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.
We need more information to proceed further.
Without suspend, Are you able to use the tg3 port?
Which Broadcom card are you having in laptop?
Please provide complete tg3 specific logs in dmesg.

>> 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