From: Mike Rapoport <rppt@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
X86 ML <x86@kernel.org>
Subject: Re: linux-next: Tree for Apr 9 (x86 boot problem)
Date: Tue, 13 Apr 2021 09:06:20 +0300 [thread overview]
Message-ID: <YHU03AIwrpHCUlU/@kernel.org> (raw)
In-Reply-To: <d56ebb95-1c40-5994-383f-70d8f226e8c3@infradead.org>
Hi Randy,
On Mon, Apr 12, 2021 at 01:53:34PM -0700, Randy Dunlap wrote:
> On 4/12/21 10:01 AM, Mike Rapoport wrote:
> > On Mon, Apr 12, 2021 at 08:49:49AM -0700, Randy Dunlap wrote:
> >
> > I thought about adding some prints to see what's causing the hang, the
> > reservations or their absence. Can you replace the debug patch with this
> > one:
> >
> > diff --git a/arch/x86/kernel/setup.c b/arch/x86/kernel/setup.c
> > index 776fc9b3fafe..a10ac252dbcc 100644
> > --- a/arch/x86/kernel/setup.c
> > +++ b/arch/x86/kernel/setup.c
> > @@ -600,10 +600,13 @@ static bool __init snb_gfx_workaround_needed(void)
> > return false;
> >
> > vendor = read_pci_config_16(0, 2, 0, PCI_VENDOR_ID);
> > + devid = read_pci_config_16(0, 2, 0, PCI_DEVICE_ID);
> > +
> > + pr_info("%s: vendor: %x, device: %x\n", __func__, vendor, device);
>
> s/device)/devid)/
Oh, sorry.
> > +
> > if (vendor != 0x8086)
> > return false;
> >
> > - devid = read_pci_config_16(0, 2, 0, PCI_DEVICE_ID);
> > for (i = 0; i < ARRAY_SIZE(snb_ids); i++)
> > if (devid == snb_ids[i])
> > return true;
>
> That prints:
>
> [ 0.000000] snb_gfx_workaround_needed: vendor: 8086, device: 126
> [ 0.000000] early_reserve_memory: snb_gfx: 1
> ...
> [ 0.014061] snb_gfx_workaround_needed: vendor: 8086, device: 126
> [ 0.014064] reserving inaccessible SNB gfx pages
>
>
> The full boot log is attached.
Can you please send the log with memblock=debug added to the kernel command
line?
Probably should have started from this...
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2021-04-13 6:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-09 11:51 linux-next: Tree for Apr 9 Stephen Rothwell
2021-04-10 23:50 ` linux-next: Tree for Apr 9 (drivers/iommu/intel/pasid.c) Randy Dunlap
2021-04-12 2:41 ` linux-next: Tree for Apr 9 (x86 boot problem) Randy Dunlap
2021-04-12 6:14 ` Mike Rapoport
2021-04-12 15:49 ` Randy Dunlap
2021-04-12 17:01 ` Mike Rapoport
2021-04-12 20:53 ` Randy Dunlap
2021-04-13 6:06 ` Mike Rapoport [this message]
2021-04-13 6:21 ` Randy Dunlap
2021-04-13 16:58 ` Mike Rapoport
2021-04-13 17:34 ` Randy Dunlap
2021-04-13 18:23 ` Mike Rapoport
2021-04-13 19:07 ` Randy Dunlap
2021-04-13 19:09 ` Hugh Dickins
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=YHU03AIwrpHCUlU/@kernel.org \
--to=rppt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
--cc=x86@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;
as well as URLs for NNTP newsgroup(s).