linux-kernel - RE: Strange output on the console

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]

Date:   Fri, 25 Feb 2022 06:12:35 +0000
From:   David Laight <David.Laight@...LAB.COM>
To:     'Steven Rostedt' <rostedt@...dmis.org>,
        LKML <linux-kernel@...r.kernel.org>
CC:     Petr Mladek <pmladek@...e.com>,
        Sergey Senozhatsky <senozhatsky@...omium.org>,
        John Ogness <john.ogness@...utronix.de>
Subject: RE: Strange output on the console

From: Steven Rostedt
> Sent: 25 February 2022 04:01
> 
> 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? :-/

Looks very much like the serial baud rate is being reset.

	David

-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)