From: Doug Siebert <dsiebert@divms.uiowa.edu>
To: nfp3033@privat.cybercity.no
Cc: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: pci bridge fails to wake up from suspend/resume( Inspiron 8000 )
Date: Mon, 19 Feb 2001 22:40:31 -0600 (CST) [thread overview]
Message-ID: <200102200440.WAA10118@server.divms.uiowa.edu> (raw)
Morten,
I'm not subscribed to linux-kernel, but I've been following the list archive
somewhat for the past month (watching 2.4 development so I can figure out
when it is safe to make the jump without too much hassle)
I just bought a Dell Inspiron 4000 laptop a month ago, and have the same
problem with suspend/resume, with both devices on the PCI bridge (both the
eepro100 ethernet as well as the LT winmodem) Same symptoms, both work fine
until suspend, after resume neither work at all. I tried your fix, and it
worked for me. I did the same thing you did, running 'lspci -vx' to see
the PCI registers before and after, and then use 'setpci' to fix them.
Since the i4000 uses a 440BX mobile chipset, it isn't exactly the same
commands, but I got it to work (I had to ifconfig eth0 down then 'ifup
eth0' to make it work) Its a pretty general fix, as I'm running Redhat 6.2
with kernel 2.2.16. Yeah, kind of old, but I hope to be running 2.4 pretty
soon! (BTW, as you probably already know, your fix works fine for
re-enabling the winmodem after resume as well)
I'm cc:ing linux-kernel also, in case anyone working this problem can benefit
from the additional data point. If anyone working this needs further info
from me (lspci results or whatever) feel free to email me at this address.
--
Douglas Siebert
douglas-siebert@uiowa.edu
A computer without Microsoft software is like chocolate cake without ketchup.
next reply other threads:[~2001-02-20 4:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-20 4:40 Doug Siebert [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-02-18 21:02 PROBLEM: pci bridge fails to wake up from suspend/resume( Inspiron 8000 ) Morten Stenseth
2001-02-19 13:09 ` Andrew Morton
2001-02-20 0:00 ` Morten Stenseth
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=200102200440.WAA10118@server.divms.uiowa.edu \
--to=dsiebert@divms.uiowa.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=nfp3033@privat.cybercity.no \
/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