linux-kernel - Re: [E1000-devel] e1000: "eeprom checksum is not valid" after 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: <200905111724.12606.rjw@sisk.pl>
Date:	Mon, 11 May 2009 17:24:12 +0200
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Jiri Slaby <jirislaby@...il.com>
Cc:	Thadeu Lima de Souza Cascardo <cascardo@...oscopio.com>,
	e1000-devel@...ts.sourceforge.net, Ingo Molnar <mingo@...e.hu>,
	LKML <linux-kernel@...r.kernel.org>,
	Jesse Barnes <jbarnes@...tuousgeek.org>
Subject: Re: [E1000-devel] e1000: "eeprom checksum is not valid" after kexec

On Monday 11 May 2009, Jiri Slaby wrote:
> On 04/24/2009 06:09 PM, Rafael J. Wysocki wrote:
> > My understanding is that the commit pointed to by Jiri caused a problem
> > if the current mainline kernel was kexeced from an older kernel (2.6.27.x from
> > openSUSE-11.1 in this particular case), because the older kernel didn't
> > have the recent network driver fixes applied.  Is this correct?
> 
> Exactly!
> 
> > Also, I'm still interested in whether or not removig the following three lines:
> > 
> >         /* Check if we're already there */
> >         if (dev->current_state == state)
> >                 return 0;
> > 
> > from pci_set_power_state() in the current mainline kernel fixes the problem
> > in the configuration where it is readily reproducible.
> 
> After removing those lines, the problem still persists:
> e1000: 0000:02:01.0: e1000_probe: The EEPROM Checksum Is Not Valid

So it's more complicated than I thought.  Well ...

What if the driver in question is rmmoded before kexec?
--
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/