* No userspace processes scheduled for execution when ethernet link state changes
@ 2010-04-08 6:55 Elison Niven
0 siblings, 0 replies; only message in thread
From: Elison Niven @ 2010-04-08 6:55 UTC (permalink / raw)
To: linuxppc-dev
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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2010-04-08 7:09 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-04-08 6:55 No userspace processes scheduled for execution when ethernet link state changes Elison Niven
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).