Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753545AbWLRIxq (ORCPT ); Mon, 18 Dec 2006 03:53:46 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753544AbWLRIxp (ORCPT ); Mon, 18 Dec 2006 03:53:45 -0500 Received: from ara.aytolacoruna.es ([195.55.102.196]:55950 "EHLO mx.aytolacoruna.es" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753540AbWLRIxp (ORCPT ); Mon, 18 Dec 2006 03:53:45 -0500 X-Greylist: delayed 1768 seconds by postgrey-1.27 at vger.kernel.org; Mon, 18 Dec 2006 03:53:44 EST Date: Mon, 18 Dec 2006 09:24:13 +0100 From: Santiago Garcia Mantinan To: linux-kernel@vger.kernel.org Cc: ebtables-devel@lists.sourceforge.net Subject: ebtables problems on 2.6.19.1 Message-ID: <20061218082413.GA11064@clandestino.aytolacoruna.es> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.5.13 (2006-08-11) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 5001 Lines: 79 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:[] Not tainted VLI EFLAGS: 00010282 (2.6.19.1 #1) EIP is at translate_table+0x600/0xe90 eax: e081df98 ebx: 0000000e ecx: e081df98 edx: e081df98 esi: 00000028 edi: dfb37cec ebp: e081d000 esp: dfb37c30 ds: 007b es: 007b ss: 0068 Process ebtables (pid: 609, ti=dfb36000 task=c14d1550 task.ti=dfb36000) Stack: e081df4c 00000024 e081b000 dfb37cec 00000020 00000000 00000010 00000000 00000000 00000fc8 00000f98 e081df98 00000044 00000110 00000001 00000001 00000110 00000138 00000000 00000000 e081d000 e081df98 00000005 00000010 Call Trace: [] do_ebt_set_ctl+0x28f/0x6b0 [] __alloc_pages+0x4f/0x2e0 [] nf_sockopt+0xad/0x100 [] nf_setsockopt+0x1e/0x30 [] ip_setsockopt+0x12c/0xc50 [] do_page_fault+0x0/0x640 [] error_code+0x39/0x40 [] current_fs_time+0x48/0x60 [] touch_atime+0x5d/0xb0 [] do_generic_mapping_read+0x385/0x490 [] file_read_actor+0x0/0x100 [] generic_file_aio_read+0xf0/0x220 [] __alloc_pages+0x4f/0x2e0 [] filemap_nopage+0x14d/0x350 [] unmap_vmas+0x29d/0x480 [] __handle_mm_fault+0x53e/0x630 [] free_pgtables+0x85/0xb0 [] sock_common_setsockopt+0x23/0x30 [] sys_setsockopt+0x5f/0xb0 [] sys_socketcall+0x209/0x280 [] do_page_fault+0x0/0x640 [] syscall_call+0x7/0xb [] br_stp_change_bridge_id+0xb/0x1a0 ======================= Code: 17 0f 83 a2 03 00 00 8b 4c 24 08 8b 5c 24 28 8b 7c 24 0c 8b 69 24 01 eb 89 5c 24 2c 8b 44 24 2c 8b 54 24 2c 8b 5f 20 8b 4c 24 2c <8b> 40 6c 89 44 24 44 8b 52 68 89 54 24 40 8b 01 85 c0 0f 84 3a EIP: [] translate_table+0x600/0xe90 SS:ESP 0068:dfb37c30 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. 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. Regards... -- Santiago Garc?a Manti??n - 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/