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 22:40:14 +0200 [thread overview]
Message-ID: <49F0D22E.6050101@gmail.com> (raw)
In-Reply-To: <20090423144145.GA3749@vespa.holoscopio.com>
On 04/23/2009 04:41 PM, Thadeu Lima de Souza Cascardo wrote:
> 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:
>>> 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?
The latter.
> If b43fcd7dc7b is applied to the running kernel, it fixes the shutdown
> issue, and the next loaded kernel probes e1000 fine.
Makes sense.
> 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.
To make things clear: on that machine, there was stock opensuse 11.1
distro kernel which is 2.6.27-based (no b43fcd7dc7b). I needed to debug
a wireless bug, so I kexec'ed wireless-testing (contains 4a865905f already).
So in fact, 4a865905f from the testing kernel triggered a bug fixed in
near past by b43fcd7dc7b.
Did the other two e100* drivers suffer from the same and were fixed
recently? It would render kexec pretty unusable from the older kernels
if this is not going to be fixed anyhow :(.
next prev parent reply other threads:[~2009-04-23 20:40 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 [this message]
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=49F0D22E.6050101@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox