From: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
To: bugzilla-daemon@bugzilla.kernel.org
Cc: Steven Rostedt <rostedt@goodmis.org>,
Petr Mladek <pmladek@suse.com>,
Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
bugzilla-daemon@bugzilla.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
wen.yang99@zte.com.cn, Peter Zijlstra <peterz@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>,
Christoph Hellwig <hch@infradead.org>
Subject: Re: [Bug 199003] console stalled, cause Hard LOCKUP.
Date: Mon, 26 Mar 2018 14:18:45 +0900 [thread overview]
Message-ID: <20180326051845.GB7779@jagdpanzerIV> (raw)
In-Reply-To: <bug-199003-14532-DgJdGAHEOE@https.bugzilla.kernel.org/>
Cc-ing the kernel list and printk people.
Wen Yang, any chance we can switch to email? Bugzilla is not very handful.
On (03/26/18 02:40), bugzilla-daemon@bugzilla.kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=199003
>
> --- Comment #11 from Wen Yang (wen.yang99@zte.com.cn) ---
> Hello Steven,
>
> +module_param_named(synchronous, printk_sync, bool, S_IRUGO);
> +MODULE_PARM_DESC(synchronous, "make printing to console synchronous");
>
> It's depend on this kernel parameter(printk.synchronous), but this parameter is
> readonly.
> So we must change grub files, and alse need to restart the server for changes
> to take effect.
> If we can configure it dynamically, it will be more useful.
So you are testing printk_kthread now, right? May I ask why?
Did Steven's patch help?
-ss
next prev parent reply other threads:[~2018-03-26 5:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-199003-14532@https.bugzilla.kernel.org/>
[not found] ` <bug-199003-14532-lzL5ySZS5x@https.bugzilla.kernel.org/>
2018-03-05 9:27 ` [Bug 199003] console stalled, cause Hard LOCKUP Sergey Senozhatsky
[not found] ` <bug-199003-14532-4aWzZJgGHz@https.bugzilla.kernel.org/>
2018-03-21 7:28 ` Sergey Senozhatsky
[not found] ` <bug-199003-14532-DgJdGAHEOE@https.bugzilla.kernel.org/>
2018-03-26 5:18 ` Sergey Senozhatsky [this message]
[not found] ` <bug-199003-14532-IBTfRpvy7t@https.bugzilla.kernel.org/>
2018-03-27 10:37 ` Sergey Senozhatsky
[not found] <bug-199003-8243@https.bugzilla.kernel.org/>
[not found] ` <bug-199003-8243-Txkdkdv5Cm@https.bugzilla.kernel.org/>
2018-03-21 13:44 ` Steven Rostedt
2018-03-22 2:14 ` Sergey Senozhatsky
2018-03-22 2:34 ` Sergey Senozhatsky
2018-03-22 22:25 ` Steven Rostedt
2018-03-23 12:06 ` Sergey Senozhatsky
2018-03-23 13:16 ` Petr Mladek
2018-03-26 5:12 ` Sergey Senozhatsky
2018-03-26 9:26 ` Petr Mladek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180326051845.GB7779@jagdpanzerIV \
--to=sergey.senozhatsky.work@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=wen.yang99@zte.com.cn \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.