From: Igor Mammedov <imammedo@redhat.com>
To: Fiona Ebner <f.ebner@proxmox.com>
Cc: Bjorn Helgaas <helgaas@kernel.org>,
linux-pci@vger.kernel.org, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org, bhelgaas@google.com,
lenb@kernel.org, rafael@kernel.org,
Thomas Lamprecht <t.lamprecht@proxmox.com>,
mst@redhat.com
Subject: Re: SCSI hotplug issues with UEFI VM with guest kernel >= 6.5
Date: Tue, 12 Dec 2023 16:25:29 +0100 [thread overview]
Message-ID: <20231212162529.09c27fdf@imammedo.users.ipa.redhat.com> (raw)
In-Reply-To: <62363899-d7aa-4f1c-abfa-1f87f0b6b43f@proxmox.com>
On Tue, 12 Dec 2023 13:50:20 +0100
Fiona Ebner <f.ebner@proxmox.com> wrote:
> Am 12.12.23 um 12:26 schrieb Igor Mammedov:
> >
> > it's not necessary, but it would help to find out what's going wrong faster.
> > Otherwise we would need to fallback to debugging over email.
> > Are you willing to help with testing/providing debug logs to track down
> > the cause?.
> >
>
> I submitted the dmesg logs in bugzilla:
> https://bugzilla.kernel.org/show_bug.cgi?id=218255
>
> > Though debug over email would be slow, so our best option is to revert
> > offending patches until the cause if found/fixed.
> >
> >>>>> Do you have to revert both cc22522fd55e2 and 40613da52b13f to make it
> >>>>> work reliably? If we have to revert something, reverting one would be
> >>>>> better than reverting both.
> >>>>
> >>
> >> Just reverting cc22522fd55e2 is not enough (and cc22522fd55e2 fixes
> >> 40613da52b13f so I can't revert just 40613da52b13f).
> >
> > With UEFI setup, it still works for me fine with current master.
> >
> > Kernel 6.7.0-rc5-00014-g26aff849438c on an x86_64 (ttyS0)
> >
>
> I also built from current master (still 26aff849438c) to verify and it's
> still broken for me.
>
> >
> > it still doesn't work with Fedora's 6.7.0-0.rc2.20231125git0f5cc96c367f.26.fc40.x86_64 kernel.
> > However it's necessary to have -smp 4 for it to break,
> > with -smp 1 it works fine as well.
> >
>
> For me it's (always with build from current master):
>
> -smp 1 -> it worked 5 times out of 5
> -smp 2 -> it worked 3 times out of 5
> -smp 4 -> it worked 0 times out of 5
> -smp 8 -> it worked 0 times out of 5
I managed to reproduce it with upstream using fedora 40 config as is
(without converting it to mod2yesconfig).
So give me a couple of days to debug it before reverting.
>
> Best Regards,
> Fiona
>
next prev parent reply other threads:[~2023-12-12 15:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-29 15:22 SCSI hotplug issues with UEFI VM with guest kernel >= 6.5 Fiona Ebner
2023-11-30 23:18 ` Bjorn Helgaas
2023-12-01 9:24 ` Fiona Ebner
2023-12-07 14:55 ` Igor Mammedov
2023-12-07 23:28 ` Bjorn Helgaas
2023-12-08 15:47 ` Igor Mammedov
2023-12-11 7:46 ` Igor Mammedov
2023-12-11 13:52 ` Fiona Ebner
2023-12-11 14:12 ` Bjorn Helgaas
2023-12-11 14:53 ` Fiona Ebner
2023-12-11 16:18 ` Bjorn Helgaas
2023-12-12 9:40 ` Fiona Ebner
2023-12-12 11:26 ` Igor Mammedov
2023-12-12 12:50 ` Fiona Ebner
2023-12-12 15:25 ` Igor Mammedov [this message]
2023-12-12 20:02 ` Igor Mammedov
2023-12-15 7:41 ` 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=20231212162529.09c27fdf@imammedo.users.ipa.redhat.com \
--to=imammedo@redhat.com \
--cc=bhelgaas@google.com \
--cc=f.ebner@proxmox.com \
--cc=helgaas@kernel.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mst@redhat.com \
--cc=rafael@kernel.org \
--cc=t.lamprecht@proxmox.com \
/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;
as well as URLs for NNTP newsgroup(s).