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: <20090423144145.GA3749@vespa.holoscopio.com>
Date:	Thu, 23 Apr 2009 11:41:45 -0300
From:	Thadeu Lima de Souza Cascardo <cascardo@...oscopio.com>
To:	Jiri Slaby <jirislaby@...il.com>
Cc:	"Rafael J. Wysocki" <rjw@...k.pl>,
	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 Thu, Apr 23, 2009 at 04:30:01PM +0200, Jiri Slaby wrote:
> On 04/23/2009 04:10 PM, Thadeu Lima de Souza Cascardo wrote:
> > On Thu, Apr 23, 2009 at 03:36:43PM +0200, Jiri Slaby wrote:
> >> Hi,
> >>
> >> 4a865905f685eaefaedf6ade362323dc52aa703b
> >> (PCI PM: Make pci_set_power_state() handle devices with no PM support)
> >> breaks e1000 after being kexec'ed. These reverts fix the problem:
> >>     Revert "PCI PM: Make pci_set_power_state() handle devices with no PM
> >> support"
> >>     Revert "PCI PM: Introduce __pci_[start|complete]_power_transition()
> >> (rev. 2)"
> >>
> >> I reverted the second one just for an easy revert of the former one,
> >> which is actually the culprit.
> >>
> >> The symptoms:
> >> e1000 0000:02:01.0: enabling device (0000 -> 0003)
> >> e1000 0000:02:01.0: PCI INT A -> Link[LNKA] -> GSI 11 (level, low) -> IRQ 11
> >> e1000 0000:02:01.0: setting latency timer to 64
> >> e1000: 0000:02:01.0: e1000_probe: The EEPROM Checksum Is Not Valid
> >> Switched to high resolution mode on CPU 0
> > 
> > Have you tried b43fcd7dc7b, found in v2.6.30-rc3?
> 
> I've tried 2.6.30-rc3-next-20090423 without success.

You mean next-20090423. The patch is really found there.

But, then, I realize you mean reverting these patches for the kernel
that is running or the kernel that is being kexec'd?

If b43fcd7dc7b is applied to the running kernel, it fixes the shutdown
issue, and the next loaded kernel probes e1000 fine.

If you are reverting 4a865905f in the kexec'd kernel and the running
kernel does not have b43fcd7dc7b, then I'd like to test the revert for
my case here, which is e100.

Which is it?

Regards,
Cascardo.

Download attachment "signature.asc" of type "application/pgp-signature" (198 bytes)