W dniu 30.01.2023 o 16:56, Rafael J. Wysocki pisze: > On Mon, Jan 23, 2023 at 10:44 PM Bjorn Helgaas <helgaas@xxxxxxxxxx> wrote: >> On Mon, Jan 23, 2023 at 10:00:43PM +0100, Mateusz Jończyk wrote: >>> W dniu 23.01.2023 o 21:33, Bjorn Helgaas pisze: >>>> On Sat, Jan 21, 2023 at 04:33:14PM +0100, Mateusz Jończyk wrote: >>>>> On some platforms, the ACPI _PRT function returns duplicate interrupt >>>>> routing entries. Linux uses the first matching entry, but sometimes the >>>>> second matching entry contains the correct interrupt vector. >>>>> >>>>> Print an error to dmesg if duplicate interrupt routing entries are >>>>> present, so that we could check how many models are affected. >>>> It shouldn't be too hard to use qemu to figure out whether Windows >>>> uses the last matching entry, i.e., treating _PRT entries as >>>> assignments. If so, maybe Linux could just do the same. >>>> >>>> Is anybody up for that? >>> The hardware in question has a working Windows XP installation, >>> and I could in theory check which interrupt vector it uses - but >>> I think that such reverse engineering is forbidden by Windows' EULA. >> I'm not talking about any sort of disassembly or anything like that; >> just that we can observe what Windows does given the _PRT contents. >> You've already figured out that on your particular hardware, the _PRT >> has two entries, and Linux uses the first one while Windows uses the >> second one, right? >> >> On qemu, we have control over the BIOS and can easily update _PRT to >> whatever we want, and then we could boot Windows and see what it uses. >> But I guess maybe that wouldn't tell us anything more than what you >> already discovered. >> >> So my inclination would be to make Linux use the last matching entry. > But it would be able to log a diagnostic message anyway IMO. > > So maybe two steps can be taken here, (1) adding the message printout > (this patch) and (2) changing the behavior? I have checked and Windows XP uses a different interrupt number for the device than both numbers from the table returned by the _PRT method (the correct and the incorrect ones). It uses IRQ3, as shown in the Device Manager and in HWiNFO32 output: Intel 82801IB ICH9 - SMBus Controller [A3] -------------------------------- [General Information] Device Name: Intel 82801IB ICH9 - SMBus Controller [A3] Original Device Name: Intel 82801IB ICH9 - SMBus Controller [A3] Device Class: SMBus (System Management Bus) Revision ID: 3 [A3] PCI Address (Bus:Device:Function) Number: 0:31:3 PCI Latency Timer: 0 Hardware ID: PCI\VEN_8086&DEV_2930&SUBSYS_024F1028&REV_03 [System Resources] Interrupt Line: IRQ3 Interrupt Pin: INTB# Memory Base Address 0 F6ADAF00 I/O Base Address 4 1100 [Features] Bus Mastering: Disabled Running At 66 MHz: Not Capable Fast Back-to-Back Transactions: Capable DeviceInstanceId PCI\VEN_8086&DEV_2930&SUBSYS_024F1028&REV_03\3&61AAA01&0&FB Unpatched Linux kernel uses IRQ19, which is incorrect; the correct vector (under Linux at least) is IRQ17. On the other hand, HWiNFO32 has neatly decoded contents of the SPD EEPROMs, which are connected to the SMBus controller in question. So either: 1. Windows' driver (or driver from HWiNFO32 perhaps?) does not use interrupts for the device. 2. Windows somehow has reassigned the interrupt vector for the device. The datasheet [1] indicates it is possible (page 375, Device 31 Interrupt Route Register), but I'm not sure if the interrupt can be reassigned to such a low number. So all in all, I would suggest shipping a patch that only prints a warning for a release or two before changing the default. Greetings, Mateusz [1] https://www.intel.com/content/www/us/en/io/io-controller-hub-9-datasheet.html
