On Sat, Aug 03, 2013 at 02:15:16PM +0200, Mark Kettenis wrote: > Theo and I predicted this would happen. When Windows would start > using message signalled interrupts (MSIs), support for APIC interrupts > in BIOSen for new machines would get broken. On a HP Pavillion > Sleekbook 15 I have here the ACPI tables claim the network controller > is connected to pin 16 on the APIC, but in reality it is connected to > pin 17. Funnily enough the BIOS also defines a table with the right > mappings, but nothing is referencing that table. Telltale signs of > shoddy engineering and a total lack of quality control. OK, this was > pretty much the cheapest laptop I could find last June. > > Anyway, I expect to see more and more issues like these as time goes > by. The solution is to be more aggressive with using MSIs in our > drivers. So here is a diff that switches re(4) over to use MSIs on > the RTL8101E "fast" Ethernet variants. These chips are fairly new so > there isn't a gazillion different variants of them, so it's very > likely that MSI will work on all of them. We can take a look at the > other variants later.
Fwiw, works fine on my MSI Wind U100 : re0 at pci1 dev 0 function 0 "Realtek 8101E" rev 0x02: RTL8102E (0x3480), apic 2 int 16, address 00:21:85:e2:8f:8f rlphy0 at re0 phy 7: RTL8201L 10/100 PHY, rev. 1 => re0 at pci1 dev 0 function 0 "Realtek 8101E" rev 0x02: RTL8102E (0x3480), msi, address 00:21:85:e2:8f:8f rlphy0 at re0 phy 7: RTL8201L 10/100 PHY, rev. 1 Landry
