ifconfig problem
Rob Landley
rob at landley.net
Sat Sep 2 17:52:04 UTC 2006
On Friday 01 September 2006 10:58 am, Raphaël HUCK wrote:
> ifconfig has been working great up to now, but suddenly, it stopped working.
>
> No change was made neither in the hardware nor in the software. It was
> working 1 hour ago, it is working anymore now.
>
> When I launch "/sbin/ifconfig", it nevers displays anything, never
> returns. It is not killable also.
Unkillable processes are not a userspace problem, they're the kernel.
If this "not killable" is stuck in D state, it's a kernel problem. If the
stat field (third field of "ps ax" or fourth field of busybox's ps) is "D",
then the process is in uninterruptible sleep waiting on a device driver.
This normally lasts for small fractions of a section. If it ever lasts
longer than that, then there was a dropped lock or lost interrupt or some
such in the kernel.
> This error is maybe caused by a hardware problem of the interface, I
> have to investigate further on this point.
Google for "process stuck in D state".
> ioctl(4, 0x8915
An ioctl didn't return. That ain't us.
Rob
--
Never bet against the cheap plastic solution.
More information about the busybox
mailing list