lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Yhhh730RX1HpdXp2@google.com>
Date:   Fri, 25 Feb 2022 13:58:23 +0900
From:   Sergey Senozhatsky <senozhatsky@...omium.org>
To:     Steven Rostedt <rostedt@...dmis.org>
Cc:     LKML <linux-kernel@...r.kernel.org>,
        Petr Mladek <pmladek@...e.com>,
        Sergey Senozhatsky <senozhatsky@...omium.org>,
        John Ogness <john.ogness@...utronix.de>
Subject: Re: Strange output on the console

On (22/02/24 23:00), Steven Rostedt wrote:
> I've been noticing that my tests have been spitting out strange output on
> the console. It would happen at boot up and then clear up. It looks like
> something screwed up with the serial timing.
> 
> Attached is a dmesg of one of my test runs as an example.
> 
> I've noticed this on both 32 bit and 64 bit x86.
> 
> I haven't had time to look deeper into this, but I figured I let you know
> about it.
> 
> And it always seems to happen right after:
> 
>   Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
> 
> Maybe this is a serial issue and not a printk one? :-/

Steven, did you notice this recently?
May I perhaps suggest git bisect? (sorry)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