mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: John Linn <John.Linn@xilinx.com>
To: <linux-kernel@vger.kernel.org>
Subject: console problem?, close(2) hangs /sbin/init
Date: Sat, 22 Jan 2011 14:45:09 -0700	[thread overview]
Message-ID: <7110b8bd-1411-4a92-81b7-1a76f5d5cb65@SG2EHSMHS005.ehs.local> (raw)

I have a kernel that runs fine with a busybox root file system using
inittab.  When I move to a non-busybox init (sysvinit), I see init
hanging when doing a close of standard error very early when it starts.
I have debugged it with GDB but not found the source of the hang as it's
in the kernel it appears.

To debug this, I use init=/bin/sh on the kernel command line, then exec
init to start it. The same root file system works on another board with
a different kernel.  I have also noticed that building init with
INITDEBUG on so that it forks for debugging makes it work fine. This
seems to indicate the device nodes are all fine to me.

It seems related to PID 1 and the console device.

Adding debug to the kernel in sys_close() shows it hanging in
filp_close() and I'm still digging more (maybe locking issue). The
console is a serial device with a newer driver which I suspected to be
the issue, but can't see anything wrong.

Any hints or similar problems seen would be much appreciated.
Thanks,
John


This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.



             reply	other threads:[~2011-01-22 22:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-22 21:45 John Linn [this message]
2011-01-22 22:14 ` Jesper Juhl
2011-01-22 22:17   ` John Linn
2011-01-22 22:40   ` John Linn

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=7110b8bd-1411-4a92-81b7-1a76f5d5cb65@SG2EHSMHS005.ehs.local \
    --to=john.linn@xilinx.com \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®