linux-kernel - Re: WOL with forcedeth broken since f55c21fd9a92a444e55ad1ca4e4732d56661bf2e

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 for Android: free password hash cracker in your pocket

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

Message-ID: <86802c440901292253ie9e2a9dmb4580a3da1480c81@mail.gmail.com>
Date:	Thu, 29 Jan 2009 22:53:40 -0800
From:	Yinghai Lu <yhlu.kernel@...il.com>
To:	Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Yinghai Lu <yhlu.kernel@...il.com>,
	Tobias Diedrich <ranma+kernel@...edrich.de>,
	Ayaz Abdulla <aabdulla@...dia.com>,
	Jeff Garzik <jeff@...zik.org>,
	"Rafael J. Wysocki" <rjw@...k.pl>
Subject: Re: WOL with forcedeth broken since f55c21fd9a92a444e55ad1ca4e4732d56661bf2e

On Wed, Jan 28, 2009 at 10:31 PM, Philipp Matthias Hahn
<pmhahn@...an.lahn.de> wrote:
> Hello!
>
> Somewhere between 2.6.26 and 2.6.27 WOL stopped working on my MS-7350
> motherboard with an "nVidia Corporation MCP51 Ethernet Controller (rev a3)".
>        "etherwake 00:19:db:f2:e1:35" did not work
>        "etherwake 35:e1:f2:db:19:00" did work
> Since I did a BIOS update during the same time window I (wrongly) put
> the fault on the BIOS. (See /sys/class/dmi/id/modalias for yourself:
> dmi:bvnAmericanMegatrendsInc.:bvrV1.7:bd07/29/2008:svnMSI:pnMS-7350:pvr1.0:rvnMSI:rnMS-7350:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
> )
>
> Today I finally found the time to test various old versions of
> "drivers/net/forcedeth.c" and also did a "git-bisect v2.6.26 v2.6.27"
> which lead to the following culprit:
>

can not find the reason why the WOL doesn't work...

please post
1. boot log for just after AC is pluged-in... ===> you should have
"nv_probe: set workaround bit for reversed mac addr"
2. and boot log after boot from WOL...==> you have have "nv_probe: set
workaround bit for reversed mac addr" too.

YH
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/