Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1763821AbXHVPJ0 (ORCPT ); Wed, 22 Aug 2007 11:09:26 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1762226AbXHVPJR (ORCPT ); Wed, 22 Aug 2007 11:09:17 -0400 Received: from re01.intra2net.com ([82.165.28.202]:4946 "EHLO re01.intra2net.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1760285AbXHVPJP (ORCPT ); Wed, 22 Aug 2007 11:09:15 -0400 From: Thomas Jarosch Organization: Intra2net AG To: linux-kernel@vger.kernel.org Subject: Re: Kernel oops during netfilter memory allocation Date: Wed, 22 Aug 2007 17:09:04 +0200 User-Agent: KMail/1.9.6 References: <200708201808.08880.thomas.jarosch@intra2net.com> <20070820193103.GC2488@martell.zuzino.mipt.ru> <200708211133.56261.thomas.jarosch@intra2net.com> In-Reply-To: <200708211133.56261.thomas.jarosch@intra2net.com> Cc: netfilter-devel@lists.netfilter.org MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200708221709.04992.thomas.jarosch@intra2net.com> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3358 Lines: 81 Hello, > > kernel BUG at arch/i386/mm/highmem.c:38 > > > > Try this. I just tried kernel 2.6.22.4 and 2.6.23-rc3. Using 2.6.23-rc3 vanilla, the box survives only 3 seconds with ipt_CRASH. Here's the backtrace, it's only slightly different: ------------[ cut here ]------------ kernel BUG at arch/i386/mm/highmem.c:38! invalid opcode: 0000 [#1] Modules linked in: ipt_CRASH iptable_filter ip_tables x_tables deflate zlib_deflate twofish twofish_common serpent blowfish des cbc ecb blkcipher aes xcbcd CPU: 0 EIP: 0060:[] Not tainted VLI EFLAGS: 00010286 (2.6.23-rc3 #1) EIP is at kmap_atomic_prot+0x24/0x83 eax: 0000000c ebx: c16eba60 ecx: c0002edc edx: 00000003 esi: 00000163 edi: 00000001 ebp: c16eba60 esp: f75f1b9c ds: 007b es: 007b fs: 0000 gs: 0000 ss: 0068 Process info_iponline (pid: 3469, ti=f75f0000 task=f7269ab0 task.ti=f75f0000) Stack: c16eba60 00000000 c013c695 00000001 00000044 40000000 00000001 00000000 00028020 c0327a3c c0327648 00000000 00000001 00000000 00000001 00000000 00008020 00008020 00000000 c0327a38 c013c778 00000044 63d210ac 00000000 Call Trace: [] get_page_from_freelist+0x1ed/0x284 [] __alloc_pages+0x4c/0x282 [] get_zeroed_page+0x3c/0x4a [] ipt_crash_target+0x0/0x48 [ipt_CRASH] [] ipt_crash_target+0x12/0x48 [ipt_CRASH] [] ipt_do_table+0x26d/0x2c8 [ip_tables] [] nf_iterate+0x38/0x6a [] nf_hook_slow+0x4d/0xb5 [] ip_local_deliver_finish+0x0/0x16b [] ip_local_deliver+0x72/0x1ea [] ip_local_deliver_finish+0x0/0x16b [] ip_rcv+0x3fb/0x428 [] getnstimeofday+0x2b/0xaf [] ktime_get_real+0xf/0x2b [] netif_receive_skb+0x219/0x269 [] e1000_clean_rx_irq+0x35a/0x42a [e1000] [] e1000_clean_rx_irq+0x0/0x42a [e1000] [] e1000_clean+0x304/0x4ae [e1000] [] get_unused_fd_flags+0x42/0xaa [] mntput_no_expire+0x11/0x47 [] __link_path_walk+0x83f/0x9de [] do_generic_mapping_read+0x3cd/0x3d5 [] net_rx_action+0x52/0xe9 [] __do_softirq+0x35/0x75 [] do_softirq+0x22/0x26 [] do_IRQ+0x58/0x6c [] find_lock_page+0x12/0x62 [] common_interrupt+0x23/0x28 [] __do_fault+0x136/0x2d1 [] handle_mm_fault+0x2c5/0x571 [] vma_merge+0x120/0x178 [] do_page_fault+0x212/0x58a [] do_page_fault+0x0/0x58a [] error_code+0x6a/0x70 [] tpacket_rcv+0x142/0x38e ======================= Code: 03 05 00 eb 38 c0 c3 56 89 ce 53 89 c3 89 e0 25 00 e0 ff ff ff 40 14 8b 0d f0 17 38 c0 8d 04 95 00 00 00 00 29 c1 83 39 00 74 04 <0f> 0b eb fe 8b 03 EIP: [] kmap_atomic_prot+0x24/0x83 SS:ESP 0068:f75f1b9c Kernel panic - not syncing: Fatal exception in interrupt ------------------------------------ Disabling highmem support seems to work as a temporary solution. Or does it only hide the symptoms of something really going wrong? Any help is greatly appreciated. Thomas - 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/