From: Pavel Machek <pavel@ucw.cz>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
Jan Kara <jack@suse.cz>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
Ye Xiaolong <xiaolong.ye@intel.com>,
Petr Mladek <pmladek@suse.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Peter Zijlstra <peterz@infradead.org>,
"Rafael J . Wysocki" <rjw@rjwysocki.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jslaby@suse.com>, Len Brown <len.brown@intel.com>,
linux-kernel@vger.kernel.org, lkp@01.org
Subject: Re: [printk] fbc14616f4: BUG:kernel_reboot-without-warning_in_test_stage
Date: Sun, 9 Apr 2017 11:57:32 +0200 [thread overview]
Message-ID: <20170409095732.GA27363@amd> (raw)
In-Reply-To: <20170407102917.3121e9f0@gandalf.local.home>
[-- Attachment #1: Type: text/plain, Size: 1071 bytes --]
On Fri 2017-04-07 10:29:17, Steven Rostedt wrote:
> On Fri, 7 Apr 2017 10:14:49 +0200
> Pavel Machek <pavel@ucw.cz> wrote:
>
> > > serial console can be quite slow. and port->lock, that is acquired by
> > > console_unlock()->call_console_drivers()->write(), is also accessible
> > > by serial driver's IRQ handler, and this lock may be busy long
> > > enough -- as long as that IRQ handler transmits/receives chars. but
> > > that's not the point.
> >
> > Well. This is what we had for 20 years.
>
> But for the last 20 years we were not booting on machines with over 200
> CPUs. Well, we were, but those had custom kernels (which probably
> dismantled printk).
Well, not a problem. Just find a solution that works for dual core
machines as well as it did for 20 years.
2 seconds timeout as proposed earlier should work well for big
machines, and with no regressions on small machines.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2017-04-09 9:57 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-29 9:25 [RFC][PATCHv2 0/8] printk: introduce printing kernel thread Sergey Senozhatsky
2017-03-29 9:25 ` [RFC][PATCHv2 1/8] printk: move printk_pending out of per-cpu Sergey Senozhatsky
2017-03-31 13:09 ` Petr Mladek
2017-03-31 13:33 ` Peter Zijlstra
2017-04-03 11:23 ` Sergey Senozhatsky
2017-04-03 12:43 ` Petr Mladek
2017-03-29 9:25 ` [RFC][PATCHv2 2/8] printk: introduce printing kernel thread Sergey Senozhatsky
2017-04-04 9:01 ` Petr Mladek
2017-04-04 9:36 ` Sergey Senozhatsky
2017-04-06 17:14 ` Pavel Machek
2017-04-07 5:12 ` Sergey Senozhatsky
2017-04-07 7:21 ` Pavel Machek
2017-04-07 8:15 ` Sergey Senozhatsky
2017-04-07 12:06 ` Pavel Machek
2017-03-29 9:25 ` [RFC][PATCHv2 3/8] printk: offload printing from wake_up_klogd_work_func() Sergey Senozhatsky
2017-03-31 14:56 ` Petr Mladek
2017-04-04 16:15 ` Sergey Senozhatsky
2017-03-29 9:25 ` [RFC][PATCHv2 4/8] pm: switch to printk.emergency mode in unsafe places Sergey Senozhatsky
2017-03-31 15:06 ` Petr Mladek
2017-04-06 17:20 ` Pavel Machek
2017-04-09 10:59 ` Andreas Mohr
2017-04-10 12:20 ` Petr Mladek
2017-04-10 14:38 ` Sergey Senozhatsky
2017-03-29 9:25 ` [RFC][PATCHv2 5/8] sysrq: " Sergey Senozhatsky
2017-03-31 15:37 ` Petr Mladek
2017-04-01 0:04 ` Sergey Senozhatsky
2017-03-29 9:25 ` [RFC][PATCHv2 6/8] kexec: " Sergey Senozhatsky
2017-03-31 15:39 ` Petr Mladek
2017-03-29 9:25 ` [RFC][PATCHv2 7/8] printk: add printk emergency_mode parameter Sergey Senozhatsky
2017-04-03 15:29 ` Petr Mladek
2017-04-04 8:29 ` Sergey Senozhatsky
2017-03-29 9:25 ` [RFC][PATCHv2 8/8] printk: enable printk offloading Sergey Senozhatsky
2017-03-30 21:38 ` [printk] fbc14616f4: BUG:kernel_reboot-without-warning_in_test_stage kernel test robot
2017-03-31 2:35 ` Sergey Senozhatsky
2017-03-31 4:04 ` Sergey Senozhatsky
2017-03-31 6:39 ` Ye Xiaolong
2017-03-31 14:47 ` Sergey Senozhatsky
2017-03-31 15:28 ` Eric W. Biederman
2017-04-03 9:31 ` Jan Kara
2017-04-03 10:06 ` Petr Mladek
2017-04-06 17:33 ` Pavel Machek
2017-04-07 4:44 ` Sergey Senozhatsky
2017-04-07 7:15 ` Pavel Machek
2017-04-07 7:46 ` Sergey Senozhatsky
2017-04-07 8:14 ` Pavel Machek
2017-04-07 12:10 ` Sergey Senozhatsky
2017-04-07 12:44 ` Pavel Machek
2017-04-07 14:40 ` Steven Rostedt
2017-05-08 6:37 ` Sergey Senozhatsky
2017-05-17 13:13 ` Petr Mladek
2017-04-07 15:13 ` Sergey Senozhatsky
2017-04-07 15:23 ` Peter Zijlstra
2017-04-07 15:40 ` Sergey Senozhatsky
2017-04-09 18:21 ` Eric W. Biederman
2017-04-10 4:46 ` Sergey Senozhatsky
2017-04-09 10:12 ` Pavel Machek
2017-04-10 4:53 ` Sergey Senozhatsky
2017-04-10 11:54 ` Petr Mladek
2017-04-10 15:08 ` Sergey Senozhatsky
2017-04-10 18:48 ` Pavel Machek
2017-04-11 1:46 ` Sergey Senozhatsky
2017-04-11 16:19 ` Sergey Senozhatsky
2017-04-12 18:43 ` Pavel Machek
2017-04-13 4:34 ` Sergey Senozhatsky
2017-04-13 5:50 ` Sergey Senozhatsky
2017-04-13 8:19 ` Sergey Senozhatsky
2017-04-13 14:03 ` Petr Mladek
2017-04-14 4:42 ` Sergey Senozhatsky
2017-04-07 14:29 ` Steven Rostedt
2017-04-09 9:57 ` Pavel Machek [this message]
2017-04-03 10:51 ` Sergey Senozhatsky
2017-04-05 7:29 ` Ye Xiaolong
2017-04-05 8:40 ` Sergey Senozhatsky
2017-04-03 15:42 ` [RFC][PATCHv2 8/8] printk: enable printk offloading Petr Mladek
2017-04-04 13:20 ` Sergey Senozhatsky
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=20170409095732.GA27363@amd \
--to=pavel@ucw.cz \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=gregkh@linuxfoundation.org \
--cc=jack@suse.cz \
--cc=jslaby@suse.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=peterz@infradead.org \
--cc=pmladek@suse.com \
--cc=rjw@rjwysocki.net \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky.work@gmail.com \
--cc=sergey.senozhatsky@gmail.com \
--cc=torvalds@linux-foundation.org \
--cc=xiaolong.ye@intel.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).