From: Dave Jones <davej@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Theodore Ts'o" <tytso@mit.edu>,
Wu Fengguang <fengguang.wu@intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: lockups shortly after booting in current git.
Date: Thu, 29 Mar 2012 15:53:54 -0400 [thread overview]
Message-ID: <20120329195354.GA11790@redhat.com> (raw)
In-Reply-To: <CA+55aFx-nzGm1ZZD5bNxmPF2orkXc1_4nCE0jdtznz+AqhBx3A@mail.gmail.com>
On Thu, Mar 29, 2012 at 11:36:49AM -0700, Linus Torvalds wrote:
> On Thu, Mar 29, 2012 at 11:26 AM, Dave Jones <davej@redhat.com> wrote:
> > On Thu, Mar 29, 2012 at 09:03:31AM -0700, Linus Torvalds wrote:
> > > Can you do sysrq-w (or whatever it is that does only the D-state
> > > processes)? That might give the more relevant process information without
> > > everything else making it unreadable...
> >
> > http://codemonkey.org.uk/junk/process-trace2.txt
>
> Ok, this doesn't look all that different, but now it's not truncated
> any more because the random "waits for children or poll" cases are
> gone.
>
> It's still basically all blocked on the ext4 journal. All writes as
> far as I can see.
>
> That said, there's that odd kworker/1:2 there that seems to be
> constantly running. Can you get the EIP for that one (several times)
> by doing sysrq-p (or maybe sysrq-l is better - that should give the
> stack trace too).
Took a while to reproduce that time (but now I have a theory, going
to try and reproduce that after sending this mail).
sysrq-p looks kinda boring. I couldn't get sysrq-l to coincide
with kworker running.
http://codemonkey.org.uk/junk/process-trace3.txt
Dave
next prev parent reply other threads:[~2012-03-29 19:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-29 15:55 lockups shortly after booting in current git Dave Jones
2012-03-29 18:23 ` Linus Torvalds
2012-03-29 18:29 ` Dave Jones
[not found] ` <CA+55aFxOcMt_mcr+ZYwc-SpKbROnh4Gn7jqrFY_SZcBy1Ev7Qw@mail.gmail.com>
[not found] ` <20120329182632.GA6891@redhat.com>
2012-03-29 18:36 ` Linus Torvalds
2012-03-29 19:53 ` Dave Jones [this message]
2012-03-29 20:10 ` Linus Torvalds
2012-03-29 20:26 ` Dave Jones
2012-03-29 20:38 ` Linus Torvalds
2012-03-29 20:39 ` Ted Ts'o
2012-03-29 20:59 ` Linus Torvalds
2012-03-29 21:12 ` Dave Jones
2012-03-29 21:45 ` Ted Ts'o
2012-03-29 21:49 ` Dave Jones
2012-03-29 21:52 ` Linus Torvalds
2012-03-29 22:54 ` Dave Jones
2012-03-29 23:04 ` Linus Torvalds
2012-03-29 23:35 ` Ted Ts'o
2012-03-29 23:25 ` Ted Ts'o
2012-03-29 21:52 ` Dave Jones
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=20120329195354.GA11790@redhat.com \
--to=davej@redhat.com \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox