From: Jiri Slaby <jirislaby@gmail.com>
To: Thadeu Lima de Souza Cascardo <cascardo@holoscopio.com>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
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: Thu, 23 Apr 2009 16:30:01 +0200 [thread overview]
Message-ID: <49F07B69.1020305@gmail.com> (raw)
In-Reply-To: <20090423141026.GB4046@vespa.holoscopio.com>
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.
next prev parent reply other threads:[~2009-04-23 14:30 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 [this message]
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
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=49F07B69.1020305@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.