From: TB <lkml@techboom.com>
To: Stephen Hemminger <shemminger@vyatta.com>
Cc: netdev@vger.kernel.org
Subject: Re: divide error: 0000, in bictcp_cong_avoid, kernel 2.6.39
Date: Thu, 01 Sep 2011 16:30:35 -0400 [thread overview]
Message-ID: <4E5FEB6B.2040204@techboom.com> (raw)
In-Reply-To: <4E1369FA.1090008@techboom.com>
On 11-07-05 03:46 PM, TB wrote:
> On 11-07-05 01:16 PM, Stephen Hemminger wrote:
>> On Mon, 04 Jul 2011 14:10:16 -0400
>> TB <lkml@techboom.com> wrote:
>>
>>> On 11-07-04 01:36 PM, Stephen Hemminger wrote:
>>>> Any data about the type of connection, kernel configuration or other
>>>> information that might be useful in reproducing the problem?
>>>>
>>>> Also please try 2.6.39.2
>>>
>>> We haven't found a sure way of reproducing it.
>>> It happened on 1.2% of our servers over the weekend and seems random.
>>> Both are connected with 2 gigabit ports using bonding. Traffic tends to
>>> be heavy, but doesn't seem to be a factor.
>>>
>>> Would a .config help ?
>>>
>>> Only the very basic filter module for iptables is compiled in.
>>>
>>> We will try 2.6.39.2 soon
>>
>> Kernel config (and compiler version) would help in identifying which
>> of the three divides is getting divide by zero.
>
> # gcc --version
> gcc (Debian 4.3.2-1.1) 4.3.2
>
>
> # as --version
> GNU assembler (GNU Binutils for Debian) 2.18.0.20080103
> This assembler was configured for a target of `x86_64-linux-gnu'.
We have tried 3.0.4 and the bug is still present, however we have still
been unable to get a proper backtrace. It seems a lot of times the
netlog isn't working.
prev parent reply other threads:[~2011-09-01 21:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-04 14:23 divide error: 0000, in bictcp_cong_avoid, kernel 2.6.39 TB
2011-07-04 17:36 ` Stephen Hemminger
2011-07-04 18:10 ` TB
2011-07-05 17:16 ` Stephen Hemminger
2011-07-05 19:46 ` TB
2011-09-01 20:30 ` TB [this message]
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=4E5FEB6B.2040204@techboom.com \
--to=lkml@techboom.com \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.com \
/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.