netdev - Re: [PATCH 0/4] Fix forcedeth hibernate/wake-on-lan problems

lists.openwall.net		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 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <200805271432.12881.david-b@pacbell.net>
Date:	Tue, 27 May 2008 14:32:12 -0700
From:	David Brownell <david-b@...bell.net>
To:	Tobias Diedrich <ranma+kernel@...edrich.de>
Cc:	netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
	Ayaz Abdulla <aabdulla@...dia.com>,
	"Rafael J. Wysocki" <rjw@...k.pl>,
	Stephen Hemminger <shemminger@...ux-foundation.org>,
	linux-acpi@...r.kernel.org, linux-pm@...ts.linux-foundation.org
Subject: Re: [PATCH 0/4] Fix forcedeth hibernate/wake-on-lan problems

On Monday 26 May 2008, Tobias Diedrich wrote:
> The platform_enable_wakeup() hook is still there, but unused.

The patches to support it (still) haven't been merged.

> AFAICS this patch should solve the "'ethtool -s eth0 wol g' doesn't
> suffice, I also have to write magic values into /proc/acpi/wakeup"
> issue.

Yeah; under ACPI, PCI does not act like it does everywhere else.
Nor does wakeup in general.

After sending patches to fix that for a couple years now, I'm
well past being tired of doing that.  I suggest it's overdue for
the ACPI team to get this part of their act together.

That is:  either start merging those patches, possibly with updates
to handle broken hardware better; or rewrite them; ... or just say
explicitly the message I've been receiving:  "Linux ACPI will never
support wakeup the way the rest of Linux can and does".  (And the
"why" should be something reasonable.)

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html