Re: usmsc weirdness

[christos%astron.com@localhost (Christos Zoulas)]

In article <m27es1u54d.fsf%thuvia.hamartun.priv.no@localhost>,
Tom Ivar Helbekkmo  <tih%hamartun.priv.no@localhost> wrote:
>-=-=-=-=-=-
>
>I've realized that I didn't need to ping Google to study this: just
>pinging the local gateway, my access router to my ISP, will show it.
>If I ping it at a fast rate, a tcpdump running on the Pi will show that
>it's sending the packets out at the right rate, but receiving responses
>in periodic bursts.  Since I've never experienced this problem with any
>other machines on that network, I suspect it's happening within the Pi.
>
>I thought I'd take a look at interrupt counters, but then this happens:
>
>: otium# ;intrctl list
>intrctl: intrctl_io_alloc: Cannot allocate memory
>
>It's actually this call that fails:
>
>    error = sysctlbyname("kern.intr.list", NULL, &buf_size, NULL, 0);
>
>This is with 8.99.10.  Is that a local problem, or are others seeing it?

It is probable because interrupt_construct_intrids fails. It always
returns ENOMEM on failure. I will fix it.

christos