The MSI Driver Guide HOWTO

The MSI Driver Guide HOWTO

[rec]

Hi,

Like asked in :  
https://www.kernel.org/doc/html/latest/PCI/msi-howto.html#disabling-msis-globally


00:00.0 Host bridge: Silicon Integrated Systems [SiS] 671MX
     Subsystem: ASUSTeK Computer Inc. 671MX
     Flags: bus master, medium devsel, latency 64
00:01.0 PCI bridge: Silicon Integrated Systems [SiS] PCI-to-PCI bridge  
(prog-if 00 [Normal decode])
     Subsystem: Silicon Integrated Systems [SiS] PCI-to-PCI bridge
     Flags: bus master, fast devsel, latency 0
     Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
     I/O behind bridge: d000-dfff [size=4K] [16-bit]
     Memory behind bridge: fa000000-fdefffff [size=63M] [32-bit]
     Prefetchable memory behind bridge: d0000000-dfffffff [size=256M]  
[32-bit]
     Capabilities: <access denied>
     Kernel driver in use: pcieport
00:02.0 ISA bridge: Silicon Integrated Systems [SiS] SiS968 [MuTIOL  
Media IO] (rev 01)
     Flags: bus master, medium devsel, latency 0
00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 IDE  
Controller (rev 01) (prog-if 80 [ISA Compatibility mode-only  
controller, supports bus mastering])
     Subsystem: ASUSTeK Computer Inc. 5513 IDE Controller
     Flags: bus master, medium devsel, latency 128
     I/O ports at 01f0 [size=8]
     I/O ports at 03f4
     I/O ports at 0170 [size=8]
     I/O ports at 0374
     I/O ports at fff0 [size=16]
     Capabilities: <access denied>
     Kernel driver in use: pata_sis
     Kernel modules: pata_sis, ata_generic
00:03.0 USB controller: Silicon Integrated Systems [SiS] USB 1.1  
Controller (rev 0f) (prog-if 10 [OHCI])
     Subsystem: ASUSTeK Computer Inc. USB 1.1 Controller
     Flags: bus master, medium devsel, latency 64, IRQ 20
     Memory at f9fff000 (32-bit, non-prefetchable) [size=4K]
     Kernel driver in use: ohci-pci
     Kernel modules: ohci_pci
00:03.1 USB controller: Silicon Integrated Systems [SiS] USB 1.1  
Controller (rev 0f) (prog-if 10 [OHCI])
     Subsystem: ASUSTeK Computer Inc. USB 1.1 Controller
     Flags: bus master, medium devsel, latency 64, IRQ 21
     Memory at f9ffe000 (32-bit, non-prefetchable) [size=4K]
     Kernel driver in use: ohci-pci
     Kernel modules: ohci_pci
00:03.3 USB controller: Silicon Integrated Systems [SiS] USB 2.0  
Controller (prog-if 20 [EHCI])
     Subsystem: ASUSTeK Computer Inc. USB 2.0 Controller
     Flags: bus master, medium devsel, latency 64, IRQ 22
     Memory at f9ffd000 (32-bit, non-prefetchable) [size=4K]
     Capabilities: <access denied>
     Kernel driver in use: ehci-pci
     Kernel modules: ehci_pci
00:04.0 Ethernet controller: Silicon Integrated Systems [SiS] 191  
Gigabit Ethernet Adapter (rev 02)
     Subsystem: ASUSTeK Computer Inc. 191 Gigabit Ethernet Adapter
     Flags: bus master, medium devsel, latency 0, IRQ 19
     Memory at f9ffcc00 (32-bit, non-prefetchable) [size=128]
     I/O ports at cc00 [size=128]
     Capabilities: <access denied>
     Kernel driver in use: sis190
     Kernel modules: sis190
