public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Santiago Garcia Mantinan <manty@manty.net>
Cc: linux-kernel@vger.kernel.org, ebtables-devel@lists.sourceforge.net
Subject: Re: ebtables problems on 2.6.19.1
Date: Wed, 20 Dec 2006 10:24:05 +0100	[thread overview]
Message-ID: <45890135.9000306@trash.net> (raw)
In-Reply-To: <20061218082413.GA11064@clandestino.aytolacoruna.es>

Santiago Garcia Mantinan wrote:
> Hi!
> 
> When trying to upgrade a machine from 2.6.18 to 2.6.19.1 I found that it
> crashed when loading the ebtables rules on startup.
> 
> This is an example of the crash I get:
> 
> BUG: unable to handle kernel paging request at virtual address e081e004         
>  printing eip:                                                                  
> c0283da0                                                                        
> *pde = 1fbcb067                                                                 
> *pte = 00000000                                                                 
> Oops: 0000 [#1]                                                                 
> CPU:    0                                                                       
> EIP:    0060:[<c0283da0>]    Not tainted VLI                                    
> EFLAGS: 00010282   (2.6.19.1 #1)                                                
> EIP is at translate_table+0x600/0xe90                                           
>
> [..]
>
> I've tried to find a subset of the rules that are causing this and I found
> that to be very difficult as I have only got this to fail if I load the
> ebtables rules at boot time, if I try to load them after the machine is
> completely booted it works ok. 2.6.18 still works ok, both kernels have the
> "same" config where posible and they are not SMP.

At what point during boot time do you load your rules? Is networking
already up?

> The machine that was having the failure was a PIII 1GHz, I have copied the
> filesystem to a PIV 1.6Ghz where it also fails and where I can do tests and
> access the console via serial port.
> 
> The machine is not being used as a brouter but only as a bridge firewall, it
> has some ebtables rules to cut non IP stuff and then does all the work at
> iptables level.
> 
> I don't know what other info to add here, tell me if you need any other
> stuff to diagnose this or any testing here.

I'm trying to reproduce this (without success so far), please send your
kernel config and your ebtables script.

You could try if 2.6.19 works, there were some ebtables changes in
2.6.19.1 that touched this code.

  reply	other threads:[~2006-12-20  9:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-18  8:24 ebtables problems on 2.6.19.1 Santiago Garcia Mantinan
2006-12-20  9:24 ` Patrick McHardy [this message]
2006-12-24  3:07   ` ebtables problems on 2.6.19.1 *and* 2.6.16.36 Christopher S. Aker
2006-12-25  1:09     ` Christopher S. Aker

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=45890135.9000306@trash.net \
    --to=kaber@trash.net \
    --cc=ebtables-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manty@manty.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox