linux-kernel - Re: netconsole and a serial one

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] [day] [month] [year] [list]

Message-ID: <9e4733910809220623ka3670f7r8937d248fec4c986@mail.gmail.com>
Date:	Mon, 22 Sep 2008 09:23:59 -0400
From:	"Jon Smirl" <jonsmirl@...il.com>
To:	"Jeff Moyer" <jmoyer@...hat.com>
Cc:	lkml <linux-kernel@...r.kernel.org>, dhowells@...hat.com
Subject: Re: netconsole and a serial one

On Mon, Sep 22, 2008 at 9:19 AM, Jeff Moyer <jmoyer@...hat.com> wrote:
> "Jon Smirl" <jonsmirl@...il.com> writes:
>
>> I have both netconsole and a serial console setup on an embedded
>> system. This is what I need for the boot process.
>>
>> After I'm booted I want to turn off printk() output to the serial
>> console but keep it going to netconsole.
>> I've been googling for an hour, how do I do this?
>>
>> I need to turn off the serial output after boot because serial
>> printk() disables interrupts for up to 1ms which is enough to cause me
>> to lose a lot of other interrupts.
>
> There's no way (that I know of) to do this presently.  However, I think
> David Howells has been working on a patch that reduces the amount of
> time printk spends with IRQs disabled.

I looked into interrupts and printk several years ago. If I recall
correctly printk() prints with interrupts off to ensure stability in
an OOPS situation.  Could serial printk() be changed to disable
interrupts only in the OOPS situation? It's all of the other
non-critical printks that are impacting my system.

-- 
Jon Smirl
jonsmirl@...il.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/