00:05.0 IDE interface: Silicon Integrated Systems [SiS] SATA Controller  
/ IDE mode (rev 03) (prog-if 8f [PCI native mode controller, supports  
both channels switched to ISA compatibility mode, supports bus  
mastering])
     Subsystem: ASUSTeK Computer Inc. SATA Controller / IDE mode
     Flags: bus master, medium devsel, latency 64, IRQ 17
     I/O ports at c800 [size=8]
     I/O ports at c400 [size=4]
     I/O ports at c000 [size=8]
     I/O ports at bc00 [size=4]
     I/O ports at b800 [size=16]
     I/O ports at b400 [size=128]
     Capabilities: <access denied>
     Kernel driver in use: sata_sis
     Kernel modules: sata_sis, ata_generic
00:06.0 PCI bridge: Silicon Integrated Systems [SiS] PCI-to-PCI bridge  
(prog-if 00 [Normal decode])
     Subsystem: Silicon Integrated Systems [SiS] PCI-to-PCI bridge
     Flags: bus master, fast devsel, latency 0
     Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
     I/O behind bridge: [disabled] [32-bit]
     Memory behind bridge: fdf00000-fdffffff [size=1M] [32-bit]
     Prefetchable memory behind bridge: [disabled] [64-bit]
     Capabilities: <access denied>
     Kernel driver in use: pcieport
00:07.0 PCI bridge: Silicon Integrated Systems [SiS] PCI-to-PCI bridge  
(prog-if 00 [Normal decode])
     Subsystem: Silicon Integrated Systems [SiS] PCI-to-PCI bridge
     Flags: bus master, fast devsel, latency 0
     Bus: primary=00, secondary=03, subordinate=06, sec-latency=0
     I/O behind bridge: e000-efff [size=4K] [16-bit]
     Memory behind bridge: fe000000-febfffff [size=12M] [32-bit]
     Prefetchable memory behind bridge: f6000000-f8ffffff [size=48M]  
[32-bit]
     Capabilities: <access denied>
     Kernel driver in use: pcieport
00:0d.0 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller  
(rev 05) (prog-if 10 [OHCI])
     Subsystem: ASUSTeK Computer Inc. R5C832 IEEE 1394 Controller
     Flags: bus master, medium devsel, latency 64, IRQ 16
     Memory at f9ffc000 (32-bit, non-prefetchable) [size=2K]
     Capabilities: <access denied>
     Kernel driver in use: firewire_ohci
     Kernel modules: firewire_ohci
00:0d.1 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro  
Host Adapter (rev 22)
     Subsystem: ASUSTeK Computer Inc. R5C822 SD/SDIO/MMC/MS/MSPro Host  
Adapter
     Flags: bus master, medium devsel, latency 64, IRQ 17
     Memory at f9ffc800 (32-bit, non-prefetchable) [size=256]
     Capabilities: <access denied>
     Kernel driver in use: sdhci-pci
     Kernel modules: sdhci_pci
00:0d.2 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host  
Adapter (rev 12)
     Subsystem: ASUSTeK Computer Inc. R5C592 Memory Stick Bus Host  
Adapter
     Flags: bus master, medium devsel, latency 64, IRQ 17
     Memory at f9ff7c00 (32-bit, non-prefetchable) [size=256]
     Capabilities: <access denied>
     Kernel driver in use: r592
     Kernel modules: r592
00:0d.3 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev  
12)
     Subsystem: ASUSTeK Computer Inc. xD-Picture Card Controller
     Flags: bus master, medium devsel, latency 64, IRQ 17
     Memory at f9ff7800 (32-bit, non-prefetchable) [size=256]
     Capabilities: <access denied>
     Kernel driver in use: r852
     Kernel modules: r852
00:0f.0 Audio device: Silicon Integrated Systems [SiS] Azalia Audio  
Controller
     Subsystem: ASUSTeK Computer Inc. Azalia Audio Controller
     Flags: bus master, medium devsel, latency 0, IRQ 18
     Memory at f9ff0000 (32-bit, non-prefetchable) [size=16K]
     Capabilities: <access denied>
     Kernel driver in use: snd_hda_intel
     Kernel modules: snd_hda_intel
