From: "dilieto@lineone.net" <dilieto@lineone.net>
To: Knut_Petersen@t-online.de
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Stephen Hemminger <shemminger@vyatta.com>,
"David S. Miller" <davem@davemloft.net>,
arekm@maven.pl, Jared <nitro@legroom.net>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [REGRESSION][PATCH] Fix an old sky2 WOL regression
Date: Fri, 4 May 2012 21:17:02 +0100 (BST) [thread overview]
Message-ID: <32467848.260261336162622524.JavaMail.defaultUser@defaultHost> (raw)
Dear Knut,
I am sorry it took a while to try it due to other
commitments, however I can now confirm the patch works on my ASUS P5LD2
motherboard.
Many thanks
Nicola
On 2012-03-21 12:40, Knut Petersen
wrote:
> Sky2 Wake on LAN is broken since February 2010 on a number of
systems.
> Yes. More than two years.
>
> We know about the problem and
the cause since October 2010
> (Bugzilla bug #19492). It´s commit
87b09f1f25cd1e01d7c50bf423c7fe33027d7511.
>
> Stephen, David: You
signed off that commit.
>
> Andrew: You called it a regression in
October 2010.
>
> It has been proposed to revert the commit that caused
the problem.
> Nothing happened.
>
> I proposed to re-establish the old
code for dmi_match()ed systems.
> Without success.
>
> Now it is
proposed to re-establish the old code as a configuration option.
> If
nothing happens again I will propose a module parameter ;-)
>
>
Stephen, I don´t want to be a pain in the neck, and it is not my
intention
> to offend you by my "attitude". But I simply cannot
understand why this
> know regression is not fixed. The bit we talk
about is documented,
> and in fact it was set for a number of kernel
versions unconditionally.
> Nobody complained about ruined hardware or
minor problems.
>
> The systems affected are old enough that no
manufacturer cares about
> them, but they are still quite usable for a
lot of jobs (kernel 3.3 compile
> time here is below 15 minutes).
>
>
If there is a problem in the kernel and if we do know an easy solution,
> that solution should be commited to the kernel, no matter what is
written
> in some random documentation, no matter if we could blame
some
> BIOS authors. That´s the way Linux works - at least I thought
so.
>
> cu,
> Knut
next reply other threads:[~2012-05-04 20:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-04 20:17 dilieto [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-03-21 11:40 [REGRESSION][PATCH] Fix an old sky2 WOL regression Knut Petersen
2012-03-21 15:08 ` Stephen Hemminger
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=32467848.260261336162622524.JavaMail.defaultUser@defaultHost \
--to=dilieto@lineone.net \
--cc=Knut_Petersen@t-online.de \
--cc=akpm@linux-foundation.org \
--cc=arekm@maven.pl \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nitro@legroom.net \
--cc=shemminger@vyatta.com \
--cc=torvalds@linux-foundation.org \
/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.