From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: Jiri Slaby <jirislaby@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] firewire updates for 6.5-rc1
Date: Tue, 17 Oct 2023 00:56:57 +0900 [thread overview]
Message-ID: <20231016155657.GA7904@workstation.local> (raw)
In-Reply-To: <13363c8e-22ec-48de-a471-91535ad1249f@kernel.org>
Hi Jiri,
I purchased 1394 OHCI hardware quite similar to the issued hardware
(VIA VT6307 + Asmedia ASM1083), then experienced that it causes the
issue in AMD chipset, but it does not in Intel chipset.
I use below machines:
* AMD Ryzen 5 2400G in Gigabyte AX370-Gaming 5 rev.1.0 (Bios version F51h) [1]
* Intel Core i3-2120T in Intel DH77DF (Bios version 0112) [2]
As long as seeing filed issues, the reporters use AMD chipset.
AMD Ryzen 5 3400G, MSI B450-A Pro: https://bugzilla.suse.com/show_bug.cgi?id=1215436
AMD Ryzen 7 3700X, MSI X570-A Pro: https://bugzilla.redhat.com/show_bug.cgi?id=2240973
Furthermore, I experienced that:
* guest machine can cause host reboot in Ryzen machine even if the 1394
OHCI hardware is passed-through to the guest by vfio-pci (and
firewire-ohci is loaded in the guest machine side)
* execution of lspci(8) in the host can cause the reboot when the hardware
is associated to vfio-pci (thus firewire-ohci is not loaded in the case).
This issue is in Ubuntu 23.04 (v6.2 kernel).
At present, I suspect either or both iommu function and kernel
implementation.
For further investigation, I would like you to give some instructions
about the way to use OpenSUSE distribution. I want to boot the distribution
in 'low graphics mode' which debian/ubuntu distribution has. In the mode,
I expect to boot it without loading amdgpu module which depends on iommuv2
module.
Anyway, I would like you to check reporters' chipset when the similar
issues are reported. If they encounter the issue still in Intel chipset,
please inform it to me, since it could deny my current presumption.
[1] https://www.gigabyte.com/Motherboard/GA-AX370-Gaming-5-rev-10#kf
[2] https://www.intel.com/content/www/us/en/products/sku/59503/intel-desktop-board-dh77df/specifications.html
Thanks
Takashi Sakamoto
next prev parent reply other threads:[~2023-10-16 15:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-04 12:18 [GIT PULL] firewire updates for 6.5-rc1 Takashi Sakamoto
2023-07-04 18:38 ` pr-tracker-bot
2023-09-26 9:11 ` Jiri Slaby
2023-09-26 14:09 ` Takashi Sakamoto
2023-09-27 5:03 ` Jiri Slaby
2023-10-01 5:15 ` Takashi Sakamoto
2023-10-02 10:42 ` Jiri Slaby
2023-10-04 0:24 ` Takashi Sakamoto
2023-10-04 8:33 ` Jiri Slaby
2023-10-16 15:56 ` Takashi Sakamoto [this message]
2023-10-17 7:36 ` Jiri Slaby
2023-09-27 13:15 ` Linux regression tracking #adding (Thorsten Leemhuis)
2024-01-21 10:04 ` Linux regression tracking #update (Thorsten Leemhuis)
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=20231016155657.GA7904@workstation.local \
--to=o-takashi@sakamocchi.jp \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@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