From: Waiman Long <waiman.long@hpe.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Theodore Ts'o" <tytso@mit.edu>, Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Scott J Norton <scott.norton@hpe.com>,
Douglas Hatch <doug.hatch@hpe.com>
Subject: Re: [PATCH] random: Fix kernel panic due to system_wq use before init
Date: Wed, 14 Sep 2016 15:34:11 -0400 [thread overview]
Message-ID: <57D9A633.2030904@hpe.com> (raw)
In-Reply-To: <CA+55aFwkwUpE1Yg29br6NUt5Y3ggHUR7g3ERHM64J8MBkfrAXQ@mail.gmail.com>
On 09/14/2016 03:19 PM, Linus Torvalds wrote:
> On Wed, Sep 14, 2016 at 12:14 PM, Waiman Long<waiman.long@hpe.com> wrote:
>> In the stack backtrace above, the kernel hadn't even reached SMP boot after
>> about 50s. That was extremely slow. I tried the 4.7.3 kernel and it booted
>> up fine. So I suspect that there may be too many interrupts going on and it
>> consumes most of the CPU cycles. The prime suspect is the random driver, I
>> think.
> Any chance of bisecting it at least partially? The random driver
> doesn't do interrupts itself, it just gets called by other drivers
> doing intterrupts. So if there are too many of them, that would be
> something else..
>
> Linus
I can try, but the 16-socket system that I have at the moment takes a
long time (more than an hour) for one shutdown-reboot cycle. It may not
be really more interrupts in 4.8, it may be that the random driver just
somehow run very slow on my test machine as it seems to have a major
rewrite in the 4.8 cycle. So I would like to solicit what sort of test
that I can run to pinpoint where the problem is. I currently has the
machine till the end of the week.
Cheers,
Longman
next prev parent reply other threads:[~2016-09-14 19:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-14 19:03 [PATCH] random: Fix kernel panic due to system_wq use before init Waiman Long
2016-09-14 19:14 ` Linus Torvalds
2016-09-14 19:24 ` Waiman Long
2016-09-14 19:55 ` Tejun Heo
2016-09-14 22:26 ` Tejun Heo
2016-09-14 19:14 ` Waiman Long
2016-09-14 19:19 ` Linus Torvalds
2016-09-14 19:34 ` Waiman Long [this message]
2016-09-14 21:06 ` Linus Torvalds
2016-09-14 22:15 ` Waiman Long
2016-09-19 3:09 ` Waiman Long
2016-09-19 9:25 ` Matt Fleming
2016-09-19 12:43 ` Matt Fleming
2016-09-19 14:48 ` Waiman Long
2016-09-19 14:51 ` Matt Fleming
2016-09-19 17:09 ` Waiman Long
2016-09-20 14:04 ` Matt Fleming
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=57D9A633.2030904@hpe.com \
--to=waiman.long@hpe.com \
--cc=arnd@arndb.de \
--cc=doug.hatch@hpe.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=scott.norton@hpe.com \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
/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.