Subject: Re: 2.6.10: e100 network broken after swsusp/resume
From: =?ISO-8859-1?Q?H=E5kan?= Lindqvist <lindqvist@netstar.se>
To: linux-kernel@vger.kernel.org
In-Reply-To: <20050102184239.GA21322@butterfly.hjsoft.com>
References: <20041228144741.GA2969@butterfly.hjsoft.com>
	 <20050101172344.GA1355@elf.ucw.cz>
	 <20050102055753.GB7406@ip68-4-98-123.oc.oc.cox.net>
	 <20050102184239.GA21322@butterfly.hjsoft.com>
Content-Type: text/plain; charset=ISO-8859-15
Date: Sun, 02 Jan 2005 21:09:16 +0100
Message-Id: <1104696556.2478.12.camel@pefyra>
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 971
Lines: 27

On s?n, 2005-01-02 at 13:42 -0500, John M Flinchbaugh wrote:
> pci=routeirq worked for me to get my e100 working again after resume.

For the record: It works around my problems with e100 and snd-intel8x0,
too.

> 
> so what's that mean?  what's the trade-off for using this option?


The Documentation/kernel-parameters.txt says this about pci=routeirq:
"Do IRQ routing for all PCI devices. This is normally done in
pci_enable_device(), so this option is a temporary workaround for broken
drivers that don't call it."

Ie, it doesn't sound too bad to use it until the problem is solved.
And I don't know if this particular issue is a case of broken drivers,
but that was what the parameter was added to work around.


/H?kan

-
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/