linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Al Viro <viro@ZenIV.linux.org.uk>
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: "linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
	"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>
Subject: Re: Boot hang due to "pipe: fold file_operations instances in one" in next-20130408
Date: Mon, 8 Apr 2013 22:22:49 +0100	[thread overview]
Message-ID: <20130408212249.GT4068@ZenIV.linux.org.uk> (raw)
In-Reply-To: <5163346B.5090602@wwwdotorg.org>

On Mon, Apr 08, 2013 at 03:19:39PM -0600, Stephen Warren wrote:
> Al,
> 
> I'm seeing a boot hang on Tegra in next-20130408. Even sysrq on the
> serial console doesn't work, yet I think cpuidle is still running since
> the LED that shows CPU power is flickering.
> 
> git bisect points at commit 9984d73 "pipe: fold file_operations
> instances in one". Reverting
> the-merge-of-the-branch-that-contains-this-patch from next-20130408
> certainly solves the problem; reverting just that one patch is a bit
> painful since it's in the middle of a bunch of other cleanup.
> 
> Do you have any idea what might be wrong? I can't see anything obvious
> in the patch.

What userland do you have?

  reply	other threads:[~2013-04-08 21:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-08 21:19 Boot hang due to "pipe: fold file_operations instances in one" in next-20130408 Stephen Warren
2013-04-08 21:22 ` Al Viro [this message]
     [not found]   ` <20130408212249.GT4068-3bDd1+5oDREiFSDQTTA3OLVCufUGDwFn@public.gmane.org>
2013-04-08 21:36     ` Stephen Warren

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=20130408212249.GT4068@ZenIV.linux.org.uk \
    --to=viro@zeniv.linux.org.uk \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=swarren@wwwdotorg.org \
    /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).