[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080806202029.63f25c81@extreme>
Date: Wed, 6 Aug 2008 20:20:29 -0700
From: Stephen Hemminger <stephen.hemminger@...tta.com>
To: David Miller <davem@...emloft.net>
Cc: kaber@...sh.net, netdev@...r.kernel.org
Subject: Re: sfq dump broken in 2.6.27-rc1
On Wed, 06 Aug 2008 18:13:27 -0700 (PDT)
David Miller <davem@...emloft.net> wrote:
> From: Stephen Hemminger <stephen.hemminger@...tta.com>
> 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?"
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists