netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Heiner Kallweit <hkallweit1@gmail.com>
Cc: nic_swsd@realtek.com, netdev@vger.kernel.org
Subject: Fw: [Bug 217069] New: Wake on Lan is broken on r8169
Date: Wed, 22 Feb 2023 07:02:04 -0800	[thread overview]
Message-ID: <20230222070204.2548cd99@hermes.local> (raw)



Begin forwarded message:

Date: Wed, 22 Feb 2023 00:51:52 +0000
From: bugzilla-daemon@kernel.org
To: stephen@networkplumber.org
Subject: [Bug 217069] New: Wake on Lan is broken on r8169


https://bugzilla.kernel.org/show_bug.cgi?id=217069

            Bug ID: 217069
           Summary: Wake on Lan is broken on r8169
           Product: Networking
           Version: 2.5
    Kernel Version: 6.2
          Hardware: Intel
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Other
          Assignee: stephen@networkplumber.org
          Reporter: iivanich@gmail.com
        Regression: No

After upgrade to 6.2 having issues with wake on lan on 2 systems:
- first is an old lenovo laptop from 2012(Ivy Bridge) with realtek network
adapter
- second is a PC(Haswell refresh) with PCIE realtek network adapter

Both uses r8169 driver for network.

On laptop it's not possible to wake on lan after poweroff
On PC it's not possible to wake on lan up after hibernate but works after
poweroff

In both cases downgrade to 6.1.x kernel fixes the issue.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.

                 reply	other threads:[~2023-02-22 15:02 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20230222070204.2548cd99@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=hkallweit1@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=nic_swsd@realtek.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).