netdev - RE: [PATCH] e1000e: Fix usage under kexec

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: <EA929A9653AAE14F841771FB1DE5A1365FA68EE90F@rrsmsx501.amr.corp.intel.com>
Date:	Tue, 17 Nov 2009 14:28:54 -0700
From:	"Tantilov, Emil S" <emil.s.tantilov@...el.com>
To:	Stefan Assmann <sassmann@...hat.com>, Sven Anders <sven@...uras.de>
CC:	netdev <netdev@...r.kernel.org>
Subject: RE: [PATCH] e1000e: Fix usage under kexec

Stefan Assmann wrote:
> On 09.11.2009 21:25, Sven Anders wrote:
>> Hello!
>> 
>> We're experiencing the following problem:
>> 
>> We start a minimal linux system, prepare the system and start the
>> final system via kexec. On two different systems (one with a 82573
>> and one with a 82574), the driver cannot initialize the network
>> hardware, because the PHY is not recognized. 
>> 
>> We get the following error:
>>   e1000e: probe of 0000:02:00.0 failed with error -2
> 
> Hi Sven,
> 
> have a look at the following thread, it seems very similar.
> http://kerneltrap.org/mailarchive/linux-netdev/2009/3/7/5114394
> 
>   Stefan
> --
> Stefan Assmann         | Red Hat GmbH
> Software Engineer      | Otto-Hahn-Strasse 20, 85609 Dornach
>                        | HR: Amtsgericht Muenchen HRB 153243
>                        | GF: Brendan Lane, Charlie Peters,
> sassmann at redhat.com |     Michael Cunningham, Charles Cachera

But there is already similar code in e1000e:
http://git.kernel.org/?p=linux/kernel/git/davem/net-2.6.git;a=commit;h=4f9de721ab73a5271a79b126f7b5140b01a05c99--
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