From: Chris Friesen <chris.friesen@genband.com>
To: netdev <netdev@vger.kernel.org>
Subject: anyone know of a bug which causes dev->qdisc to be noop_qdisc for a working interface?
Date: Thu, 26 Jul 2012 17:30:39 -0600 [thread overview]
Message-ID: <5011D31F.4060001@genband.com> (raw)
Hi all,
I've been asked to help debug an issue we've had in the field where
after a month or so of uptime for a server the router it was connected
to was rebooted and one of the eth links stopped transmitting packets.
Downing and upping the link doesn't fix it. An ethtool offline selftest
doesn't fix it. Only known fix is a reboot of the server.
The server is running 2.6.14, which makes things interesting.
Luckily we had kprobes enabled and I tracked down the source code, and
I've been able to isolate the source of the problem. It seems that for
the problematic eth device (which is up and is receiving packets)
dev->qdisc is set to noop_qdisc, which ends up silently dropping all
outgoing packets on the floor. dev->qdisc_sleeping is pfifo_fast as
expected.
Does anyone have any ideas how this might have happened? Does anyone
remember a bug in this area from that long ago?
Thanks,
Chris
--
Chris Friesen
Software Designer
3500 Carling Avenue
Ottawa, Ontario K2H 8E9
www.genband.com
reply other threads:[~2012-07-26 23:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5011D31F.4060001@genband.com \
--to=chris.friesen@genband.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.