Date: Sat, 1 Jan 2005 21:57:53 -0800
From: "Barry K. Nathan" <barryn@pobox.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: John M Flinchbaugh <john@hjsoft.com>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.10: e100 network broken after swsusp/resume
Message-ID: <20050102055753.GB7406@ip68-4-98-123.oc.oc.cox.net>
References: <20041228144741.GA2969@butterfly.hjsoft.com> <20050101172344.GA1355@elf.ucw.cz>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20050101172344.GA1355@elf.ucw.cz>
User-Agent: Mutt/1.5.5.1i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 820
Lines: 18

On Sat, Jan 01, 2005 at 06:23:44PM +0100, Pavel Machek wrote:
> e100 seems to have some suspend/resume support [but if even reloading
> 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.)

-Barry K. Nathan <barryn@pobox.com>

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/