All of lore.kernel.org
 help / color / mirror / Atom feed
From: kwijibo@zianet.com
To: Roland Kuhn <rkuhn@e18.physik.tu-muenchen.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kernel BUG at tg3.c:1557
Date: Wed, 07 Aug 2002 13:52:24 -0600	[thread overview]
Message-ID: <3D517A78.704@zianet.com> (raw)
In-Reply-To: Pine.LNX.4.44.0208071332110.3394-100000@pc40.e18.physik.tu-muenchen.de

I just tried this on a dual Athlon box with two 7850's in it
and a 3C996B-T as well.  Lucky for me though, this
error did not show up.  I transfered/received two 800MB files
to the RAID and it held up ok.  What driver version are you
using? Or even kernel version.

Steve

Roland Kuhn wrote:

>Dear kernel hackers!
>
>I've been chasing this bug now for weeks without further ideas, so please 
>tell me your thoughts about it:
>
>On a dual Athlon MP with a 3ware-7850 RAID (640GB RAID-5) and 3C996B-T GE 
>NIC I can crash the machine with the above BUG message in virtually no 
>time simply by copying data both ways between the RAID and the NIC. The 
>BUG message shows that this can happen any time, it doesn't matter if the 
>interrupt is received in cpu_idle or something else. I tried noapic, but 
>to no avail.
>
>Does anybody know about this problem?
>How can I get more debugging information?
>Can the driver be patched to gracefully handle this situation, e.g. by 
>resetting the card and trying again?
>
>What I've found out till now is only that the kernel's and the NIC's view 
>of the world seem to be inconsistent :-(
>
>For our application stability is much more important than a few TCP 
>retransmits...
>
>Thanks in advance,
>					Roland
>
>+---------------------------+-------------------------+
>|    TU Muenchen            |                         |
>|    Physik-Department E18  |  Raum    3558           |
>|    James-Franck-Str.      |  Telefon 089/289-12592  |
>|    85747 Garching         |                         |
>+---------------------------+-------------------------+
>
>-
>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/
>
>
>  
>




  parent reply	other threads:[~2002-08-07 19:41 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-07 11:40 kernel BUG at tg3.c:1557 Roland Kuhn
2002-08-07 13:14 ` Alan Cox
2002-08-07 12:03   ` David S. Miller
2002-08-07 14:25     ` Roland Kuhn
2002-08-07 14:20       ` David S. Miller
2002-08-07 14:49         ` Roland Kuhn
2002-08-07 14:48           ` David S. Miller
2002-08-07 15:36             ` Roland Kuhn
2002-08-07 15:24               ` David S. Miller
2002-08-07 16:28                 ` Roland Kuhn
2002-08-07 19:18                   ` [SOLVED] " Roland Kuhn
2002-08-07 19:43                     ` Roland Kuhn
2002-08-07 12:22   ` kernel
2002-08-07 13:08   ` Willy Tarreau
2002-08-07 19:52 ` kwijibo [this message]
2002-08-07 19:53   ` Roland Kuhn
2002-08-07 21:41     ` kwijibo
2002-08-07 22:10       ` Roland Kuhn
2002-08-07 22:40         ` David S. Miller
2002-08-08  8:33           ` Roland Kuhn
2002-08-08 12:39             ` Roland Kuhn
2002-08-08 15:32               ` David S. Miller
2002-08-30 23:43           ` David S. Miller
2002-09-11  9:11             ` Roland Kuhn
2002-09-18 13:57             ` Ryan Sweet
2002-08-07 23:42   ` Alan Cox

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=3D517A78.704@zianet.com \
    --to=kwijibo@zianet.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rkuhn@e18.physik.tu-muenchen.de \
    /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.