Bug 7024
| Summary: | sky2 No interrupt was generated using MSI | ||
|---|---|---|---|
| Product: | Drivers | Reporter: | Avuton Olrich (avuton) |
| Component: | Network | Assignee: | Stephen Hemminger (stephen) |
| Status: | REJECTED INVALID | ||
| Severity: | low | CC: | stephen |
| Priority: | P2 | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Kernel Version: | 2.6.18-rc4 git tree b5f2eaeecd41c868d83d6aa443da776852cd4c95 | Subsystem: | |
| Regression: | --- | Bisected commit-id: | |
| Attachments: |
The full dmesg
The kernel config The full lspci -vvv |
||
Created attachment 8831 [details]
The full dmesg
Created attachment 8832 [details]
The kernel config
The message is harmless, warning only. MSI support for sky2 driver was added after 2.6.16 and it checks for broken hardware before using it. Unfortunately, that motherboard seems to have tripped it. Most likely it is an issue with ACPI on that motherboard. Could you attach a complete lspci output. Created attachment 8841 [details]
The full lspci -vvv
Okay, is this i386 or x86_64 kernel? not that it matters much. x86_64 kernel Is this still a problem with 2.6.18? Since it is a warning only, I will just change the warning to be less verbose. The failure of MSI is a BIOS and hardware related issue that can not be resolved without the vendor fixing the BIOS. Since Windows doesn't support MSI, vendors have been slow to address this. |
Most recent kernel where this bug did not occur: This begins to occur somewhere between v2.6.16 and v2.6.17, will bisect if necessary, but this sounded like a warning that was put in to inform. Distribution: Gentoo Problem Description: In dmesg I get the following message: sky2 v1.5 addr 0xf7ffc000 irq 50 Yukon-EC (0xb6) rev 1 sky2 eth0: addr 00:13:d3:ee:b1:b3 sky2 0000:02:00.0: No interrupt was generated using MSI, switching to INTx mode. Please report this failure to the PCI maintainer and include system chipset information. This does occur without the nvidia taint, I tried personally. lspci -vvv for only this enthernet controller: 02:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8053 PCI-E Gigabit Ethernet Controller (rev 15) Subsystem: Micro-Star International Co., Ltd. Marvell 88E8053 Gigabit Ethernet Controller (MSI) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- Latency: 0, Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 50 Region 0: Memory at f7ffc000 (64-bit, non-prefetchable) [size=16K] Region 2: I/O ports at c800 [size=256] Expansion ROM at f7fc0000 [disabled] [size=128K] Capabilities: [48] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=1 PME- Capabilities: [50] Vital Product Data Capabilities: [5c] Message Signalled Interrupts: 64bit+ Queue=0/1 Enable- Address: 00000000fee00000 Data: 403a Capabilities: [e0] Express Legacy Endpoint IRQ 0 Device: Supported: MaxPayload 128 bytes, PhantFunc 0, ExtTag- Device: Latency L0s unlimited, L1 unlimited Device: AtnBtn- AtnInd- PwrInd- Device: Errors: Correctable- Non-Fatal- Fatal- Unsupported- Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr+ NoSnoop- Device: MaxPayload 128 bytes, MaxReadReq 512 bytes Link: Supported Speed 2.5Gb/s, Width x1, ASPM L0s, Port 1 Link: Latency L0s <256ns, L1 unlimited Link: ASPM Disabled RCB 128 bytes CommClk+ ExtSynch- Link: Speed 2.5Gb/s, Width x1