From owner-freebsd-current Sun Dec 20 10:31:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA06897 for freebsd-current-outgoing; Sun, 20 Dec 1998 10:31:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp03.wxs.nl (smtp03.wxs.nl [195.121.6.37]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA06891 for ; Sun, 20 Dec 1998 10:31:09 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from chronias.ninth-circle.org ([195.121.56.64]) by smtp03.wxs.nl (Netscape Messaging Server 3.6) with ESMTP id AAA1895 for ; Sun, 20 Dec 1998 19:31:06 +0100 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Sun, 20 Dec 1998 19:37:25 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: FreeBSD Current Subject: Problem with SCSI-bus and high diskaccess? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I just want some thoughts on this: In the last 24 hours my workstation is been going nuts, whereas it has been running along nicely for weeks before. The things that kept me bugging today were these happy messages: Dec 20 10:51:14 chronias /kernel: Unexpected busfree. LASTPHASE == 0xa0 Dec 20 10:51:15 chronias /kernel: SEQADDR == 0x157 Dec 20 10:51:15 chronias /kernel: (da1:ahc0:0:1:0): SCB 0x5 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0xc Dec 20 10:51:15 chronias /kernel: (da1:ahc0:0:1:0): Queuing a BDR SCB Dec 20 10:51:15 chronias /kernel: (da1:ahc0:0:1:0): Bus Device Reset Message Sent Dec 20 10:51:15 chronias /kernel: (da1:ahc0:0:1:0): no longer in timeout, status = 353 After which page and swap process were running wild. The weird thing is, these HD's (two SCSI Quantum Fireballs) have been checked, the HA (AHA 2940UW) is likewise in good shape and the memory chips have been tested as well... The mainboard is also in good shape and is cooled by a few fans (3) which all work, including the one on the CPU. The circumstances when this happened was when I did a locate.updatedb at the same time as downloading a PDF file to the HD, and then I opened a mailbox at which time the whole time went haywire... Unfortunately I wasn't able to write down the pager messages since they went by with warpspeed 9 and they weren't logged in /var/log/messages =\ Does anybody have any ideas what to check to narrow down the problem? --- Jeroen Ruigrok van der Werven Life is the only Pain asmodai(at)wxs.nl we endeavour... Network/Security Specialist BSD & picoBSD: The Power to Serve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message