[Bugme-new] [Bug 9173] New: BUG: soft lockup detected on CPU#0 - maybe related to TCP_MD5SIG

bugme-daemon at bugzilla.kernel.org bugme-daemon at bugzilla.kernel.org
Wed Oct 17 07:34:50 PDT 2007


http://bugzilla.kernel.org/show_bug.cgi?id=9173

           Summary: BUG: soft lockup detected on CPU#0 - maybe related to
                    TCP_MD5SIG
           Product: Networking
           Version: 2.5
     KernelVersion: 2.6.20-9-server-lp2
          Platform: All
        OS/Version: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: IPV4
        AssignedTo: shemminger at linux-foundation.org
        ReportedBy: tore at linpro.no
                CC: yoshfuji at linux-ipv6.org


Most recent kernel where this bug did not occur: 2.6.12 (with
TCP_MD5SIG-implementation from
http://hasso.linux.ee/doku.php/english:network:rfc2385)
Distribution: Ubuntu 6.06.1 LTS
Hardware Environment: Sun X4100 (x86_64, SMP)
Software Environment: Ubuntu 2.6.20-9-server-lp2 (-lp2 because it's recompiled
with TCP_MD5SIG enabled), 64-bits userspace
Problem Description:

The server is a border router running Quagga for BGP and OSPF, and usually
forwards 4-500Mbps worth of traffic between around 80 VLAN interfaces.  Four
network interfaces, bonded pairwise.  It has three BGP sessions with MD5
signatures enabled.

The server has an identical twin (for failover) which has also locked up like
this, although it happens much more frequently on the active one (no matter
which one is active, unfortunately).  We've got lots of these servers, but only
the border routers have had these lockups.

Once in a while (say, once every four to six weeks) it will flood the console
with BUG: soft lockup detected on CPU#0! and shortly after fail completely.This
time I had increased the default prink level one notch and got the back traces
too.  I'm not used to reading those, but the md5sig stuff seems to stand out...

I'll try to attach the trace somehow (got an error message about the bug being
to large when attempting to include it here).

Steps to reproduce:  It happens completely out of the blue, so I don't know
how.

Tore


-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


More information about the Bugme-new mailing list