lkml.org 
[lkml]   [2022]   [Jun]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Boot stall regression from "printk for 5.19" merge
On (22/06/19 20:49), Marek Behún wrote:
[..]
> causes a regression on arm64 (Marvell CN9130-CRB board) where the
> system boot freezes in most cases (and is unusable until restarted by
> watchdog), or, in some cases boots, but the console output gets mangled
> for a while (the serial console spits garbage characters).

Can you please try disabling console kthreads and see how the boot
process goes? Just `return 0` from printk_activate_kthreads() (I think
this should do the trick).

> The stall example:
>
> ...
> [ 1.108141] io scheduler mq-deadline registered
> [ 1.108143] io scheduler kyber registered
> [ 1.163484] armada-ap806-pinctrl f06f4000.system-controller:pinctrl: registered pinctrl driver
> [
>
> Or another:
>
> ...
> [ 1.108155] io scheduler mq-deadline registered
> [ 1.108156] io scheduler kyber registered
> [ 1.162991] armada-ap806-pinctrl f06f4000.system-controller:pinctrl: registered pinctrl driver
> [ 1.163361] armada-cp110-pinctrl f2440000.system-controller:pinctrl: registered pinctrl driver
> [ 1.180827] mv_xor_v2 f0400000.xor: Marvell Version 2 XOR driver
> [
>
> The garbage example:
>
> ...
> [ 0.920951] raid6: using neon recovery algorithm
> [ 0.921228] iommu: Default domain type: Translated
> %
>
> gb@k+cFL/[ 4.954974] DSA: tree 0 setup
> [ 4.955286] cfg80211: Loading compiled-in X.509 certificates for regulatory database

This is pretty suspicious. I don't see how console kthreads would
corrupt the output. I suspect that something else is going on, some
memory corruption, etc.

\
 
 \ /
  Last update: 2022-06-20 07:25    [W:0.153 / U:0.440 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site