All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Slaby <jirislaby@gmail.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Thadeu Lima de Souza Cascardo <cascardo@holoscopio.com>,
	e1000-devel@lists.sourceforge.net, Ingo Molnar <mingo@elte.hu>,
	LKML <linux-kernel@vger.kernel.org>,
	Jesse Barnes <jbarnes@virtuousgeek.org>
Subject: Re: [E1000-devel] e1000: "eeprom checksum is not valid" after kexec
Date: Mon, 11 May 2009 16:31:38 +0200	[thread overview]
Message-ID: <4A0836CA.5070709@gmail.com> (raw)
In-Reply-To: <200904241809.45240.rjw@sisk.pl>

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




  reply	other threads:[~2009-05-11 14:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-23 13:36 e1000: "eeprom checksum is not valid" after kexec Jiri Slaby
2009-04-23 14:10 ` [E1000-devel] " Thadeu Lima de Souza Cascardo
2009-04-23 14:30   ` Jiri Slaby
2009-04-23 14:41     ` Thadeu Lima de Souza Cascardo
2009-04-23 20:40       ` Jiri Slaby
2009-04-23 21:17         ` Thadeu Lima de Souza Cascardo
2009-04-24 16:09           ` Rafael J. Wysocki
2009-05-11 14:31             ` Jiri Slaby [this message]
2009-05-11 15:24               ` Rafael J. Wysocki
2009-05-11 15:31                 ` Rafael J. Wysocki
2009-04-23 15:15 ` Rafael J. Wysocki
2009-04-23 15:36   ` Jiri Slaby
2009-04-23 21:48     ` Rafael J. Wysocki

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=4A0836CA.5070709@gmail.com \
    --to=jirislaby@gmail.com \
    --cc=cascardo@holoscopio.com \
    --cc=e1000-devel@lists.sourceforge.net \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rjw@sisk.pl \
    /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.