From: Dave Jones <davej@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
Wu Fengguang <fengguang.wu@intel.com>,
"Theodore Ts'o" <tytso@mit.edu>
Subject: Re: lockups shortly after booting in current git.
Date: Thu, 29 Mar 2012 14:29:19 -0400 [thread overview]
Message-ID: <20120329182919.GB6891@redhat.com> (raw)
In-Reply-To: <CA+55aFySh2VJ3+Hdu8oFR3oBERS0uh=3ezBsbkWQNfsLHSDyqw@mail.gmail.com>
On Thu, Mar 29, 2012 at 11:23:57AM -0700, Linus Torvalds wrote:
> That's doubly true since I see processes waiting for the journal lock,
> but I don't actually see anything waiting for journal IO completion.
> Did something not release the journal lock. Even banshee - that *is*
> waiting for actual IO - seems to wait for page_writeback, which is not
> done by the *disk* driver, but by the filesystem (end_page_writeback).
> So that would be consistent with the ext4 changes having broken that.
>
> Was there a previous post-3.3 git kernel that worked?
This is the first one I tried. (I've not been anywhere with the laptop
since 3.3 -- clearly I need to get out more).
3.3 final worked ok though.
Dave
next prev parent reply other threads:[~2012-03-29 18:29 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 [this message]
[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
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=20120329182919.GB6891@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