From: John M Flinchbaugh <john@hjsoft.com>
To: Pavel Machek <pavel@ucw.cz>, John M Flinchbaugh <john@hjsoft.com>,
linux-kernel@vger.kernel.org
Subject: Re: 2.6.10: e100 network broken after swsusp/resume
Date: Sun, 2 Jan 2005 13:42:39 -0500 [thread overview]
Message-ID: <20050102184239.GA21322@butterfly.hjsoft.com> (raw)
In-Reply-To: <20050102055753.GB7406@ip68-4-98-123.oc.oc.cox.net>
[-- Attachment #1: Type: text/plain, Size: 718 bytes --]
On Sat, Jan 01, 2005 at 09:57:53PM -0800, Barry K. Nathan wrote:
> > e100 does not help, fault is not in e100]. Are you running with APIC
> > enabled? Try noapic. Try acpi=off.
> Reloading doesn't help, with either e100 or 8139too. I forgot to
> mention
> that in my other e-mail in this thread. (As I previously mentioned,
> on
> my system with 8139too, noapic makes matters worse, and the problem
> goes
> away if I use *either* pci=routeirq or acpi=off. I haven't tried
> using
> both.)
pci=routeirq worked for me to get my e100 working again after resume.
so what's that mean? what's the trade-off for using this option?
thanks for the guidance.
--
John M Flinchbaugh
john@hjsoft.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-01-02 18:42 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-28 14:47 2.6.10: e100 network broken after swsusp/resume John M Flinchbaugh
2004-12-28 21:25 ` Håkan Lindqvist
2005-01-01 23:41 ` Eduard Bloch
2005-01-01 17:23 ` Pavel Machek
2005-01-01 22:17 ` John M Flinchbaugh
2005-01-01 22:52 ` Pavel Machek
2005-01-01 23:14 ` Matthew Garrett
2005-01-02 3:46 ` Barry K. Nathan
2005-01-02 5:57 ` Barry K. Nathan
2005-01-02 18:42 ` John M Flinchbaugh [this message]
2005-01-02 20:09 ` Håkan Lindqvist
2005-01-03 5:10 ` Barry K. Nathan
2005-01-03 8:31 ` Barry K. Nathan
2005-01-03 8:53 ` Pavel Machek
2005-01-03 8:47 ` Pavel Machek
2005-01-03 10:14 ` Barry K. Nathan
2005-01-03 15:05 ` [PATCH] swsusp: properly suspend and resume *all* devices Barry K. Nathan
2005-01-03 17:08 ` Pavel Machek
2005-01-03 18:33 ` Pavel Machek
2005-01-04 5:15 ` Barry K. Nathan
2005-01-04 5:18 ` Barry K. Nathan
2005-01-04 8:44 ` Martin Lucina
2005-01-04 10:30 ` 2.6.10 suspend/resume bustage (was Re: [PATCH] swsusp: properly suspend and resume *all* devices) Martin Lucina
2005-01-04 21:43 ` [PATCH] swsusp: properly suspend and resume *all* devices Pavel Machek
2005-01-05 15:57 ` Lion Vollnhals
2005-01-06 22:29 ` Pavel Machek
2005-01-07 13:47 ` Takashi Iwai
2005-01-07 13:54 ` Pavel Machek
2005-01-07 14:48 ` Dmitry Torokhov
2005-01-07 15:35 ` Vojtech Pavlik
2005-01-07 15:59 ` Lion Vollnhals
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=20050102184239.GA21322@butterfly.hjsoft.com \
--to=john@hjsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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.