Skip to contentSkip to conversation

Boot hang due to "pipe: fold file_operations instances in one" in next-20130408

DISCUSSION Stephen Warren 2 participants 3 messages Apr 8, 2013 1 message not in the archive

Subsystems (2)
lore
Share & tools
lore
#0 lore raw

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.

#1 lore raw
Quoted 6 lines · Stephen Warren

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.

Quoted 8 lines

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?

A message that is not in the archive (sent off-list or not yet received): 20130408212249.GT4068-3bDd1+5oDREiFSDQTTA3OLVCufUGDwFn@public.gmane.org

#3 lore raw
Quoted 13 lines · Al Viro
Quoted 12 lines · Stephen Warren

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.

Quoted 4 lines
Quoted 2 lines

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.