From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 23 May 2001 15:19:17 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 23 May 2001 15:19:08 -0400 Received: from imr1.ericy.com ([208.237.135.240]:42232 "EHLO imr1.ericy.com") by vger.kernel.org with ESMTP id ; Wed, 23 May 2001 15:18:52 -0400 From: "David Gordon (LMC)" To: linux-kernel@vger.kernel.org Cc: "Ibrahim Haddad (LMC)" Message-ID: <3B0C0D0B.2010101@lmc.ericsson.se> Date: Wed, 23 May 2001 15:18:35 -0400 User-Agent: Mozilla/5.0 (X11; U; Linux 2.4.4 i686; en-US; m18) Gecko/20001107 Netscape6/6.0 X-Accept-Language: en MIME-Version: 1.0 Subject: IPv6 implementation in kernel 2.4.4 oopses Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Hi, Can I be cc'ed at lmcdgor@lmc.ericsson.se (as per a normal reply) ? Thank you. Included at the end is the ksymoops output after the crash (one of them anyhow :-) My setup involves 2 PII installed with Linux RedHat 7.0 and 2.4.4 kernel with IPv6 enabled: CONFIG_EXPERIMENTAL=y CONFIG_IPV6=y CONFIG_IPV6_EUI64=y CONFIG_IPV6_NO_PB=y Also, the following application web servers were installed (enabled for IPv6) : Jigsaw 2.2.0 Tomcat 3.2.1 Apache 1.3.19 To enable IPv6 with the Java based web servers, I used jipsy 0.2.1. Lastly, netkit 0.5.1 was installed containing in particular ping6 utility. To reproduce the crash, I ping6'ed one machine from the other in command-line mode, no servers running. That's it. Originally, the first crash occurred in a X server environment while querying the web servers in IPv6. Thank you, David Gordon Ericsson Research Here's the output: ************** ksymoops 2.3.4 on i686 2.4.4. Options used -V (default) -k /proc/ksyms (default) -l /proc/modules (default) -o /lib/modules/2.4.4/ (default) -m /usr/src/linux/System.map (default) Warning: You did not tell me where to find symbol information. I will assume that the log matches the kernel and modules that are running right now and I'll use the default options above for symbol resolution. If the current kernel and/or modules do not match the log, you can get more accurate output by telling me the kernel version and where to find map, modules, ksyms etc. ksymoops -h explains the options. No modules in ksyms, skipping objects Warning (read_lsmod): no symbols in lsmod, is /proc/modules a valid lsmod file? Warning (compare_maps): ksyms_base symbol __VERSIONED_SYMBOL(shmem_file_setup) not found in System.map. Ignoring ksyms_base entry c0237bc4 *pde = 00000000 Oops: 0000 CPU: 0 EIP: 0010:[] Using defaults from ksymoops -t elf32-i386 -a i386 EFLAGS: 00010206 eax: c157c040 ebx: fffffffd ecx: 00000000 edx: 00000000 esi: 00000000 edi: 00000018 ebp: c15ac800 esp: c02f1e84 ds: 0018 es: 0018 ss: 0018 Process swapper (pid: 0, stackpage=c02f100) Stack: c023f913 00000000 00000000 c157c040 cfb8ebd4 c022fc6b cfcab780 00000000 c020ce8d cfcab780 010000e0 7d4985ce cfcab780 fffffffd ccf90d84 00000000 c15ac800 c023fe74 c15ac800 ccf90d20 ccf90d84 ccf90d84 00000000 c15ac800 Call Trace: [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] Code: 8b 11 f7 c2 e0 00 00 00 74 14 89 d0 25 e0 00 00 00 3d e0 00 >>EIP; c0237bc4 <===== Trace; c023f913 Trace; c022fc6b Trace; c020ce8d Trace; c023fe74 Trace; c020e986 Trace; c023fdc0 Trace; c02088a0 Trace; c011ac90 Trace; c0208710 Trace; c011afb6 Trace; c0117dfc Trace; c0117cb5 Trace; c0117b2d Trace; c0108a07 Trace; c01051a0 Trace; c0106ef8 Trace; c01051a0 Trace; c0100018 Trace; c01051cc Trace; c0105252 Trace; c0105000 Trace; c01001cf Code; c0237bc4 00000000 <_EIP>: Code; c0237bc4 <===== 0: 8b 11 mov (%ecx),%edx <===== Code; c0237bc6 2: f7 c2 e0 00 00 00 test $0xe0,%edx Code; c0237bcc 8: 74 14 je 1e <_EIP+0x1e> c0237be2 Code; c0237bce a: 89 d0 mov %edx,%eax Code; c0237bd0 c: 25 e0 00 00 00 and $0xe0,%eax Code; c0237bd5 11: 3d e0 00 00 00 cmp $0xe0,%eax Kernel panic: Aiee, killing interrupt handler! 3 warnings issued. Results may not be reliable. *********************** End email message