Re: Debian SID kernel doesn't boot on PowerBook 3400c

Re: Debian SID kernel doesn't boot on PowerBook 3400c

[Christophe Leroy]

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


> commit db972a3787d12b1ce9ba7a31ec376d8a79e04c47
> Author: Christophe Leroy <christophe.leroy@csgroup.eu>
> Date:   Tue Dec 8 05:24:19 2020 +0000
>
>     powerpc/powermac: Fix low_sleep_handler with CONFIG_VMAP_STACK
>
>     low_sleep_handler() can't restore the context from standard
>     stack because the stack can hardly be accessed with MMU OFF.
>
>     Store everything in a global storage area instead of storing
>     a pointer to the stack in that global storage area.
>
>     To avoid a complete churn of the function, still use r1 as
>     the pointer to the storage area during restore.
>
>     Fixes: cd08f109e262 ("powerpc/32s: Enable CONFIG_VMAP_STACK")
>     Reported-by: Giuseppe Sacco <giuseppe@sguazz.it>
>     Signed-off-by: Christophe Leroy <christophe.leroy@csgroup.eu>
>     Tested-by: Giuseppe Sacco <giuseppe@sguazz.it>
>     Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
>     Link:
> https://lore.kernel.org/r/e3e0d8042a3ba75cb4a9546c19c408b5b5b28994.1607404931.git.christophe.leroy@csgroup.eu
>
> :040000 040000 d5039513d19748fc13712a2c67ae034371b95fe7
> cbbdbdc4b05c713ea2577674260fd37e71306cc0 M	arch
>
> Please let me know if you need more information.
>
> -Stan Johnson

Re: Debian SID kernel doesn't boot on PowerBook 3400c

[Stan Johnson]

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?

thanks

-Stan Johnson

Re: Debian SID kernel doesn't boot on PowerBook 3400c

[Christophe Leroy]

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

Re: Debian SID kernel doesn't boot on PowerBook 3400c

[Stan Johnson]

[-- Attachment #1: Type: text/plain, Size: 5574 bytes --]

On 8/2/21 8:41 AM, Christophe Leroy wrote:
> 
> 
> 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
> 

Christophe,

Thanks for your response. It looks like I never tested v5.13 (I was
originally just reporting that the default Debian SID kernel,
5.10.0-8-powerpc, hangs at boot on the PB 3400c).

So I rebuilt the stock v5.13 from kernel.org using Finn's
dot-config-powermac-5.13, which got changed slightly at compilation (see
dot-config-v5.13-pmac, attached). It has CONFIG_VMAP_STACK and
CONFIG_ADB_PMU set, and it booted, but there were multiple memory
errors. So it looks like the hang-at-boot problem was fixed sometime
after v5.11, but there are now memory errors (similar to Wallstreet).

With CONFIG_VMAP_STACK not set (CONFIG_ADB_PMU is still set), the
.config file turns into the attached dot-config-v5.13-pmac_NO_VMAP. And
there were still memory errors (dmesg output attached).

The memory errors may be a completely unrelated issue, since they occur
regardless of the CONFIG_VMAP_STACK setting.

To help rule out a hardware issue, I confirmed that memory errors don't
occur with v5.8.2 (dmesg output attached).

A useful git bisect might be possible if CONFIG_VMAP_STACK is disabled
for each build. I would need to determine where the memory errors
started (v5.9, v5.10, v5.11, or v5.12). There is the complication that
(at least) several v5.10 kernels won't compile if SMP is set, so I might
need to disable that everywhere as well, assuming the SMP fix didn't
cause the memory errors.

-Stan

[-- Attachment #2: dot-config-v5.13-pmac.xz --]
[-- Type: application/octet-stream, Size: 17980 bytes --]

[-- Attachment #3: dot-config-v5.13-pmac_NO_VMAP.xz --]
[-- Type: application/octet-stream, Size: 17976 bytes --]

[-- Attachment #4: dmesg_5.13_VMAP.txt.xz --]
[-- Type: application/octet-stream, Size: 8700 bytes --]

[-- Attachment #5: dmesg_5.13_NO_VMAP.txt.xz --]
[-- Type: application/octet-stream, Size: 6656 bytes --]

[-- Attachment #6: dmesg_5.8.2.txt.xz --]
[-- Type: application/octet-stream, Size: 6096 bytes --]

Re: Debian SID kernel doesn't boot on PowerBook 3400c

[Christophe Leroy]

Le 02/08/2021 à 19:32, Stan Johnson a écrit :
> On 8/2/21 8:41 AM, Christophe Leroy wrote:
>>
>>
>> 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
>>
> 
> Christophe,
> 
> Thanks for your response. It looks like I never tested v5.13 (I was
> originally just reporting that the default Debian SID kernel,
> 5.10.0-8-powerpc, hangs at boot on the PB 3400c).
> 
> So I rebuilt the stock v5.13 from kernel.org using Finn's
> dot-config-powermac-5.13, which got changed slightly at compilation (see
> dot-config-v5.13-pmac, attached). It has CONFIG_VMAP_STACK and
> CONFIG_ADB_PMU set, and it booted, but there were multiple memory
> errors. So it looks like the hang-at-boot problem was fixed sometime
> after v5.11, but there are now memory errors (similar to Wallstreet).
> 
> With CONFIG_VMAP_STACK not set (CONFIG_ADB_PMU is still set), the
> .config file turns into the attached dot-config-v5.13-pmac_NO_VMAP. And
> there were still memory errors (dmesg output attached).
> 
> The memory errors may be a completely unrelated issue, since they occur
> regardless of the CONFIG_VMAP_STACK setting.
> 
> To help rule out a hardware issue, I confirmed that memory errors don't
> occur with v5.8.2 (dmesg output attached).
> 
> A useful git bisect might be possible if CONFIG_VMAP_STACK is disabled
> for each build. I would need to determine where the memory errors
> started (v5.9, v5.10, v5.11, or v5.12). There is the complication that
> (at least) several v5.10 kernels won't compile if SMP is set, so I might
> need to disable that everywhere as well, assuming the SMP fix didn't
> cause the memory errors.
> 

Thanks a lot for the information.

Looks like the memory errors are linked to KUAP (Kernel Userspace Access Protection). Based on the 
places the problems happen, I don't think there are any invalid access, so there must be something 
wrong in the KUAP logic, probably linked to some interrupts happenning in kernel mode while the KUAP 
window is opened. And because is not selected by default on book3s/32 until 5.14, probably nobody 
ever tested it in a real environment before you.

I think the issue may be linked to commit https://github.com/linuxppc/linux/commit/c16728835 which 
happened between 5.12 and 5.13. Would be nice if you could confirm that 5.12 doesn't have the 
problem (At the same time maybe you can see if 5.12 also boots OK with CONFIG_VMAP_STACK)

Note that the error detected in the other thread which is being discussed with Finn might also be an 
issue to be checked while we are here.

Thanks
Christophe

Re: Debian SID kernel doesn't boot on PowerBook 3400c

[Stan Johnson]

[-- Attachment #1: Type: text/plain, Size: 6284 bytes --]

On 8/3/21 4:08 AM, Christophe Leroy wrote:
> 
> 
> Le 02/08/2021 à 19:32, Stan Johnson a écrit :
>> On 8/2/21 8:41 AM, Christophe Leroy wrote:
>>>
>>> ...
>>>>>
>>>>> 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
>>>
>>
>> Christophe,
>>
>> Thanks for your response. It looks like I never tested v5.13 (I was
>> originally just reporting that the default Debian SID kernel,
>> 5.10.0-8-powerpc, hangs at boot on the PB 3400c).
>>
>> So I rebuilt the stock v5.13 from kernel.org using Finn's
>> dot-config-powermac-5.13, which got changed slightly at compilation (see
>> dot-config-v5.13-pmac, attached). It has CONFIG_VMAP_STACK and
>> CONFIG_ADB_PMU set, and it booted, but there were multiple memory
>> errors. So it looks like the hang-at-boot problem was fixed sometime
>> after v5.11, but there are now memory errors (similar to Wallstreet).
>>
>> With CONFIG_VMAP_STACK not set (CONFIG_ADB_PMU is still set), the
>> .config file turns into the attached dot-config-v5.13-pmac_NO_VMAP. And
>> there were still memory errors (dmesg output attached).
>>
>> The memory errors may be a completely unrelated issue, since they occur
>> regardless of the CONFIG_VMAP_STACK setting.
>>
>> To help rule out a hardware issue, I confirmed that memory errors don't
>> occur with v5.8.2 (dmesg output attached).
>>
>> A useful git bisect might be possible if CONFIG_VMAP_STACK is disabled
>> for each build. I would need to determine where the memory errors
>> started (v5.9, v5.10, v5.11, or v5.12). There is the complication that
>> (at least) several v5.10 kernels won't compile if SMP is set, so I might
>> need to disable that everywhere as well, assuming the SMP fix didn't
>> cause the memory errors.
>>
> 
> Thanks a lot for the information.
> 
> Looks like the memory errors are linked to KUAP (Kernel Userspace Access
> Protection). Based on the places the problems happen, I don't think
> there are any invalid access, so there must be something wrong in the
> KUAP logic, probably linked to some interrupts happenning in kernel mode
> while the KUAP window is opened. And because is not selected by default
> on book3s/32 until 5.14, probably nobody ever tested it in a real
> environment before you.
> 
> I think the issue may be linked to commit
> https://github.com/linuxppc/linux/commit/c16728835 which happened
> between 5.12 and 5.13. Would be nice if you could confirm that 5.12
> doesn't have the problem (At the same time maybe you can see if 5.12
> also boots OK with CONFIG_VMAP_STACK)

On the PB 3400c:
1) v5.12 with CONFIG_VMAP_STACK -- hangs at boot; see attached config.
2) v5.12 without CONFIG_VMAP_STACK -- did not hang at boot, but hung at
"Run /sbin/init as init process" (I tested it twice; there were no
errors logged); see attached config and serial console log.
3) v5.11 with CONFIG_VMAP_STACK -- hangs at boot, no output at serial
console (see attached config).
4) v5.11 without CONFIG_VMAP_STACK -- no errors (confirms earlier
result); see attached config and dmesg output.

The PB 3400C has a 240 MHz 603e and 144M memory. It's a text-only system
running Debian SID with sysvinit (X Windows and systemd would run too
slowly here).

Please note that the issue on the PB 3400c appears to be different than
the memory problem on the Wallstreet (I think Finn sent you some
Wallstreet dmesg outputs for the Wallstreet problem).

On the Wallstreet, with CONFIG_VMAP_STACK, X logins start to fail and
memory errors start happening somewhere around mem=464M (I've never seen
problems at <= 464M, but it's possible the memory errors are just more
likely to start happening somewhere >384M). With CONFIG_VMAP_STACK off,
X logins work on the Wallstreet and there are no memory errors with any
memory size <= 512M.

On the PB 3400c, there was the hang-at-boot problem that went away in
v5.11 with CONFIG_VMAP_STACK off. However, it appears a new issue may
have happened between v5.11 and v5.12 that causes v5.12 to hang at "Run
/sbin/init as init process" when CONFIG_VMAP_STACK is off (further
complicating any possible bisect).

> 
> Note that the error detected in the other thread which is being
> discussed with Finn might also be an issue to be checked while we are here.
> 

I'm not sure of the issue you are referencing. If it's the Wallstreet
issue, I believe we were waiting to hear back from you regarding the
memory errors that crop up with CONFIG_VMAP_STACK=y and mem >464M. Finn,
if that is not correct, please let me know.

thanks

-Stan

[-- Attachment #2: config-v5.12-pmac_VMAP.xz --]
[-- Type: application/octet-stream, Size: 17824 bytes --]

[-- Attachment #3: config-v5.12-pmac_NO_VMAP.xz --]
[-- Type: application/octet-stream, Size: 17832 bytes --]

[-- Attachment #4: serial_log_v5.12-NO_VMAP.txt.xz --]
[-- Type: application/octet-stream, Size: 4328 bytes --]

[-- Attachment #5: config-v5.11-pmac_VMAP.xz --]
[-- Type: application/octet-stream, Size: 17804 bytes --]

[-- Attachment #6: config-v5.11-pmac_NO_VMAP.xz --]
[-- Type: application/octet-stream, Size: 17828 bytes --]

[-- Attachment #7: dmesg-5.11.0-pmac-NO_VMAP.txt.xz --]
[-- Type: application/octet-stream, Size: 5736 bytes --]

Re: Debian SID kernel doesn't boot on PowerBook 3400c

[Finn Thain]

On Tue, 3 Aug 2021, Stan Johnson wrote:

> 
> I'm not sure of the issue you are referencing. If it's the Wallstreet 
> issue, I believe we were waiting to hear back from you regarding the 
> memory errors that crop up with CONFIG_VMAP_STACK=y and mem >464M. 
> Finn, if that is not correct, please let me know.
> 

No, it's not correct. I sent a message dated 3 Aug 2021 with a patch from 
Christophe. I also sent (privately) a message with instructions for 
testing that patch. I will resend these now.

Re: Debian SID kernel doesn't boot on PowerBook 3400c

[Finn Thain]

On Tue, 3 Aug 2021, Christophe Leroy wrote:

> 
> Looks like the memory errors are linked to KUAP (Kernel Userspace Access 
> Protection). Based on the places the problems happen, I don't think 
> there are any invalid access, so there must be something wrong in the 
> KUAP logic, probably linked to some interrupts happenning in kernel mode 
> while the KUAP window is opened. And because is not selected by default 
> on book3s/32 until 5.14, probably nobody ever tested it in a real 
> environment before you.
> 
> I think the issue may be linked to commit 
> https://github.com/linuxppc/linux/commit/c16728835 which happened 
> between 5.12 and 5.13.

The messages, "Kernel attempted to write user page (c6207c) - exploit 
attempt? (uid: 0)", appear in the console logs generated by v5.13. Those 
logs come from the Powerbook G3 discussion in the other thread. Could that 
be the same bug?

Re: Debian SID kernel doesn't boot on PowerBook 3400c

[Christophe Leroy]

Le 04/08/2021 à 02:34, Finn Thain a écrit :
> 
> On Tue, 3 Aug 2021, Christophe Leroy wrote:
> 
>>
>> Looks like the memory errors are linked to KUAP (Kernel Userspace Access
>> Protection). Based on the places the problems happen, I don't think
>> there are any invalid access, so there must be something wrong in the
>> KUAP logic, probably linked to some interrupts happenning in kernel mode
>> while the KUAP window is opened. And because is not selected by default
>> on book3s/32 until 5.14, probably nobody ever tested it in a real
>> environment before you.
>>
>> I think the issue may be linked to commit
>> https://github.com/linuxppc/linux/commit/c16728835 which happened
>> between 5.12 and 5.13.
> 
> The messages, "Kernel attempted to write user page (c6207c) - exploit
> attempt? (uid: 0)", appear in the console logs generated by v5.13. Those
> logs come from the Powerbook G3 discussion in the other thread. Could that
> be the same bug?
> 

Yes, most likely.

So you confirm this appears with 5.13 and not 5.12 ?

Can you check if they happen at commit c16728835
Can you check if they DO NOT happen at preceding commit c16728835~

Could you test without CONFIG_PPC_KUAP
Could you test with CONFIG_PPC_KUAP and CONFIG_PPC_KUAP_DEBUG

Thanks
Christophe

Re: Debian SID kernel doesn't boot on PowerBook 3400c

[Finn Thain]

[-- Attachment #1: Type: text/plain, Size: 6039 bytes --]

(Christophe, you've seen some of this before, however there are new 
results added at the end. I've Cc'd the mailing lists this time.)

On Wed, 4 Aug 2021, Stan Johnson wrote:

> On 8/4/21 8:41 PM, Finn Thain wrote:
> 
> >
> > $ curl https://lore.kernel.org/lkml/9b64dde3-6ebd-b446-41d9-61e8cb0d8c39@csgroup.eu/raw
> > ../message.mbox
> ok
> 
> $ sha1 ../message.mbox
> SHA1 (../message.mbox) = 436ce0adf893c46c84c54607f73c838897caeeea
> 
> >
> > On Wed, 4 Aug 2021, Christophe Leroy wrote:
> >
> >> Can you check if they happen at commit c16728835
> >>
> 
> $ git checkout c16728835eec
> Checking out files: 100% (20728/20728), done.
> Note: checking out 'c16728835eec'.
> 
> You are in 'detached HEAD' state. You can look around, make experimental
> changes and commit them, and you can discard any commits you make in this
> state without impacting any branches by performing another checkout.
> 
> If you want to create a new branch to retain commits you create, you may
> do so (now or later) by using -b with the checkout command again. Example:
> 
>   git checkout -b <new-branch-name>
> 
> HEAD is now at c16728835eec powerpc/32: Manage KUAP in C
> $ git am ../message.mbox
> warning: Patch sent with format=flowed; space at the end of lines might be lost.
> Applying: powerpc/32: Dismantle EXC_XFER_STD/LITE/TEMPLATE
> $ cp ../dot-config-powermac-5.13 .config
> $ make ARCH=powerpc CROSS_COMPILE=powerpc-linux-gnu- -j4 clean olddefconfig vmlinux
> $ strings vmlinux | fgrep 'Linux version'
> Linux version 5.12.0-rc3-pmac-00078-geb51c431b81 (johnson@ThinkPad) (powerpc-linux-gnu-gcc (Debian 8.3.0-2) 8.3.0, GNU ld (GNU Binutils for Debian) 2.31.1) #1 SMP Wed Aug 4 21:50:47 MDT 2021
> 
> 1) PB 3400c
> Hangs at boot (Mac OS screen), no serial console output
> 
> 2) Wallstreet
> X fails, errors ("Kernel attempted to write user page", "BUG: Unable to
> handle kernel instruction fetch"), see Wallstreet_console-1.txt.
> 

The log shows that the error "Kernel attempted to write user page 
(b3399774) - exploit attempt?" happens after commit c16728835eec 
("powerpc/32: Manage KUAP in C").

> >>
> >> Can you check if they DO NOT happen at preceding commit c16728835~
> >>
> 
> $ git checkout c16728835~
> Previous HEAD position was c16728835eec powerpc/32: Manage KUAP in C
> HEAD is now at 0b45359aa2df powerpc/8xx: Create C version of kuap save/restore/check helpers
> $ git am ../message.mbox
> warning: Patch sent with format=flowed; space at the end of lines might be lost.
> Applying: powerpc/32: Dismantle EXC_XFER_STD/LITE/TEMPLATE
> $ cp ../dot-config-powermac-5.13 .config
> $ make ARCH=powerpc CROSS_COMPILE=powerpc-linux-gnu- -j4 clean olddefconfig vmlinux
> 
> Linux version 5.12.0-rc3-pmac-00077-gc9f6e8dd045
> 
> 3) PB 3400c
> Hangs at boot (Mac OS screen)
> 
> 4) Wallstreet
> X fails, errors in console log (different than test 2), see
> Wallstreet_console-2.txt.
> 

This log shows that the errors "xfce4-session[1775]: bus error (7)" and 
"kernel BUG at arch/powerpc/kernel/interrupt.c:49!" happen prior to commit 
c16728835eec ("powerpc/32: Manage KUAP in C").

> 
> $ git checkout 0b45359aa2df
> ...
> HEAD is now at 0b45359aa2df powerpc/8xx: Create C version of kuap save/restore/check helpers
> $ git am ../message.mbox
> warning: Patch sent with format=flowed; space at the end of lines might be lost.
> Applying: powerpc/32: Dismantle EXC_XFER_STD/LITE/TEMPLATE
> $ cp ../dot-config-powermac-5.13 .config
> $ make ARCH=powerpc CROSS_COMPILE=powerpc-linux-gnu- -j4 clean olddefconfig vmlinux
> 
> Linux version 5.12.0-rc3-pmac-00077-ge06b29ce146
> 
> 5) PB 3400c
> Hangs at boot (Mac OS screen)
> 
> 6) Wallstreet
> X failed (X login succeeded, but setting up desktop failed), errors in
> console log, see Wallstreet_console-3.txt.
> 

(No need for those two tests: it's exactly the same code and almost the 
same failure modes: "kernel BUG at arch/powerpc/kernel/interrupt.c:50".)

On Thu, 5 Aug 2021, Stan Johnson wrote:

> On 8/5/21 12:47 AM, Finn Thain wrote:
> 
> > On Wed, 4 Aug 2021, Christophe Leroy wrote:
> >
> >> Could you test without CONFIG_PPC_KUAP
> ...
> 
> $ git checkout c16728835eec
> ...
> HEAD is now at c16728835eec powerpc/32: Manage KUAP in C
> $ git am ../message.mbox
> warning: Patch sent with format=flowed; space at the end of lines might be lost.
> Applying: powerpc/32: Dismantle EXC_XFER_STD/LITE/TEMPLATE
> $ cp ../dot-config-powermac-5.13 .config
> $ scripts/config -d CONFIG_PPC_KUAP
> $ make ARCH=powerpc CROSS_COMPILE=powerpc-linux-gnu- -j4 clean olddefconfig vmlinux
> $ grep CONFIG_PPC_KUAP .config
> # CONFIG_PPC_KUAP is not set
> 
> Linux version 5.12.0-rc3-pmac-00078-g5cac2bc3752
> 
> 7) PB 3400c
> Hangs at boot (Mac OS screen)
> 
> 8) Wallstreet
> Everything works, no errors (see Wallstreet_console-4.txt).
> 

That would seem to implicate CONFIG_PPC_KUAP itself. (Note that all builds 
up until this one have CONFIG_PPC_KUAP=y.)

> 
> >
> >> Could you test with CONFIG_PPC_KUAP and CONFIG_PPC_KUAP_DEBUG
> ...
> 
> $scripts/config -e CONFIG_PPC_KUAP
> $ scripts/config -e CONFIG_PPC_KUAP_DEBUG
> $ make ARCH=powerpc CROSS_COMPILE=powerpc-linux-gnu- -j4 clean olddefconfig vmlinux
> $ grep CONFIG_PPC_KUAP .config
> CONFIG_PPC_KUAP=y
> CONFIG_PPC_KUAP_DEBUG=y
> 
> Linux version 5.12.0-rc3-pmac-00078-g5cac2bc3752
> 
> 9) PB 3400c
> Hangs at boot (Mac OS screen)
> 
> 10) Wallstreet
> X failed at first login, worked at second login, one error in console
> log ("BUG: Unable to handle kernel instruction fetch"), see
> Wallstreet_console-5.txt.
> 

One might expect to see "Kernel attempted to write user page (b3399774) - 
exploit attempt?" again here (see c16728835eec build above) but instead 
this log says "Oops: Kernel access of bad area, sig: 11".

BTW, this procedure could be made simpler and easier if I pushed git 
branches to a public repo for Stan to build, which included Christophe's 
fix plus hard-wired Kconfig changes. That way, the .config file could be 
held constant and the commit hash in the serial console log would be more 
meaningful.

