linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Elison Niven" <elison.niven@matrixcomsec.com>
To: <linuxppc-dev@lists.ozlabs.org>
Subject: No userspace processes scheduled for execution when ethernet link state changes
Date: Thu, 8 Apr 2010 12:25:24 +0530	[thread overview]
Message-ID: <20100408122524@dummy.ozlabs.org> (raw)

Hi List,

I am using linux 2.6.22 on a MPC8358E custom board.

I use a simple userspace process that periodically (100 ms) calls an ioctl
to a watchdog driver to toggle its pin state.

The problem is that when I insert or remove the Ethernet cable, this process
is not scheduled for execution. The watchdog IC resets the board if a pulse
is not received in 1.2 seconds.

I am clueless as to where to look in - the vitesse (PHY) driver or the
ucc_geth driver or the kernel scheduler.

I have tried modifying the priority of the process but there are no changes
to this behavior.

Then I wrote another driver that uses a kernel timer, that periodically (100
ms) toggles the pin state. In this case, I have observed on an oscilloscope
that the pulses are regular even when the Ethernet cable is inserted or
removed.

It means that the kernel itself is not in a waiting state when the cable is
inserted or removed but *however* (as per my observations) it does not
schedule all userspace processes for the next 1 - 2 seconds.

Well, ofcourse an alternate solution to implementing the watchdog on my
board would be to toggle the watchdog pin using a kernel timer.

But, Why the userspace process is not getting its time share to execute?
Please throw some light as to where to look? Is this issue known or could it
be my board-specific?

Thanks,
Elison

                 reply	other threads:[~2010-04-08  7:09 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20100408122524@dummy.ozlabs.org \
    --to=elison.niven@matrixcomsec.com \
    --cc=linuxppc-dev@lists.ozlabs.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).