From: Stephen Hemminger <shemminger@vyatta.com>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: TB <lkml@techboom.com>, netdev <netdev@vger.kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: Divide error in bictcp_cong_avoid ?
Date: Wed, 4 May 2011 11:33:51 -0700 [thread overview]
Message-ID: <20110504113351.4643a0c9@nehalam> (raw)
In-Reply-To: <20110504104940.cd0d9e9a.rdunlap@xenotime.net>
On Wed, 4 May 2011 10:49:40 -0700
Randy Dunlap <rdunlap@xenotime.net> wrote:
> [add cc to netdev]
>
>
> On Wed, 04 May 2011 12:03:31 -0400 TB wrote:
>
> > We're having this issue sporadically on a few servers and this is the
> > backtrace we get from netconsole.
> >
> >
> > [28522.642419] divide error: 0000 [#1] SMP
> > [28522.642457] last sysfs file:
> > /sys/devices/pci0000:00/0000:00:1f.2/host2/target2:0:0/2:0:0:0/vendor
> > [28522.642504] CPU 0
> > [28522.642511] Modules linked in:
> > i2c_i801
> > i2c_core
> > evdev
> > button
> > [28522.642570]
> > [28522.642590] Pid: 0, comm: swapper Not tainted 2.6.38.5 #6
> >
> > Supermicro X8DTH-i/6/iF/6F
> > /
> > X8DTH
> >
What kernel version? I suspect they are running something really old
kernel like RHEL 5 since BIC has not been the default congestion control for
several years.
--
next prev parent reply other threads:[~2011-05-04 18:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-04 16:03 Divide error in bictcp_cong_avoid ? TB
2011-05-04 17:49 ` Randy Dunlap
2011-05-04 18:33 ` Stephen Hemminger [this message]
2011-05-04 18:35 ` Randy Dunlap
2011-05-04 19:03 ` TB
2011-05-04 18:56 ` David Miller
2011-05-04 19:31 ` Valdis.Kletnieks
2011-05-04 19:37 ` Stephen Hemminger
2011-05-04 19:40 ` David Miller
2011-05-04 20:01 ` Valdis.Kletnieks
2011-05-04 20:04 ` [PATCH] tcp_cubic: limit delayed_ack ratio to prevent divide error Stephen Hemminger
2011-05-04 20:53 ` Brandeburg, Jesse
2011-05-06 16:15 ` TB
2011-05-06 16:53 ` Stephen Hemminger
2011-05-06 17:39 ` TB
2011-05-11 14:49 ` TB
2011-05-11 15:22 ` Stephen Hemminger
2011-05-11 15:35 ` TB
2011-05-08 22:52 ` David Miller
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=20110504113351.4643a0c9@nehalam \
--to=shemminger@vyatta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@techboom.com \
--cc=netdev@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/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.