From: James Morris <jmorris@namei.org>
To: netdev@vger.kernel.org
Subject: FYI: Xen or kernel bug? (fwd)
Date: Fri, 20 Apr 2007 16:39:27 -0400 (EDT) [thread overview]
Message-ID: <Line.LNX.4.64.0704201638500.19208@d.namei> (raw)
Could be an upstream kernel issue lurking.
---------- Forwarded message ----------
Date: Fri, 20 Apr 2007 22:21:26 +0200
From: Mark Stier <markstier@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: FYI: Xen or kernel bug?
Hello,
tcp_vegas produces division by zero kernel oopses in dom0 when running
a Xen-patched 2.6.16.28 kernel. I have tracked down the problem to
line #256 in tcp_vegas.c: presumably due to flaky Xen timing, the rtt
seems to get zero from time to time (adding 1 to the rtt variable
solves the problem for me). The same should apply to line #140 in
tcp_veno.c, too.
Best regards,
Mark
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2007-04-20 20:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-20 20:39 James Morris [this message]
2007-04-20 21:24 ` FYI: Xen or kernel bug? (fwd) Stephen Hemminger
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=Line.LNX.4.64.0704201638500.19208@d.namei \
--to=jmorris@namei.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox