lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <037FCE6B-850E-4A88-B4C3-B856B306377E@petlund.no>
Date:	Thu, 6 Nov 2008 17:31:46 +0100
From:	Andreas Petlund <andreas@...lund.no>
To:	netdev@...r.kernel.org
Subject: forcedeth MCP55 msi problems

I have a machine with an Asus motherboard (P5N32-SLI Premium - NVidia  
MCP55 chipset) where the forcedeth module does not work with msi. This  
seems to bother quite some people ( see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/136836 
  ).

Reading various forum posts makes me inclined to believe this is a  
firmware problem, but Asus have no fix with their latest BIOS-upgrade  
(and I am starting to believe that we will never see one as the last  
update came in March this year).

Is it an option to workaround this problem using a hardware-specific  
quirk that disables msi/msix for the device, or will that affect a lot  
of users that have no issues with this? On my system the NIC  
identifies as "cb84". I don't know if this is a common factor for all  
who has this problem, or only for my motherboard.
Maybe the benefit of making it work with all MCP55-NICs is worth  
disabling msi/msix also for unaffected ones?

Does anybody have alternative suggestions?


Download attachment "smime.p7s" of type "application/pkcs7-signature" (2213 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