From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
X86 ML <x86@kernel.org>, Mike Rapoport <rppt@kernel.org>
Subject: Re: linux-next: Tree for Apr 9 (x86 boot problem)
Date: Sun, 11 Apr 2021 19:41:37 -0700 [thread overview]
Message-ID: <f67d3e03-af90-f790-baf4-8d412fe055af@infradead.org> (raw)
In-Reply-To: <20210409215103.03999588@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 3295 bytes --]
On 4/9/21 4:51 AM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20210408:
>
Hi,
I cannot boot linux-next 20210408 nor 20210409 on an antique
x86_64 laptop (Toshiba Portege).
After many failed tests, I finally resorted to git bisect,
which led me to:
git bisect start
# good: [e49d033bddf5b565044e2abe4241353959bc9120] Linux 5.12-rc6
git bisect good e49d033bddf5b565044e2abe4241353959bc9120
# bad: [e99d8a8495175df8cb8b739f8cf9b0fc9d0cd3b5] Add linux-next specific files for 20210409
git bisect bad e99d8a8495175df8cb8b739f8cf9b0fc9d0cd3b5
# good: [24c5f79572740c1744a7ec2e9e21b541acab6de3] Merge remote-tracking branch 'crypto/master'
git bisect good 24c5f79572740c1744a7ec2e9e21b541acab6de3
# bad: [4b90473874c7b6af320b9815f82ac305fd8807f7] Merge remote-tracking branch 'ftrace/for-next'
git bisect bad 4b90473874c7b6af320b9815f82ac305fd8807f7
# good: [9cf3382276b26848891c7e072db0a774fadd10e4] Merge remote-tracking branch 'sound/for-next'
git bisect good 9cf3382276b26848891c7e072db0a774fadd10e4
# good: [f8d16164c586548d7ccedc058ca9ae547e0cebbe] Merge remote-tracking branch 'mmc/next'
git bisect good f8d16164c586548d7ccedc058ca9ae547e0cebbe
# good: [761ab817c8710fd601d90bfc5179b0f83b1424bb] Merge remote-tracking branch 'devicetree/for-next'
git bisect good 761ab817c8710fd601d90bfc5179b0f83b1424bb
# bad: [9ed0086faca0aefcc429a219ab1bd80654093937] Merge branch 'objtool/core'
git bisect bad 9ed0086faca0aefcc429a219ab1bd80654093937
# good: [4abeb983d38461f36b0aefa909d8b420c60b05be] Merge branch 'x86/core'
git bisect good 4abeb983d38461f36b0aefa909d8b420c60b05be
# bad: [6842a3ece3b7c0d558b6664dd6bf19b9ec4fc526] Merge branch 'timers/core'
git bisect bad 6842a3ece3b7c0d558b6664dd6bf19b9ec4fc526
# bad: [5247390b761f1f9e255a59123ffab302a83a581b] Merge branch 'x86/boot'
git bisect bad 5247390b761f1f9e255a59123ffab302a83a581b
# good: [7dfe553affd0d003c7535b7ba60d09193471ea9d] x86/syscalls: Fix -Wmissing-prototypes warnings from COND_SYSCALL()
git bisect good 7dfe553affd0d003c7535b7ba60d09193471ea9d
# good: [fda215642945f0b128e91c24c9b90c567f008887] Merge branch 'x86/build'
git bisect good fda215642945f0b128e91c24c9b90c567f008887
# good: [e14cfb3bdd0f82147d09e9f46bedda6302f28ee1] x86/boot/compressed: Avoid gcc-11 -Wstringop-overread warning
git bisect good e14cfb3bdd0f82147d09e9f46bedda6302f28ee1
# bad: [4c674481dcf9974834b96622fa4b079c176f36f9] x86/setup: Merge several reservations of start of memory
git bisect bad 4c674481dcf9974834b96622fa4b079c176f36f9
I reverted both of these patches and the laptop boots successfully:
commit a799c2bd29d19c565f37fa038b31a0a1d44d0e4d
Author: Mike Rapoport <rppt@kernel.org>
Date: Tue Mar 2 12:04:05 2021 +0200
x86/setup: Consolidate early memory reservations
&&
commit 4c674481dcf9974834b96622fa4b079c176f36f9
Author: Mike Rapoport <rppt@kernel.org>
Date: Tue Mar 2 12:04:06 2021 +0200
x86/setup: Merge several reservations of start of memory
There is no (zero, nil) console display when I try to boot
next 0408 or 0409. I connected a USB serial debug cable and
booted with earlyprintk=dbgp,keep and still got nothing.
The attached boot log is linux-next 20210409 minus the 2 patches
listed above.
Mike- what data would you like to see?
--
~Randy
Reported-by: Randy Dunlap <rdunlap@infradead.org>
[-- Attachment #2: boot0409-2.log.gz --]
[-- Type: application/gzip, Size: 46180 bytes --]
next prev parent reply other threads:[~2021-04-12 2:41 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 ` Randy Dunlap [this message]
2021-04-12 6:14 ` linux-next: Tree for Apr 9 (x86 boot problem) 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
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=f67d3e03-af90-f790-baf4-8d412fe055af@infradead.org \
--to=rdunlap@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rppt@kernel.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).