lkml.org 
[lkml]   [2022]   [Jun]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    From
    Date
    SubjectRe: [BUG] Threaded printk breaks early debugging
    On Sat, Jun 11, 2022 at 10:57 PM Sergey Senozhatsky
    <senozhatsky@chromium.org> wrote:
    >
    > On (22/06/10 11:34), Peter Geis wrote:
    > > > On 2022-06-10, Peter Geis <pgwipeout@gmail.com> wrote:
    > > > > However I've run into an issue debugging early boot issues. Anything
    > > > > that causes the kernel threading system to die (for example here, a
    > > > > NPE) causes the boot console to halt before it outputs the error.
    > > >
    > > > A null pointer exception should trigger a panic, which will cause printk
    > > > to enter direct mode for the oops. It should be just as effective as
    > > > before introducing the printing kthreads.
    > >
    > > This might be a side effect of the fact that this is on a low powered
    > > arm64 board. I noticed with threading enabled during large bursts the
    > > console drops an excessive amount of messages. It's especially
    > > apparent during the handover from earlycon to the normal console.
    >
    > How many CPUs does it have?

    Four and all are online when the error occurs.

    \
     
     \ /
      Last update: 2022-06-12 15:32    [W:2.551 / U:0.320 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site