From: Jiri Slaby <jirislaby@gmail.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: e1000-devel@lists.sourceforge.net,
LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
Jesse Barnes <jbarnes@virtuousgeek.org>
Subject: Re: e1000: "eeprom checksum is not valid" after kexec
Date: Thu, 23 Apr 2009 17:36:53 +0200 [thread overview]
Message-ID: <49F08B15.4080808@gmail.com> (raw)
In-Reply-To: <200904231715.44918.rjw@sisk.pl>
On 04/23/2009 05:15 PM, Rafael J. Wysocki wrote:
> On Thursday 23 April 2009, Jiri Slaby wrote:
>> 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
>
> I don't think it can be reverted.
But it works :). I'm not saying, it's correct to revert them upstream.
It was just confirmation, that it causes the problem.
>> just for an easy revert of the former one, which is actually the culprit.
>
> Can you just try to revert the changes in pci_raw_set_power_state() and check
> if that has any effect (it shouldn't)?
Please send a patch. I'm lost in the changes done there. Let's say
against the top of 20090423 next tree.
>> e1000: 0000:02:01.0: e1000_probe: Invalid MAC Address
>> e1000: 0000:02:01.0: e1000_probe: (PCI-X:33MHz:64-bit) 00:00:00:00:00:00
>
> So this is after kexec?
yes
> What happens if you remove just the
>
> /* Check if we're already there */
> if (dev->current_state == state)
> return 0;
>
> part from pci_set_power_state()?
Will try later.
Thanks.
next prev parent reply other threads:[~2009-04-23 15:37 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
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 [this message]
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=49F08B15.4080808@gmail.com \
--to=jirislaby@gmail.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.