[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <m1d43drt0g.fsf@fess.ebiederm.org>
Date: Fri, 20 Nov 2009 09:43:59 -0800
From: ebiederm@...ssion.com (Eric W. Biederman)
To: Dhananjay Phadke <dhananjay.phadke@...gic.com>
Cc: Jens Rosenboom <me@...r.de>,
"netdev\@vger.kernel.org" <netdev@...r.kernel.org>,
Amit Salecha <amit.salecha@...gic.com>,
Ameen Rahman <ameen.rahman@...gic.com>
Subject: Re: [BUG] netxen: Stops working between 2.6.30 and 2.6.31-rc1
Dhananjay Phadke <dhananjay.phadke@...gic.com> writes:
>> Weird. MSI's definitely weren't disabled. Looking a little farther at
>> your quoted setup MSI work on your board. This is definitely
>> something specific to the driver. Except for a few initialization
>> races that are an issue for bonding I am running 2.6.31 just fine.
>
>
> Jens,
>
> Even if /proc/interrupt says PCI-MSI in both cases, single interrupt case is msi
> vs. 4 vector case is msi-x. To confirm that msi-x doesn't work with your
> card/machine, you can still stay on 2.6.31 and set use_msi_x=0 in
> netxen_nic_main.c.
>
> I had tried to make a available a module param to disable msi/msi-x for
> platforms where msi-x doesn't work cleanly, but it was declined by David Miller,
> et al.
MSI-X uses the same messages on the wire is the same as MSI it is
only the programming interface that is different. So if MSI works and
MSI-X does not it is not a platform problem.
Eric
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists