All of lore.kernel.org
 help / color / mirror / Atom feed
From: John OSullivan <john.osullivan@cloudiumsystems.com>
To: buildroot@busybox.net
Subject: [Buildroot] Init not handling signals
Date: Tue, 12 Nov 2013 16:27:16 -0000	[thread overview]
Message-ID: <000301cedfc4$0dfbe880$29f3b980$@osullivan@cloudiumsystems.com> (raw)

Hi,

I'm not sure if this is the correct forum to ask this question but I have
seen a few buildroot/busybox references to this problem but none with a
clear solution.

I am running buildroot-2012-05 with busybox 1.19, using the busybox init
with an inittab based on the default one provided.

In the init tab there is a trap for ctrlaltdel

::ctrlaltdel:/sbin/reboot

 

This line is never called after hitting ctrl alt del on a keyboard

Instead we get a signal pending on the init task

Cat /proc/1/status

---------------------------

Name:   swapper

State:    R (running)

Tgid:      1

Pid:        1

PPid:      0

TracerPid:            0

Uid:        0             0             0             0

Gid:        0             0             0             0

FDSize:  32

Groups: 

Threads:              1

SigQ:      1/938

SigPnd:  0000000000000100

ShdPnd: 0000000000000002

SigBlk:   0000000000000000

SigIgn:   0000000000000000

SigCgt:  0000000000000000

CapInh: 0000000000000000

 

After the init process is signalled the Swapper task assumes 100% processor
occupancy and system performance degenerates. (as evidenced by top)

The kernel version is 2.6.33.3 (I also tried 2.6.39.4). This happens on a
minimal system built from buildroot without any other processes running, the
only way to recover the situation is with a reboot.

Any ideas or suggestions on what the issue might be?

I was going to try a non-busybox init but before I do that I want to make
sure that there is not an available explanation for the behaviour I am
observing.

 

Regards

johnos

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20131112/c0ea04d5/attachment.html>

             reply	other threads:[~2013-11-12 16:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-12 16:27 John OSullivan [this message]
2013-11-13 20:32 ` [Buildroot] Init not handling signals Arnout Vandecappelle
     [not found] <5282583a.e630420a.3bfb.507aSMTPIN_ADDED_BROKEN@mx.google.com>
2013-11-12 20:51 ` Thomas De Schampheleire

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='000301cedfc4$0dfbe880$29f3b980$@osullivan@cloudiumsystems.com' \
    --to=john.osullivan@cloudiumsystems.com \
    --cc=buildroot@busybox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.