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, 25 Sep 2002 12:12:28 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 25 Sep 2002 12:12:28 -0400 Received: from thumper2.emsphone.com ([199.67.51.102]:25997 "EHLO thumper2.emsphone.com") by vger.kernel.org with ESMTP id ; Wed, 25 Sep 2002 12:12:27 -0400 Date: Wed, 25 Sep 2002 11:17:42 -0500 From: Andrew Ryan To: linux-kernel@vger.kernel.org Subject: Network related oops Message-ID: <20020925161742.GA9101@thumper2.emsphone.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Maybe this has been fixed in pre6/7, but here is a dump of a recent crash I had on one of our systems. There were NO modules loaded. ksymoops 2.4.0 on i686 2.4.20-pre5. Options used -V (default) -k /proc/ksyms (default) -l /proc/modules (default) -o /lib/modules/2.4.20-pre5/ (default) -m /boot/System.map-2.4.20-pre5 (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? Sep 25 08:12:13 jci1 kernel: wait_on_irq, CPU 2: Sep 25 08:12:13 jci1 kernel: irq: 1 [ 0 0 0 1 ] Sep 25 08:12:13 jci1 kernel: bh: 1 [ 1 1 0 1 ] Sep 25 08:12:13 jci1 kernel: Stack dumps: Sep 25 08:12:13 jci1 kernel: CPU 0: Sep 25 08:12:13 jci1 kernel: CPU 1:00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Sep 25 08:12:13 jci1 kernel: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Sep 25 08:12:13 jci1 kernel: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Sep 25 08:12:13 jci1 kernel: Call Trace: [] [] [] [] [] Sep 25 08:12:13 jci1 kernel: [] [] [] [] [] [] Sep 25 08:12:13 jci1 kernel: [] [] [] [] [] [] Sep 25 08:12:13 jci1 kernel: [] [] [] [] Sep 25 08:12:13 jci1 kernel: CPU 3:00000016 05802a10 e0244fd2 61010000 00000b6c 0002d4d9 6afb0000 00000014 Sep 25 08:12:13 jci1 kernel: 0502d917 e0244fd2 65010000 00000b6c 0002d448 64fe0000 0000000a 0280456c Sep 25 08:12:13 jci1 kernel: e0244fd2 6a020000 00000b6c 0002d4e8 63fd0000 00000011 04410456 e0244fd2 Sep 25 08:12:13 jci1 kernel: Call Trace: Sep 25 08:12:13 jci1 kernel: CPU 2:f7bfff28 c02781dd 00000002 00000001 ffffffff 00000002 c010a2b2 c02781f2 Sep 25 08:12:13 jci1 kernel: 00000000 f7502000 00000001 c01a42b8 f7502168 c02d9b84 f7bfff74 f7bfe664 Sep 25 08:12:13 jci1 kernel: f7bfe000 c011e2cd f7502000 f7502130 c02d9b84 00010000 f7bfe674 c0126e05 Sep 25 08:12:13 jci1 kernel: Call Trace: [] [] [] [] [] Sep 25 08:12:13 jci1 kernel: [] [] [] Warning (Oops_read): Code line not seen, dumping what data is available Trace; c022664d Trace; c0245397 Trace; c022664d Trace; c022673d <__kfree_skb+dd/e0> Trace; c0247aa8 Trace; c0227644 Trace; c024f89b Trace; c024f7cf Trace; c024fd8d Trace; c0237860 Trace; c0237be4 Trace; c0131563 Trace; c022a3e9 Trace; c022641f Trace; c01c8a3f Trace; c01c6a07 Trace; c0116383 Trace; c011de1b Trace; c011e39f Trace; c0107166 Trace; c011e2e0 Trace; c010a2b2 <__global_cli+e2/170> Trace; c01a42b8 Trace; c011e2cd <__run_task_queue+5d/70> Trace; c0126e05 Trace; c0126cc0 Trace; c0105000 <_stext+0/0> Trace; c0107166 Trace; c0126cc0 3 warnings issued. Results may not be reliable. Andy