From owner-freebsd-current Sat Nov 18 05:40:28 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id FAA24523 for current-outgoing; Sat, 18 Nov 1995 05:40:28 -0800 Received: from hauki.clinet.fi (root@hauki.clinet.fi [194.100.0.1]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id FAA24506 for ; Sat, 18 Nov 1995 05:40:18 -0800 Received: from katiska.clinet.fi (root@katiska.clinet.fi [194.100.0.4]) by hauki.clinet.fi (8.6.12/8.6.4) with ESMTP id PAA24835 for ; Sat, 18 Nov 1995 15:40:03 +0200 Received: (news@localhost) by katiska.clinet.fi (8.6.12/8.6.4) id PAA23086; Sat, 18 Nov 1995 15:40:12 +0200 To: clinet-list-freebsd-current@clinet.fi Path: cs.hut.fi!hsu From: hsu@cs.hut.fi (Heikki Suonsivu) Newsgroups: clinet.list.freebsd-current Subject: Re: 2.1-stable just hangs Date: 18 Nov 1995 13:40:05 GMT Organization: Helsinki University of Technology, Finland Lines: 29 Message-ID: References: NNTP-Posting-Host: shadows.cs.hut.fi In-reply-to: Tom Samplonius's message of 17 Nov 1995 20:14:09 +0200 Sender: owner-current@FreeBSD.ORG Precedence: bulk In article Tom Samplonius writes: > sometimes (at elast 2 times a weak) a p55tp4xe with p90, 32mb Ram, > 2940 , smc elite + just hangs. ASUS SIS chipset based board + p90 + 64mB + 2 * NCR SCSI + probably smc isa ethernet board. Around same frequency, but we also get disk errors sometimes (seagate hawks currently). > You can still enter commands on any ttys and ptys but as soon as the > command is to be executed, the machine hangs. pressing reset is the > only way to get it going again. > Any hints on debugging this? I have seen this before, with same motherboard and SCSI controller. It turned out to be heat related. I just left the cover off the system, and so far it is hasn't happened again. The cause may be overheated disks getting looped, but there still is a bug in kernel if the situation is not detected (it should do *something*, even reboot would be better than getting hung). I also saw this after a nfs server (FreeBSD 1.1.5.1) got its nfsd processes killed somehow (out of swap, maybe), the -current machine deadlocked like above after printing couple of nfs errors. -- Heikki Suonsivu, T{ysikuu 10 C 83/02210 Espoo/FINLAND, hsu@cs.hut.fi home +358-0-8031121 work -4513377 fax -4555276 riippu SN