From: Petr Tesarik <ptesarik@suse.cz>
To: Heiner Kallweit <hkallweit1@gmail.com>
Cc: Realtek linux nic maintainers <nic_swsd@realtek.com>,
netdev@vger.kernel.org
Subject: Re: RTL8402 stops working after hibernate/resume
Date: Wed, 30 Sep 2020 23:44:07 +0200 [thread overview]
Message-ID: <20200930234407.0ce0b6d9@ezekiel.suse.cz> (raw)
In-Reply-To: <2e91f3b7-b675-e117-2200-e97b089e9996@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1179 bytes --]
On Wed, 30 Sep 2020 22:11:02 +0200
Heiner Kallweit <hkallweit1@gmail.com> wrote:
> On 30.09.2020 20:00, Petr Tesarik wrote:
>[...]
> > WoL still does not work on my laptop, but this might be an unrelated
> > issue, and I can even imagine the BIOS is buggy in this regard.
> >
> A simple further check you could do:
> After sending the WoL packet (that doesn't wake the system) you wake
> the system by e.g. a keystroke. Then check in /proc/interrupts for
> a PCIe PME interrupt. If there's a PME interrupt, then the network
> chip successfully detected the WoL packet, and it seems we have to
> blame the BIOS.
Well, the switch does not sense carrier on the corresponding port while
the laptop is suspended, so I'm pretty sure nothing gets delivered over
that link. No, I suspect the ACPI suspend method turns off the RTL8208
PHY chip, maybe as a side effect...
But I don't need working WoL on this system - look, this is cheap old
stuff that the previous owner considered electronic waste. I even
suspect this was because wired network never worked well after resume.
With your fix, this piece can still serve some purpose.
Thank you!
Petr T
[-- Attachment #2: Digitální podpis OpenPGP --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-09-30 21:44 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-15 8:28 RTL8402 stops working after hibernate/resume Petr Tesarik
2020-07-15 15:22 ` Heiner Kallweit
2020-07-16 8:58 ` Petr Tesarik
2020-07-18 12:07 ` Heiner Kallweit
2020-09-03 8:41 ` Petr Tesarik
2020-09-17 14:10 ` Petr Tesarik
2020-09-23 9:57 ` Heiner Kallweit
2020-09-24 19:14 ` Petr Tesarik
2020-09-24 19:37 ` Heiner Kallweit
2020-09-24 20:12 ` Heiner Kallweit
2020-09-25 7:30 ` Petr Tesarik
2020-09-25 8:54 ` Petr Tesarik
2020-09-25 9:44 ` Heiner Kallweit
2020-09-25 9:52 ` Petr Tesarik
2020-09-25 12:56 ` Petr Tesarik
2020-09-25 14:47 ` Heiner Kallweit
2020-09-29 19:07 ` Petr Tesarik
2020-09-29 19:41 ` Heiner Kallweit
2020-09-29 20:08 ` Hans de Goede
2020-09-29 20:29 ` Hans de Goede
2020-09-29 20:35 ` Heiner Kallweit
2020-09-29 20:42 ` Heiner Kallweit
2020-09-30 9:04 ` Hans de Goede
2020-09-30 15:47 ` Heiner Kallweit
2020-09-30 16:41 ` Petr Tesarik
2020-09-30 17:13 ` Heiner Kallweit
2020-09-30 17:32 ` Petr Tesarik
2020-09-30 18:00 ` Petr Tesarik
2020-09-30 20:11 ` Heiner Kallweit
2020-09-30 21:44 ` Petr Tesarik [this message]
2020-10-01 6:14 ` Heiner Kallweit
2020-09-30 18:10 ` Petr Tesarik
2020-09-29 21:17 ` Petr Tesarik
2020-07-15 15:25 ` Heiner Kallweit
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=20200930234407.0ce0b6d9@ezekiel.suse.cz \
--to=ptesarik@suse.cz \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.