netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michał Margula" <alchemyx@uznam.net.pl>
To: Bart De Schuymer <bdschuym@pandora.be>
Cc: Andrew Morton <akpm@osdl.org>, netdev@oss.sgi.com
Subject: Re: Fw: [Bugme-new] [Bug 3746] New: Bridge causes machine lockups
Date: Sun, 21 Nov 2004 23:21:23 +0100	[thread overview]
Message-ID: <41A114E3.5070705@uznam.net.pl> (raw)
In-Reply-To: <200411211727.43320.bdschuym@pandora.be>

Bart De Schuymer napisał(a):

># cd /usr/src/linux-2.6.9/
># patch -p1 < patch
>When your system hangs again, the message "EBTABLES: BEFORE WRITE LOCK"
>should be in your syslog, and check that it is not followed by "EBTABLES: 
>AFTER WRITE LOCK".
>
>  
>
I have just applied that patch. Tomorrow I will reboot a new kernel. So 
in about no more than two days, I should get some results.

>Is the bridge still forwarding packets while it hangs?
>
>  
>
No. Box is completly frozen.

>Perhaps try to link all network traffic to one cpu before doing your ebtables 
>updates...
>  
>
Could you give me more details about that? Should it be done before 
updating ebtables, and after that reverting? And most important - how? :).


-- 
Michał Margula, alchemyx@uznam.net.pl, http://alchemyx.uznam.net.pl/
"W życiu piękne są tylko chwile" [Ryszard Riedel]

      reply	other threads:[~2004-11-21 22:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-15 20:20 Fw: [Bugme-new] [Bug 3746] New: Bridge causes machine lockups Andrew Morton
2004-11-15 20:46 ` Bart De Schuymer
2004-11-15 20:48   ` Andrew Morton
2004-11-15 21:57     ` Michał Margula
2004-11-16 10:16     ` Michał Margula
2004-11-18 11:27     ` Michał Margula
2004-11-18 19:59       ` Bart De Schuymer
2004-11-21 16:27       ` Bart De Schuymer
2004-11-21 22:21         ` Michał Margula [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=41A114E3.5070705@uznam.net.pl \
    --to=alchemyx@uznam.net.pl \
    --cc=akpm@osdl.org \
    --cc=bdschuym@pandora.be \
    --cc=netdev@oss.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).