From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: Stan Johnson <userm57@yahoo.com>
Cc: Debian PowerPC <debian-powerpc@lists.debian.org>,
linuxppc-dev@lists.ozlabs.org, Finn Thain <fthain@linux-m68k.org>
Subject: Re: Debian SID kernel doesn't boot on PowerBook 3400c
Date: Mon, 2 Aug 2021 16:41:41 +0200 [thread overview]
Message-ID: <fbd08736-9738-35cf-3b47-b5c9c455c552@csgroup.eu> (raw)
In-Reply-To: <cd7c931c-a578-a2ff-0632-7767a0e90bb9@yahoo.com>
Le 31/07/2021 à 20:24, Stan Johnson a écrit :
> Hi Christophe,
>
> On 7/31/21 9:58 AM, Christophe Leroy wrote:
>> Stan Johnson <userm57@yahoo.com> a écrit :
>>
>>> Hello,
>>>
>>> The current Debian SID kernel will not boot on a PowerBook 3400c running
>>> the latest version of Debian SID. If booted using the BootX extension,
>>> the kernel hangs immediately:
>>>
>>> "Welcome to Linux, kernel 5.10.0-8-powerpc"
>>>
>>> If booted from Mac OS, the Mac OS screen hangs.
>>>
>>> Booting also hangs if the "No video driver" option is selected in BootX,
>>> "No video driver" causes "video=ofonly" to be passed to the kernel.
>>>
>>> This is the current command line that I'm using in BootX:
>>> root=/dev/sda13 video=chips65550:vmode:14,cmode:16
>>>
>>> Kernel v5.9 works as expected.
>>>
>>> The config file I'm using is attached.
>>>
>>> Here are the results of a git bisect, marking v5.9 as "good" and the
>>> most current kernel as "bad":
>>>
>>> $ cd linux
>>> $ git remote update
>>> $ git bisect reset
>>> $ git bisect start
>>> $ git bisect bad
>>> $ git bisect good v5.9
>>>
>>> Note: "bad" -> hangs at boot; "good" -> boots to login prompt
>>>
>>> 1) 5.11.0-rc5-pmac-00034-g684da7628d9 (bad)
>>> 2) 5.10.0-rc3-pmac-00383-gbb9dd3ce617 (good)
>>> 3) 5.10.0-pmac-06637-g2911ed9f47b (good)
>>> Note: I had to disable SMP to build this kernel.
>>> 4) 5.10.0-pmac-10584-g9805529ec54 (good)
>>> Note: I had to disable SMP to build this kernel.
>>> 5) 5.10.0-pmac-12577-g8552d28e140 (bad)
>>> 6) 5.10.0-pmac-11576-g8a5be36b930 (bad)
>>> 7) 5.10.0-pmac-11044-gbe695ee29e8 (good)
>>> Note: I had to disable SMP to build this kernel.
>>> 8) 5.10.0-rc2-pmac-00288-g59d512e4374 (bad)
>>> 9) 5.10.0-rc2-pmac-00155-gc3d35ddd1ec (good)
>>> 10) 5.10.0-rc2-pmac-00221-g7049b288ea8 (good)
>>> 11) 5.10.0-rc2-pmac-00254-g4b74a35fc7e (bad)
>>> 12) 5.10.0-rc2-pmac-00237-ged22bb8d39f (good)
>>> 13) 5.10.0-rc2-pmac-00245-g87b57ea7e10 (good)
>>> 14) 5.10.0-rc2-pmac-00249-gf10881a46f8 (bad)
>>> 15) 5.10.0-rc2-pmac-00247-gf8a4b277c3c (good)
>>> 16) 5.10.0-rc2-pmac-00248-gdb972a3787d (bad)
>>>
>>> db972a3787d12b1ce9ba7a31ec376d8a79e04c47 is the first bad commit
>>
>> Not sure this is really the root of the problem.
>>
>> Can you try again without CONFIG_VMAP_STACK ?
>>
>> Thanks
>> Christophe
>> ...
>
>
> With CONFIG_VMAP_STACK=y, 5.11.0-rc5-pmac-00034-g684da7628d9 hangs at
> boot on the PB 3400c.
>
> Without CONFIG_VMAP_STACK, 5.11.0-rc5-pmac-00034-g684da7628d9 boots as
> expected.
>
> I didn't re-build the Debian SID kernel, though I confirmed that the
> Debian config file for 5.10.0-8-powerpc includes CONFIG_VMAP_STACK=y.
> It's not clear whether removing CONFIG_VMAP_STACK would be appropriate
> for other powerpc systems.
>
> Please let me know why removing CONFIG_VMAP_STACK fixed the problem on
> the PB 3400c. Should CONFIG_HAVE_ARCH_VMAP_STACK also be removed?
>
When CONFIG_HAVE_ARCH_VMAP_STACK is selected by the architecture, CONFIG_VMAP_STACK is selected by
default.
The point is that your config has CONFIG_ADB_PMU.
A bug with VMAP stack was detected during 5.9 release cycle for platforms selecting CONFIG_ADB_PMU.
Because fixing the bug was an heavy change, we prefered at that time to disable VMAP stack, so VMAP
stack was deselected for CONFIG_ADB_PMU by commit 4a133eb351ccc275683ad49305d0b04dde903733.
Then as a second step, the proper fix was implemented and then VMAP stack was enabled again by the
commit you bisected.
Taking into account that the problem disappears for you when you manually deselect VMAP stacks, it
means the problem is not the fix itself, but the fact that VMAP stacks are now enable by default.
We need to understand why VMAP stack doesn't work on your platform, more than that why it doesn't
boot at all with VMAP stack.
Could you send me the dmesg output of your system when it properly boots ?
Did you check with kernel 5.13 ?
Thanks
Christophe
next prev parent reply other threads:[~2021-08-02 14:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <60841a75-ed7c-8789-15db-272bf43055f5.ref@yahoo.com>
[not found] ` <60841a75-ed7c-8789-15db-272bf43055f5@yahoo.com>
2021-07-31 15:58 ` Debian SID kernel doesn't boot on PowerBook 3400c Christophe Leroy
2021-07-31 18:24 ` Stan Johnson
2021-08-02 14:41 ` Christophe Leroy [this message]
2021-08-02 17:32 ` Stan Johnson
2021-08-03 10:08 ` Christophe Leroy
2021-08-03 22:20 ` Stan Johnson
2021-08-04 0:02 ` Finn Thain
2021-08-04 0:34 ` Finn Thain
2021-08-04 6:28 ` Christophe Leroy
[not found] ` <f6a3746e-80ef-a6b3-925a-69aed01ba98c@linux-m68k.org>
[not found] ` <b6fe0c8e-8af5-e0e9-629b-fce61750ec2e@yahoo.com>
[not found] ` <4ac28304-4519-fb8a-a868-e8c79cb5f9e4@yahoo.com>
[not found] ` <7532219a-4fd0-416-6365-304033fa6abd@linux-m68k.org>
[not found] ` <9659419d-da9e-5aa6-ffbb-758748e2d6e9@linux-m68k.org>
[not found] ` <2eb2b452-51d5-c495-3ffe-896c62a1633f@yahoo.com>
[not found] ` <da9c16b4-70bc-6fe0-ad5c-8b226ca08b23@yahoo.com>
[not found] ` <cc5a203f-9df5-a0b-a4d7-bcaddde777d5@linux-m68k.org>
[not found] ` <6ea50cd7-84d3-5180-0430-1211aaf0e308@yahoo.com>
2021-08-06 1:06 ` Finn Thain
2021-08-06 6:09 ` Christophe Leroy
2021-08-06 9:43 ` Finn Thain
2021-08-06 9:58 ` Christophe Leroy
2021-08-07 2:05 ` Finn Thain
[not found] ` <06ddf5ab-b0c9-1c64-92ea-a9cfbfb9f3b0@yahoo.com>
2021-08-07 4:08 ` Finn Thain
2021-08-07 13:09 ` Stan Johnson
2021-08-07 14:35 ` Christophe Leroy
2021-08-07 16:26 ` Stan Johnson
2021-08-07 17:08 ` Christophe Leroy
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=fbd08736-9738-35cf-3b47-b5c9c455c552@csgroup.eu \
--to=christophe.leroy@csgroup.eu \
--cc=debian-powerpc@lists.debian.org \
--cc=fthain@linux-m68k.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=userm57@yahoo.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).