[-- Attachment #2: Type: text/plain, Size: 21560 bytes --]

printk: console [ttyS0] enabled
printk: bootconsole [udbg0] disabled
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
rcu: Hierarchical SRCU implementation.
smp: Bringing up secondary CPUs ...
smp: Brought up 1 node, 1 CPU
devtmpfs: initialized
Duplicate name in PowerPC,750, renamed to "l2-cache#1"
Duplicate name in pci, renamed to "mac-io#1"
Duplicate name in pci, renamed to "pccard#1"
Found Grackle (MPC106) PCI host bridge at 0x0000000080000000. Firmware bus number: 0->0
PCI host bridge /pci (primary) ranges:
  IO 0x00000000fe000000..0x00000000fe7fffff -> 0x0000000000000000
 MEM 0x00000000fd000000..0x00000000fdffffff -> 0x0000000000000000
 MEM 0x0000000080000000..0x00000000fcffffff -> 0x0000000080000000
clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
futex hash table entries: 512 (order: 2, 16384 bytes, linear)
NET: Registered protocol family 16
PMU i2c /pci/mac-io/via-pmu
 channel 1 bus <multibus>
 channel 2 bus <multibus>
PCI: Probing PCI hardware
PCI host bridge to bus 0000:00
pci_bus 0000:00: root bus resource [io  0x0000-0x7fffff]
pci_bus 0000:00: root bus resource [mem 0xfd000000-0xfdffffff] (bus address [0x00000000-0x00ffffff])
pci_bus 0000:00: root bus resource [mem 0x80000000-0xfcffffff]
pci_bus 0000:00: root bus resource [bus 00-ff]
pci_bus 0000:00: busn_res: [bus 00-ff] end is updated to ff
pci 0000:00:00.0: [1057:0002] type 00 class 0x060000
pci 0000:00:0d.0: [106b:0017] type 00 class 0xff0000
pci 0000:00:0d.0: reg 0x10: [mem 0xf4000000-0xf407ffff]
pci 0000:00:10.0: [106b:0017] type 00 class 0xff0000
pci 0000:00:10.0: reg 0x10: [mem 0xf3000000-0xf307ffff]
pci 0000:00:11.0: [1002:4c50] type 00 class 0x038000
pci 0000:00:11.0: reg 0x10: [mem 0x82000000-0x82ffffff]
pci 0000:00:11.0: reg 0x14: [io  0x0400-0x04ff]
pci 0000:00:11.0: reg 0x18: [mem 0x82fff000-0x82ffffff]
pci 0000:00:11.0: reg 0x30: [mem 0xfd000000-0xfd01ffff pref]
pci 0000:00:11.0: supports D1 D2
pci 0000:00:13.0: [104c:ac15] type 02 class 0x060700
pci 0000:00:13.0: reg 0x10: [mem 0x81803000-0x81803fff]
pci 0000:00:13.1: [104c:ac15] type 02 class 0x060700
pci 0000:00:13.1: reg 0x10: [mem 0x81802000-0x81802fff]
pci_bus 0000:01: extended config space not accessible
pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 04
pci_bus 0000:05: extended config space not accessible
pci_bus 0000:05: busn_res: [bus 05-ff] end is updated to 08
pci_bus 0000:00: busn_res: [bus 00-ff] end is updated to 08
PCI: Cannot allocate resource region 2 of device 0000:00:11.0, will remap
PCI 0000:00 Cannot reserve Legacy IO [io  0x0000-0x0fff]
pci 0000:00:13.0: BAR 9: assigned [mem 0x84000000-0x87ffffff pref]
pci 0000:00:13.0: BAR 10: assigned [mem 0x88000000-0x8bffffff]
pci 0000:00:13.1: BAR 9: assigned [mem 0x8c000000-0x8fffffff pref]
pci 0000:00:13.1: BAR 10: assigned [mem 0x90000000-0x93ffffff]
pci 0000:00:11.0: BAR 6: assigned [mem 0xfd000000-0xfd01ffff pref]
pci 0000:00:11.0: BAR 2: assigned [mem 0xfd020000-0xfd020fff]
pci 0000:00:13.0: BAR 7: assigned [io  0x1000-0x10ff]
pci 0000:00:13.0: BAR 8: assigned [io  0x1100-0x11ff]
pci 0000:00:13.1: BAR 7: assigned [io  0x1200-0x12ff]
pci 0000:00:13.1: BAR 8: assigned [io  0x1300-0x13ff]
pci 0000:00:13.0: CardBus bridge to [bus 01-04]
pci 0000:00:13.0:   bridge window [io  0x1000-0x10ff]
pci 0000:00:13.0:   bridge window [io  0x1100-0x11ff]
pci 0000:00:13.0:   bridge window [mem 0x84000000-0x87ffffff pref]
pci 0000:00:13.0:   bridge window [mem 0x88000000-0x8bffffff]
pci 0000:00:13.1: CardBus bridge to [bus 05-08]
pci 0000:00:13.1:   bridge window [io  0x1200-0x12ff]
pci 0000:00:13.1:   bridge window [io  0x1300-0x13ff]
pci 0000:00:13.1:   bridge window [mem 0x8c000000-0x8fffffff pref]
pci 0000:00:13.1:   bridge window [mem 0x90000000-0x93ffffff]
pci_bus 0000:00: resource 4 [io  0x0000-0x7fffff]
pci_bus 0000:00: resource 5 [mem 0xfd000000-0xfdffffff]
pci_bus 0000:00: resource 6 [mem 0x80000000-0xfcffffff]
pci_bus 0000:01: resource 0 [io  0x1000-0x10ff]
pci_bus 0000:01: resource 1 [io  0x1100-0x11ff]
pci_bus 0000:01: resource 2 [mem 0x84000000-0x87ffffff pref]
pci_bus 0000:01: resource 3 [mem 0x88000000-0x8bffffff]
pci_bus 0000:05: resource 0 [io  0x1200-0x12ff]
pci_bus 0000:05: resource 1 [io  0x1300-0x13ff]
pci_bus 0000:05: resource 2 [mem 0x8c000000-0x8fffffff pref]
pci_bus 0000:05: resource 3 [mem 0x90000000-0x93ffffff]
vgaarb: loaded
SCSI subsystem initialized
libata version 3.00 loaded.
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
clocksource: Switched to clocksource timebase
NET: Registered protocol family 2
tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 6144 bytes, linear)
TCP established hash table entries: 4096 (order: 2, 16384 bytes, linear)
TCP bind hash table entries: 4096 (order: 3, 32768 bytes, linear)
TCP: Hash tables configured (established 4096 bind 4096)
UDP hash table entries: 256 (order: 1, 8192 bytes, linear)
UDP-Lite hash table entries: 256 (order: 1, 8192 bytes, linear)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
PCI: CLS 32 bytes, default 32
Thermal assist unit using workqueue, shrink_timer: 2000 ms
workingset: timestamp_bits=30 max_order=17 bucket_order=0
squashfs: version 4.0 (2009/01/31) Phillip Lougher
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
io scheduler mq-deadline registered
pci 0000:00:11.0: enabling device (0086 -> 0087)
Using unsupported 1024x768 (null) at 82801000, depth=32, pitch=4096
Console: switching to colour frame buffer device 128x48
fb0: Open Firmware frame buffer device on /pci/ATY,RageLTPro
pmac_zilog: 0.6 (Benjamin Herrenschmidt <benh@kernel.crashing.org>)
Non-volatile memory driver v1.3
brd: module loaded
loop: module loaded
MacIO PCI driver attached to Gatwick chipset
MacIO PCI driver attached to Heathrow chipset
swim3 0.00015000:floppy: [fd0] SWIM3 floppy controller in media bay
0.00013020:ch-a: ttyS0 at MMIO 0xf3013020 (irq = 16, base_baud = 230400) is a Z85c30 ESCC - Serial port
0.00013000:ch-b: ttyS1 at MMIO 0xf3013000 (irq = 17, base_baud = 230400) is a Z85c30 ESCC - Infrared port
macio: fixed media-bay irq on gatwick
macio: fixed left floppy irqs
swim3 1.00015000:floppy: [fd1] Couldn't request interrupt
swim3: probe of 1.00015000:floppy failed with error -16
macio: fixed left ide irqs
macio: fixed SCC irqs on gatwick
1.00013020:ch-a: ttyS2 at MMIO 0xf4013020 (irq = 79, base_baud = 230400) is a Z85c30 ESCC - Internal modem
mediabay0: Registered Heathrow media-bay
mediabay1: Registered Heathrow media-bay
mediabay0: Bay contains an ATA device
PMU Backlight initialized (pmubl)
mesh: configured for synchronous 5 MB/s
mediabay1: Bay contains a floppy drive
mesh: performing initial bus reset...
random: fast init done
adb device [2]: 2 0xC3
adb device [3]: 3 0x1
adb device [7]: 7 0x1F
ADB keyboard at 2 has handler 0xC3
Detected ADB keyboard, type ANSI.
input: ADB keyboard as /devices/virtual/input/input0
input: ADB Powerbook buttons as /devices/virtual/input/input1
ADB mouse (trackpad) at 3 has handler 0x4
input: ADB mouse as /devices/virtual/input/input2
scsi host0: MESH
pata-macio 0.00020000:ata0: Activating pata-macio chipset Heathrow ATA, Apple bus ID 0
scsi host1: pata_macio
ata1: PATA max MWDMA2 irq 30
ata1.00: ATA-7: SAMSUNG HM100JC, YN100-08, max UDMA/100
ata1.00: 195371568 sectors, multi 8: LBA48
scsi 1:0:0:0: Direct-Access     ATA      SAMSUNG HM100JC  0-08 PQ: 0 ANSI: 5
sd 1:0:0:0: [sda] 195371568 512-byte logical blocks: (100 GB/93.2 GiB)
sd 1:0:0:0: Attached scsi generic sg0 type 0
sd 1:0:0:0: [sda] Write Protect is off
sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 1:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
pata-macio 0.00021000:ata1: Activating pata-macio chipset Heathrow ATA, Apple bus ID 1
scsi host2: pata_macio
ata2: PATA max MWDMA2 irq 36
pata-macio 1.00021000:ata4: Activating pata-macio chipset Heathrow ATA, Apple bus ID 4
genirq: Flags mismatch irq 36. 00000000 (pata-macio[1.00021000:ata4]) vs. 00000000 (pata-macio[0.00021000:ata1])
pata-macio: probe of 1.00021000:ata4 failed with error -16
ata2.00: ATA-6: ST9160821A, 3.ALD, max UDMA/100
ata2.00: 312581808 sectors, multi 0: LBA48
eth0: BMAC at 00:05:02:07:5a:a6

aoe: AoE v85 initialised.
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-pci: EHCI PCI platform driver
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
ohci-pci: OHCI PCI platform driver
usbcore: registered new interface driver uas
usbcore: registered new interface driver usb-storage
mousedev: PS/2 mouse device common for all mice
rtc-generic rtc-generic: registered as rtc0
i2c /dev entries driver
PowerMac i2c bus pmu 2 registered
PowerMac i2c bus pmu 1 registered
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
NET: Registered protocol family 17
drmem: No dynamic reconfiguration memory found
 sda: [mac] sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10 sda11 sda12 sda13 sda14 sda15
sd 1:0:0:0: [sda] Attached SCSI disk
scsi 2:0:0:0: Direct-Access     ATA      ST9160821A       D    PQ: 0 ANSI: 5
sd 2:0:0:0: [sdb] 312581808 512-byte logical blocks: (160 GB/149 GiB)
sd 2:0:0:0: Attached scsi generic sg1 type 0
sd 2:0:0:0: [sdb] Write Protect is off
sd 2:0:0:0: [sdb] Mode Sense: 00 3a 00 00
sd 2:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sdb: [mac] sdb1 sdb2 sdb3 sdb4 sdb5 sdb6 sdb7 sdb8 sdb9 sdb10 sdb11 sdb12 sdb13 sdb14
sd 2:0:0:0: [sdb] Attached SCSI disk
EXT4-fs (sda12): mounting ext3 file system using the ext4 subsystem
EXT4-fs (sda12): mounted filesystem with ordered data mode. Opts: (null). Quota mode: disabled.
VFS: Mounted root (ext3 filesystem) readonly on device 8:12.
Freeing unused kernel memory: 1224K
Kernel memory protection not selected by kernel config.
Run /sbin/init as init process
  with arguments:
    /sbin/init
  with environment:
    HOME=/
    TERM=linux
INIT: version 2.96 booting
Using makefile-style concurrent boot in runlevel S.
findfs: unable to resolve 'LABEL=Debian_sid'
Starting hotplug events dispatcher: systemd-udevd.
Synthesizing the initial hotplug events (subsystems)...done.
Synthesizing the initial hotplug events (devices)...done.
Waiting for /dev to be fully populated...random: crng init done
phy registers:
 0000 0000 0000 0000 0000 0000 0000 0000
 0000 0000 0000 0000 0000 0000 0000 0000
 0000 0000 0000 0000 0000 0000 0000 0000
 0000 0000 0000 0000 0000 0000 0000 0000
done.
Setting up keyboard layout...done.
Activating swap...Adding 524284k swap on /dev/sda14.  Priority:-2 extents:1 across:524284k
done.
EXT4-fs (sda12): re-mounted. Opts: (null). Quota mode: disabled.
Checking root file system...Debian_sid: clean, 76261/524288 files, 1036537/2097152 blocks
done.
EXT4-fs (sda12): re-mounted. Opts: errors=remount-ro. Quota mode: disabled.
Checking file systems...data: clean, 83287/3325952 files, 2159937/13280326 blocks
done.
Cleaning up temporary files...
 /tmp.
Loading kernel module lp.
modprobe: FATAL: Module lp not found in directory /lib/modules/5.12.0-rc3-pmac-00078-geb51c431b81
Loading kernel module ppdev.
modprobe: FATAL: Module ppdev not found in directory /lib/modules/5.12.0-rc3-pmac-00078-geb51c431b81
Loading kernel module parport_pc.
modprobe: FATAL: Module parport_pc not found in directory /lib/modules/5.12.0-rc3-pmac-00078-geb51c431b81
Loading kernel module apm_emu.
modprobe: FATAL: Module apm_emu not found in directory /lib/modules/5.12.0-rc3-pmac-00078-geb51c431b81
Loading kernel module bmac.
modprobe: FATAL: Module bmac not found in directory /lib/modules/5.12.0-rc3-pmac-00078-geb51c431b81
Loading kernel module mesh.
modprobe: FATAL: Module mesh not found in directory /lib/modules/5.12.0-rc3-pmac-00078-geb51c431b81
Loading kernel module snd-powermac.
modprobe: FATAL: Module snd-powermac not found in directory /lib/modules/5.12.0-rc3-pmac-00078-geb51c431b81
EXT4-fs (sda15): mounting ext3 file system using the ext4 subsystem
EXT4-fs (sda15): mounted filesystem with ordered data mode. Opts: (null). Quota mode: disabled.
Mounting local filesystems...done.
Activating swapfile swap, if any...done.
Cleaning up temporary files....
Starting Setting kernel variables: sysctl.
Configuring network interfaces...done.
Cleaning up temporary files....
Setting up X socket directories... /tmp/.X11-unix /tmp/.ICE-unix
.
INIT: Entering runlevel: 2
Using makefile-style concurrent boot in runlevel 2.
Setting up console font and keymap...done.
Recovering nvi editor sessions.
none found.
Starting enhanced syslogd: rsyslogd.
Starting periodic command scheduler: cron.
Starting system message bus: dbus.
Starting OpenBSD Secure Shell server: sshd.
Starting S.M.A.R.T. daemon: smartd.
Starting WINGs display manager: wdm:.
Deconfiguring network interfaces...
done.
phy registers:
 0000 0000 0000 0000 0000 0000 0000 0000
 0000 0000 0000 0000 0000 0000 0000 0000
 0000 0000 0000 0000 0000 0000 0000 0000
 0000 0000 0000 0000 0000 0000 0000 0000

Debian GNU/Linux 11 mac-server ttyS0

