From owner-freebsd-alpha Thu Apr 13 17:48:50 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 41DF637BCB9 for ; Thu, 13 Apr 2000 17:48:48 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id UAA27437; Thu, 13 Apr 2000 20:48:47 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id UAA72867; Thu, 13 Apr 2000 20:48:16 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 13 Apr 2000 20:48:16 -0400 (EDT) To: "brian j. peterson" Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: ICMP flood causes panic? In-Reply-To: References: X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14582.26816.657967.136182@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org brian j. peterson writes: > amidst an ICMP flood today, my machine panicked. i have included what i > think is the relevant syslog info below. (the kernel on this box was > built from a CVSup to FreeBSD/alpha 4.0-CURRENT on or about March > 4th... world was rebuilt at the same time.) anyone care to tell me where > the problem lies? (my box, FreeBSD, both, neither?) if more info is > required, please ask me for it. > <...> > Apr 13 16:16:21 nikita /kernel: mces = 0x1 > Apr 13 16:16:21 nikita /kernel: vector = 0x660 > Apr 13 16:16:21 nikita /kernel: param = 0xfffffc0000006000 > Apr 13 16:16:21 nikita /kernel: pc = 0xfffffc0000383278 > Apr 13 16:16:21 nikita /kernel: ra = 0xfffffc00005075d4 > Apr 13 16:16:21 nikita /kernel: curproc = 0 > Apr 13 16:16:21 nikita /kernel: > Apr 13 16:16:21 nikita /kernel: panic: machine check > Apr 13 16:16:21 nikita /kernel: > Apr 13 16:16:21 nikita /kernel: syncing disks... ncr0:0: ERROR (20:0) (0-20-0) (8/13) @ (script 918:18000120). There's really not a whole lot of information to go on here. It might help if you were able to map the above pc and ra to functions in the kernel. If you have a kernel with symbols (kernel.debug from config -g), try gdb on the kernel, then do (gdb) l *0xfffffc0000383278 (gdb) l *0xfffffc00005075d4 If you don't have a debug kernel, map the addresses to functions via nm -n. BTW, Can you reproduce this? Thanks, Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message