From: Ed L Cashin <ecashin@uga.edu>
To: Andy Pfiffer <andyp@osdl.org>
Cc: fastboot@osdl.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: maybe: kexec + e100 + CONFIG_PM != working
Date: Tue, 08 Jul 2003 12:07:40 -0400 [thread overview]
Message-ID: <877k6tf1df.fsf@uga.edu> (raw)
In-Reply-To: <1057179998.4341.22.camel@andyp.pdx.osdl.net> (Andy Pfiffer's message of "02 Jul 2003 14:06:38 -0700")
Andy Pfiffer <andyp@osdl.org> writes:
> On Tue, 2003-07-01 at 15:03, Ed L Cashin wrote:
>> Ed L Cashin <ecashin@uga.edu> writes:
>>
>> ...
>> > I haven't tried the experiment you suggested where I disable e100 in
>> > the kernel configuration.
>>
>> OK, I just tried taking out the intel e100 driver and building in
>> Becker's eepro100 driver. This kernel can do kexec fine.
>
> I just had lunch with someone that knows a lot more about the e100
> driver than I do.
>
> I would be curious to know what happens if you disable CONFIG_PM (as
> seen in your .config), disable the eepro100 driver, re-enable the e100
> driver, and then try kexec again.
Yes, kexec works on the same system when I disable CONFIG_PM and use
the e100 driver. Sorry it took a while for me to get around to
testing it.
I should mention that the kernel is a little different than the other
one I was using. It's 2.5.73-osdl3 with this .config file:
http://www.cs.uga.edu/~cashin/temp/config-2.5.73-osdl3-20030708-120629
--
--Ed L Cashin | PGP public key:
ecashin@uga.edu | http://noserose.net/e/pgp/
prev parent reply other threads:[~2003-07-08 15:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030626120244.B29672@atlas.cs.uga.edu>
[not found] ` <1056753599.1200.53.camel@andyp.pdx.osdl.net>
[not found] ` <87k7b2q6mt.fsf@uga.edu>
[not found] ` <87d6gtrjjs.fsf@uga.edu>
2003-07-02 21:06 ` maybe: kexec + e100 + CONFIG_PM != working Andy Pfiffer
2003-07-08 16:07 ` Ed L Cashin [this message]
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=877k6tf1df.fsf@uga.edu \
--to=ecashin@uga.edu \
--cc=andyp@osdl.org \
--cc=fastboot@osdl.org \
--cc=linux-kernel@vger.kernel.org \
/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