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
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
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-4-g63e3756d1bd ...
> $ cp vmlinux
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
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
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
+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
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
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
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
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 a écrit :
Hello,
The current Debian SID kernel will not boot on a PowerBook
Le 31/07/2021 à 20:24, Stan Johnson a écrit :
Hi Christophe,
On 7/31/21 9:58 AM, Christophe Leroy wrote:
Stan Johnson 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
Hi Christophe,
On 7/31/21 9:58 AM, Christophe Leroy wrote:
> Stan Johnson 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:
>>
>>
Stan Johnson 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
14 matches
Mail list logo
