From owner-freebsd-stable Thu Dec 27 16: 0: 7 2001 Delivered-To: freebsd-stable@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id C733F37B417; Thu, 27 Dec 2001 15:59:47 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id fBRNxjK90152; Thu, 27 Dec 2001 15:59:45 -0800 (PST) (envelope-from dillon) Date: Thu, 27 Dec 2001 15:59:45 -0800 (PST) From: Matthew Dillon Message-Id: <200112272359.fBRNxjK90152@apollo.backplane.com> To: "Kristian K. Nielsen" Cc: "Nils Holland" , =?iso-8859-1?Q?S=F8ren_Schmidt?= , "Matthew Gilbert" , , Subject: Re: 4.4-STABLE crashes - suspects new ata-driver over wd-drivers References: <200112262355.fBQNtfK48250@apollo.backplane.com> <200112270945.fBR9j1e97273@freebsd.dk> <20011227163252.A151@tisys.org> <200112271847.fBRIlxh52129@apollo.backplane.com> <008d01c18f2f$ab983b40$bb5ca8c0@jkkn.net> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :Hey, : :It is great if you are finding a solution for the VIA-chipset. :Do you have any idea if it is a simular problem that I am experiencing? : :I am not enough into chip code to have a clue what exactly the patch :is doing - but maybe it is just decreasing the load on the kernel/system in :a :way that the crashes are avoided tough there is still a bug outthere :somewhere?! : :I do not have a single VIA-chip in my box that I know of - all Intel :and is running the latest BIOS version avialable for my motherboard :and still having crashes whenever I put any pressure on the box, like :compiling/moving large files across filesystems/etc: Well, as Soren says, there are lots of things that can result in crashes. In order for us to attempt to diagnose the crashes you are having you need to post a backtrace of that core file - usually it is a good idea to do it with the kernel.debug binary from the kernel build directory rather then the stripped 'kernel' that the crash dump saves, but either will work for a start. cd /var/crash gdb -k kernel.4 vmcore.4 gdb> back If you have the kernel.debug associated with the kernel, usually found in the original build directory (i.e. /usr/src/sys/compile /JKKN_KRNL/kernel.debug) if you had done a config -g or used the makeoptions DEBUG=-g option in the kernel config file, then you can gdb using the debug binary and get a much more interesting back trace. cd /var/crash gdb -k /usr/src/sys/compile/JKKN_KRNL/kernel.debug vmcore.4 gdb> back -Matt :dumpon: crash dumps to /dev/ad0s1b (116, 131073) :Checking for core dump: :savecore: reboot after panic: page fault :Dec 26 04:11:11 jkkn savecore: reboot after panic: page fault :savecore: system went down at Wed Dec 26 04:07:57 2001 :savecore: writing core to /var/crash/vmcore.4 : :.....snip end..... : :Regards :Kristian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message