On Wed, Apr 10, 2024 at 11:31 AM Christophe Leroy
wrote:
>
>
>
> Le 10/04/2024 à 17:22, Joel Savitz a écrit :
> > [Vous ne recevez pas souvent de courriers de jsav...@redhat.com. Découvrez
> > pourquoi ceci est important à https://aka.ms/LearnAboutSenderIdentification
> > ]
> >
> > On Mon, Apr
Le 10/04/2024 à 17:22, Joel Savitz a écrit :
> [Vous ne recevez pas souvent de courriers de jsav...@redhat.com. Découvrez
> pourquoi ceci est important à https://aka.ms/LearnAboutSenderIdentification ]
>
> On Mon, Apr 1, 2024 at 10:17 AM Joel Savitz wrote:
>>
>> On Tue, Mar 26, 2024 at 12:45
On Mon, Apr 1, 2024 at 10:17 AM Joel Savitz wrote:
>
> On Tue, Mar 26, 2024 at 12:45 AM Joel Savitz wrote:
> >
> > On Fri, Mar 8, 2024 at 5:18 AM Aneesh Kumar K.V
> > wrote:
> > >
> > > Joel Savitz writes:
> > >
> > > > On 64-bit powerpc, usage of a non-16MB-aligned value for the mem= kernel
On Tue, Mar 26, 2024 at 12:45 AM Joel Savitz wrote:
>
> On Fri, Mar 8, 2024 at 5:18 AM Aneesh Kumar K.V
> wrote:
> >
> > Joel Savitz writes:
> >
> > > On 64-bit powerpc, usage of a non-16MB-aligned value for the mem= kernel
> > > cmdline parameter results in a system hang at boot.
> > >
> > >
On Fri, Mar 8, 2024 at 5:18 AM Aneesh Kumar K.V wrote:
>
> Joel Savitz writes:
>
> > On 64-bit powerpc, usage of a non-16MB-aligned value for the mem= kernel
> > cmdline parameter results in a system hang at boot.
> >
> > For example, using 'mem=4198400K' will always reproduce this issue.
> >
>
Joel Savitz writes:
> On 64-bit powerpc, usage of a non-16MB-aligned value for the mem= kernel
> cmdline parameter results in a system hang at boot.
>
> For example, using 'mem=4198400K' will always reproduce this issue.
>
> This patch fixes the problem by aligning any argument to mem= to 16MB
>
Joel Savitz writes:
> On Fri, Mar 1, 2024 at 6:23 PM Michael Ellerman wrote:
>> Joel Savitz writes:
>> > On 64-bit powerpc, usage of a non-16MB-aligned value for the mem= kernel
>> > cmdline parameter results in a system hang at boot.
>>
>> Can you give us any more details on that? It might be
On 3/2/24 4:53 AM, Michael Ellerman wrote:
> Hi Joel,
>
> Joel Savitz writes:
>> On 64-bit powerpc, usage of a non-16MB-aligned value for the mem= kernel
>> cmdline parameter results in a system hang at boot.
>
> Can you give us any more details on that? It might be a bug we can fix.
>
>> For
On Fri, Mar 1, 2024 at 6:23 PM Michael Ellerman wrote:
>
> Hi Joel,
>
> Joel Savitz writes:
> > On 64-bit powerpc, usage of a non-16MB-aligned value for the mem= kernel
> > cmdline parameter results in a system hang at boot.
>
> Can you give us any more details on that? It might be a bug we can
Hi Joel,
Joel Savitz writes:
> On 64-bit powerpc, usage of a non-16MB-aligned value for the mem= kernel
> cmdline parameter results in a system hang at boot.
Can you give us any more details on that? It might be a bug we can fix.
> For example, using 'mem=4198400K' will always reproduce this
On 64-bit powerpc, usage of a non-16MB-aligned value for the mem= kernel
cmdline parameter results in a system hang at boot.
For example, using 'mem=4198400K' will always reproduce this issue.
This patch fixes the problem by aligning any argument to mem= to 16MB
corresponding with the large page
11 matches
Mail list logo