mac-server login: Kernel attempted to write user page (b3399774) - exploit attempt? (uid: 1000)
BUG: Unable to handle kernel data access on write at 0xb3399774
Faulting instruction address: 0xb21cb370
Oops: Kernel access of bad area, sig: 11 [#1]
BE PAGE_SIZE=4K MMU=Hash SMP NR_CPUS=2 PowerMac
Modules linked in:
CPU: 0 PID: 1880 Comm: xfwm4 Not tainted 5.12.0-rc3-pmac-00078-geb51c431b81 #1
NIP:  b21cb370 LR: b21cb34c CTR: b21cb340
REGS: e2e79f40 TRAP: 0300   Not tainted  (5.12.0-rc3-pmac-00078-geb51c431b81)
MSR:  0000d032 <EE,PR,ME,IR,DR,RI>  CR: 44004202  XER: 20000000
DAR: b3399774 DSISR: 42000000
GPR00: b7de5d50 bf8ab0e0 b559f720 b259b430 b3399774 b3302cb0 00000688 b3395d10
GPR08: b3395d00 00000000 b3395d20 b696c690 b21cb290 0055f694 00000000 bff67e04
GPR16: 00000000 00000000 0000002e 90000000 0075c718 0000001c 00000000 00200000
GPR24: 00000000 0000002b 00567880 bf8ad1a4 00000005 b326d24c b32f4d44 00000027
NIP [b21cb370] 0xb21cb370
LR [b21cb34c] 0xb21cb34c
Call Trace:
---[ end trace 8c58fa6ae8a8114e ]---

BUG: Unable to handle kernel instruction fetch
Faulting instruction address: 0x706d2e70
Oops: Kernel access of bad area, sig: 11 [#2]
BE PAGE_SIZE=4K MMU=Hash SMP NR_CPUS=2 PowerMac
Modules linked in:
CPU: 0 PID: 1889 Comm: xfsettingsd Tainted: G      D           5.12.0-rc3-pmac-00078-geb51c431b81 #1
NIP:  706d2e70 LR: 706d2e73 CTR: c0218ebc
REGS: e2e79e70 TRAP: 0400   Tainted: G      D            (5.12.0-rc3-pmac-00078-geb51c431b81)
MSR:  40001030 <ME,IR,DR>  CR: 24048828  XER: 00000000

GPR00: 706d2e73 e2e79f30 c14f6ac0 00000000 00000000 00000000 00000001 c1c52400
GPR08: 00000000 402386ea 402387fb ffffffff 24048424 00c1fac8 00000000 bff67e04
GPR16: 00000000 00000000 00cba8c0 00000012 00000000 b7f99cb8 bf8e6470 00000000
GPR24: bf8e667c 00000002 90000002 b7f99cb8 00000000 00cba8c0 b7f9aff0 bf8e6400
NIP [706d2e70] 0x706d2e70
LR [706d2e73] 0x706d2e73
Call Trace:
[e2e79f30] [c0016058] ret_from_syscall+0xc/0x28 (unreliable)
--- interrupt: c00 at 0xb7f7ab14
NIP:  b7f7ab14 LR: b7f62f08 CTR: c0152b1c
REGS: e2e79f40 TRAP: 0c00   Tainted: G      D            (5.12.0-rc3-pmac-00078-geb51c431b81)
MSR:  0000f932 <EE,PR,FP,ME,IR,DR,RI>  CR: 44048224  XER: 00000000

GPR00: 0000011e bf8e63d0 b3b01db0 0000000f 00cba8c0 00090000 00000000 bf8e667c
GPR08: 00000000 676c6962 b7f80d74 00000000 00000005 00c1fac8 00000000 bff67e04
GPR16: 00000000 00000000 00cba8c0 00000012 00000000 b7f99cb8 bf8e6470 00000000
GPR24: bf8e667c 00000002 90000002 b7f99cb8 00000000 00cba8c0 b7f9aff0 bf8e6400
NIP [b7f7ab14] 0xb7f7ab14
LR [b7f62f08] 0xb7f62f08
--- interrupt: c00
Instruction dump:
XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX
XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX
---[ end trace 8c58fa6ae8a8114f ]---

BUG: Unable to handle kernel instruction fetch (NULL pointer?)
Faulting instruction address: 0x00000000
Oops: Kernel access of bad area, sig: 11 [#3]
BE PAGE_SIZE=4K MMU=Hash SMP NR_CPUS=2 PowerMac
Modules linked in:
CPU: 0 PID: 1903 Comm: xfdesktop Tainted: G      D           5.12.0-rc3-pmac-00078-geb51c431b81 #1
NIP:  00000000 LR: 00000000 CTR: 000003f7
REGS: e2eb1e70 TRAP: 0400   Tainted: G      D            (5.12.0-rc3-pmac-00078-geb51c431b81)
MSR:  40001030 <ME,IR,DR>  CR: 28444468  XER: 20000000

GPR00: 00000000 e2eb1f30 cdc73400 00000000 00000000 00000000 00000062 c0000000
GPR08: 00000000 4025ef9a 4025f0ab c193ad48 24444268 009bf34c 00c01a90 bff67d14
GPR16: 00000000 00000064 80003555 00c0ca90 00000000 00c0e4b0 00000000 00c0e4b0
GPR24: b60c3cdc 00c0e490 00c0e470 00000001 00c0e470 b60c3cdc b6963ff4 00c0e4c0
NIP [00000000] 0x0
LR [00000000] 0x0
Call Trace:
[e2eb1f30] [c0016058] ret_from_syscall+0xc/0x28 (unreliable)
--- interrupt: c00 at 0xb6876048
NIP:  b6876048 LR: b6096dc8 CTR: b6810b70
REGS: e2eb1f40 TRAP: 0c00   Tainted: G      D            (5.12.0-rc3-pmac-00078-geb51c431b81)
MSR:  0000f932 <EE,PR,FP,ME,IR,DR,RI>  CR: 24444260  XER: 00000000

GPR00: 00000021 bfbf9440 b52bc4e0 00000000 00000004 00c0e4d4 00000000 7f7f7f7f
GPR08: 74732f00 00000000 00000000 b6810b70 44444260 009bf34c 00c01a90 bff67d14
GPR16: 00000000 00000064 80003555 00c0ca90 00000000 00c0e4b0 00000000 00c0e4b0
GPR24: b60c3cdc 00c0e490 00c0e470 00000001 00c0e470 b60c3cdc b6963ff4 00c0e4c0
NIP [b6876048] 0xb6876048
LR [b6096dc8] 0xb6096dc8
--- interrupt: c00
Instruction dump:
XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX
XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX
---[ end trace 8c58fa6ae8a81150 ]---


mac-server login: root
Password:
Linux mac-server 5.12.0-rc3-pmac-00078-geb51c431b81 #1 SMP Wed Aug 4 21:50:47 MDT 2021 ppc

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Wed Aug  4 22:04:38 MDT 2021 on ttyS0
root@mac-server:~# shutdown -r now

Broadcast message from root@mac-server (ttyS0) (Wed Aug  4 22:33:07 2021):

The system is going down for reboot NOW!

Broadcast message from root@mac-server (ttyS0) (Wed Aug  4 22:33:07 2021):

The system is going down for reboot NOW!
INIT: Sending processes configured via /etc/iUsing makefile-style concurrent boot in runlevel 6.
Stopping mouse emulation daemon: mouseemu.
Stopping hotplug events dispatcher: systemd-udevd.
Stopping S.M.A.R.T. daemon: smartd.
BUG: Unable to handle kernel instruction fetch
Faulting instruction address: 0x7d6903a4
Oops: Kernel access of bad area, sig: 11 [#4]
BE PAGE_SIZE=4K MMU=Hash SMP NR_CPUS=2 PowerMac
Modules linked in:
CPU: 0 PID: 1882 Comm: gdbus Tainted: G      D           5.12.0-rc3-pmac-00078-geb51c431b81 #1
NIP:  7d6903a4 LR: 7d6903a6 CTR: c00d08ac
REGS: e2e7de70 TRAP: 0400   Tainted: G      D            (5.12.0-rc3-pmac-00078-geb51c431b81)
MSR:  40001030 <ME,IR,DR>  CR: 20022248  XER: 20000000

GPR00: 7d6903a6 e2e7df30 c47720c0 00000000 00000000 00000000 cc7ae1de b9f4812a
GPR08: 00000000 401eed9a 401eeeab 00000000 20022248 0055f694 00801000 b6b5e308
GPR16: b6b5c2a8 00000000 00000000 00000000 00000008 b6fe77cc 00000001 00000000
GPR24: 00000000 b6fe77e0 b6fe780c b43fe35c b6fe79b0 b6fe79ac b6feea94 b6fe780c
NIP [7d6903a4] 0x7d6903a4
LR [7d6903a6] 0x7d6903a6
Call Trace:
[e2e7df30] [c0016058] ret_from_syscall+0xc/0x28 (unreliable)
--- interrupt: c00 at 0xb6a3b860
NIP:  b6a3b860 LR: b6f2e648 CTR: 00000000
REGS: e2e7df40 TRAP: 0c00   Tainted: G      D            (5.12.0-rc3-pmac-00078-geb51c431b81)
MSR:  0000d032 <EE,PR,ME,IR,DR,RI>  CR: 20022242  XER: 20000000

GPR00: 000000dd b43fe280 b44066e0 00000000 00000081 7fffffff 00000000 b3a02f58
GPR08: 00000140 00000425 b3a19df8 b69c64f0 44022228 0055f694 00801000 b6b5e308
GPR16: b6b5c2a8 00000000 00000000 00000000 00000008 b6fe77cc 00000001 00000000
GPR24: 00000000 b6fe77e0 b6fe780c b43fe35c b6fe79b0 b6fe79ac b6feea94 b6fe780c
NIP [b6a3b860] 0xb6a3b860
LR [b6f2e648] 0xb6f2e648
--- interrupt: c00
Instruction dump:
XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX
XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX
---[ end trace 8c58fa6ae8a81151 ]---

Stopping WINGs display manager: wdm:
 (removing stale /var/run/wdm.pid).
Asking all remaining processes to terminate...done.
All processes ended within 4 seconds...done.
Stopping enhanced syslogd: rsyslogd.
Saving the system clock to /dev/rtc0.
Hardware Clock updated to Wed Aug  4 22:33:18 MDT 2021.
Deconfiguring network interfaces...done.
Deactivating swap...done.
Unmounting local filesystems...done.
mount: /: mount point is busy.
Will now restart.
sd 2:0:0:0: [sdb] Synchronizing SCSI cache
resetting MESH scsi bus(es)
reboot: Restarting system

[-- Attachment #3: Type: text/plain, Size: 21158 bytes --]

printk: console [ttyS0] enabled
printk: bootconsole [udbg0] disabled
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
rcu: Hierarchical SRCU implementation.
smp: Bringing up secondary CPUs ...
smp: Brought up 1 node, 1 CPU
devtmpfs: initialized
Duplicate name in PowerPC,750, renamed to "l2-cache#1"
Duplicate name in pci, renamed to "mac-io#1"
Duplicate name in pci, renamed to "pccard#1"
Found Grackle (MPC106) PCI host bridge at 0x0000000080000000. Firmware bus number: 0->0
PCI host bridge /pci (primary) ranges:
  IO 0x00000000fe000000..0x00000000fe7fffff -> 0x0000000000000000
 MEM 0x00000000fd000000..0x00000000fdffffff -> 0x0000000000000000
 MEM 0x0000000080000000..0x00000000fcffffff -> 0x0000000080000000
clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
futex hash table entries: 512 (order: 2, 16384 bytes, linear)
NET: Registered protocol family 16
PMU i2c /pci/mac-io/via-pmu
 channel 1 bus <multibus>
 channel 2 bus <multibus>
PCI: Probing PCI hardware
PCI host bridge to bus 0000:00
pci_bus 0000:00: root bus resource [io  0x0000-0x7fffff]
pci_bus 0000:00: root bus resource [mem 0xfd000000-0xfdffffff] (bus address [0x00000000-0x00ffffff])
pci_bus 0000:00: root bus resource [mem 0x80000000-0xfcffffff]
pci_bus 0000:00: root bus resource [bus 00-ff]
pci_bus 0000:00: busn_res: [bus 00-ff] end is updated to ff
pci 0000:00:00.0: [1057:0002] type 00 class 0x060000
pci 0000:00:0d.0: [106b:0017] type 00 class 0xff0000
pci 0000:00:0d.0: reg 0x10: [mem 0xf4000000-0xf407ffff]
pci 0000:00:10.0: [106b:0017] type 00 class 0xff0000
pci 0000:00:10.0: reg 0x10: [mem 0xf3000000-0xf307ffff]
pci 0000:00:11.0: [1002:4c50] type 00 class 0x038000
pci 0000:00:11.0: reg 0x10: [mem 0x82000000-0x82ffffff]
pci 0000:00:11.0: reg 0x14: [io  0x0400-0x04ff]
pci 0000:00:11.0: reg 0x18: [mem 0x82fff000-0x82ffffff]
pci 0000:00:11.0: reg 0x30: [mem 0xfd000000-0xfd01ffff pref]
pci 0000:00:11.0: supports D1 D2
pci 0000:00:13.0: [104c:ac15] type 02 class 0x060700
pci 0000:00:13.0: reg 0x10: [mem 0x81803000-0x81803fff]
pci 0000:00:13.1: [104c:ac15] type 02 class 0x060700
pci 0000:00:13.1: reg 0x10: [mem 0x81802000-0x81802fff]
pci_bus 0000:01: extended config space not accessible
pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 04
pci_bus 0000:05: extended config space not accessible
pci_bus 0000:05: busn_res: [bus 05-ff] end is updated to 08
pci_bus 0000:00: busn_res: [bus 00-ff] end is updated to 08
PCI: Cannot allocate resource region 2 of device 0000:00:11.0, will remap
PCI 0000:00 Cannot reserve Legacy IO [io  0x0000-0x0fff]
pci 0000:00:13.0: BAR 9: assigned [mem 0x84000000-0x87ffffff pref]
pci 0000:00:13.0: BAR 10: assigned [mem 0x88000000-0x8bffffff]
pci 0000:00:13.1: BAR 9: assigned [mem 0x8c000000-0x8fffffff pref]
pci 0000:00:13.1: BAR 10: assigned [mem 0x90000000-0x93ffffff]
pci 0000:00:11.0: BAR 6: assigned [mem 0xfd000000-0xfd01ffff pref]
pci 0000:00:11.0: BAR 2: assigned [mem 0xfd020000-0xfd020fff]
pci 0000:00:13.0: BAR 7: assigned [io  0x1000-0x10ff]
pci 0000:00:13.0: BAR 8: assigned [io  0x1100-0x11ff]
pci 0000:00:13.1: BAR 7: assigned [io  0x1200-0x12ff]
pci 0000:00:13.1: BAR 8: assigned [io  0x1300-0x13ff]
pci 0000:00:13.0: CardBus bridge to [bus 01-04]
pci 0000:00:13.0:   bridge window [io  0x1000-0x10ff]
pci 0000:00:13.0:   bridge window [io  0x1100-0x11ff]
pci 0000:00:13.0:   bridge window [mem 0x84000000-0x87ffffff pref]
pci 0000:00:13.0:   bridge window [mem 0x88000000-0x8bffffff]
pci 0000:00:13.1: CardBus bridge to [bus 05-08]
pci 0000:00:13.1:   bridge window [io  0x1200-0x12ff]
pci 0000:00:13.1:   bridge window [io  0x1300-0x13ff]
pci 0000:00:13.1:   bridge window [mem 0x8c000000-0x8fffffff pref]
pci 0000:00:13.1:   bridge window [mem 0x90000000-0x93ffffff]
pci_bus 0000:00: resource 4 [io  0x0000-0x7fffff]
pci_bus 0000:00: resource 5 [mem 0xfd000000-0xfdffffff]
pci_bus 0000:00: resource 6 [mem 0x80000000-0xfcffffff]
pci_bus 0000:01: resource 0 [io  0x1000-0x10ff]
pci_bus 0000:01: resource 1 [io  0x1100-0x11ff]
pci_bus 0000:01: resource 2 [mem 0x84000000-0x87ffffff pref]
pci_bus 0000:01: resource 3 [mem 0x88000000-0x8bffffff]
pci_bus 0000:05: resource 0 [io  0x1200-0x12ff]
pci_bus 0000:05: resource 1 [io  0x1300-0x13ff]
pci_bus 0000:05: resource 2 [mem 0x8c000000-0x8fffffff pref]
pci_bus 0000:05: resource 3 [mem 0x90000000-0x93ffffff]
vgaarb: loaded
SCSI subsystem initialized
libata version 3.00 loaded.
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
clocksource: Switched to clocksource timebase
NET: Registered protocol family 2
tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 6144 bytes, linear)
TCP established hash table entries: 4096 (order: 2, 16384 bytes, linear)
TCP bind hash table entries: 4096 (order: 3, 32768 bytes, linear)
TCP: Hash tables configured (established 4096 bind 4096)
UDP hash table entries: 256 (order: 1, 8192 bytes, linear)
UDP-Lite hash table entries: 256 (order: 1, 8192 bytes, linear)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
PCI: CLS 32 bytes, default 32
Thermal assist unit using workqueue, shrink_timer: 2000 ms
workingset: timestamp_bits=30 max_order=17 bucket_order=0
squashfs: version 4.0 (2009/01/31) Phillip Lougher
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
io scheduler mq-deadline registered
pci 0000:00:11.0: enabling device (0086 -> 0087)
Using unsupported 1024x768 (null) at 82801000, depth=32, pitch=4096
Console: switching to colour frame buffer device 128x48
fb0: Open Firmware frame buffer device on /pci/ATY,RageLTPro
pmac_zilog: 0.6 (Benjamin Herrenschmidt <benh@kernel.crashing.org>)
Non-volatile memory driver v1.3
brd: module loaded
loop: module loaded
MacIO PCI driver attached to Gatwick chipset
MacIO PCI driver attached to Heathrow chipset
swim3 0.00015000:floppy: [fd0] SWIM3 floppy controller in media bay
0.00013020:ch-a: ttyS0 at MMIO 0xf3013020 (irq = 16, base_baud = 230400) is a Z85c30 ESCC - Serial port
0.00013000:ch-b: ttyS1 at MMIO 0xf3013000 (irq = 17, base_baud = 230400) is a Z85c30 ESCC - Infrared port
macio: fixed media-bay irq on gatwick
macio: fixed left floppy irqs
swim3 1.00015000:floppy: [fd1] Couldn't request interrupt
swim3: probe of 1.00015000:floppy failed with error -16
macio: fixed left ide irqs
macio: fixed SCC irqs on gatwick
1.00013020:ch-a: ttyS2 at MMIO 0xf4013020 (irq = 79, base_baud = 230400) is a Z85c30 ESCC - Internal modem
mediabay0: Registered Heathrow media-bay
mediabay1: Registered Heathrow media-bay
mediabay0: Bay contains an ATA device
PMU Backlight initialized (pmubl)
mesh: configured for synchronous 5 MB/s
mediabay1: Bay contains a floppy drive
mesh: performing initial bus reset...
random: fast init done
adb device [2]: 2 0xC3
adb device [3]: 3 0x1
adb device [7]: 7 0x1F
ADB keyboard at 2 has handler 0xC3
Detected ADB keyboard, type ANSI.
input: ADB keyboard as /devices/virtual/input/input0
input: ADB Powerbook buttons as /devices/virtual/input/input1
ADB mouse (trackpad) at 3 has handler 0x4
input: ADB mouse as /devices/virtual/input/input2
scsi host0: MESH
pata-macio 0.00020000:ata0: Activating pata-macio chipset Heathrow ATA, Apple bus ID 0
scsi host1: pata_macio
ata1: PATA max MWDMA2 irq 30
ata1.00: ATA-7: SAMSUNG HM100JC, YN100-08, max UDMA/100
ata1.00: 195371568 sectors, multi 8: LBA48
scsi 1:0:0:0: Direct-Access     ATA      SAMSUNG HM100JC  0-08 PQ: 0 ANSI: 5
sd 1:0:0:0: [sda] 195371568 512-byte logical blocks: (100 GB/93.2 GiB)
sd 1:0:0:0: Attached scsi generic sg0 type 0
sd 1:0:0:0: [sda] Write Protect is off
sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 1:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
pata-macio 0.00021000:ata1: Activating pata-macio chipset Heathrow ATA, Apple bus ID 1
scsi host2: pata_macio
ata2: PATA max MWDMA2 irq 36
pata-macio 1.00021000:ata4: Activating pata-macio chipset Heathrow ATA, Apple bus ID 4
genirq: Flags mismatch irq 36. 00000000 (pata-macio[1.00021000:ata4]) vs. 00000000 (pata-macio[0.00021000:ata1])
pata-macio: probe of 1.00021000:ata4 failed with error -16
ata2.00: ATA-6: ST9160821A, 3.ALD, max UDMA/100
ata2.00: 312581808 sectors, multi 0: LBA48
eth0: BMAC at 00:05:02:07:5a:a6

aoe: AoE v85 initialised.
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-pci: EHCI PCI platform driver
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
ohci-pci: OHCI PCI platform driver
usbcore: registered new interface driver uas
usbcore: registered new interface driver usb-storage
mousedev: PS/2 mouse device common for all mice
rtc-generic rtc-generic: registered as rtc0
i2c /dev entries driver
PowerMac i2c bus pmu 2 registered
PowerMac i2c bus pmu 1 registered
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
NET: Registered protocol family 17
drmem: No dynamic reconfiguration memory found
 sda: [mac] sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10 sda11 sda12 sda13 sda14 sda15
sd 1:0:0:0: [sda] Attached SCSI disk
scsi 2:0:0:0: Direct-Access     ATA      ST9160821A       D    PQ: 0 ANSI: 5
sd 2:0:0:0: [sdb] 312581808 512-byte logical blocks: (160 GB/149 GiB)
sd 2:0:0:0: Attached scsi generic sg1 type 0
sd 2:0:0:0: [sdb] Write Protect is off
sd 2:0:0:0: [sdb] Mode Sense: 00 3a 00 00
sd 2:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sdb: [mac] sdb1 sdb2 sdb3 sdb4 sdb5 sdb6 sdb7 sdb8 sdb9 sdb10 sdb11 sdb12 sdb13 sdb14
sd 2:0:0:0: [sdb] Attached SCSI disk
EXT4-fs (sda12): mounting ext3 file system using the ext4 subsystem
EXT4-fs (sda12): INFO: recovery required on readonly filesystem
EXT4-fs (sda12): write access will be enabled during recovery
EXT4-fs (sda12): recovery complete
EXT4-fs (sda12): mounted filesystem with ordered data mode. Opts: (null). Quota mode: disabled.
VFS: Mounted root (ext3 filesystem) readonly on device 8:12.
Freeing unused kernel memory: 1228K
Kernel memory protection not selected by kernel config.
Run /sbin/init as init process
  with arguments:
    /sbin/init
  with environment:
    HOME=/
    TERM=linux
INIT: version 2.96 booting
Using makefile-style concurrent boot in runlevel S.
findfs: unable to resolve 'LABEL=Debian_sid'
Starting hotplug events dispatcher: systemd-udevd.
Synthesizing the initial hotplug events (subsystems)...done.
Synthesizing the initial hotplug events (devices)...done.
Waiting for /dev to be fully populated...random: crng init done
phy registers:
 0000 0000 0000 0000 0000 0000 0000 0000
 0000 0000 0000 0000 0000 0000 0000 0000
 0000 0000 0000 0000 0000 0000 0000 0000
 0000 0000 0000 0000 0000 0000 0000 0000
done.
Setting up keyboard layout...done.
Activating swap...Adding 524284k swap on /dev/sda14.  Priority:-2 extents:1 across:524284k
done.
EXT4-fs (sda12): re-mounted. Opts: (null). Quota mode: disabled.
Checking root file system...Debian_sid: clean, 76261/524288 files, 1036569/2097152 blocks
done.
EXT4-fs (sda12): re-mounted. Opts: errors=remount-ro. Quota mode: disabled.
Checking file systems...data: clean, 83287/3325952 files, 2159937/13280326 blocks
done.
Cleaning up temporary files...
 /tmp.
Loading kernel module lp.
modprobe: FATAL: Module lp not found in directory /lib/modules/5.12.0-rc3-pmac-00077-gc9f6e8dd045
Loading kernel module ppdev.
modprobe: FATAL: Module ppdev not found in directory /lib/modules/5.12.0-rc3-pmac-00077-gc9f6e8dd045
Loading kernel module parport_pc.
modprobe: FATAL: Module parport_pc not found in directory /lib/modules/5.12.0-rc3-pmac-00077-gc9f6e8dd045
Loading kernel module apm_emu.
modprobe: FATAL: Module apm_emu not found in directory /lib/modules/5.12.0-rc3-pmac-00077-gc9f6e8dd045
Loading kernel module bmac.
modprobe: FATAL: Module bmac not found in directory /lib/modules/5.12.0-rc3-pmac-00077-gc9f6e8dd045
Loading kernel module mesh.
modprobe: FATAL: Module mesh not found in directory /lib/modules/5.12.0-rc3-pmac-00077-gc9f6e8dd045
LoadinEXT4-fs (sda15): mounting ext3 file system using the ext4 subsystem
g kernel module snd-powermac.
modprobe: FATAL: Module snd-powermac not found in directory /lib/modules/5.12.0-rc3-pmac-00077-gc9f6e8dd045
EXT4-fs (sda15): mounted filesystem with ordered data mode. Opts: (null). Quota mode: disabled.
Mounting local filesystems...done.
Activating swapfile swap, if any...done.
Cleaning up temporary files....
Starting Setting kernel variables: sysctl.
Configuring network interfaces...done.
Cleaning up temporary files....
Setting up X socket directories... /tmp/.X11-unix /tmp/.ICE-unix
.
INIT: Entering runlevel: 2
Using makefile-style concurrent boot in runlevel 2.
Setting up console font and keymap...done.
Recovering nvi editor sessions.
none found.
Starting enhanced syslogd: rsyslogd.
Starting periodic command scheduler: cron.
Starting system message bus: dbus.
Starting OpenBSD Secure Shell server: sshd.
Starting S.M.A.R.T. daemon: smartd.
Starting WINGs display manager: wdm:.
Deconfiguring network interfaces...
done.
phy registers:
 0000 0000 0000 0000 0000 0000 0000 0000
 0000 0000 0000 0000 0000 0000 0000 0000
 0000 0000 0000 0000 0000 0000 0000 0000
 0000 0000 0000 0000 0000 0000 0000 0000

Debian GNU/Linux 11 mac-server ttyS0

mac-server login: xfce4-session[1775]: bus error (7) at b3976078 nip aefb1710 lr aefb16e0 code 3 in libLLVM-11.so.1[ae83e000+4d1b000
]
xfce4-session[1775]: code: 7fc802a6 807effac 7fc3f214 835e8054 82fe8134 82de8138 82be813c 80fe8140
xfce4-session[1775]: code: 38600020 90610014 a09a0006 7f45d378 <96e50030> 38da0048 548407fe 90da0034
------------[ cut here ]------------
WARNING: CPU: 0 PID: 1657 at arch/powerpc/mm/fault.c:357 do_page_fault+0x70/0x6b4
Modules linked in:
CPU: 0 PID: 1657 Comm: Xorg Not tainted 5.12.0-rc3-pmac-00077-gc9f6e8dd045 #2
NIP:  c001a094 LR: c001a1d4 CTR: b12622f4
REGS: e2c65e40 TRAP: 0700   Not tainted  (5.12.0-rc3-pmac-00077-gc9f6e8dd045)
MSR:  00021032 <ME,IR,DR,RI>  CR: 44c24f38  XER: 00000000

GPR00: c0004320 e2c65f00 c1562260 e2c65f40 00000000 40000000 04544060 00000000
GPR08: c1562260 38a00000 08000000 e2c65f30 44c65f30 0094fff0 00000000 00000000
GPR16: 00813458 008102f8 00000001 00000063 00000a7a 00000001 b7aee478 00000000
GPR24: 00000001 00000000 00000000 00000000 c1e71240 b12622f4 00000400 e2c65f40
NIP [c001a094] do_page_fault+0x70/0x6b4
LR [c001a1d4] do_page_fault+0x1b0/0x6b4
Call Trace:
[e2c65f00] [c001a164] do_page_fault+0x140/0x6b4 (unreliable)
[e2c65f30] [c0004320] InstructionAccess_virt+0xc4/0xc8
--- interrupt: 400 at 0xb12622f4
NIP:  b12622f4 LR: b7941100 CTR: b12622f4
REGS: e2c65f40 TRAP: 0400   Not tainted  (5.12.0-rc3-pmac-00077-gc9f6e8dd045)
MSR:  4000d032 <EE,PR,ME,IR,DR,RI>  CR: 24000424  XER: 00000000

GPR00: b7941100 bfbd6eb0 b73f45c0 b52c8df8 00000000 b4ed8df8 04544060 00000007
GPR08: b7aed64c b12622f4 aceadebe b7999b70 b7999b70 0094fff0 00000000 00000000
GPR16: 00813458 008102f8 00000001 00000063 00000a7a 00000001 b7aee478 00000000
GPR24: 00000001 00000000 00000000 009e9290 b7aee530 b7aee538 b7aecff4 009e9380
NIP [b12622f4] 0xb12622f4
LR [b7941100] 0xb7941100
--- interrupt: 400
Instruction dump:
83c300a0 752a8410 83820298 553b018c 83a300a4 57de0034 2e0a0000 40920360
2d9b0000 408e0264 752a0800 4182025c <0fe00000> 41920254 81220594 7c4a1378
---[ end trace c40b220173ea820f ]---
------------[ cut here ]------------
kernel BUG at arch/powerpc/kernel/interrupt.c:49!
Oops: Exception in kernel mode, sig: 5 [#1]
BE PAGE_SIZE=4K MMU=Hash SMP NR_CPUS=2 PowerMac
Modules linked in:
CPU: 0 PID: 1657 Comm: Xorg Tainted: G        W         5.12.0-rc3-pmac-00077-gc9f6e8dd045 #2
NIP:  c0010e4c LR: c0010e3c CTR: b79d2b10
REGS: e2c65e40 TRAP: 0700   Tainted: G        W          (5.12.0-rc3-pmac-00077-gc9f6e8dd045)
MSR:  00021032 <ME,IR,DR,RI>  CR: 44002424  XER: 00000000

GPR00: c00150c0 e2c65f00 c1562260 b7323030 00000001 00000003 b7aeefec 00000004
GPR08: b716c994 00000001 50db435b 4e800020 c1562810 0094fff0 00000000 b716c994
GPR16: 00813458 009acf90 b7d5d058 bfbd6e40 00000000 b7d76cb8 bfbd6d9c 00000019
GPR24: b7323030 b716c994 00000004 b7aeefec 00000003 00000001 e2c65f40 00000014
NIP [c0010e4c] system_call_exception+0x60/0x164
LR [c0010e3c] system_call_exception+0x50/0x164
Call Trace:
[e2c65f00] [c001a164] do_page_fault+0x140/0x6b4 (unreliable)
[e2c65f30] [c00150c0] ret_from_syscall+0x0/0x28
--- interrupt: c00 at 0xb79d2b18
NIP:  b79d2b18 LR: b71417f8 CTR: b7d50a94
REGS: e2c65f40 TRAP: 0c00   Tainted: G        W          (5.12.0-rc3-pmac-00077-gc9f6e8dd045)
MSR:  0000d032 <EE,PR,ME,IR,DR,RI>  CR: 44002424  XER: 00000000

GPR00: 00000014 bfbd6cf0 b73f45c0 b7323030 00000001 00000003 b7aeefec 00000004
GPR08: b716c994 b716cf90 b7907684 00000003 44002424 0094fff0 00000000 b716c994
GPR16: 00813458 009acf90 b7d5d058 bfbd6e40 00000000 b7d76cb8 bfbd6d9c 00000019
GPR24: b7d78534 b7d78030 00000043 00000000 b7d78030 00000000 b7174be8 bfbd6e40
NIP [b79d2b18] 0xb79d2b18
LR [b71417f8] 0xb71417f8
--- interrupt: c00
Instruction dump:
7cdb3378 93810020 7cbc2b78 93a10024 7c9d2378 93e1002c 7d3f4b78 4800cacd
817e0084 931e0088 69690002 5529fffe <0f090000> 69694000 552997fe 0f090000
---[ end trace c40b220173ea8210 ]---

------------[ cut here ]------------
kernel BUG at arch/powerpc/kernel/interrupt.c:49!
Oops: Exception in kernel mode, sig: 5 [#2]
BE PAGE_SIZE=4K MMU=Hash SMP NR_CPUS=2 PowerMac
Modules linked in:
CPU: 0 PID: 1850 Comm: Xorg Tainted: G      D W         5.12.0-rc3-pmac-00077-gc9f6e8dd045 #2
NIP:  c0010e4c LR: c0010e3c CTR: b7995b20
REGS: e1075e40 TRAP: 0700   Tainted: G      D W          (5.12.0-rc3-pmac-00077-gc9f6e8dd045)
MSR:  00021032 <ME,IR,DR,RI>  CR: 420084ec  XER: 00000000

GPR00: c00150c0 e1075f00 c2a9ace0 ada73280 0000000c b7ad60cc ada73904 b7ad57cc
GPR08: ada73900 00000001 50185ccb 7ca42378 c2a9b290 00d8fff0 00801000 00313308
GPR16: 003112a8 00000000 00e483d0 b5aeedc0 bfb3aef8 00313300 00000000 00000000
GPR24: ada73280 ada73900 b7ad57cc ada73904 b7ad60cc 0000000c e1075f40 0000012c
NIP [c0010e4c] system_call_exception+0x60/0x164
LR [c0010e3c] system_call_exception+0x50/0x164
Call Trace:
[e1075f00] [bfb3ae6c] 0xbfb3ae6c (unreliable)
[e1075f30] [c00150c0] ret_from_syscall+0x0/0x28
--- interrupt: c00 at 0x2d970c
NIP:  002d970c LR: 002d96dc CTR: b7a76874
REGS: e1075f40 TRAP: 0c00   Tainted: G      D W          (5.12.0-rc3-pmac-00077-gc9f6e8dd045)
MSR:  0000d932 <EE,PR,ME,IR,DR,RI>  CR: 420084ec  XER: 20000000

GPR00: 0000012c ada72b50 ada7a6e0 ada73280 0000000c b7ad60cc ada73904 b7ad57cc
GPR08: ada73900 ada73278 ffffffff b7a76874 280044ec 00d8fff0 00801000 00313308
GPR16: 003112a8 00000000 00e483d0 b5aeedc0 bfb3aef8 00313300 00000000 00000000
GPR24: ada73270 ada72d80 ada73210 bfb3ae6b 003d0f00 ada73210 00310ff4 ada72b50
NIP [002d970c] 0x2d970c
LR [002d96dc] 0x2d96dc
--- interrupt: c00
Instruction dump:
7cdb3378 93810020 7cbc2b78 93a10024 7c9d2378 93e1002c 7d3f4b78 4800cacd
817e0084 931e0088 69690002 5529fffe <0f090000> 69694000 552997fe 0f090000
---[ end trace c40b220173ea8211 ]---


mac-server login: root
Password:
Linux mac-server 5.12.0-rc3-pmac-00077-gc9f6e8dd045 #2 SMP Wed Aug 4 22:35:13 MDT 2021 ppc

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Wed Aug  4 22:32:58 MDT 2021 on ttyS0
root@mac-server:~# shutdown -r now

Broadcast message from root@mac-server (ttyS0) (Wed Aug  4 22:50:57 2021):

The system is going down for reboot NOW!
INIT: Sending processes configured vUsing makefile-style concurrent boot in runlevel 6.
Stopping mouse emulation daemon: mouseemu.
Stopping hotplug events dispatcher: systemd-udevd.
Stopping S.M.A.R.T. daemon: smartd.
Stopping WINGs display manager: wdm:
Asking all remaining processes to terminate...done.
Currently running processes (pstree):
init-+-rc---startpar---sendsigs---pstree
     |-rsyslogd---3*[{rsyslogd}]
     `-wdm---wdm---Xorg---3*[{Xorg}]
Killing all remaining processes...failed.
Stopping enhanced syslogd: rsyslogd.
Saving the system clock to /dev/rtc0.
Hardware Clock updated to Wed Aug  4 22:51:21 MDT 2021.
Deconfiguring network interfaces...done.
Deactivating swap...done.
Unmounting local filesystems...done.
EXT4-fs (sda12): re-mounted. Opts: (null). Quota mode: disabled.
Will now restart.
sd 2:0:0:0: [sdb] Synchronizing SCSI cache
resetting MESH scsi bus(es)
reboot: Restarting system

[-- Attachment #4: Type: text/plain, Size: 22621 bytes --]

printk: console [ttyS0] enabled
printk: bootconsole [udbg0] disabled
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
rcu: Hierarchical SRCU implementation.
smp: Bringing up secondary CPUs ...
smp: Brought up 1 node, 1 CPU
devtmpfs: initialized
Duplicate name in PowerPC,750, renamed to "l2-cache#1"
Duplicate name in pci, renamed to "mac-io#1"
Duplicate name in pci, renamed to "pccard#1"
Found Grackle (MPC106) PCI host bridge at 0x0000000080000000. Firmware bus number: 0->0
PCI host bridge /pci (primary) ranges:
  IO 0x00000000fe000000..0x00000000fe7fffff -> 0x0000000000000000
 MEM 0x00000000fd000000..0x00000000fdffffff -> 0x0000000000000000
 MEM 0x0000000080000000..0x00000000fcffffff -> 0x0000000080000000
clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
futex hash table entries: 512 (order: 2, 16384 bytes, linear)
NET: Registered protocol family 16
PMU i2c /pci/mac-io/via-pmu
 channel 1 bus <multibus>
 channel 2 bus <multibus>
PCI: Probing PCI hardware
PCI host bridge to bus 0000:00
pci_bus 0000:00: root bus resource [io  0x0000-0x7fffff]
pci_bus 0000:00: root bus resource [mem 0xfd000000-0xfdffffff] (bus address [0x00000000-0x00ffffff])
pci_bus 0000:00: root bus resource [mem 0x80000000-0xfcffffff]
pci_bus 0000:00: root bus resource [bus 00-ff]
pci_bus 0000:00: busn_res: [bus 00-ff] end is updated to ff
pci 0000:00:00.0: [1057:0002] type 00 class 0x060000
pci 0000:00:0d.0: [106b:0017] type 00 class 0xff0000
pci 0000:00:0d.0: reg 0x10: [mem 0xf4000000-0xf407ffff]
pci 0000:00:10.0: [106b:0017] type 00 class 0xff0000
pci 0000:00:10.0: reg 0x10: [mem 0xf3000000-0xf307ffff]
pci 0000:00:11.0: [1002:4c50] type 00 class 0x038000
pci 0000:00:11.0: reg 0x10: [mem 0x82000000-0x82ffffff]
pci 0000:00:11.0: reg 0x14: [io  0x0400-0x04ff]
pci 0000:00:11.0: reg 0x18: [mem 0x82fff000-0x82ffffff]
pci 0000:00:11.0: reg 0x30: [mem 0xfd000000-0xfd01ffff pref]
pci 0000:00:11.0: supports D1 D2
pci 0000:00:13.0: [104c:ac15] type 02 class 0x060700
pci 0000:00:13.0: reg 0x10: [mem 0x81803000-0x81803fff]
pci 0000:00:13.1: [104c:ac15] type 02 class 0x060700
pci 0000:00:13.1: reg 0x10: [mem 0x81802000-0x81802fff]
pci_bus 0000:01: extended config space not accessible
pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 04
pci_bus 0000:05: extended config space not accessible
pci_bus 0000:05: busn_res: [bus 05-ff] end is updated to 08
pci_bus 0000:00: busn_res: [bus 00-ff] end is updated to 08
PCI: Cannot allocate resource region 2 of device 0000:00:11.0, will remap
PCI 0000:00 Cannot reserve Legacy IO [io  0x0000-0x0fff]
pci 0000:00:13.0: BAR 9: assigned [mem 0x84000000-0x87ffffff pref]
pci 0000:00:13.0: BAR 10: assigned [mem 0x88000000-0x8bffffff]
pci 0000:00:13.1: BAR 9: assigned [mem 0x8c000000-0x8fffffff pref]
pci 0000:00:13.1: BAR 10: assigned [mem 0x90000000-0x93ffffff]
pci 0000:00:11.0: BAR 6: assigned [mem 0xfd000000-0xfd01ffff pref]
pci 0000:00:11.0: BAR 2: assigned [mem 0xfd020000-0xfd020fff]
pci 0000:00:13.0: BAR 7: assigned [io  0x1000-0x10ff]
pci 0000:00:13.0: BAR 8: assigned [io  0x1100-0x11ff]
pci 0000:00:13.1: BAR 7: assigned [io  0x1200-0x12ff]
pci 0000:00:13.1: BAR 8: assigned [io  0x1300-0x13ff]
pci 0000:00:13.0: CardBus bridge to [bus 01-04]
pci 0000:00:13.0:   bridge window [io  0x1000-0x10ff]
pci 0000:00:13.0:   bridge window [io  0x1100-0x11ff]
pci 0000:00:13.0:   bridge window [mem 0x84000000-0x87ffffff pref]
pci 0000:00:13.0:   bridge window [mem 0x88000000-0x8bffffff]
pci 0000:00:13.1: CardBus bridge to [bus 05-08]
pci 0000:00:13.1:   bridge window [io  0x1200-0x12ff]
pci 0000:00:13.1:   bridge window [io  0x1300-0x13ff]
pci 0000:00:13.1:   bridge window [mem 0x8c000000-0x8fffffff pref]
pci 0000:00:13.1:   bridge window [mem 0x90000000-0x93ffffff]
pci_bus 0000:00: resource 4 [io  0x0000-0x7fffff]
pci_bus 0000:00: resource 5 [mem 0xfd000000-0xfdffffff]
pci_bus 0000:00: resource 6 [mem 0x80000000-0xfcffffff]
pci_bus 0000:01: resource 0 [io  0x1000-0x10ff]
pci_bus 0000:01: resource 1 [io  0x1100-0x11ff]
pci_bus 0000:01: resource 2 [mem 0x84000000-0x87ffffff pref]
pci_bus 0000:01: resource 3 [mem 0x88000000-0x8bffffff]
pci_bus 0000:05: resource 0 [io  0x1200-0x12ff]
pci_bus 0000:05: resource 1 [io  0x1300-0x13ff]
pci_bus 0000:05: resource 2 [mem 0x8c000000-0x8fffffff pref]
pci_bus 0000:05: resource 3 [mem 0x90000000-0x93ffffff]
vgaarb: loaded
SCSI subsystem initialized
libata version 3.00 loaded.
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
clocksource: Switched to clocksource timebase
NET: Registered protocol family 2
tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 6144 bytes, linear)
TCP established hash table entries: 4096 (order: 2, 16384 bytes, linear)
TCP bind hash table entries: 4096 (order: 3, 32768 bytes, linear)
TCP: Hash tables configured (established 4096 bind 4096)
UDP hash table entries: 256 (order: 1, 8192 bytes, linear)
UDP-Lite hash table entries: 256 (order: 1, 8192 bytes, linear)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
PCI: CLS 32 bytes, default 32
Thermal assist unit using workqueue, shrink_timer: 2000 ms
workingset: timestamp_bits=30 max_order=17 bucket_order=0
squashfs: version 4.0 (2009/01/31) Phillip Lougher
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
io scheduler mq-deadline registered
pci 0000:00:11.0: enabling device (0086 -> 0087)
Using unsupported 1024x768 (null) at 82801000, depth=32, pitch=4096
Console: switching to colour frame buffer device 128x48
fb0: Open Firmware frame buffer device on /pci/ATY,RageLTPro
pmac_zilog: 0.6 (Benjamin Herrenschmidt <benh@kernel.crashing.org>)
Non-volatile memory driver v1.3
brd: module loaded
loop: module loaded
MacIO PCI driver attached to Gatwick chipset
MacIO PCI driver attached to Heathrow chipset
swim3 0.00015000:floppy: [fd0] SWIM3 floppy controller in media bay
0.00013020:ch-a: ttyS0 at MMIO 0xf3013020 (irq = 16, base_baud = 230400) is a Z85c30 ESCC - Serial port
0.00013000:ch-b: ttyS1 at MMIO 0xf3013000 (irq = 17, base_baud = 230400) is a Z85c30 ESCC - Infrared port
macio: fixed media-bay irq on gatwick
macio: fixed left floppy irqs
swim3 1.00015000:floppy: [fd1] Couldn't request interrupt
swim3: probe of 1.00015000:floppy failed with error -16
macio: fixed left ide irqs
macio: fixed SCC irqs on gatwick
1.00013020:ch-a: ttyS2 at MMIO 0xf4013020 (irq = 79, base_baud = 230400) is a Z85c30 ESCC - Internal modem
mediabay0: Registered Heathrow media-bay
mediabay1: Registered Heathrow media-bay
mediabay0: Bay contains an ATA device
PMU Backlight initialized (pmubl)
mesh: configured for synchronous 5 MB/s
mediabay1: Bay contains a floppy drive
mesh: performing initial bus reset...
random: fast init done
adb device [2]: 2 0xC3
adb device [3]: 3 0x1
adb device [7]: 7 0x1F
ADB keyboard at 2 has handler 0xC3
Detected ADB keyboard, type ANSI.
input: ADB keyboard as /devices/virtual/input/input0
input: ADB Powerbook buttons as /devices/virtual/input/input1
ADB mouse (trackpad) at 3 has handler 0x4
input: ADB mouse as /devices/virtual/input/input2
scsi host0: MESH
pata-macio 0.00020000:ata0: Activating pata-macio chipset Heathrow ATA, Apple bus ID 0
scsi host1: pata_macio
ata1: PATA max MWDMA2 irq 30
ata1.00: ATA-7: SAMSUNG HM100JC, YN100-08, max UDMA/100
ata1.00: 195371568 sectors, multi 8: LBA48
scsi 1:0:0:0: Direct-Access     ATA      SAMSUNG HM100JC  0-08 PQ: 0 ANSI: 5
sd 1:0:0:0: [sda] 195371568 512-byte logical blocks: (100 GB/93.2 GiB)
sd 1:0:0:0: Attached scsi generic sg0 type 0
sd 1:0:0:0: [sda] Write Protect is off
sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 1:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
pata-macio 0.00021000:ata1: Activating pata-macio chipset Heathrow ATA, Apple bus ID 1
scsi host2: pata_macio
ata2: PATA max MWDMA2 irq 36
pata-macio 1.00021000:ata4: Activating pata-macio chipset Heathrow ATA, Apple bus ID 4
genirq: Flags mismatch irq 36. 00000000 (pata-macio[1.00021000:ata4]) vs. 00000000 (pata-macio[0.00021000:ata1])
pata-macio: probe of 1.00021000:ata4 failed with error -16
ata2.00: ATA-6: ST9160821A, 3.ALD, max UDMA/100
ata2.00: 312581808 sectors, multi 0: LBA48
eth0: BMAC at 00:05:02:07:5a:a6

aoe: AoE v85 initialised.
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-pci: EHCI PCI platform driver
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
ohci-pci: OHCI PCI platform driver
usbcore: registered new interface driver uas
usbcore: registered new interface driver usb-storage
mousedev: PS/2 mouse device common for all mice
rtc-generic rtc-generic: registered as rtc0
i2c /dev entries driver
PowerMac i2c bus pmu 2 registered
PowerMac i2c bus pmu 1 registered
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
NET: Registered protocol family 17
drmem: No dynamic reconfiguration memory found
 sda: [mac] sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10 sda11 sda12 sda13 sda14 sda15
sd 1:0:0:0: [sda] Attached SCSI disk
scsi 2:0:0:0: Direct-Access     ATA      ST9160821A       D    PQ: 0 ANSI: 5
sd 2:0:0:0: [sdb] 312581808 512-byte logical blocks: (160 GB/149 GiB)
sd 2:0:0:0: Attached scsi generic sg1 type 0
sd 2:0:0:0: [sdb] Write Protect is off
sd 2:0:0:0: [sdb] Mode Sense: 00 3a 00 00
sd 2:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sdb: [mac] sdb1 sdb2 sdb3 sdb4 sdb5 sdb6 sdb7 sdb8 sdb9 sdb10 sdb11 sdb12 sdb13 sdb14
sd 2:0:0:0: [sdb] Attached SCSI disk
EXT4-fs (sda12): mounting ext3 file system using the ext4 subsystem
EXT4-fs (sda12): mounted filesystem with ordered data mode. Opts: (null). Quota mode: disabled.
VFS: Mounted root (ext3 filesystem) readonly on device 8:12.
Freeing unused kernel memory: 1228K
Kernel memory protection not selected by kernel config.
Run /sbin/init as init process
  with arguments:
    /sbin/init
  with environment:
    HOME=/
    TERM=linux
INIT: version 2.96 booting
Using makefile-style concurrent boot in runlevel S.
findfs: unable to resolve 'LABEL=Debian_sid'
Starting hotplug events dispatcher: systemd-udevd.
Synthesizing the initial hotplug events (subsystems)...done.
Synthesizing the initial hotplug events (devices)...done.
Waiting for /dev to be fully populated...random: crng init done
phy registers:
 0000 0000 0000 0000 0000 0000 0000 0000
 0000 0000 0000 0000 0000 0000 0000 0000
 0000 0000 0000 0000 0000 0000 0000 0000
 0000 0000 0000 0000 0000 0000 0000 0000
done.
Setting up keyboard layout...done.
Activating swap...Adding 524284k swap on /dev/sda14.  Priority:-2 extents:1 across:524284k
done.
EXT4-fs (sda12): re-mounted. Opts: (null). Quota mode: disabled.
Checking root file system...Debian_sid: clean, 76262/524288 files, 1036605/2097152 blocks
done.
EXT4-fs (sda12): re-mounted. Opts: errors=remount-ro. Quota mode: disabled.
Checking file systems...data: clean, 83287/3325952 files, 2159937/13280326 blocks
done.
Cleaning up temporary files...
 /tmp.
Loading kernel module lp.
modprobe: FATAL: Module lp not found in directory /lib/modules/5.12.0-rc3-pmac-00077-ge06b29ce146
Loading kernel module ppdev.
modprobe: FATAL: Module ppdev not found in directory /lib/modules/5.12.0-rc3-pmac-00077-ge06b29ce146
Loading kernel module parport_pc.
modprobe: FATAL: Module parport_pc not found in directory /lib/modules/5.12.0-rc3-pmac-00077-ge06b29ce146
Loading kernel module apm_emu.
modprobe: FATAL: Module apm_emu not found in directory /lib/modules/5.12.0-rc3-pmac-00077-ge06b29ce146
Loading kernel module bmac.
modprobe: FATAL: Module bmac not found in directory /lib/modules/5.12.0-rc3-pmac-00077-ge06b29ce146
Loading kernel module mesh.
modprobe: FATAL: Module mesh not found in directory /lib/modules/5.12.0-rc3-pmac-00077-ge06b29ce146
Loading kernel module snd-powermac.
modprobe: FATAL: Module snd-powermac not found in directory /lib/modules/5.12.0-rc3-pmac-00077-ge06b29ce146
EXT4-fs (sda15): mounting ext3 file system using the ext4 subsystem
EXT4-fs (sda15): mounted filesystem with ordered data mode. Opts: (null). Quota mode: disabled.
Mounting local filesystems...done.
Activating swapfile swap, if any...done.
Cleaning up temporary files....
Starting Setting kernel variables: sysctl.
Configuring network interfaces...done.
Cleaning up temporary files....
Setting up X socket directories... /tmp/.X11-unix /tmp/.ICE-unix
.
INIT: Entering runlevel: 2
Using makefile-style concurrent boot in runlevel 2.
Setting up console font and keymap...done.
Recovering nvi editor sessions.
none found.
Starting enhanced syslogd: rsyslogd.
Starting periodic command scheduler: cron.
Starting system message bus: dbus.
Starting OpenBSD Secure Shell server: sshd.
Starting S.M.A.R.T. daemon: smartd.
Starting WINGs display manager: wdm:.
Deconfiguring network interfaces...
done.
phy registers:
 0000 0000 0000 0000 0000 0000 0000 0000
 0000 0000 0000 0000 0000 0000 0000 0000
 0000 0000 0000 0000 0000 0000 0000 0000
 0000 0000 0000 0000 0000 0000 0000 0000

Debian GNU/Linux 11 mac-server ttyS0

mac-server login: ------------[ cut here ]------------
kernel BUG at arch/powerpc/kernel/interrupt.c:50!
Oops: Exception in kernel mode, sig: 5 [#1]
BE PAGE_SIZE=4K MMU=Hash SMP NR_CPUS=2 PowerMac
Modules linked in:
CPU: 0 PID: 1878 Comm: xfdesktop Not tainted 5.12.0-rc3-pmac-00077-ge06b29ce146 #3
NIP:  c0010e58 LR: c0010e3c CTR: b699b7b0
REGS: e2ec9e40 TRAP: 0700   Not tainted  (5.12.0-rc3-pmac-00077-ge06b29ce146)
MSR:  00021032 <ME,IR,DR,RI>  CR: 24422202  XER: 00000000

GPR00: c00150c0 e2ec9f00 ce430160 00000016 00000000 00000000 00000000 b09c1000
GPR08: 00000007 00000001 501894db 152233ff ce430710 0093f34c 00b93eb8 00000000
GPR16: 001cb710 00000004 00000185 00000000 00000400 00000002 0090a8c8 0090a8c0
GPR24: 00000016 00000007 b09c1000 00000000 00000000 00000000 e2ec9f40 00000075
NIP [c0010e58] system_call_exception+0x6c/0x164
LR [c0010e3c] system_call_exception+0x50/0x164
Call Trace:
[e2ec9f00] [e2ec9f04] 0xe2ec9f04 (unreliable)
[e2ec9f30] [c00150c0] ret_from_syscall+0x0/0x28
--- interrupt: c00 at 0xb699b7ec
NIP:  b699b7ec LR: b6f76050 CTR: 00000004
REGS: e2ec9f40 TRAP: 0c00   Not tainted  (5.12.0-rc3-pmac-00077-ge06b29ce146)
MSR:  0000d032 <EE,PR,ME,IR,DR,RI>  CR: 24422202  XER: 20000000

GPR00: 00000075 bfe27390 b53e94e0 00000016 00000000 00000000 00000000 b09c1000
GPR08: 00000007 000000ff 00000015 b6eebef0 000002ff 0093f34c 00b93eb8 00000000
GPR16: 001cb710 00000004 00000185 00000000 00000400 00000002 0090a8c8 0090a8c0
GPR24: 00b01c80 00000300 00000400 00b52730 000001c4 00b48a30 b6a6fff4 00a20bd0
NIP [b699b7ec] 0xb699b7ec
LR [b6f76050] 0xb6f76050
--- interrupt: c00
Instruction dump:
93a10024 7c9d2378 93e1002c 7d3f4b78 4800cacd 817e0084 931e0088 69690002
5529fffe 0f090000 69694000 552997fe <0f090000> 696b8000 556b8ffe 0f0b0000
---[ end trace 97c12cfe3c8acf20 ]---

------------[ cut here ]------------
kernel BUG at arch/powerpc/kernel/interrupt.c:50!
Oops: Exception in kernel mode, sig: 5 [#2]
BE PAGE_SIZE=4K MMU=Hash SMP NR_CPUS=2 PowerMac
Modules linked in:
CPU: 0 PID: 1881 Comm: gmain Tainted: G      D           5.12.0-rc3-pmac-00077-ge06b29ce146 #3
NIP:  c0010e58 LR: c0010e3c CTR: b699983c
REGS: e2ee1e40 TRAP: 0700   Tainted: G      D            (5.12.0-rc3-pmac-00077-ge06b29ce146)
MSR:  00021032 <ME,IR,DR,RI>  CR: 48004444  XER: 00000000

GPR00: c00150c0 e2ee1f00 c1565540 0000000d 00b78a80 01002fce b4f66a34 b4602ef0
GPR08: b4602ef0 00000001 501894db 152233ff c1565af0 0093f34c 00801000 0018d308
GPR16: 0018b2a8 00000000 009806f0 00000000 b6add680 00000000 00a16130 b4f66a34
GPR24: 0000000d b4602ef0 b4602ef0 b4f66a34 01002fce 00b78a80 e2ee1f40 00000114
NIP [c0010e58] system_call_exception+0x6c/0x164
LR [c0010e3c] system_call_exception+0x50/0x164
Call Trace:
[e2ee1f00] [c0154c1c] ksys_read+0x70/0x118 (unreliable)
[e2ee1f30] [c00150c0] ret_from_syscall+0x0/0x28
--- interrupt: c00 at 0xb6999844
NIP:  b6999844 LR: b6dc63cc CTR: b6abfc10
REGS: e2ee1f40 TRAP: 0c00   Tainted: G      D            (5.12.0-rc3-pmac-00077-ge06b29ce146)
MSR:  0000d032 <EE,PR,ME,IR,DR,RI>  CR: 48004444  XER: 00000000

GPR00: 00000114 b4f66970 b4f6e6e0 0000000d 00b78a80 01002fce b4f66a34 b4602ef0
GPR08: b4602ef0 43300000 b6b54ea0 b6ad9ca0 28004444 0093f34c 00801000 0018d308
GPR16: 0018b2a8 00000000 009806f0 00000000 b6add680 00000000 00a16130 b4f66a34
GPR24: b4f66a38 00000000 b6ea5310 b6ea6370 00000000 b4f669a8 b6eabebc 00b8b850
NIP [b6999844] 0xb6999844
LR [b6dc63cc] 0xb6dc63cc
--- interrupt: c00
Instruction dump:
93a10024 7c9d2378 93e1002c 7d3f4b78 4800cacd 817e0084 931e0088 69690002
5529fffe 0f090000 69694000 552997fe <0f090000> 696b8000 556b8ffe 0f0b0000
---[ end trace 97c12cfe3c8acf21 ]---

------------[ cut here ]------------
kernel BUG at arch/powerpc/kernel/interrupt.c:50!
Oops: Exception in kernel mode, sig: 5 [#3]
BE PAGE_SIZE=4K MMU=Hash SMP NR_CPUS=2 PowerMac
Modules linked in:
CPU: 0 PID: 1912 Comm: pool-xfdesktop Tainted: G      D           5.12.0-rc3-pmac-00077-ge06b29ce146 #3
NIP:  c0010e58 LR: c0010e3c CTR: c014069c
REGS: e2f09e40 TRAP: 0700   Tainted: G      D            (5.12.0-rc3-pmac-00077-ge06b29ce146)
MSR:  00021032 <ME,IR,DR,RI>  CR: 284284ec  XER: 20000000

GPR00: c00150c0 e2f09f00 ce562b60 00000000 00153978 484284ec b38d9000 00000000
GPR08: 00000000 00000001 501894db 152233ff ce563110 0093f34c 00801000 0018d308
GPR16: 0018b2a8 00000000 00b6ad30 b6b49eb0 00b6ad50 0018d300 00000000 00000000
GPR24: 00000000 00000000 00000000 b38d9000 484284ec 00153978 e2f09f40 00000001
NIP [c0010e58] system_call_exception+0x6c/0x164
LR [c0010e3c] system_call_exception+0x50/0x164
Call Trace:
[e2f09f00] [0018d300] 0x18d300 (unreliable)
[e2f09f30] [c00150c0] ret_from_syscall+0x0/0x28
--- interrupt: c00 at 0x15381c
NIP:  0015381c LR: 00153984 CTR: 00000000
REGS: e2f09f40 TRAP: 0c00   Tainted: G      D            (5.12.0-rc3-pmac-00077-ge06b29ce146)
MSR:  0000d032 <EE,PR,ME,IR,DR,RI>  CR: 284284ec  XER: 00000000

GPR00: 00000001 b38f9b50 b39016e0 00000000 00153978 484284ec b38d9000 00000000
GPR08: 00000000 b38f9a80 00000000 610b7076 ce563110 0093f34c 00801000 0018d308
GPR16: 0018b2a8 00000000 00b6ad30 b6b49eb0 00b6ad50 0018d300 00000000 00000000
GPR24: b38fa270 b38f9d80 b38fa210 bfe26d0b b30fa000 b38fa210 0018aff4 b38f9b50
NIP [0015381c] 0x15381c
LR [00153984] 0x153984
--- interrupt: c00
Instruction dump:
93a10024 7c9d2378 93e1002c 7d3f4b78 4800cacd 817e0084 931e0088 69690002
5529fffe 0f090000 69694000 552997fe <0f090000> 696b8000 556b8ffe 0f0b0000
---[ end trace 97c12cfe3c8acf22 ]---


mac-server login: root
Password:
Linux mac-server 5.12.0-rc3-pmac-00077-ge06b29ce146 #3 SMP Wed Aug 4 22:52:47 MDT 2021 ppc

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Wed Aug  4 22:50:51 MDT 2021 on ttyS0
root@mac-server:~# shutdown -r now

Broadcast message from root@mac-server (ttyS0) (Wed Aug  4 23:01:42 2021):

The system is going down for reboot NOW!

Broadcast message from root@mac-server (ttyS0) (Wed Aug  4 23:01:42 2021):

The system is going down for reboot NOW!
INIT: Sending processes configured via /etUsing makefile-style concurrent boot in runlevel 6.
Stopping mouse emulation daemon: mouseemu.
Stopping S.M.A.R.T. daemon: smartd.
Stopping hotplug events dispatcher: systemd-udevd.
------------[ cut here ]------------
kernel BUG at arch/powerpc/kernel/interrupt.c:50!
Oops: Exception in kernel mode, sig: 5 [#4]
BE PAGE_SIZE=4K MMU=Hash SMP NR_CPUS=2 PowerMac
Modules linked in:
CPU: 0 PID: 1882 Comm: gdbus Tainted: G      D           5.12.0-rc3-pmac-00077-ge06b29ce146 #3
NIP:  c0010e58 LR: c0010e3c CTR: 00000000
REGS: e2ee5e40 TRAP: 0700   Tainted: G      D            (5.12.0-rc3-pmac-00077-ge06b29ce146)
MSR:  00021032 <ME,IR,DR,RI>  CR: 40004424  XER: 20000000

GPR00: c00150c0 e2ee5f00 ce4721a0 00000004 00162c38 20004424 00000000 00162c50
GPR08: 0000d032 00000001 501894db 152233ff ce472750 0093f34c 00801000 0018d308
GPR16: 0018b2a8 00000000 00980798 b6b49eb0 009807b8 0018d300 00000000 00000000
GPR24: 00000004 0000d032 00162c50 00000000 20004424 00162c38 e2ee5f40 00000077
NIP [c0010e58] system_call_exception+0x6c/0x164
LR [c0010e3c] system_call_exception+0x50/0x164
Call Trace:
[e2ee5f00] [c0154dd0] ksys_write+0x100/0x118 (unreliable)
[e2ee5f30] [c00150c0] ret_from_syscall+0x0/0x28
--- interrupt: c00 at 0x1013bc
NIP:  001013bc LR: 001013b4 CTR: 00000000
REGS: e2ee5f40 TRAP: 0c00   Tainted: G      D            (5.12.0-rc3-pmac-00077-ge06b29ce146)
MSR:  0000d032 <EE,PR,ME,IR,DR,RI>  CR: 40004424  XER: 00000000

GPR00: 00000077 b45fe510 b46066e0 00000004 00162c38 20004424 00000000 00162c50
GPR08: 0000d032 43300000 b6b54ea0 b691cb70 40004424 0093f34c 00801000 0018d308
GPR16: 0018b2a8 00000000 00980798 b6b49eb0 009807b8 0018d300 00000000 00000000
GPR24: 00000001 ffffffff b45fea88 b6af0b80 00000000 009bb090 b6a6fff4 ffffffff
NIP [001013bc] 0x1013bc
LR [001013b4] 0x1013b4
--- interrupt: c00
Instruction dump:
93a10024 7c9d2378 93e1002c 7d3f4b78 4800cacd 817e0084 931e0088 69690002
5529fffe 0f090000 69694000 552997fe <0f090000> 696b8000 556b8ffe 0f0b0000
---[ end trace 97c12cfe3c8acf23 ]---

Stopping WINGs display manager: wdm: (removing stale /var/run/wdm.pid).
Asking all remaining processes to terminate...done.
All processes ended within 1 seconds...done.
Stopping enhanced syslogd: rsyslogd.
Saving the system clock to /dev/rtc0.
Hardware Clock updated to Wed Aug  4 23:01:48 MDT 2021.
Deconfiguring network interfaces...done.
Deactivating swap...done.
Unmounting local filesystems...done.
EXT4-fs (sda12): re-mounted. Opts: (null). Quota mode: disabled.
Will now restart.
sd 2:0:0:0: [sdb] Synchronizing SCSI cache
resetting MESH scsi bus(es)
reboot: Restarting system

[-- Attachment #5: Type: text/plain, Size: 15149 bytes --]

printk: console [ttyS0] enabled
printk: bootconsole [udbg0] disabled
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
rcu: Hierarchical SRCU implementation.
smp: Bringing up secondary CPUs ...
smp: Brought up 1 node, 1 CPU
devtmpfs: initialized
Duplicate name in PowerPC,750, renamed to "l2-cache#1"
Duplicate name in pci, renamed to "mac-io#1"
Duplicate name in pci, renamed to "pccard#1"
Found Grackle (MPC106) PCI host bridge at 0x0000000080000000. Firmware bus number: 0->0
PCI host bridge /pci (primary) ranges:
  IO 0x00000000fe000000..0x00000000fe7fffff -> 0x0000000000000000
 MEM 0x00000000fd000000..0x00000000fdffffff -> 0x0000000000000000
 MEM 0x0000000080000000..0x00000000fcffffff -> 0x0000000080000000
clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
futex hash table entries: 512 (order: 2, 16384 bytes, linear)
NET: Registered protocol family 16
PMU i2c /pci/mac-io/via-pmu
 channel 1 bus <multibus>
 channel 2 bus <multibus>
PCI: Probing PCI hardware
PCI host bridge to bus 0000:00
pci_bus 0000:00: root bus resource [io  0x0000-0x7fffff]
pci_bus 0000:00: root bus resource [mem 0xfd000000-0xfdffffff] (bus address [0x00000000-0x00ffffff])
pci_bus 0000:00: root bus resource [mem 0x80000000-0xfcffffff]
pci_bus 0000:00: root bus resource [bus 00-ff]
pci_bus 0000:00: busn_res: [bus 00-ff] end is updated to ff
pci 0000:00:00.0: [1057:0002] type 00 class 0x060000
pci 0000:00:0d.0: [106b:0017] type 00 class 0xff0000
pci 0000:00:0d.0: reg 0x10: [mem 0xf4000000-0xf407ffff]
pci 0000:00:10.0: [106b:0017] type 00 class 0xff0000
pci 0000:00:10.0: reg 0x10: [mem 0xf3000000-0xf307ffff]
pci 0000:00:11.0: [1002:4c50] type 00 class 0x038000
pci 0000:00:11.0: reg 0x10: [mem 0x82000000-0x82ffffff]
pci 0000:00:11.0: reg 0x14: [io  0x0400-0x04ff]
pci 0000:00:11.0: reg 0x18: [mem 0x82fff000-0x82ffffff]
pci 0000:00:11.0: reg 0x30: [mem 0xfd000000-0xfd01ffff pref]
pci 0000:00:11.0: supports D1 D2
pci 0000:00:13.0: [104c:ac15] type 02 class 0x060700
pci 0000:00:13.0: reg 0x10: [mem 0x81803000-0x81803fff]
pci 0000:00:13.1: [104c:ac15] type 02 class 0x060700
pci 0000:00:13.1: reg 0x10: [mem 0x81802000-0x81802fff]
pci_bus 0000:01: extended config space not accessible
pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 04
pci_bus 0000:05: extended config space not accessible
pci_bus 0000:05: busn_res: [bus 05-ff] end is updated to 08
pci_bus 0000:00: busn_res: [bus 00-ff] end is updated to 08
PCI: Cannot allocate resource region 2 of device 0000:00:11.0, will remap
PCI 0000:00 Cannot reserve Legacy IO [io  0x0000-0x0fff]
pci 0000:00:13.0: BAR 9: assigned [mem 0x84000000-0x87ffffff pref]
pci 0000:00:13.0: BAR 10: assigned [mem 0x88000000-0x8bffffff]
pci 0000:00:13.1: BAR 9: assigned [mem 0x8c000000-0x8fffffff pref]
pci 0000:00:13.1: BAR 10: assigned [mem 0x90000000-0x93ffffff]
pci 0000:00:11.0: BAR 6: assigned [mem 0xfd000000-0xfd01ffff pref]
pci 0000:00:11.0: BAR 2: assigned [mem 0xfd020000-0xfd020fff]
pci 0000:00:13.0: BAR 7: assigned [io  0x1000-0x10ff]
pci 0000:00:13.0: BAR 8: assigned [io  0x1100-0x11ff]
pci 0000:00:13.1: BAR 7: assigned [io  0x1200-0x12ff]
pci 0000:00:13.1: BAR 8: assigned [io  0x1300-0x13ff]
pci 0000:00:13.0: CardBus bridge to [bus 01-04]
pci 0000:00:13.0:   bridge window [io  0x1000-0x10ff]
pci 0000:00:13.0:   bridge window [io  0x1100-0x11ff]
pci 0000:00:13.0:   bridge window [mem 0x84000000-0x87ffffff pref]
pci 0000:00:13.0:   bridge window [mem 0x88000000-0x8bffffff]
pci 0000:00:13.1: CardBus bridge to [bus 05-08]
pci 0000:00:13.1:   bridge window [io  0x1200-0x12ff]
pci 0000:00:13.1:   bridge window [io  0x1300-0x13ff]
pci 0000:00:13.1:   bridge window [mem 0x8c000000-0x8fffffff pref]
pci 0000:00:13.1:   bridge window [mem 0x90000000-0x93ffffff]
pci_bus 0000:00: resource 4 [io  0x0000-0x7fffff]
pci_bus 0000:00: resource 5 [mem 0xfd000000-0xfdffffff]
pci_bus 0000:00: resource 6 [mem 0x80000000-0xfcffffff]
pci_bus 0000:01: resource 0 [io  0x1000-0x10ff]
pci_bus 0000:01: resource 1 [io  0x1100-0x11ff]
pci_bus 0000:01: resource 2 [mem 0x84000000-0x87ffffff pref]
pci_bus 0000:01: resource 3 [mem 0x88000000-0x8bffffff]
pci_bus 0000:05: resource 0 [io  0x1200-0x12ff]
pci_bus 0000:05: resource 1 [io  0x1300-0x13ff]
pci_bus 0000:05: resource 2 [mem 0x8c000000-0x8fffffff pref]
pci_bus 0000:05: resource 3 [mem 0x90000000-0x93ffffff]
vgaarb: loaded
SCSI subsystem initialized
libata version 3.00 loaded.
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
clocksource: Switched to clocksource timebase
NET: Registered protocol family 2
tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 6144 bytes, linear)
TCP established hash table entries: 4096 (order: 2, 16384 bytes, linear)
TCP bind hash table entries: 4096 (order: 3, 32768 bytes, linear)
TCP: Hash tables configured (established 4096 bind 4096)
UDP hash table entries: 256 (order: 1, 8192 bytes, linear)
UDP-Lite hash table entries: 256 (order: 1, 8192 bytes, linear)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
PCI: CLS 32 bytes, default 32
Thermal assist unit using workqueue, shrink_timer: 2000 ms
workingset: timestamp_bits=30 max_order=17 bucket_order=0
squashfs: version 4.0 (2009/01/31) Phillip Lougher
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
io scheduler mq-deadline registered
pci 0000:00:11.0: enabling device (0086 -> 0087)
Using unsupported 1024x768 (null) at 82801000, depth=32, pitch=4096
Console: switching to colour frame buffer device 128x48
fb0: Open Firmware frame buffer device on /pci/ATY,RageLTPro
pmac_zilog: 0.6 (Benjamin Herrenschmidt <benh@kernel.crashing.org>)
Non-volatile memory driver v1.3
brd: module loaded
loop: module loaded
MacIO PCI driver attached to Gatwick chipset
MacIO PCI driver attached to Heathrow chipset
swim3 0.00015000:floppy: [fd0] SWIM3 floppy controller in media bay
0.00013020:ch-a: ttyS0 at MMIO 0xf3013020 (irq = 16, base_baud = 230400) is a Z85c30 ESCC - Serial port
0.00013000:ch-b: ttyS1 at MMIO 0xf3013000 (irq = 17, base_baud = 230400) is a Z85c30 ESCC - Infrared port
macio: fixed media-bay irq on gatwick
macio: fixed left floppy irqs
swim3 1.00015000:floppy: [fd1] Couldn't request interrupt
swim3: probe of 1.00015000:floppy failed with error -16
macio: fixed left ide irqs
macio: fixed SCC irqs on gatwick
1.00013020:ch-a: ttyS2 at MMIO 0xf4013020 (irq = 79, base_baud = 230400) is a Z85c30 ESCC - Internal modem
mediabay0: Registered Heathrow media-bay
mediabay1: Registered Heathrow media-bay
mediabay0: Bay contains an ATA device
PMU Backlight initialized (pmubl)
mesh: configured for synchronous 5 MB/s
mediabay1: Bay contains a floppy drive
mesh: performing initial bus reset...
random: fast init done
adb device [2]: 2 0xC3
adb device [3]: 3 0x1
adb device [7]: 7 0x1F
ADB keyboard at 2 has handler 0xC3
Detected ADB keyboard, type ANSI.
input: ADB keyboard as /devices/virtual/input/input0
input: ADB Powerbook buttons as /devices/virtual/input/input1
ADB mouse (trackpad) at 3 has handler 0x4
input: ADB mouse as /devices/virtual/input/input2
scsi host0: MESH
pata-macio 0.00020000:ata0: Activating pata-macio chipset Heathrow ATA, Apple bus ID 0
scsi host1: pata_macio
ata1: PATA max MWDMA2 irq 30
ata1.00: ATA-7: SAMSUNG HM100JC, YN100-08, max UDMA/100
ata1.00: 195371568 sectors, multi 8: LBA48
scsi 1:0:0:0: Direct-Access     ATA      SAMSUNG HM100JC  0-08 PQ: 0 ANSI: 5
sd 1:0:0:0: [sda] 195371568 512-byte logical blocks: (100 GB/93.2 GiB)
sd 1:0:0:0: Attached scsi generic sg0 type 0
sd 1:0:0:0: [sda] Write Protect is off
sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 1:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
pata-macio 0.00021000:ata1: Activating pata-macio chipset Heathrow ATA, Apple bus ID 1
scsi host2: pata_macio
ata2: PATA max MWDMA2 irq 36
pata-macio 1.00021000:ata4: Activating pata-macio chipset Heathrow ATA, Apple bus ID 4
genirq: Flags mismatch irq 36. 00000000 (pata-macio[1.00021000:ata4]) vs. 00000000 (pata-macio[0.00021000:ata1])
pata-macio: probe of 1.00021000:ata4 failed with error -16
ata2.00: ATA-6: ST9160821A, 3.ALD, max UDMA/100
ata2.00: 312581808 sectors, multi 0: LBA48
eth0: BMAC at 00:05:02:07:5a:a6

aoe: AoE v85 initialised.
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-pci: EHCI PCI platform driver
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
ohci-pci: OHCI PCI platform driver
usbcore: registered new interface driver uas
usbcore: registered new interface driver usb-storage
mousedev: PS/2 mouse device common for all mice
rtc-generic rtc-generic: registered as rtc0
i2c /dev entries driver
PowerMac i2c bus pmu 2 registered
PowerMac i2c bus pmu 1 registered
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
NET: Registered protocol family 17
drmem: No dynamic reconfiguration memory found
 sda: [mac] sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10 sda11 sda12 sda13 sda14 sda15
sd 1:0:0:0: [sda] Attached SCSI disk
scsi 2:0:0:0: Direct-Access     ATA      ST9160821A       D    PQ: 0 ANSI: 5
sd 2:0:0:0: [sdb] 312581808 512-byte logical blocks: (160 GB/149 GiB)
sd 2:0:0:0: Attached scsi generic sg1 type 0
sd 2:0:0:0: [sdb] Write Protect is off
sd 2:0:0:0: [sdb] Mode Sense: 00 3a 00 00
sd 2:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sdb: [mac] sdb1 sdb2 sdb3 sdb4 sdb5 sdb6 sdb7 sdb8 sdb9 sdb10 sdb11 sdb12 sdb13 sdb14
sd 2:0:0:0: [sdb] Attached SCSI disk
EXT4-fs (sda12): mounting ext3 file system using the ext4 subsystem
EXT4-fs (sda12): mounted filesystem with ordered data mode. Opts: (null). Quota mode: disabled.
VFS: Mounted root (ext3 filesystem) readonly on device 8:12.
Freeing unused kernel memory: 1284K
Kernel memory protection not selected by kernel config.
Run /sbin/init as init process
  with arguments:
    /sbin/init
  with environment:
    HOME=/
    TERM=linux
INIT: version 2.96 booting
Using makefile-style concurrent boot in runlevel S.
findfs: unable to resolve 'LABEL=Debian_sid'
Starting hotplug events dispatcher: systemd-udevd.
Synthesizing the initial hotplug events (subsystems)...done.
Synthesizing the initial hotplug events (devices)...done.
Waiting for /dev to be fully populated...random: crng init done
phy registers:
 0000 0000 0000 0000 0000 0000 0000 0000
 0000 0000 0000 0000 0000 0000 0000 0000
 0000 0000 0000 0000 0000 0000 0000 0000
 0000 0000 0000 0000 0000 0000 0000 0000
done.
Setting up keyboard layout...done.
Activating swap...Adding 524284k swap on /dev/sda14.  Priority:-2 extents:1 across:524284k
done.
EXT4-fs (sda12): re-mounted. Opts: (null). Quota mode: disabled.
Checking root file system...Debian_sid: clean, 76261/524288 files, 1036636/2097152 blocks
done.
EXT4-fs (sda12): re-mounted. Opts: errors=remount-ro. Quota mode: disabled.
Checking file systems...data: clean, 83287/3325952 files, 2159937/13280326 blocks
done.
Cleaning up temporary files...
 /tmp.
Loading kernel module lp.
modprobe: FATAL: Module lp not found in directory /lib/modules/5.12.0-rc3-pmac-00078-g5cac2bc3752
Loading kernel module ppdev.
modprobe: FATAL: Module ppdev not found in directory /lib/modules/5.12.0-rc3-pmac-00078-g5cac2bc3752
Loading kernel module parport_pc.
modprobe: FATAL: Module parport_pc not found in directory /lib/modules/5.12.0-rc3-pmac-00078-g5cac2bc3752
Loading kernel module apm_emu.
modprobe: FATAL: Module apm_emu not found in directory /lib/modules/5.12.0-rc3-pmac-00078-g5cac2bc3752
Loading kernel module bmac.
modprobe: FATAL: Module bmac not found in directory /lib/modules/5.12.0-rc3-pmac-00078-g5cac2bc3752
Loading kernel module mesh.
modprobe: FATAL: Module mesh not found in directory /lib/modules/5.12.0-rc3-pmac-00078-g5cac2bc3752
Loading kernel module snd-powermac.
modprobe: FATAL: Module snd-powermac not found in directory /lib/modules/5.12.0-rc3-pmac-00078-g5cac2bc3752
EXT4-fs (sda15): mounting ext3 file system using the ext4 subsystem
EXT4-fs (sda15): mounted filesystem with ordered data mode. Opts: (null). Quota mode: disabled.
Mounting local filesystems...done.
Activating swapfile swap, if any...done.
Cleaning up temporary files....
Starting Setting kernel variables: sysctl.
Configuring network interfaces...done.
Cleaning up temporary files....
Setting up X socket directories...
 /tmp/.X11-unix
 /tmp/.ICE-unix
.
INIT: Entering runlevel: 2
Using makefile-style concurrent boot in runlevel 2.
Setting up console font and keymap...done.
Recovering nvi editor sessions.
none found.
Starting enhanced syslogd: rsyslogd.
Starting periodic command scheduler: cron.
Starting system message bus: dbus.
Starting S.M.A.R.T. daemon: smartd
.
Starting OpenBSD Secure Shell server: sshd.
Starting WINGs display manager: wdm:.
Deconfiguring network interfaces...
done.
phy registers:
 0000 0000 0000 0000 0000 0000 0000 0000
 0000 0000 0000 0000 0000 0000 0000 0000
 0000 0000 0000 0000 0000 0000 0000 0000
 0000 0000 0000 0000 0000 0000 0000 0000

Debian GNU/Linux 11 mac-server ttyS0

mac-server login: root
Password:
Linux mac-server 5.12.0-rc3-pmac-00078-g5cac2bc3752 #4 SMP Thu Aug 5 06:51:39 MDT 2021 ppc

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Wed Aug  4 23:01:38 MDT 2021 on ttyS0
root@mac-server:~# shutdown -r now

Broadcast message from root@mac-server (ttyS0) (Thu Aug  5 07:03:06 2021):

The system is going down for reboot NOW!

Broadcast message from root@mac-server (ttyS0) (Thu Aug  5 07:03:06 2021):

The system is going down for reboot NOW!
INIT: SenUsing makefile-style concurrent boot in runlevel 6.
Stopping mouse emulation daemon: mouseemu.
Stopping hotplug events dispatcher: systemd-udevd.
Stopping S.M.A.R.T. daemon: smartd.
Stopping WINGs display manager: wdm: (removing stale /var/run/wdm.pid).
Asking all remaining processes to terminate...done.
All processes ended within 4 seconds...done.
Stopping enhanced syslogd: rsyslogd.
Saving the system clock to /dev/rtc0.
Hardware Clock updated to Thu Aug  5 07:03:15 MDT 2021.
Deconfiguring network interfaces...done.
Deactivating swap...done.
Unmounting local filesystems...done.
EXT4-fs (sda12): re-mounted. Opts: (null). Quota mode: disabled.
Will now restart.
sd 2:0:0:0: [sdb] Synchronizing SCSI cache
resetting MESH scsi bus(es)
reboot: Restarting system

[-- Attachment #6: Type: text/plain, Size: 16939 bytes --]

printk: console [ttyS0] enabled
printk: bootconsole [udbg0] disabled
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
rcu: Hierarchical SRCU implementation.
smp: Bringing up secondary CPUs ...
smp: Brought up 1 node, 1 CPU
devtmpfs: initialized
Duplicate name in PowerPC,750, renamed to "l2-cache#1"
Duplicate name in pci, renamed to "mac-io#1"
Duplicate name in pci, renamed to "pccard#1"
Found Grackle (MPC106) PCI host bridge at 0x0000000080000000. Firmware bus number: 0->0
PCI host bridge /pci (primary) ranges:
  IO 0x00000000fe000000..0x00000000fe7fffff -> 0x0000000000000000
 MEM 0x00000000fd000000..0x00000000fdffffff -> 0x0000000000000000
 MEM 0x0000000080000000..0x00000000fcffffff -> 0x0000000080000000
clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
futex hash table entries: 512 (order: 2, 16384 bytes, linear)
NET: Registered protocol family 16
PMU i2c /pci/mac-io/via-pmu
 channel 1 bus <multibus>
 channel 2 bus <multibus>
PCI: Probing PCI hardware
PCI host bridge to bus 0000:00
pci_bus 0000:00: root bus resource [io  0x0000-0x7fffff]
pci_bus 0000:00: root bus resource [mem 0xfd000000-0xfdffffff] (bus address [0x00000000-0x00ffffff])
pci_bus 0000:00: root bus resource [mem 0x80000000-0xfcffffff]
pci_bus 0000:00: root bus resource [bus 00-ff]
pci_bus 0000:00: busn_res: [bus 00-ff] end is updated to ff
pci 0000:00:00.0: [1057:0002] type 00 class 0x060000
pci 0000:00:0d.0: [106b:0017] type 00 class 0xff0000
pci 0000:00:0d.0: reg 0x10: [mem 0xf4000000-0xf407ffff]
pci 0000:00:10.0: [106b:0017] type 00 class 0xff0000
pci 0000:00:10.0: reg 0x10: [mem 0xf3000000-0xf307ffff]
pci 0000:00:11.0: [1002:4c50] type 00 class 0x038000
pci 0000:00:11.0: reg 0x10: [mem 0x82000000-0x82ffffff]
pci 0000:00:11.0: reg 0x14: [io  0x0400-0x04ff]
pci 0000:00:11.0: reg 0x18: [mem 0x82fff000-0x82ffffff]
pci 0000:00:11.0: reg 0x30: [mem 0xfd000000-0xfd01ffff pref]
pci 0000:00:11.0: supports D1 D2
pci 0000:00:13.0: [104c:ac15] type 02 class 0x060700
pci 0000:00:13.0: reg 0x10: [mem 0x81803000-0x81803fff]
pci 0000:00:13.1: [104c:ac15] type 02 class 0x060700
pci 0000:00:13.1: reg 0x10: [mem 0x81802000-0x81802fff]
pci_bus 0000:01: extended config space not accessible
pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 04
pci_bus 0000:05: extended config space not accessible
pci_bus 0000:05: busn_res: [bus 05-ff] end is updated to 08
pci_bus 0000:00: busn_res: [bus 00-ff] end is updated to 08
PCI: Cannot allocate resource region 2 of device 0000:00:11.0, will remap
PCI 0000:00 Cannot reserve Legacy IO [io  0x0000-0x0fff]
pci 0000:00:13.0: BAR 9: assigned [mem 0x84000000-0x87ffffff pref]
pci 0000:00:13.0: BAR 10: assigned [mem 0x88000000-0x8bffffff]
pci 0000:00:13.1: BAR 9: assigned [mem 0x8c000000-0x8fffffff pref]
pci 0000:00:13.1: BAR 10: assigned [mem 0x90000000-0x93ffffff]
pci 0000:00:11.0: BAR 6: assigned [mem 0xfd000000-0xfd01ffff pref]
pci 0000:00:11.0: BAR 2: assigned [mem 0xfd020000-0xfd020fff]
pci 0000:00:13.0: BAR 7: assigned [io  0x1000-0x10ff]
pci 0000:00:13.0: BAR 8: assigned [io  0x1100-0x11ff]
pci 0000:00:13.1: BAR 7: assigned [io  0x1200-0x12ff]
pci 0000:00:13.1: BAR 8: assigned [io  0x1300-0x13ff]
pci 0000:00:13.0: CardBus bridge to [bus 01-04]
pci 0000:00:13.0:   bridge window [io  0x1000-0x10ff]
pci 0000:00:13.0:   bridge window [io  0x1100-0x11ff]
pci 0000:00:13.0:   bridge window [mem 0x84000000-0x87ffffff pref]
pci 0000:00:13.0:   bridge window [mem 0x88000000-0x8bffffff]
pci 0000:00:13.1: CardBus bridge to [bus 05-08]
pci 0000:00:13.1:   bridge window [io  0x1200-0x12ff]
pci 0000:00:13.1:   bridge window [io  0x1300-0x13ff]
pci 0000:00:13.1:   bridge window [mem 0x8c000000-0x8fffffff pref]
pci 0000:00:13.1:   bridge window [mem 0x90000000-0x93ffffff]
pci_bus 0000:00: resource 4 [io  0x0000-0x7fffff]
pci_bus 0000:00: resource 5 [mem 0xfd000000-0xfdffffff]
pci_bus 0000:00: resource 6 [mem 0x80000000-0xfcffffff]
pci_bus 0000:01: resource 0 [io  0x1000-0x10ff]
pci_bus 0000:01: resource 1 [io  0x1100-0x11ff]
pci_bus 0000:01: resource 2 [mem 0x84000000-0x87ffffff pref]
pci_bus 0000:01: resource 3 [mem 0x88000000-0x8bffffff]
pci_bus 0000:05: resource 0 [io  0x1200-0x12ff]
pci_bus 0000:05: resource 1 [io  0x1300-0x13ff]
pci_bus 0000:05: resource 2 [mem 0x8c000000-0x8fffffff pref]
pci_bus 0000:05: resource 3 [mem 0x90000000-0x93ffffff]
vgaarb: loaded
SCSI subsystem initialized
libata version 3.00 loaded.
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
clocksource: Switched to clocksource timebase
NET: Registered protocol family 2
tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 6144 bytes, linear)
TCP established hash table entries: 4096 (order: 2, 16384 bytes, linear)
TCP bind hash table entries: 4096 (order: 3, 32768 bytes, linear)
TCP: Hash tables configured (established 4096 bind 4096)
UDP hash table entries: 256 (order: 1, 8192 bytes, linear)
UDP-Lite hash table entries: 256 (order: 1, 8192 bytes, linear)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
PCI: CLS 32 bytes, default 32
Thermal assist unit using workqueue, shrink_timer: 2000 ms
workingset: timestamp_bits=30 max_order=17 bucket_order=0
squashfs: version 4.0 (2009/01/31) Phillip Lougher
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
io scheduler mq-deadline registered
pci 0000:00:11.0: enabling device (0086 -> 0087)
Using unsupported 1024x768 (null) at 82801000, depth=32, pitch=4096
Console: switching to colour frame buffer device 128x48
fb0: Open Firmware frame buffer device on /pci/ATY,RageLTPro
pmac_zilog: 0.6 (Benjamin Herrenschmidt <benh@kernel.crashing.org>)
Non-volatile memory driver v1.3
brd: module loaded
loop: module loaded
MacIO PCI driver attached to Gatwick chipset
MacIO PCI driver attached to Heathrow chipset
swim3 0.00015000:floppy: [fd0] SWIM3 floppy controller in media bay
0.00013020:ch-a: ttyS0 at MMIO 0xf3013020 (irq = 16, base_baud = 230400) is a Z85c30 ESCC - Serial port
0.00013000:ch-b: ttyS1 at MMIO 0xf3013000 (irq = 17, base_baud = 230400) is a Z85c30 ESCC - Infrared port
macio: fixed media-bay irq on gatwick
macio: fixed left floppy irqs
swim3 1.00015000:floppy: [fd1] Couldn't request interrupt
swim3: probe of 1.00015000:floppy failed with error -16
macio: fixed left ide irqs
macio: fixed SCC irqs on gatwick
1.00013020:ch-a: ttyS2 at MMIO 0xf4013020 (irq = 79, base_baud = 230400) is a Z85c30 ESCC - Internal modem
mediabay0: Registered Heathrow media-bay
mediabay1: Registered Heathrow media-bay
mediabay0: Bay contains an ATA device
PMU Backlight initialized (pmubl)
mesh: configured for synchronous 5 MB/s
mediabay1: Bay contains a floppy drive
mesh: performing initial bus reset...
random: fast init done
adb device [2]: 2 0xC3
adb device [3]: 3 0x1
adb device [7]: 7 0x1F
ADB keyboard at 2 has handler 0xC3
Detected ADB keyboard, type ANSI.
input: ADB keyboard as /devices/virtual/input/input0
input: ADB Powerbook buttons as /devices/virtual/input/input1
ADB mouse (trackpad) at 3 has handler 0x4
input: ADB mouse as /devices/virtual/input/input2
scsi host0: MESH
pata-macio 0.00020000:ata0: Activating pata-macio chipset Heathrow ATA, Apple bus ID 0
scsi host1: pata_macio
ata1: PATA max MWDMA2 irq 30
ata1.00: ATA-7: SAMSUNG HM100JC, YN100-08, max UDMA/100
ata1.00: 195371568 sectors, multi 8: LBA48
scsi 1:0:0:0: Direct-Access     ATA      SAMSUNG HM100JC  0-08 PQ: 0 ANSI: 5
sd 1:0:0:0: [sda] 195371568 512-byte logical blocks: (100 GB/93.2 GiB)
sd 1:0:0:0: Attached scsi generic sg0 type 0
sd 1:0:0:0: [sda] Write Protect is off
sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 1:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
pata-macio 0.00021000:ata1: Activating pata-macio chipset Heathrow ATA, Apple bus ID 1
scsi host2: pata_macio
ata2: PATA max MWDMA2 irq 36
pata-macio 1.00021000:ata4: Activating pata-macio chipset Heathrow ATA, Apple bus ID 4
genirq: Flags mismatch irq 36. 00000000 (pata-macio[1.00021000:ata4]) vs. 00000000 (pata-macio[0.00021000:ata1])
pata-macio: probe of 1.00021000:ata4 failed with error -16
ata2.00: ATA-6: ST9160821A, 3.ALD, max UDMA/100
ata2.00: 312581808 sectors, multi 0: LBA48
eth0: BMAC at 00:05:02:07:5a:a6

aoe: AoE v85 initialised.
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-pci: EHCI PCI platform driver
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
ohci-pci: OHCI PCI platform driver
usbcore: registered new interface driver uas
usbcore: registered new interface driver usb-storage
mousedev: PS/2 mouse device common for all mice
rtc-generic rtc-generic: registered as rtc0
i2c /dev entries driver
PowerMac i2c bus pmu 2 registered
PowerMac i2c bus pmu 1 registered
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
NET: Registered protocol family 17
drmem: No dynamic reconfiguration memory found
 sda: [mac] sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10 sda11 sda12 sda13 sda14 sda15
sd 1:0:0:0: [sda] Attached SCSI disk
scsi 2:0:0:0: Direct-Access     ATA      ST9160821A       D    PQ: 0 ANSI: 5
sd 2:0:0:0: [sdb] 312581808 512-byte logical blocks: (160 GB/149 GiB)
sd 2:0:0:0: Attached scsi generic sg1 type 0
sd 2:0:0:0: [sdb] Write Protect is off
sd 2:0:0:0: [sdb] Mode Sense: 00 3a 00 00
sd 2:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sdb: [mac] sdb1 sdb2 sdb3 sdb4 sdb5 sdb6 sdb7 sdb8 sdb9 sdb10 sdb11 sdb12 sdb13 sdb14
sd 2:0:0:0: [sdb] Attached SCSI disk
EXT4-fs (sda12): mounting ext3 file system using the ext4 subsystem
EXT4-fs (sda12): mounted filesystem with ordered data mode. Opts: (null). Quota mode: disabled.
VFS: Mounted root (ext3 filesystem) readonly on device 8:12.
Freeing unused kernel memory: 1224K
Kernel memory protection not selected by kernel config.
Run /sbin/init as init process
  with arguments:
    /sbin/init
  with environment:
    HOME=/
    TERM=linux
INIT: version 2.96 booting
Using makefile-style concurrent boot in runlevel S.
findfs: unable to resolve 'LABEL=Debian_sid'
Starting hotplug events dispatcher: systemd-udevd.
Synthesizing the initial hotplug events (subsystems)...done.
Synthesizing the initial hotplug events (devices)...done.
Waiting for /dev to be fully populated...random: crng init done
phy registers:
 0000 0000 0000 0000 0000 0000 0000 0000
 0000 0000 0000 0000 0000 0000 0000 0000
 0000 0000 0000 0000 0000 0000 0000 0000
 0000 0000 0000 0000 0000 0000 0000 0000
done.
Setting up keyboard layout...done.
Activating swap...Adding 524284k swap on /dev/sda14.  Priority:-2 extents:1 across:524284k
done.
EXT4-fs (sda12): re-mounted. Opts: (null). Quota mode: disabled.
Checking root file system...Debian_sid: clean, 76261/524288 files, 1036661/2097152 blocks
done.
EXT4-fs (sda12): re-mounted. Opts: errors=remount-ro. Quota mode: disabled.
Checking file systems...data: clean, 83287/3325952 files, 2159937/13280326 blocks
done.
Cleaning up temporary files...
 /tmp.
Loading kernel module lp.
modprobe: FATAL: Module lp not found in directory /lib/modules/5.12.0-rc3-pmac-00078-g5cac2bc3752
Loading kernel module ppdev.
modprobe: FATAL: Module ppdev not found in directory /lib/modules/5.12.0-rc3-pmac-00078-g5cac2bc3752
Loading kernel module parport_pc.
modprobe: FATAL: Module parport_pc not found in directory /lib/modules/5.12.0-rc3-pmac-00078-g5cac2bc3752
Loading kernel module apm_emu.
modprobe: FATAL: Module apm_emu not found in directory /lib/modules/5.12.0-rc3-pmac-00078-g5cac2bc3752
Loading kernel module bmac.
modprobe: FATAL: Module bmac not found in directory /lib/modules/5.12.0-rc3-pmac-00078-g5cac2bc3752
Loading kernel module mesh.
modprobe: FATAL: Module mesh not found in directory /lib/modules/5.12.0-rc3-pmac-00078-g5cac2bc3752
Loading kernel module snd-powermac.
modprobe: FATAL: Module snd-powermac not found in directory /lib/modules/5.12.0-rc3-pmac-00078-g5cac2bc3752
EXT4-fs (sda15): mounting ext3 file system using the ext4 subsystem
EXT4-fs (sda15): mounted filesystem with ordered data mode. Opts: (null). Quota mode: disabled.
Mounting local filesystems...done.
Activating swapfile swap, if any...done.
Cleaning up temporary files....
Starting Setting kernel variables: sysctl.
Configuring network interfaces...done.
Cleaning up temporary files....
Setting up X socket directories... /tmp/.X11-unix /tmp/.ICE-unix
.
INIT: Entering runlevel: 2
Using makefile-style concurrent boot in runlevel 2.
Setting up console font and keymap...done.
Recovering nvi editor sessions.
none found.
Starting enhanced syslogd: rsyslogd.
Starting periodic command scheduler: cron.
Starting system message bus: dbus.
Starting OpenBSD Secure Shell server: sshd.
Starting S.M.A.R.T. daemon: smartd.
Starting WINGs display manager: wdm:.
Deconfiguring network interfaces...
done.
phy registers:
 0000 0000 0000 0000 0000 0000 0000 0000
 0000 0000 0000 0000 0000 0000 0000 0000
 0000 0000 0000 0000 0000 0000 0000 0000
 0000 0000 0000 0000 0000 0000 0000 0000

Debian GNU/Linux 11 mac-server ttyS0

mac-server login: BUG: Unable to handle kernel instruction fetch
Faulting instruction address: 0xfe88731c
Oops: Kernel access of bad area, sig: 11 [#1]
BE PAGE_SIZE=4K MMU=Hash SMP NR_CPUS=2 PowerMac
Modules linked in:
CPU: 0 PID: 1775 Comm: xfce4-session Not tainted 5.12.0-rc3-pmac-00078-g5cac2bc3752 #5
NIP:  fe88731c LR: fe88731c CTR: 00000000
REGS: e2ddde70 TRAP: 0400   Not tainted  (5.12.0-rc3-pmac-00078-g5cac2bc3752)
MSR:  40001030 <ME,IR,DR>  CR: 28024428  XER: 00000000

GPR00: fe88731c e2dddf30 c16820e0 00000000 00000000 00000000 c1a763a4 00000100
GPR08: 00000000 401239fa 40123b0b 00000000 88024428 008ef778 00000000 00000000
GPR16: 00c15b20 00c102f8 00000001 bfc1e248 00000000 b50ef658 0092d120 b4be3d60
GPR24: bfc1e188 0090093c 00000000 00000000 bfc1e0cc 00900930 b6cbcff4 0000005d
NIP [fe88731c] 0xfe88731c
LR [fe88731c] 0xfe88731c
Call Trace:
[e2dddf30] [c0016058] ret_from_syscall+0xc/0x28 (unreliable)
--- interrupt: c00 at 0xb6bd76f8
NIP:  b6bd76f8 LR: b6bd76cc CTR: b6bd76c0
REGS: e2dddf40 TRAP: 0c00   Not tainted  (5.12.0-rc3-pmac-00078-g5cac2bc3752)
MSR:  0000d032 <EE,PR,ME,IR,DR,RI>  CR: 28024422  XER: 00000000

GPR00: 000000a7 bfc1e090 b579dca0 00000001 00000001 ffffffff 00000000 00000001
GPR08: 00000000 0090093c 00000000 b6bd76c0 44044248 008ef778 00000000 00000000
GPR16: 00c15b20 00c102f8 00000001 bfc1e248 00000000 b50ef658 0092d120 b4be3d60
GPR24: bfc1e188 0090093c 00000000 00000000 bfc1e0cc 00900930 b6cbcff4 0000005d
NIP [b6bd76f8] 0xb6bd76f8
LR [b6bd76cc] 0xb6bd76cc
--- interrupt: c00
Instruction dump:
XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX
XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX
---[ end trace 95647df21d0753a5 ]---


mac-server login: root
Password:
Linux mac-server 5.12.0-rc3-pmac-00078-g5cac2bc3752 #5 SMP Thu Aug 5 07:02:31 MDT 2021 ppc

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Thu Aug  5 07:03:01 MDT 2021 on ttyS0
root@mac-server:~# shutdown -r now

Broadcast message from root@mac-server (ttyS0) (Thu Aug  5 07:16:20 2021):

The system is going down for reboot NOW!

Broadcast message from root@mac-server (ttyS0) (Thu Aug  5 07:16:20 2021):

The system is going down for reboot NOW!
INIT: Sending processes configured via /etUsing makefile-style concurrent boot in runlevel 6.
Stopping mouse emulation daemon: mouseemu.
Stopping S.M.A.R.T. daemon: smartd.
Stopping hotplug events dispatcher: systemd-udevd.
Stopping WINGs display manager: wdm: (removing stale /var/run/wdm.pid).
Asking all remaining processes to terminate...done.
All processes ended within 4 seconds...done.
Stopping enhanced syslogd: rsyslogd.
Deconfiguring network interfaces...done.
Saving the system clock to /dev/rtc0.
Hardware Clock updated to Thu Aug  5 07:16:28 MDT 2021.
Deactivating swap...done.
Unmounting local filesystems...done.
EXT4-fs (sda12): re-mounted. Opts: (null). Quota mode: disabled.
Will now restart.
sd 2:0:0:0: [sdb] Synchronizing SCSI cache
resetting MESH scsi bus(es)
reboot: Restarting system

Re: Debian SID kernel doesn't boot on PowerBook 3400c

[Christophe Leroy]

+nicholas piggin for the C interrupt stuff

Le 06/08/2021 à 03:06, Finn Thain a écrit :
> (Christophe, you've seen some of this before, however there are new
> results added at the end. I've Cc'd the mailing lists this time.)
> 
> On Wed, 4 Aug 2021, Stan Johnson wrote:
> 
>> On 8/4/21 8:41 PM, Finn Thain wrote:
>>
>>>
>>> $ curl https://lore.kernel.org/lkml/9b64dde3-6ebd-b446-41d9-61e8cb0d8c39@csgroup.eu/raw
>>> ../message.mbox
>> ok
>>
>> $ sha1 ../message.mbox
>> SHA1 (../message.mbox) = 436ce0adf893c46c84c54607f73c838897caeeea
>>
>>>
>>> On Wed, 4 Aug 2021, Christophe Leroy wrote:
>>>
>>>> Can you check if they happen at commit c16728835
>>>>
>>
>> $ git checkout c16728835eec
>> Checking out files: 100% (20728/20728), done.
>> Note: checking out 'c16728835eec'.
>>
>> You are in 'detached HEAD' state. You can look around, make experimental
>> changes and commit them, and you can discard any commits you make in this
>> state without impacting any branches by performing another checkout.
>>
>> If you want to create a new branch to retain commits you create, you may
>> do so (now or later) by using -b with the checkout command again. Example:
>>
>>    git checkout -b <new-branch-name>
>>
>> HEAD is now at c16728835eec powerpc/32: Manage KUAP in C
>> $ git am ../message.mbox
>> warning: Patch sent with format=flowed; space at the end of lines might be lost.
>> Applying: powerpc/32: Dismantle EXC_XFER_STD/LITE/TEMPLATE
>> $ cp ../dot-config-powermac-5.13 .config
>> $ make ARCH=powerpc CROSS_COMPILE=powerpc-linux-gnu- -j4 clean olddefconfig vmlinux
>> $ strings vmlinux | fgrep 'Linux version'
>> Linux version 5.12.0-rc3-pmac-00078-geb51c431b81 (johnson@ThinkPad) (powerpc-linux-gnu-gcc (Debian 8.3.0-2) 8.3.0, GNU ld (GNU Binutils for Debian) 2.31.1) #1 SMP Wed Aug 4 21:50:47 MDT 2021
>>
>> 1) PB 3400c
>> Hangs at boot (Mac OS screen), no serial console output
>>
>> 2) Wallstreet
>> X fails, errors ("Kernel attempted to write user page", "BUG: Unable to
>> handle kernel instruction fetch"), see Wallstreet_console-1.txt.
>>
> 
> The log shows that the error "Kernel attempted to write user page
> (b3399774) - exploit attempt?" happens after commit c16728835eec
> ("powerpc/32: Manage KUAP in C").

I think I found a possible cause for this. After the above patch, locking KUAP on interrupt is done 
in interrupt_enter_prepare(). But in case of NMI interrupt, that function is not called. That means 
that when leaving interrupt through interrupt_exit_kernel_prepare(), the supposedly saved previous 
KUAP status is garbage.

An easy way to fix that is to add missing stuff in interrupt_nmi_enter_prepare(), I'll do that at 
least for testing, but at the end it is not so easy, because of booke32 and 40x.

The problem on booke32 and 40x is that the "critical interrupts" exit goes through interrupt_return 
when they happened in user mode and bypass interrupt_return when they happened in kernel mode. So it 
is not easy to manage.


> 
>>>>
>>>> Can you check if they DO NOT happen at preceding commit c16728835~
>>>>
>>
>> $ git checkout c16728835~
>> Previous HEAD position was c16728835eec powerpc/32: Manage KUAP in C
>> HEAD is now at 0b45359aa2df powerpc/8xx: Create C version of kuap save/restore/check helpers
>> $ git am ../message.mbox
>> warning: Patch sent with format=flowed; space at the end of lines might be lost.
>> Applying: powerpc/32: Dismantle EXC_XFER_STD/LITE/TEMPLATE
>> $ cp ../dot-config-powermac-5.13 .config
>> $ make ARCH=powerpc CROSS_COMPILE=powerpc-linux-gnu- -j4 clean olddefconfig vmlinux
>>
>> Linux version 5.12.0-rc3-pmac-00077-gc9f6e8dd045
>>
>> 3) PB 3400c
>> Hangs at boot (Mac OS screen)
>>
>> 4) Wallstreet
>> X fails, errors in console log (different than test 2), see
>> Wallstreet_console-2.txt.
>>
> 
> This log shows that the errors "xfce4-session[1775]: bus error (7)" and
> "kernel BUG at arch/powerpc/kernel/interrupt.c:49!" happen prior to commit
> c16728835eec ("powerpc/32: Manage KUAP in C").

As mentionned by Nic, this is due to r11 being cloberred. For the time being the only r11 clobber 
identified is the one I have provided a fix for. I'm wondering whether it was applied for all 
further tests or not.

> 
>>
>> $ git checkout 0b45359aa2df
>> ...
>> HEAD is now at 0b45359aa2df powerpc/8xx: Create C version of kuap save/restore/check helpers
>> $ git am ../message.mbox
>> warning: Patch sent with format=flowed; space at the end of lines might be lost.
>> Applying: powerpc/32: Dismantle EXC_XFER_STD/LITE/TEMPLATE
>> $ cp ../dot-config-powermac-5.13 .config
>> $ make ARCH=powerpc CROSS_COMPILE=powerpc-linux-gnu- -j4 clean olddefconfig vmlinux
>>
>> Linux version 5.12.0-rc3-pmac-00077-ge06b29ce146
>>
>> 5) PB 3400c
>> Hangs at boot (Mac OS screen)
>>
>> 6) Wallstreet
>> X failed (X login succeeded, but setting up desktop failed), errors in
>> console log, see Wallstreet_console-3.txt.
>>
> 
> (No need for those two tests: it's exactly the same code and almost the
> same failure modes: "kernel BUG at arch/powerpc/kernel/interrupt.c:50".)
> 
> On Thu, 5 Aug 2021, Stan Johnson wrote:
> 
>> On 8/5/21 12:47 AM, Finn Thain wrote:
>>
>>> On Wed, 4 Aug 2021, Christophe Leroy wrote:
>>>
>>>> Could you test without CONFIG_PPC_KUAP
>> ...
>>
>> $ git checkout c16728835eec
>> ...
>> HEAD is now at c16728835eec powerpc/32: Manage KUAP in C
>> $ git am ../message.mbox
>> warning: Patch sent with format=flowed; space at the end of lines might be lost.
>> Applying: powerpc/32: Dismantle EXC_XFER_STD/LITE/TEMPLATE
>> $ cp ../dot-config-powermac-5.13 .config
>> $ scripts/config -d CONFIG_PPC_KUAP
>> $ make ARCH=powerpc CROSS_COMPILE=powerpc-linux-gnu- -j4 clean olddefconfig vmlinux
>> $ grep CONFIG_PPC_KUAP .config
>> # CONFIG_PPC_KUAP is not set
>>
>> Linux version 5.12.0-rc3-pmac-00078-g5cac2bc3752
>>
>> 7) PB 3400c
>> Hangs at boot (Mac OS screen)
>>
>> 8) Wallstreet
>> Everything works, no errors (see Wallstreet_console-4.txt).
>>
> 
> That would seem to implicate CONFIG_PPC_KUAP itself. (Note that all builds
> up until this one have CONFIG_PPC_KUAP=y.)

Yes I believe so, see at the begining of this mail.


> 
>>
>>>
>>>> Could you test with CONFIG_PPC_KUAP and CONFIG_PPC_KUAP_DEBUG
>> ...
>>
>> $scripts/config -e CONFIG_PPC_KUAP
>> $ scripts/config -e CONFIG_PPC_KUAP_DEBUG
>> $ make ARCH=powerpc CROSS_COMPILE=powerpc-linux-gnu- -j4 clean olddefconfig vmlinux
>> $ grep CONFIG_PPC_KUAP .config
>> CONFIG_PPC_KUAP=y
>> CONFIG_PPC_KUAP_DEBUG=y
>>
>> Linux version 5.12.0-rc3-pmac-00078-g5cac2bc3752
>>
>> 9) PB 3400c
>> Hangs at boot (Mac OS screen)
>>
>> 10) Wallstreet
>> X failed at first login, worked at second login, one error in console
>> log ("BUG: Unable to handle kernel instruction fetch"), see
>> Wallstreet_console-5.txt.
>>
> 
> One might expect to see "Kernel attempted to write user page (b3399774) -
> exploit attempt?" again here (see c16728835eec build above) but instead
> this log says "Oops: Kernel access of bad area, sig: 11".

Maybe the test should be done a second time. As r11 is garbage it may or may not be a user address. 
If it is a user address the we get "Kernel attempted to write user page". If it is a random kernel 
address, we likely get "Kernel access of bad area" instead.


> 
> BTW, this procedure could be made simpler and easier if I pushed git
> branches to a public repo for Stan to build, which included Christophe's
> fix plus hard-wired Kconfig changes. That way, the .config file could be
> held constant and the commit hash in the serial console log would be more
> meaningful.
> 

I like the idea, I think I'm going to provide testing fixes through a git repo, that will for sure 
make things easier.

Thanks
Christophe

Re: Debian SID kernel doesn't boot on PowerBook 3400c

[Finn Thain]

On Fri, 6 Aug 2021, Christophe Leroy wrote:

> > > > > 
> > > > > Can you check if they DO NOT happen at preceding commit c16728835~
> > > > > 
> > > 
> > > $ git checkout c16728835~
> > > Previous HEAD position was c16728835eec powerpc/32: Manage KUAP in C
> > > HEAD is now at 0b45359aa2df powerpc/8xx: Create C version of kuap
> > > save/restore/check helpers
> > > $ git am ../message.mbox
> > > warning: Patch sent with format=flowed; space at the end of lines might be
> > > lost.
> > > Applying: powerpc/32: Dismantle EXC_XFER_STD/LITE/TEMPLATE
> > > $ cp ../dot-config-powermac-5.13 .config
> > > $ make ARCH=powerpc CROSS_COMPILE=powerpc-linux-gnu- -j4 clean
> > > olddefconfig vmlinux
> > > 
> > > Linux version 5.12.0-rc3-pmac-00077-gc9f6e8dd045
> > > 
> > > 3) PB 3400c
> > > Hangs at boot (Mac OS screen)
> > > 
> > > 4) Wallstreet
> > > X fails, errors in console log (different than test 2), see
> > > Wallstreet_console-2.txt.
> > > 
> > 
> > This log shows that the errors "xfce4-session[1775]: bus error (7)" and
> > "kernel BUG at arch/powerpc/kernel/interrupt.c:49!" happen prior to commit
> > c16728835eec ("powerpc/32: Manage KUAP in C").
> 
> As mentionned by Nic, this is due to r11 being cloberred. For the time being
> the only r11 clobber identified is the one I have provided a fix for. I'm
> wondering whether it was applied for all further tests or not.
> 

Your fix was applied to this build with "git am ../message.mbox".

> ...
> > > 
> > > > 
> > > > > Could you test with CONFIG_PPC_KUAP and CONFIG_PPC_KUAP_DEBUG
> > > ...
> > > 
> > > $scripts/config -e CONFIG_PPC_KUAP
> > > $ scripts/config -e CONFIG_PPC_KUAP_DEBUG
> > > $ make ARCH=powerpc CROSS_COMPILE=powerpc-linux-gnu- -j4 clean
> > > olddefconfig vmlinux
> > > $ grep CONFIG_PPC_KUAP .config
> > > CONFIG_PPC_KUAP=y
> > > CONFIG_PPC_KUAP_DEBUG=y
> > > 
> > > Linux version 5.12.0-rc3-pmac-00078-g5cac2bc3752
> > > 
> > > 9) PB 3400c
> > > Hangs at boot (Mac OS screen)
> > > 
> > > 10) Wallstreet
> > > X failed at first login, worked at second login, one error in console
> > > log ("BUG: Unable to handle kernel instruction fetch"), see
> > > Wallstreet_console-5.txt.
> > > 
> > 
> > One might expect to see "Kernel attempted to write user page (b3399774) -
> > exploit attempt?" again here (see c16728835eec build above) but instead
> > this log says "Oops: Kernel access of bad area, sig: 11".
> 
> Maybe the test should be done a second time. As r11 is garbage it may or 
> may not be a user address. If it is a user address the we get "Kernel 
> attempted to write user page". If it is a random kernel address, we 
> likely get "Kernel access of bad area" instead.
> 

Your fix was applied here also.

Re: Debian SID kernel doesn't boot on PowerBook 3400c

[Christophe Leroy]

Le 06/08/2021 à 11:43, Finn Thain a écrit :
> On Fri, 6 Aug 2021, Christophe Leroy wrote:
> 
>>>>>>
>>>>>> Can you check if they DO NOT happen at preceding commit c16728835~
>>>>>>
>>>>
>>>> $ git checkout c16728835~
>>>> Previous HEAD position was c16728835eec powerpc/32: Manage KUAP in C
>>>> HEAD is now at 0b45359aa2df powerpc/8xx: Create C version of kuap
>>>> save/restore/check helpers
>>>> $ git am ../message.mbox
>>>> warning: Patch sent with format=flowed; space at the end of lines might be
>>>> lost.
>>>> Applying: powerpc/32: Dismantle EXC_XFER_STD/LITE/TEMPLATE
>>>> $ cp ../dot-config-powermac-5.13 .config
>>>> $ make ARCH=powerpc CROSS_COMPILE=powerpc-linux-gnu- -j4 clean
>>>> olddefconfig vmlinux
>>>>
>>>> Linux version 5.12.0-rc3-pmac-00077-gc9f6e8dd045
>>>>
>>>> 3) PB 3400c
>>>> Hangs at boot (Mac OS screen)
>>>>
>>>> 4) Wallstreet
>>>> X fails, errors in console log (different than test 2), see
>>>> Wallstreet_console-2.txt.
>>>>
>>>
>>> This log shows that the errors "xfce4-session[1775]: bus error (7)" and
>>> "kernel BUG at arch/powerpc/kernel/interrupt.c:49!" happen prior to commit
>>> c16728835eec ("powerpc/32: Manage KUAP in C").
>>
>> As mentionned by Nic, this is due to r11 being cloberred. For the time being
>> the only r11 clobber identified is the one I have provided a fix for. I'm
>> wondering whether it was applied for all further tests or not.
>>
> 
> Your fix was applied to this build with "git am ../message.mbox".

Ok good.

> 
>> ...
>>>>
>>>>>
>>>>>> Could you test with CONFIG_PPC_KUAP and CONFIG_PPC_KUAP_DEBUG
>>>> ...
>>>>
>>>> $scripts/config -e CONFIG_PPC_KUAP
>>>> $ scripts/config -e CONFIG_PPC_KUAP_DEBUG
>>>> $ make ARCH=powerpc CROSS_COMPILE=powerpc-linux-gnu- -j4 clean
>>>> olddefconfig vmlinux
>>>> $ grep CONFIG_PPC_KUAP .config
>>>> CONFIG_PPC_KUAP=y
>>>> CONFIG_PPC_KUAP_DEBUG=y
>>>>
>>>> Linux version 5.12.0-rc3-pmac-00078-g5cac2bc3752
>>>>
>>>> 9) PB 3400c
>>>> Hangs at boot (Mac OS screen)
>>>>
>>>> 10) Wallstreet
>>>> X failed at first login, worked at second login, one error in console
>>>> log ("BUG: Unable to handle kernel instruction fetch"), see
>>>> Wallstreet_console-5.txt.
>>>>
>>>
>>> One might expect to see "Kernel attempted to write user page (b3399774) -
>>> exploit attempt?" again here (see c16728835eec build above) but instead
>>> this log says "Oops: Kernel access of bad area, sig: 11".
>>
>> Maybe the test should be done a second time. As r11 is garbage it may or
>> may not be a user address. If it is a user address the we get "Kernel
>> attempted to write user page". If it is a random kernel address, we
>> likely get "Kernel access of bad area" instead.
>>
> 
> Your fix was applied here also.
> 

Anyway, it would be worth trying to boot a few times more with the same kernel, because as I said 
the value is random, so it may or may not hit userspace, hence the possible difference of message, 
either "Kernel attempted to write user page" or "Kernel access of bad area" depending on whether the 
address is a user address or not.

I have cooked a tentative fix for that KUAP stuff.
Could you try the branch 'bugtest' at https://github.com/chleroy/linux.git

Thanks
Christophe

Re: Debian SID kernel doesn't boot on PowerBook 3400c

[Finn Thain]

On Fri, 6 Aug 2021, Christophe Leroy wrote:

> 
> I have cooked a tentative fix for that KUAP stuff.
> Could you try the branch 'bugtest' at https://github.com/chleroy/linux.git
> 

Thanks, Christophe.

Stan, please test the following build.

$ git remote add chleroy-linux https://github.com/chleroy/linux.git -f -t bugtest
...
$ git checkout chleroy-linux/bugtest
HEAD is now at 63e3756d1bdf powerpc/interrupts: Also perform KUAP/KUEP lock and usertime accounting on NMI
$ cp ../dot-config-powermac-5.13 .config
$ scripts/config -e CONFIG_PPC_KUAP -e CONFIG_PPC_KUAP_DEBUG -e CONFIG_VMAP_STACK
$ make ARCH=powerpc CROSS_COMPILE=powerpc-linux-gnu- -j4 clean olddefconfig vmlinux
$ egrep "CONFIG_PPC_KUAP|CONFIG_VMAP_STACK" .config
$ strings vmlinux |grep "Linux version"

If that kernel produces errors, I'd try a second build as well:

$ scripts/config -e CONFIG_PPC_KUAP -e CONFIG_PPC_KUAP_DEBUG -d CONFIG_VMAP_STACK
$ make ARCH=powerpc CROSS_COMPILE=powerpc-linux-gnu- -j4 clean olddefconfig vmlinux
$ egrep "CONFIG_PPC_KUAP|CONFIG_VMAP_STACK" .config
$ strings vmlinux |grep "Linux version"

Please boot using the same kernel parameters as last time and capture the 
serial console logs. In case we're still dealing with intermittent bugs it 
might be necessary to repeat these tests so I suggest you retain the 
vmlinux files.

Re: Debian SID kernel doesn't boot on PowerBook 3400c

[Finn Thain]

On Fri, 6 Aug 2021, Stan Johnson wrote:

> $ egrep '(CONFIG_PPC_KUAP|CONFIG_VMAP_STACK)' .config
> CONFIG_PPC_KUAP=y
> CONFIG_PPC_KUAP_DEBUG=y
> CONFIG_VMAP_STACK=y
> $ strings vmlinux | fgrep "Linux version"
> Linux version 5.13.0-pmac-00004-g63e3756d1bd ...
> $ cp vmlinux ../vmlinux-5.13.0-pmac-00004-g63e3756d1bd-1
> 
> 1) PB 3400c
> vmlinux-5.13.0-pmac-00004-g63e3756d1bd-1
> Boots, no errors logging in at (text) fb console. Logging in via ssh and
> running "ls -Rail /usr/include" generated errors (and a hung ssh
> session). Once errors started, they repeated for almost every command.
> See pb3400c-63e3756d1bdf-1.txt.
> 
> 2) Wallstreet
> vmlinux-5.13.0-pmac-00004-g63e3756d1bd-1
> X login failed, there were errors ("Oops: Kernel access of bad area",
> "Oops: Exception in kernel mode"). Logging in via SSH, there were no
> additional errors after running "ls -Rail /usr/include" -- the errors
> did not escalate as they did on the PB 3400.
> See Wallstreet-63e3756d1bdf-1.txt.
> 
...
> $ egrep '(CONFIG_PPC_KUAP|CONFIG_VMAP_STACK)' .config
> CONFIG_PPC_KUAP=y
> CONFIG_PPC_KUAP_DEBUG=y
> # CONFIG_VMAP_STACK is not set
> $ strings vmlinux | fgrep "Linux version"
> Linux version 5.13.0-pmac-00004-g63e3756d1bd ...
> $ cp vmlinux ../vmlinux-5.13.0-pmac-00004-g63e3756d1bd-2
> 
> 3) PB 3400c
> vmlinux-5.13.0-pmac-00004-g63e3756d1bd-2
> Filesystem was corrupt from the previous test (probably from all the
> errors during shutdown). After fixing the filesystem:
> Boots, no errors logging in at (text) fb console. Logging in via ssh and
> running "ls -Rail /usr/include" generated a few errors. There didn't
> seem to be as many errors as in the previous test, there were a few
> errors during shutdown but the shutdown was otherwise normal.
> See pb3400c-63e3756d1bdf-2.txt.
> 
> 4) Wallstreet
> vmlinux-5.13.0-pmac-00004-g63e3756d1bd-2
> X login worked, and there were no errors. There were no errors during
> ssh access.
> See Wallstreet-63e3756d1bdf-2.txt.
> 

Thanks for collecting these results, Stan. Do you think that the 
successful result from test 4) could have been just chance?

It appears that the bug affecting the Powerbook 3400 is unaffected by 
CONFIG_VMAP_STACK.

Whereas the bug affecting the Powerbook G3 disappears when 
CONFIG_VMAP_STACK is disabled (assuming the result from 4 is reliable).

Either way, these results reiterate that "Oops: Kernel access of bad area, 
sig: 11" was not entirely resolved by "powerpc/32s: Fix napping restore in 
data storage interrupt (DSI)".

Re: Debian SID kernel doesn't boot on PowerBook 3400c

[Stan Johnson]

On 8/6/21 10:08 PM, Finn Thain wrote:
> 
> On Fri, 6 Aug 2021, Stan Johnson wrote:
> 
>> $ egrep '(CONFIG_PPC_KUAP|CONFIG_VMAP_STACK)' .config
>> CONFIG_PPC_KUAP=y
>> CONFIG_PPC_KUAP_DEBUG=y
>> CONFIG_VMAP_STACK=y
>> $ strings vmlinux | fgrep "Linux version"
>> Linux version 5.13.0-pmac-00004-g63e3756d1bd ...
>> $ cp vmlinux ../vmlinux-5.13.0-pmac-00004-g63e3756d1bd-1
>>
>> 1) PB 3400c
>> vmlinux-5.13.0-pmac-00004-g63e3756d1bd-1
>> Boots, no errors logging in at (text) fb console. Logging in via ssh and
>> running "ls -Rail /usr/include" generated errors (and a hung ssh
>> session). Once errors started, they repeated for almost every command.
>> See pb3400c-63e3756d1bdf-1.txt.
>>
>> 2) Wallstreet
>> vmlinux-5.13.0-pmac-00004-g63e3756d1bd-1
>> X login failed, there were errors ("Oops: Kernel access of bad area",
>> "Oops: Exception in kernel mode"). Logging in via SSH, there were no
>> additional errors after running "ls -Rail /usr/include" -- the errors
>> did not escalate as they did on the PB 3400.
>> See Wallstreet-63e3756d1bdf-1.txt.
>>
> ...
>> $ egrep '(CONFIG_PPC_KUAP|CONFIG_VMAP_STACK)' .config
>> CONFIG_PPC_KUAP=y
>> CONFIG_PPC_KUAP_DEBUG=y
>> # CONFIG_VMAP_STACK is not set
>> $ strings vmlinux | fgrep "Linux version"
>> Linux version 5.13.0-pmac-00004-g63e3756d1bd ...
>> $ cp vmlinux ../vmlinux-5.13.0-pmac-00004-g63e3756d1bd-2
>>
>> 3) PB 3400c
>> vmlinux-5.13.0-pmac-00004-g63e3756d1bd-2
>> Filesystem was corrupt from the previous test (probably from all the
>> errors during shutdown). After fixing the filesystem:
>> Boots, no errors logging in at (text) fb console. Logging in via ssh and
>> running "ls -Rail /usr/include" generated a few errors. There didn't
>> seem to be as many errors as in the previous test, there were a few
>> errors during shutdown but the shutdown was otherwise normal.
>> See pb3400c-63e3756d1bdf-2.txt.
>>
>> 4) Wallstreet
>> vmlinux-5.13.0-pmac-00004-g63e3756d1bd-2
>> X login worked, and there were no errors. There were no errors during
>> ssh access.
>> See Wallstreet-63e3756d1bdf-2.txt.
>>
> 
> Thanks for collecting these results, Stan. Do you think that the 
> successful result from test 4) could have been just chance?

No. I repeated Test 4 above two more times on the Wallstreet. After
stomping on it as hard as I could, I didn't see any errors. I ran the
following tests simultaneously, with no errors:

a) Ping flood the Wallstreet
862132 packets transmitted, 862117 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.316/0.418/12.163/0.143 ms

b) "ls -Rail /usr" in an ssh window.

c) "find /usr/include -type f -exec sha1sum {} \;" in a second ssh window.

d) With a, b and c running, I logged in at the X console (slow but it
worked). Load average was 7.0 as reported by uptime.

So the success seems to be repeatable (or at least the errors are so
unlikely to happen that I'm not seeing anything).

> 
> It appears that the bug affecting the Powerbook 3400 is unaffected by 
> CONFIG_VMAP_STACK.
> 
> Whereas the bug affecting the Powerbook G3 disappears when 
> CONFIG_VMAP_STACK is disabled (assuming the result from 4 is reliable).
> 
> Either way, these results reiterate that "Oops: Kernel access of bad area, 
> sig: 11" was not entirely resolved by "powerpc/32s: Fix napping restore in 
> data storage interrupt (DSI)".
> 

That sounds right. Thanks for investigating this.

Re: Debian SID kernel doesn't boot on PowerBook 3400c

[Christophe Leroy]

Le 07/08/2021 à 15:09, Stan Johnson a écrit :
> On 8/6/21 10:08 PM, Finn Thain wrote:
>>
>> On Fri, 6 Aug 2021, Stan Johnson wrote:
>>
>>> $ egrep '(CONFIG_PPC_KUAP|CONFIG_VMAP_STACK)' .config
>>> CONFIG_PPC_KUAP=y
>>> CONFIG_PPC_KUAP_DEBUG=y
>>> CONFIG_VMAP_STACK=y
>>> $ strings vmlinux | fgrep "Linux version"
>>> Linux version 5.13.0-pmac-00004-g63e3756d1bd ...
>>> $ cp vmlinux ../vmlinux-5.13.0-pmac-00004-g63e3756d1bd-1
>>>
>>> 1) PB 3400c
>>> vmlinux-5.13.0-pmac-00004-g63e3756d1bd-1
>>> Boots, no errors logging in at (text) fb console. Logging in via ssh and
>>> running "ls -Rail /usr/include" generated errors (and a hung ssh
>>> session). Once errors started, they repeated for almost every command.
>>> See pb3400c-63e3756d1bdf-1.txt.
>>>
>>> 2) Wallstreet
>>> vmlinux-5.13.0-pmac-00004-g63e3756d1bd-1
>>> X login failed, there were errors ("Oops: Kernel access of bad area",
>>> "Oops: Exception in kernel mode"). Logging in via SSH, there were no
>>> additional errors after running "ls -Rail /usr/include" -- the errors
>>> did not escalate as they did on the PB 3400.
>>> See Wallstreet-63e3756d1bdf-1.txt.
>>>
>> ...
>>> $ egrep '(CONFIG_PPC_KUAP|CONFIG_VMAP_STACK)' .config
>>> CONFIG_PPC_KUAP=y
>>> CONFIG_PPC_KUAP_DEBUG=y
>>> # CONFIG_VMAP_STACK is not set
>>> $ strings vmlinux | fgrep "Linux version"
>>> Linux version 5.13.0-pmac-00004-g63e3756d1bd ...
>>> $ cp vmlinux ../vmlinux-5.13.0-pmac-00004-g63e3756d1bd-2
>>>
>>> 3) PB 3400c
>>> vmlinux-5.13.0-pmac-00004-g63e3756d1bd-2
>>> Filesystem was corrupt from the previous test (probably from all the
>>> errors during shutdown). After fixing the filesystem:
>>> Boots, no errors logging in at (text) fb console. Logging in via ssh and
>>> running "ls -Rail /usr/include" generated a few errors. There didn't
>>> seem to be as many errors as in the previous test, there were a few
>>> errors during shutdown but the shutdown was otherwise normal.
>>> See pb3400c-63e3756d1bdf-2.txt.
>>>
>>> 4) Wallstreet
>>> vmlinux-5.13.0-pmac-00004-g63e3756d1bd-2
>>> X login worked, and there were no errors. There were no errors during
>>> ssh access.
>>> See Wallstreet-63e3756d1bdf-2.txt.
>>>
>>
>> Thanks for collecting these results, Stan. Do you think that the
>> successful result from test 4) could have been just chance?
> 
> No. I repeated Test 4 above two more times on the Wallstreet. After
> stomping on it as hard as I could, I didn't see any errors. I ran the
> following tests simultaneously, with no errors:
> 
> a) Ping flood the Wallstreet
> 862132 packets transmitted, 862117 packets received, 0.0% packet loss
> round-trip min/avg/max/stddev = 0.316/0.418/12.163/0.143 ms
> 
> b) "ls -Rail /usr" in an ssh window.
> 
> c) "find /usr/include -type f -exec sha1sum {} \;" in a second ssh window.
> 
> d) With a, b and c running, I logged in at the X console (slow but it
> worked). Load average was 7.0 as reported by uptime.
> 
> So the success seems to be repeatable (or at least the errors are so
> unlikely to happen that I'm not seeing anything).
> 
>>
>> It appears that the bug affecting the Powerbook 3400 is unaffected by
>> CONFIG_VMAP_STACK.
>>
>> Whereas the bug affecting the Powerbook G3 disappears when
>> CONFIG_VMAP_STACK is disabled (assuming the result from 4 is reliable).
>>
>> Either way, these results reiterate that "Oops: Kernel access of bad area,
>> sig: 11" was not entirely resolved by "powerpc/32s: Fix napping restore in
>> data storage interrupt (DSI)".
>>
> 
> That sounds right. Thanks for investigating this.
> 


Thanks a lot for your patience and for the tests.

I'm still having hard time understanding what the problem is.

Could you try the new change I pushed into the git repo ? It shouldn't have any effect, but I prefer 
to eliminate all possibilities. The documentation says that SRR1 upper bit are 0 on DSI and the code 
relies on that. But if the doc is wrong then that can explain the problem. So now I'm forcing it to 
0 regardless.

To get the change, you just have to do 'git pull -r' inside the directory where you checked out the 
sources and build.

Thanks again
Christophe

Re: Debian SID kernel doesn't boot on PowerBook 3400c

[Stan Johnson]

[-- Attachment #1: Type: text/plain, Size: 8103 bytes --]

On 8/7/21 8:35 AM, Christophe Leroy wrote:
> 
> 
> Le 07/08/2021 à 15:09, Stan Johnson a écrit :
>> On 8/6/21 10:08 PM, Finn Thain wrote:
>>>
>>> On Fri, 6 Aug 2021, Stan Johnson wrote:
>>>
>>>> $ egrep '(CONFIG_PPC_KUAP|CONFIG_VMAP_STACK)' .config
>>>> CONFIG_PPC_KUAP=y
>>>> CONFIG_PPC_KUAP_DEBUG=y
>>>> CONFIG_VMAP_STACK=y
>>>> $ strings vmlinux | fgrep "Linux version"
>>>> Linux version 5.13.0-pmac-00004-g63e3756d1bd ...
>>>> $ cp vmlinux ../vmlinux-5.13.0-pmac-00004-g63e3756d1bd-1
>>>>
>>>> 1) PB 3400c
>>>> vmlinux-5.13.0-pmac-00004-g63e3756d1bd-1
>>>> Boots, no errors logging in at (text) fb console. Logging in via ssh
>>>> and
>>>> running "ls -Rail /usr/include" generated errors (and a hung ssh
>>>> session). Once errors started, they repeated for almost every command.
>>>> See pb3400c-63e3756d1bdf-1.txt.
>>>>
>>>> 2) Wallstreet
>>>> vmlinux-5.13.0-pmac-00004-g63e3756d1bd-1
>>>> X login failed, there were errors ("Oops: Kernel access of bad area",
>>>> "Oops: Exception in kernel mode"). Logging in via SSH, there were no
>>>> additional errors after running "ls -Rail /usr/include" -- the errors
>>>> did not escalate as they did on the PB 3400.
>>>> See Wallstreet-63e3756d1bdf-1.txt.
>>>>
>>> ...
>>>> $ egrep '(CONFIG_PPC_KUAP|CONFIG_VMAP_STACK)' .config
>>>> CONFIG_PPC_KUAP=y
>>>> CONFIG_PPC_KUAP_DEBUG=y
>>>> # CONFIG_VMAP_STACK is not set
>>>> $ strings vmlinux | fgrep "Linux version"
>>>> Linux version 5.13.0-pmac-00004-g63e3756d1bd ...
>>>> $ cp vmlinux ../vmlinux-5.13.0-pmac-00004-g63e3756d1bd-2
>>>>
>>>> 3) PB 3400c
>>>> vmlinux-5.13.0-pmac-00004-g63e3756d1bd-2
>>>> Filesystem was corrupt from the previous test (probably from all the
>>>> errors during shutdown). After fixing the filesystem:
>>>> Boots, no errors logging in at (text) fb console. Logging in via ssh
>>>> and
>>>> running "ls -Rail /usr/include" generated a few errors. There didn't
>>>> seem to be as many errors as in the previous test, there were a few
>>>> errors during shutdown but the shutdown was otherwise normal.
>>>> See pb3400c-63e3756d1bdf-2.txt.
>>>>
>>>> 4) Wallstreet
>>>> vmlinux-5.13.0-pmac-00004-g63e3756d1bd-2
>>>> X login worked, and there were no errors. There were no errors during
>>>> ssh access.
>>>> See Wallstreet-63e3756d1bdf-2.txt.
>>>>
>>>
>>> Thanks for collecting these results, Stan. Do you think that the
>>> successful result from test 4) could have been just chance?
>>
>> No. I repeated Test 4 above two more times on the Wallstreet. After
>> stomping on it as hard as I could, I didn't see any errors. I ran the
>> following tests simultaneously, with no errors:
>>
>> a) Ping flood the Wallstreet
>> 862132 packets transmitted, 862117 packets received, 0.0% packet loss
>> round-trip min/avg/max/stddev = 0.316/0.418/12.163/0.143 ms
>>
>> b) "ls -Rail /usr" in an ssh window.
>>
>> c) "find /usr/include -type f -exec sha1sum {} \;" in a second ssh
>> window.
>>
>> d) With a, b and c running, I logged in at the X console (slow but it
>> worked). Load average was 7.0 as reported by uptime.
>>
>> So the success seems to be repeatable (or at least the errors are so
>> unlikely to happen that I'm not seeing anything).
>>
>>>
>>> It appears that the bug affecting the Powerbook 3400 is unaffected by
>>> CONFIG_VMAP_STACK.
>>>
>>> Whereas the bug affecting the Powerbook G3 disappears when
>>> CONFIG_VMAP_STACK is disabled (assuming the result from 4 is reliable).
>>>
>>> Either way, these results reiterate that "Oops: Kernel access of bad
>>> area,
>>> sig: 11" was not entirely resolved by "powerpc/32s: Fix napping
>>> restore in
>>> data storage interrupt (DSI)".
>>>
>>
>> That sounds right. Thanks for investigating this.
>>
> 
> 
> Thanks a lot for your patience and for the tests.
> 
> I'm still having hard time understanding what the problem is.
> 
> Could you try the new change I pushed into the git repo ? It shouldn't
> have any effect, but I prefer to eliminate all possibilities. The
> documentation says that SRR1 upper bit are 0 on DSI and the code relies
> on that. But if the doc is wrong then that can explain the problem. So
> now I'm forcing it to 0 regardless.
> 
> To get the change, you just have to do 'git pull -r' inside the
> directory where you checked out the sources and build.
> 
> Thanks again
> Christophe
> 

Thanks, Christophe.

In the same directory as previous builds:

$ git checkout chleroy-linux/bugtest
HEAD is now at 63e3756d1bdf powerpc/interrupts: Also perform KUAP/KUEP
lock and usertime accounting on NMI
$ git pull -r
You are not currently on a branch.
Please specify which branch you want to rebase against.
...
$ git pull -r chleroy-linux
remote: Enumerating objects: 6, done.
remote: Counting objects: 100% (6/6), done.
remote: Compressing objects: 100% (6/6), done.
remote: Total 6 (delta 0), reused 6 (delta 0), pack-reused 0
Unpacking objects: 100% (6/6), done.
From https://github.com/chleroy/linux
   63e3756d1bdf..9023760b1361  bugtest    -> chleroy-linux/bugtest
Updating 63e3756d1bdf..9023760b1361
Fast-forward
 arch/powerpc/kernel/head_book3s_32.S | 1 +
 1 file changed, 1 insertion(+)
HEAD is up to date.

Hopefully I did that right and ended up at the right spot.

For tests 5 and 6:

$ cp ../dot-config-powermac-5.13 .config
$ scripts/config -e CONFIG_PPC_KUAP -e CONFIG_PPC_KUAP_DEBUG -e
CONFIG_VMAP_STACK
$ make ARCH=powerpc CROSS_COMPILE=powerpc-linux-gnu- -j4 clean
olddefconfig vmlinux
$ egrep '(CONFIG_PPC_KUAP|CONFIG_VMAP_STACK)' .config
CONFIG_PPC_KUAP=y
CONFIG_PPC_KUAP_DEBUG=y
CONFIG_VMAP_STACK=y
$ strings vmlinux | grep "Linux version"
Linux version 5.13.0-pmac-00005-g9023760b136 (johnson@ThinkPad)
(powerpc-linux-gnu-gcc (Debian 8.3.0-2) 8.3.0, GNU ld (GNU Binutils for
Debian) 2.31.1) #3 SMP Sat Aug 7 09:29:11 MDT 2021
$ cp vmlinux ../vmlinux-5.13.0-pmac-00005-g9023760b136-1


5) PB 3400c
vmlinux-5.13.0-pmac-00005-g9023760b136-1
Boots, no errors logging in at (text) fb console. Logging in via ssh and
running "ls -Rail /usr/include" generated errors. As before, once errors
started, they seemed to escalate, including errors during "shutdown -r now".
See pb3400c-g9023760b136-1.txt.

6) Wallstreet
vmlinux-5.13.0-pmac-00005-g9023760b136-1
X login failed, and there were errors. Logging in via SSH, there were no
additional errors after running "ls -Rail /usr/include" -- as before,
the errors did not escalate as they did on the PB 3400.
See Wallstreet-g9023760b136-1.txt.

For tests 7 and 8:

$ cp ../dot-config-powermac-5.13 .config
$ scripts/config -e CONFIG_PPC_KUAP -e CONFIG_PPC_KUAP_DEBUG -d
CONFIG_VMAP_STACK
$ make ARCH=powerpc CROSS_COMPILE=powerpc-linux-gnu- -j4 clean
olddefconfig vmlinux
$ egrep '(CONFIG_PPC_KUAP|CONFIG_VMAP_STACK)' .config
CONFIG_PPC_KUAP=y
CONFIG_PPC_KUAP_DEBUG=y
# CONFIG_VMAP_STACK is not set
$ strings vmlinux | grep "Linux version"
Linux version 5.13.0-pmac-00005-g9023760b136 (johnson@ThinkPad)
(powerpc-linux-gnu-gcc (Debian 8.3.0-2) 8.3.0, GNU ld (GNU Binutils for
Debian) 2.31.1) #4 SMP Sat Aug 7 09:49:03 MDT 2021
$ cp vmlinux ../vmlinux-5.13.0-pmac-00005-g9023760b136-2


7) PB 3400c
vmlinux-5.13.0-pmac-00005-g9023760b136-2
As before, the filesystem was corrupt from the previous test. After
fixing that, this kernel boots, and there were no errors from logging in
at the (text) fb console. Logging in via ssh and running "ls -Rail
/usr/include" generated errors. There were a few errors logging in at
the serial console and during shutdown, but the shutdown was otherwise
normal.
See pb3400c-g9023760b136-2.txt.

8) Wallstreet
vmlinux-5.13.0-pmac-00005-g9023760b136-2
X login worked, and there were no errors. There were also no errors
during ssh access.
Simultaneous stress test, also no errors:
a) Login at X console.
b) Ping flood the Wallstreet
359695 packets transmitted, 359688 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.322/0.428/16.857/0.165 ms
c) "ls -Rail /usr" in an ssh window.
d) "find /usr/include -type f -exec sha1sum {} \;" in a second ssh window.
See Wallstreet-g9023760b136-2.txt.

As far as I could tell, there were no significant changes from the
previous four tests.

-Stan

[-- Attachment #2: pb3400c-g9023760b136-1.txt.xz --]
[-- Type: application/octet-stream, Size: 10208 bytes --]

[-- Attachment #3: Wallstreet-g9023760b136-1.txt.xz --]
[-- Type: application/octet-stream, Size: 8644 bytes --]

[-- Attachment #4: pb3400c-g9023760b136-2.txt.xz --]
[-- Type: application/octet-stream, Size: 6940 bytes --]

[-- Attachment #5: Wallstreet-g9023760b136-2.txt.xz --]
[-- Type: application/octet-stream, Size: 4716 bytes --]

Re: Debian SID kernel doesn't boot on PowerBook 3400c

[Christophe Leroy]

Le 07/08/2021 à 18:26, Stan Johnson a écrit :
> On 8/7/21 8:35 AM, Christophe Leroy wrote:
>>
>>
>> Le 07/08/2021 à 15:09, Stan Johnson a écrit :
>>> On 8/6/21 10:08 PM, Finn Thain wrote:
>>>>
>>>> On Fri, 6 Aug 2021, Stan Johnson wrote:
>>>>
>>>>> $ egrep '(CONFIG_PPC_KUAP|CONFIG_VMAP_STACK)' .config
>>>>> CONFIG_PPC_KUAP=y
>>>>> CONFIG_PPC_KUAP_DEBUG=y
>>>>> CONFIG_VMAP_STACK=y
>>>>> $ strings vmlinux | fgrep "Linux version"
>>>>> Linux version 5.13.0-pmac-00004-g63e3756d1bd ...
>>>>> $ cp vmlinux ../vmlinux-5.13.0-pmac-00004-g63e3756d1bd-1
>>>>>
>>>>> 1) PB 3400c
>>>>> vmlinux-5.13.0-pmac-00004-g63e3756d1bd-1
>>>>> Boots, no errors logging in at (text) fb console. Logging in via ssh
>>>>> and
>>>>> running "ls -Rail /usr/include" generated errors (and a hung ssh
>>>>> session). Once errors started, they repeated for almost every command.
>>>>> See pb3400c-63e3756d1bdf-1.txt.
>>>>>
>>>>> 2) Wallstreet
>>>>> vmlinux-5.13.0-pmac-00004-g63e3756d1bd-1
>>>>> X login failed, there were errors ("Oops: Kernel access of bad area",
>>>>> "Oops: Exception in kernel mode"). Logging in via SSH, there were no
>>>>> additional errors after running "ls -Rail /usr/include" -- the errors
>>>>> did not escalate as they did on the PB 3400.
>>>>> See Wallstreet-63e3756d1bdf-1.txt.
>>>>>
>>>> ...
>>>>> $ egrep '(CONFIG_PPC_KUAP|CONFIG_VMAP_STACK)' .config
>>>>> CONFIG_PPC_KUAP=y
>>>>> CONFIG_PPC_KUAP_DEBUG=y
>>>>> # CONFIG_VMAP_STACK is not set
>>>>> $ strings vmlinux | fgrep "Linux version"
>>>>> Linux version 5.13.0-pmac-00004-g63e3756d1bd ...
>>>>> $ cp vmlinux ../vmlinux-5.13.0-pmac-00004-g63e3756d1bd-2
>>>>>
>>>>> 3) PB 3400c
>>>>> vmlinux-5.13.0-pmac-00004-g63e3756d1bd-2
>>>>> Filesystem was corrupt from the previous test (probably from all the
>>>>> errors during shutdown). After fixing the filesystem:
>>>>> Boots, no errors logging in at (text) fb console. Logging in via ssh
>>>>> and
>>>>> running "ls -Rail /usr/include" generated a few errors. There didn't
>>>>> seem to be as many errors as in the previous test, there were a few
>>>>> errors during shutdown but the shutdown was otherwise normal.
>>>>> See pb3400c-63e3756d1bdf-2.txt.
>>>>>
>>>>> 4) Wallstreet
>>>>> vmlinux-5.13.0-pmac-00004-g63e3756d1bd-2
>>>>> X login worked, and there were no errors. There were no errors during
>>>>> ssh access.
>>>>> See Wallstreet-63e3756d1bdf-2.txt.
>>>>>
>>>>
>>>> Thanks for collecting these results, Stan. Do you think that the
>>>> successful result from test 4) could have been just chance?
>>>
>>> No. I repeated Test 4 above two more times on the Wallstreet. After
>>> stomping on it as hard as I could, I didn't see any errors. I ran the
>>> following tests simultaneously, with no errors:
>>>
>>> a) Ping flood the Wallstreet
>>> 862132 packets transmitted, 862117 packets received, 0.0% packet loss
>>> round-trip min/avg/max/stddev = 0.316/0.418/12.163/0.143 ms
>>>
>>> b) "ls -Rail /usr" in an ssh window.
>>>
>>> c) "find /usr/include -type f -exec sha1sum {} \;" in a second ssh
>>> window.
>>>
>>> d) With a, b and c running, I logged in at the X console (slow but it
>>> worked). Load average was 7.0 as reported by uptime.
>>>
>>> So the success seems to be repeatable (or at least the errors are so
>>> unlikely to happen that I'm not seeing anything).
>>>
>>>>
>>>> It appears that the bug affecting the Powerbook 3400 is unaffected by
>>>> CONFIG_VMAP_STACK.
>>>>
>>>> Whereas the bug affecting the Powerbook G3 disappears when
>>>> CONFIG_VMAP_STACK is disabled (assuming the result from 4 is reliable).
>>>>
>>>> Either way, these results reiterate that "Oops: Kernel access of bad
>>>> area,
>>>> sig: 11" was not entirely resolved by "powerpc/32s: Fix napping
>>>> restore in
>>>> data storage interrupt (DSI)".
>>>>
>>>
>>> That sounds right. Thanks for investigating this.
>>>
>>
>>
>> Thanks a lot for your patience and for the tests.
>>
>> I'm still having hard time understanding what the problem is.
>>
>> Could you try the new change I pushed into the git repo ? It shouldn't
>> have any effect, but I prefer to eliminate all possibilities. The
>> documentation says that SRR1 upper bit are 0 on DSI and the code relies
>> on that. But if the doc is wrong then that can explain the problem. So
>> now I'm forcing it to 0 regardless.
>>
>> To get the change, you just have to do 'git pull -r' inside the
>> directory where you checked out the sources and build.
>>
>> Thanks again
>> Christophe
>>
> 
> Thanks, Christophe.
> 
> In the same directory as previous builds:
> 
> $ git checkout chleroy-linux/bugtest
> HEAD is now at 63e3756d1bdf powerpc/interrupts: Also perform KUAP/KUEP
> lock and usertime accounting on NMI
> $ git pull -r
> You are not currently on a branch.
> Please specify which branch you want to rebase against.
> ...
> $ git pull -r chleroy-linux
> remote: Enumerating objects: 6, done.
> remote: Counting objects: 100% (6/6), done.
> remote: Compressing objects: 100% (6/6), done.
> remote: Total 6 (delta 0), reused 6 (delta 0), pack-reused 0
> Unpacking objects: 100% (6/6), done.
>  From https://github.com/chleroy/linux
>     63e3756d1bdf..9023760b1361  bugtest    -> chleroy-linux/bugtest
> Updating 63e3756d1bdf..9023760b1361
> Fast-forward
>   arch/powerpc/kernel/head_book3s_32.S | 1 +
>   1 file changed, 1 insertion(+)
> HEAD is up to date.
> 
> Hopefully I did that right and ended up at the right spot.
> 
> For tests 5 and 6:
> 
> $ cp ../dot-config-powermac-5.13 .config
> $ scripts/config -e CONFIG_PPC_KUAP -e CONFIG_PPC_KUAP_DEBUG -e
> CONFIG_VMAP_STACK
> $ make ARCH=powerpc CROSS_COMPILE=powerpc-linux-gnu- -j4 clean
> olddefconfig vmlinux
> $ egrep '(CONFIG_PPC_KUAP|CONFIG_VMAP_STACK)' .config
> CONFIG_PPC_KUAP=y
> CONFIG_PPC_KUAP_DEBUG=y
> CONFIG_VMAP_STACK=y
> $ strings vmlinux | grep "Linux version"
> Linux version 5.13.0-pmac-00005-g9023760b136 (johnson@ThinkPad)
> (powerpc-linux-gnu-gcc (Debian 8.3.0-2) 8.3.0, GNU ld (GNU Binutils for
> Debian) 2.31.1) #3 SMP Sat Aug 7 09:29:11 MDT 2021
> $ cp vmlinux ../vmlinux-5.13.0-pmac-00005-g9023760b136-1
> 
> 
> 5) PB 3400c
> vmlinux-5.13.0-pmac-00005-g9023760b136-1
> Boots, no errors logging in at (text) fb console. Logging in via ssh and
> running "ls -Rail /usr/include" generated errors. As before, once errors
> started, they seemed to escalate, including errors during "shutdown -r now".
> See pb3400c-g9023760b136-1.txt.
> 
> 6) Wallstreet
> vmlinux-5.13.0-pmac-00005-g9023760b136-1
> X login failed, and there were errors. Logging in via SSH, there were no
> additional errors after running "ls -Rail /usr/include" -- as before,
> the errors did not escalate as they did on the PB 3400.
> See Wallstreet-g9023760b136-1.txt.
> 
> For tests 7 and 8:
> 
> $ cp ../dot-config-powermac-5.13 .config
> $ scripts/config -e CONFIG_PPC_KUAP -e CONFIG_PPC_KUAP_DEBUG -d
> CONFIG_VMAP_STACK
> $ make ARCH=powerpc CROSS_COMPILE=powerpc-linux-gnu- -j4 clean
> olddefconfig vmlinux
> $ egrep '(CONFIG_PPC_KUAP|CONFIG_VMAP_STACK)' .config
> CONFIG_PPC_KUAP=y
> CONFIG_PPC_KUAP_DEBUG=y
> # CONFIG_VMAP_STACK is not set
> $ strings vmlinux | grep "Linux version"
> Linux version 5.13.0-pmac-00005-g9023760b136 (johnson@ThinkPad)
> (powerpc-linux-gnu-gcc (Debian 8.3.0-2) 8.3.0, GNU ld (GNU Binutils for
> Debian) 2.31.1) #4 SMP Sat Aug 7 09:49:03 MDT 2021
> $ cp vmlinux ../vmlinux-5.13.0-pmac-00005-g9023760b136-2
> 
> 
> 7) PB 3400c
> vmlinux-5.13.0-pmac-00005-g9023760b136-2
> As before, the filesystem was corrupt from the previous test. After
> fixing that, this kernel boots, and there were no errors from logging in
> at the (text) fb console. Logging in via ssh and running "ls -Rail
> /usr/include" generated errors. There were a few errors logging in at
> the serial console and during shutdown, but the shutdown was otherwise
> normal.
> See pb3400c-g9023760b136-2.txt.
> 
> 8) Wallstreet
> vmlinux-5.13.0-pmac-00005-g9023760b136-2
> X login worked, and there were no errors. There were also no errors
> during ssh access.
> Simultaneous stress test, also no errors:
> a) Login at X console.
> b) Ping flood the Wallstreet
> 359695 packets transmitted, 359688 packets received, 0.0% packet loss
> round-trip min/avg/max/stddev = 0.322/0.428/16.857/0.165 ms
> c) "ls -Rail /usr" in an ssh window.
> d) "find /usr/include -type f -exec sha1sum {} \;" in a second ssh window.
> See Wallstreet-g9023760b136-2.txt.
> 
> As far as I could tell, there were no significant changes from the
> previous four tests.
> 

Ok, that was expected, but I wanted to be 100% sure to avoid looking into the wrong direction.

To be honnest, I'm running out of ideas.

We have two remaining independant problems as far as I understand:

PB3400C (603ev core = No hash table)
- A KUAP fault, regardless of CONFIG_VMAP_STACK, due to a clobber of r11 registers apparently.

Wallstreet (Hash table)
- Random faults, only with CONFIG_VMAP_STACK


One thing I am wondering, could there be a link with SMP ?

Would you mind trying with a kernel built without CONFIG_SMP ?

Thanks
Christophe