Some more info.
There is indeed no difference in the sundance driver module between
2.6.18.dfsg.1-23etch1 & 2.6.18.dfsg.1-24etch1 as mentioned by dann frazier in
#514833 (both driver binary and source are 100% identical).
Looking at the initial warning from my report I compared the
/net/sched/sch_generic.c from the sources for 2.6.18.dfsg.1-23etch1 &
2.6.18.dfsg.1-24etch1 and there is a difference there.
etch-dlink-test:~/tmp# diff sch_generic-2.6.18.dfsg.1-23etch1.c
sch_generic-2.6.18.dfsg.1-24etch1.c
185a186,187
> unsigned long start_time = jiffies;
>
189,190c191,204
< while (qdisc_restart(dev) < 0 && !netif_queue_stopped(dev))
< /* NOTHING */;
---
> while (qdisc_restart(dev) < 0) {
> if (netif_queue_stopped(dev))
> break;
>
> /*
> * Postpone processing if
> * 1. another process needs the CPU;
> * 2. we've been doing it for too long.
> */
> if (need_resched() || jiffies != start_time) {
> netif_schedule(dev);
> break;
> }
> }
Hope this helps,
Mike.
