From owner-freebsd-hackers Fri Jan 3 11:45:49 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA10191 for hackers-outgoing; Fri, 3 Jan 1997 11:45:49 -0800 (PST) Received: from kodiak.ucla.edu (kodiak.ucla.edu [164.67.128.11]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id LAA10184 for ; Fri, 3 Jan 1997 11:45:45 -0800 (PST) Received: from pita.cns.ucla.edu (pita.cns.ucla.edu [164.67.62.11]) by kodiak.ucla.edu (8.8.4/8.6.9) with SMTP id TAA22060 for ; Fri, 3 Jan 1997 19:45:42 GMT From: Scott Burris To: freebsd-hackers@FreeBSD.ORG Subject: 2.2-BETA hangs after a few minutes Message-ID: Date: Fri, 3 Jan 1997 11:45:42 -0800 (PST) Priority: NORMAL X-Mailer: Simeon for Motif Version 4.0.9 X-Authentication: none MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I've updated several of my FreeBSD systems at home with 2.2-BETA. One, a generic Triton chipset motherboard works just fine. The other, a Pentium system with the Opti chipset which connects the PCI bus to the VLB (instead of the other way around :-() now hangs solid after being up for anywhere between 10 and 30 minutes. No panics, no nothing, the system just appears to be completely dead. I compiled a new kernel with the debugger, but when the system hangs, I can't force it into the debugger. This system used to run the August 2.2 SNAP without problems and I have reverted back to that kernel. I'm happy to look into this further, but can anyone make a suggestion about how to debug a system that doesn't even panic? Scott ---------------------- Scott Burris UCLA Campus Telecomunications and Network Services scott@cns.ucla.edu