From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
To: Al Viro <viro-3bDd1+5oDREiFSDQTTA3OLVCufUGDwFn@public.gmane.org>
Cc: "linux-next-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-next-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: Boot hang due to "pipe: fold file_operations instances in one" in next-20130408
Date: Mon, 08 Apr 2013 15:36:06 -0600 [thread overview]
Message-ID: <51633846.2040305@wwwdotorg.org> (raw)
In-Reply-To: <20130408212249.GT4068-3bDd1+5oDREiFSDQTTA3OLVCufUGDwFn@public.gmane.org>
On 04/08/2013 03:22 PM, Al Viro wrote:
> 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?
It's Ubuntu 12.04.01 for ARM (armhf), with quite a few updates not
installed.
prev parent reply other threads:[~2013-04-08 21:36 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
[not found] ` <20130408212249.GT4068-3bDd1+5oDREiFSDQTTA3OLVCufUGDwFn@public.gmane.org>
2013-04-08 21:36 ` Stephen Warren [this message]
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=51633846.2040305@wwwdotorg.org \
--to=swarren-3lzwwm7+weoh9zmkesr00q@public.gmane.org \
--cc=linux-next-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=viro-3bDd1+5oDREiFSDQTTA3OLVCufUGDwFn@public.gmane.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).