Subject: Re: sfq dump broken in 2.6.27-rc1

From: Stephen Hemminger <[email-masked]>
Date: Wed, 6 Aug 2008 20:20:29 -0700

On Wed, 06 Aug 2008 18:13:27 -0700 (PDT)
David Miller <[email-masked]> wrote:

> From: Stephen Hemminger <[email-masked]>
> Date: Wed, 6 Aug 2008 18:02:37 -0700
> 
> > With only one sfq (on eth0), I am getting multiple results from
> > 'tc qdisc ls'
> > 
> > # tc qdisc ls
> > qdisc sfq 8001: dev eth0 root limit 127p quantum 1514b 
> > qdisc sfq 8001: dev eth0 root limit 127p quantum 1514b 
> > qdisc sfq 8001: dev eth0 root limit 127p quantum 1514b 
> > qdisc sfq 8001: dev eth0 root limit 127p quantum 1514b 
> > qdisc sfq 8001: dev eth0 root limit 127p quantum 1514b 
> > 
> > Still bisecting, since there is no obvious reason for the sudden borkage.
> 
> Don't bother bisecting, it will take longer than the obvious
> set of debug printk's you could add to net/sched/sch_api.c:tc_dump_qdisc().
> 
> Please use a "mindful" approach to debugging this instead of
> a "mindless" one like bisect :-)

What ever happened to "you broke it, you fix it?"