01:00.0 VGA compatible controller: NVIDIA Corporation G98M [GeForce  
9300M GS] (rev a1) (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. U6V laptop
     Flags: bus master, fast devsel, latency 0, IRQ 16
     Memory at fc000000 (32-bit, non-prefetchable) [size=16M]
     Memory at d0000000 (64-bit, prefetchable) [size=256M]
     Memory at fa000000 (64-bit, non-prefetchable) [size=32M]
     I/O ports at dc00 [size=128]
     Expansion ROM at 000c0000 [disabled] [size=128K]
     Capabilities: <access denied>
     Kernel driver in use: nouveau
     Kernel modules: nouveau
02:00.0 Network controller: Qualcomm Atheros AR928X Wireless Network  
Adapter (PCI-Express) (rev 01)
     Subsystem: AzureWave AW-NE771 802.11bgn Wireless Mini PCIe Card  
[AR9281]
     Flags: bus master, fast devsel, latency 0, IRQ 16
     Memory at fdff0000 (64-bit, non-prefetchable) [size=64K]
     Capabilities: <access denied>
     Kernel driver in use: ath9k
     Kernel modules: ath9k


Thanks for all.

Re: The MSI Driver Guide HOWTO

[Bjorn Helgaas]

On Tue, Mar 07, 2023 at 12:22:44PM +0100, rec wrote:
> Like asked in : https://www.kernel.org/doc/html/latest/PCI/msi-howto.html#disabling-msis-globally

Thanks for the report!  I assume this means your system has problems
with MSIs, and booting with "pci=nomsi" makes it work better?

Can you please give some details about what is broken when you boot
without "pci=nomsi"?  If you can collect a complete dmesg log both
with and without "pci=nomsi", that would be great.

Bjorn

> 00:00.0 Host bridge: Silicon Integrated Systems [SiS] 671MX
>     Subsystem: ASUSTeK Computer Inc. 671MX
>     Flags: bus master, medium devsel, latency 64
> ...

Re: The MSI Driver Guide HOWTO

[rec]

[-- Attachment #1: Type: text/plain, Size: 681 bytes --]

On 09/03/2023 00:03:04, Bjorn Helgaas wrote:
> On Tue, Mar 07, 2023 at 12:22:44PM +0100, rec wrote:
> > Like asked in :  
> https://www.kernel.org/doc/html/latest/PCI/msi-howto.html#disabling-msis-globally

> Thanks for the report!  I assume this means your system has problems
> with MSIs, and booting with "pci=nomsi" makes it work better?

You are welcome,
The system doesn't boot completely without the "pci=nomsi" option.

Attach with this message the two boots journactl log.

> Can you please give some details about what is broken when you boot
> without "pci=nomsi"?  If you can collect a complete dmesg log both
> 

Good continuation to you and the team.

[-- Attachment #2: bootnomsi.txt.7z --]
[-- Type: application/x-7z-compressed, Size: 33015 bytes --]

[-- Attachment #3: bootmsi.txt.7z --]
[-- Type: application/x-7z-compressed, Size: 12252 bytes --]

Re: The MSI Driver Guide HOWTO

[Bjorn Helgaas]

On Thu, Mar 09, 2023 at 10:57:51AM +0100, rec wrote:
> On 09/03/2023 00:03:04, Bjorn Helgaas wrote:
> > On Tue, Mar 07, 2023 at 12:22:44PM +0100, rec wrote:
> > > Like asked in : https://www.kernel.org/doc/html/latest/PCI/msi-howto.html#disabling-msis-globally
> 
> > Thanks for the report!  I assume this means your system has problems
> > with MSIs, and booting with "pci=nomsi" makes it work better?
> 
> You are welcome,
> The system doesn't boot completely without the "pci=nomsi" option.

What exactly do you mean by "it doesn't boot completely"?  I compared
the two dmesg logs, and I see that the "with MSI" log also has the
"single" parameter, so it will only boot to single-user mode.

The "pci=nomsi" log does not have "single", so it will boot normally.

But I guess if you omit both "single" and "pci=nomsi", something still
goes wrong?  Do you have a log for that case?

Bjorn

Re: The MSI Driver Guide HOWTO

[gael.seibert]

[-- Attachment #1: Type: text/plain, Size: 1054 bytes --]

On 09/03/2023 23:55:03, Bjorn Helgaas wrote:
> On Thu, Mar 09, 2023 at 10:57:51AM +0100, rec wrote:
> > On 09/03/2023 00:03:04, Bjorn Helgaas wrote:
> > > On Tue, Mar 07, 2023 at 12:22:44PM +0100, rec wrote:
> > > > Like asked in :  
> https://www.kernel.org/doc/html/latest/PCI/msi-howto.html#disabling-msis-globally
> >
> > > Thanks for the report!  I assume this means your system has  
> problems
> > > with MSIs, and booting with "pci=nomsi" makes it work better?
> >
> > You are welcome,
> > The system doesn't boot completely without the "pci=nomsi" option.
> 
> What exactly do you mean by "it doesn't boot completely"?  I compared
> the two dmesg logs, and I see that the "with MSI" log also has the
> "single" parameter, so it will only boot to single-user mode.

It does it mean than either the boot stop or the system halt, power-off  
before it can be possible to connect tty console or display manager.

Attach with this message the bootmsi log without the single option.

Thanks again for your attention,

Gaël


[-- Attachment #2: bootmsi_nosingle.txt.7z --]
[-- Type: application/x-7z-compressed, Size: 12570 bytes --]

Re: The MSI Driver Guide HOWTO

[Bjorn Helgaas]

On Fri, Mar 10, 2023 at 11:23:14AM +0100, gael.seibert@gmx.fr wrote:
> On 09/03/2023 23:55:03, Bjorn Helgaas wrote:
> > On Thu, Mar 09, 2023 at 10:57:51AM +0100, rec wrote:
> > > On 09/03/2023 00:03:04, Bjorn Helgaas wrote:
> > > > On Tue, Mar 07, 2023 at 12:22:44PM +0100, rec wrote:
> > > > > Like asked in : https://www.kernel.org/doc/html/latest/PCI/msi-howto.html#disabling-msis-globally
> > >
> > > > Thanks for the report!  I assume this means your system has problems
> > > > with MSIs, and booting with "pci=nomsi" makes it work better?
> > >
> > > You are welcome,
> > > The system doesn't boot completely without the "pci=nomsi" option.
> > 
> > What exactly do you mean by "it doesn't boot completely"?  I compared
> > the two dmesg logs, and I see that the "with MSI" log also has the
> > "single" parameter, so it will only boot to single-user mode.
> 
> It does it mean than either the boot stop or the system halt, power-off
> before it can be possible to connect tty console or display manager.

Wow.  I'm not sure what would cause a sudden halt or power-off like
that.  Is there any indication on the console when this happens?  Can
you try adding the following to your kernel boot parameters to see if
you can catch anything via a photo or video (you may have to adjust
the boot_delay to make things readable):

  nosmp ignore_loglevel lpj=lpj=7000000 boot_delay=100

> Attach with this message the bootmsi log without the single option.

Thanks for the log!  I don't see many interesting differences.

  - Command line: BOOT_IMAGE=/boot/vmlinuz-6.1.0-5-amd64 root=UUID=ad672b5b-e68c-4aaf-8bde-113269cba2d8 ro
  + Command line: BOOT_IMAGE=/boot/vmlinuz-6.1.0-5-amd64 root=UUID=ad672b5b-e68c-4aaf-8bde-113269cba2d8 ro pci=nomsi quiet
  - acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI HPX-Type3]
  + acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments HPX-Type3]
  - acpi PNP0A03:00: _OSC: OS now controls [PCIeHotplug AER PCIeCapability]
  + acpi PNP0A03:00: _OSC: not requesting OS control; OS requires [ExtendedConfig ASPM ClockPM MSI]

As expected when Linux is not using MSI.

  + pci 0000:00:0d.0: proprietary Ricoh MMC controller disabled (via FireWire function)
  + pci 0000:00:0d.0: MMC cards are now supported by standard SDHCI controller

Peculiar.

  - pcieport 0000:00:07.0: pciehp: Slot #0 AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug+ Surprise+ Interlock- NoCompl- IbPresDis- LLActRep-

As expected when Linux is not using AER, pciehp, etc.

I'm curious about the Ricoh thing because I don't see an obvious MSI
connection.  Can you collect the output of "sudo lspci -vv"?  The
lspci output in your initial email wasn't collected as root, so it
doesn't include information about Capabilities (including MSI).

Bjorn

Re: The MSI Driver Guide HOWTO

[Bjorn Helgaas]

On Fri, Mar 10, 2023 at 3:32 PM <gael.seibert@gmx.fr> wrote:
> On 10/03/2023 19:41:02, Bjorn Helgaas wrote:
> > On Fri, Mar 10, 2023 at 11:23:14AM +0100, gael.seibert@gmx.fr wrote:
> > > On 09/03/2023 23:55:03, Bjorn Helgaas wrote:
> > > > On Thu, Mar 09, 2023 at 10:57:51AM +0100, rec wrote:
> > > > > On 09/03/2023 00:03:04, Bjorn Helgaas wrote:
> > > > > > On Tue, Mar 07, 2023 at 12:22:44PM +0100, rec wrote:
> > > > > > > Like asked in :
> > https://www.kernel.org/doc/html/latest/PCI/msi-howto.html#disabling-msis-globally
> > > > >
> > > > > > Thanks for the report!  I assume this means your system has
> > problems
> > > > > > with MSIs, and booting with "pci=nomsi" makes it work better?
> > > > >
> > > > > You are welcome,
> > > > > The system doesn't boot completely without the "pci=nomsi"
> > option.
> > > >
> > > > What exactly do you mean by "it doesn't boot completely"?  I
> > compared
> > > > the two dmesg logs, and I see that the "with MSI" log also has the
> > > > "single" parameter, so it will only boot to single-user mode.
> > >
> > > It does it mean than either the boot stop or the system halt,
> > power-off
> > > before it can be possible to connect tty console or display manager.
> >
> > Wow.  I'm not sure what would cause a sudden halt or power-off like
> > that.  Is there any indication on the console when this happens?  Can
> > you try adding the following to your kernel boot parameters to see if
> > you can catch anything via a photo or video (you may have to adjust
> > the boot_delay to make things readable):
> >
> >   nosmp ignore_loglevel lpj=lpj=7000000 boot_delay=100
>
> It will be possible that is a fan problem with a cpu temperature.
> (Probably)
> I attach a video to the boot.

Thanks for this.  I should have asked at the very beginning whether
there are any older kernels that work correctly without "pci=nomsi".
If there is such an older kernel, we can try to figure out what change
broke it.  Otherwise, I'm running out of ideas.

> > I'm curious about the Ricoh thing because I don't see an obvious MSI
> > connection.  Can you collect the output of "sudo lspci -vv"?  The
> > lspci output in your initial email wasn't collected as root, so it
> > doesn't include information about Capabilities (including MSI).
>
> Output of #lspci --vv attached

Thanks!  I was hoping something from lspci would connect with
ricoh_mmc_fixup_rl5c476(), where we get the "proprietary Ricoh MMC
controller" message, e.g., if that function looked at the MSI
Capability or something.  But 00:0d has four functions and none of
them has an MSI Capability.  And 00:0d.0 has nothing we know about at
the offsets the function uses:

  00:0d.0 FireWire (IEEE 1394): Ricoh Co Ltd R5C832
    Capabilities: [dc] Power Management version 2

Bjorn