From: Bjorn Helgaas <helgaas@kernel.org>
To: gael.seibert@gmx.fr
Cc: linux-pci@vger.kernel.org
Subject: Re: The MSI Driver Guide HOWTO
Date: Fri, 10 Mar 2023 12:41:02 -0600 [thread overview]
Message-ID: <20230310184102.GA1267642@bhelgaas> (raw)
In-Reply-To: <SN44ZY2G.XQXJA4JD.P37YMNSZ@LGXWN7Q2.OD5XUULU.2REDJUZ5>
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
next prev parent reply other threads:[~2023-03-10 18:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-07 11:22 The MSI Driver Guide HOWTO rec
2023-03-08 23:03 ` Bjorn Helgaas
2023-03-09 9:57 ` rec
2023-03-09 22:55 ` Bjorn Helgaas
2023-03-10 10:23 ` gael.seibert
2023-03-10 18:41 ` Bjorn Helgaas [this message]
[not found] ` <JVFJQDZS.Q55VEGY3.FOVANOEZ@FBOHK6ZC.GEUI7GR4.PNS4DLI2>
2023-03-10 22:25 ` Bjorn Helgaas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230310184102.GA1267642@bhelgaas \
--to=helgaas@kernel.org \
--cc=gael.seibert@gmx.fr \
--cc=linux-pci@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox