From owner-freebsd-hackers Sat Jul 1 18:43:39 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id SAA10537 for hackers-outgoing; Sat, 1 Jul 1995 18:43:39 -0700 Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id SAA10531 for ; Sat, 1 Jul 1995 18:43:37 -0700 Received: from localhost.v-site.net (localhost.v-site.net [127.0.0.1]) by rah.star-gate.com (8.6.11/8.6.9) with SMTP id SAA08530; Sat, 1 Jul 1995 18:42:14 -0700 Message-Id: <199507020142.SAA08530@rah.star-gate.com> X-Authentication-Warning: rah.star-gate.com: Host localhost.v-site.net didn't use HELO protocol X-Mailer: exmh version 1.6delta 4/7/95 To: Matt Thomas cc: hackers@freebsd.org Subject: Re: Best way to diagnose system lockups? In-reply-to: Your message of "Sat, 01 Jul 1995 18:03:48 -0000." <199507011803.SAA09932@whydos.lkg.dec.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 01 Jul 1995 18:42:12 -0700 From: Amancio Hasty Sender: hackers-owner@freebsd.org Precedence: bulk >>> Matt Thomas said: > > I'm trying to debug why FreeBSD lockups when using a 4 port Ethernet > controller. (it's a PCI board with 4 DC21040's sitting behind a DC21050 > PCI-PCI bridge; it's UTP only). Have you considered tcpdump ? Perhaps snooping on the ether traffic from another machine may help. A circular trace buffer in your driver so that if the system locks up and you can get in you can find out what where the last few operations from your driver. Not sure if this matters but I heard from Best.com that their ftp site is or was locking up once a day so it may not be your driver. Regards, Amancio