Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Jonathan Woithe <jwoithe@just42.net>
To: Igor Mammedov <imammedo@redhat.com>
Cc: bhelgaas@google.com, linux-pci@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [Regression] Commit 40613da52b13 ("PCI: acpiphp: Reassign resources on bridge if necessary")
Date: Thu, 21 Dec 2023 16:46:02 +1030	[thread overview]
Message-ID: <ZYPYIpO36YE8V8hQ@marvin.atrad.com.au> (raw)
In-Reply-To: <ZXziuPCKNBLhbssO@marvin.atrad.com.au>

On Sat, Dec 16, 2023 at 10:05:22AM +1030, Jonathan Woithe wrote:
> On Fri, Dec 15, 2023 at 02:36:38PM +0100, Igor Mammedov wrote:
> > On Fri, 15 Dec 2023 21:57:43 +1030
> > Jonathan Woithe <jwoithe@just42.net> wrote:
> > > As mentioned, testing another kernel can only happen next Thursday.  If
> > > you would like other tests done let me know and I'll do them at the same
> > > time.  I have remote access to the machine, so it's possible to retrieve
> > > information from it at any time.
> > 
> > lets wait till you can get logs with dyndbg='...' (I've asked for earlier)
> > and one more test with "pci=realloc" on kernel CLI to see if that helps.
> 
> Okay.

I added the "dyndbg=" option to the 5.15.139 kernel command line and booted. 
The resulting dmesg output has been attached to bugzilla 218268.

I also tested 5.15.139 with the "pci=realloc" kernel parameter.  This was
sufficient to allow the system to boot without a GPU initialisation failure.
The dmesg output from this boot has also been attached to bugzilla 218268.

I used kernel.org's 5.15.139 for these tests because I already had it
compiled and was a little short of time.  If you'd like me to repeat the
tests with a different kernel let me know which one and I'll see what I can
do.  The Christmas break may delay this somewhat.

Regards
  jonathan

  reply	other threads:[~2023-12-21  6:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-14  1:28 [Regression] Commit 40613da52b13 ("PCI: acpiphp: Reassign resources on bridge if necessary") Jonathan Woithe
2023-12-14 13:32 ` Igor Mammedov
2023-12-14 22:13   ` Jonathan Woithe
2023-12-15  9:29     ` Igor Mammedov
2023-12-15 11:27     ` Jonathan Woithe
2023-12-15 13:36       ` Igor Mammedov
2023-12-15 23:35         ` Jonathan Woithe
2023-12-21  6:16           ` Jonathan Woithe [this message]
2024-01-03  9:04             ` Igor Mammedov

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=ZYPYIpO36YE8V8hQ@marvin.atrad.com.au \
    --to=jwoithe@just42.net \
    --cc=bhelgaas@google.com \
    --cc=imammedo@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --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