summaryrefslogtreecommitdiffstats
path: root/fs/nfs_common
diff options
context:
space:
mode:
authorAndy Gospodarek <andy@greyhouse.net>2007-05-10 22:58:57 -0700
committerGreg Kroah-Hartman <gregkh@suse.de>2007-05-31 16:56:36 -0700
commite3008dedff4bdc96a5f67224cd3d8d12237082a0 (patch)
treeb94671543b5dfcec7d2938bf25007c2237eca039 /fs/nfs_common
parent4fdadebc313f46a750e9ffca9c68c35c587ced9f (diff)
downloadop-kernel-dev-e3008dedff4bdc96a5f67224cd3d8d12237082a0.zip
op-kernel-dev-e3008dedff4bdc96a5f67224cd3d8d12237082a0.tar.gz
PCI: disable MSI by default on systems with Serverworks HT1000 chips
I've been seeing lots of messages like these: eth0: No interrupt was generated using MSI, switching to INTx mode. Please report this failure to the PCI maintainer and include system chipset information. On several systems that use the following Severworks HT1000 (also sometimes labeled as a Broadcom chipset as well) bridge chips. It doesn't appear MSI works well (if at all) on these systems. Signed-off-by: Andy Gospodarek <andy@greyhouse.net> Cc: "Eric W. Biederman" <ebiederm@xmission.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Diffstat (limited to 'fs/nfs_common')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud