[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CA+7wUsyO1QR6wzR9_Lj856m9OKOpvz4OjQKKY8SXe-iG+TbWRg@mail.gmail.com>
Date: Tue, 24 Apr 2018 20:48:00 +0200
From: Mathieu Malaterre <malat@...ian.org>
To: Michael Ellerman <mpe@...erman.id.au>
Cc: Christophe LEROY <christophe.leroy@....fr>,
Benjamin Herrenschmidt <benh@...nel.crashing.org>,
Paul Mackerras <paulus@...ba.org>,
linuxppc-dev <linuxppc-dev@...ts.ozlabs.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] powerpc: Allow selection of CONFIG_LD_DEAD_CODE_DATA_ELIMINATION
On Wed, Apr 18, 2018 at 5:13 PM, Michael Ellerman <mpe@...erman.id.au> wrote:
> Mathieu Malaterre <malat@...ian.org> writes:
>> On Wed, Apr 18, 2018 at 8:34 AM, Christophe LEROY
> ...
>>
>>> Can you also provide a copy of the messages you can see (prom_init ...) when
>>> boot is ok ?
>>
>> Hum. I've always been interested in seeing it also myself. Is there a
>> way to setup env to see those message (netconsole, delayed boot
>> messages ...) ? I never found a clear documentation on how to do that
>> on (closed) Apple hardware.
>
> If you see nothing after prom_init it usually indicates the kernel died
> very early in boot before it could find the console.
>
> The only option then is to enable one of the hard-coded EARLY_DEBUG
> options.
Right I see them now.
> I don't know which one works on a G4, maybe CONFIG_PPC_EARLY_DEBUG_BOOTX ?
Exactly !
> I assume it doesn't have a serial port.
- 56K Modem line (yes really!)
- 2 USB
- 1 Firewire
:(
> cheers
Powered by blists - more mailing lists