From owner-freebsd-hackers Tue Aug 18 18:25:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA18467 for freebsd-hackers-outgoing; Tue, 18 Aug 1998 18:25:06 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from umgah.obscurity.net (umgah.obscurity.net [198.88.183.247]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA18461 for ; Tue, 18 Aug 1998 18:25:04 -0700 (PDT) (envelope-from lb@umgah.obscurity.net) Received: (from lb@localhost) by umgah.obscurity.net (8.8.8/8.8.8) id UAA00414; Tue, 18 Aug 1998 20:24:43 -0500 (CDT) (envelope-from lb) Message-ID: <19980818202442.13894@obscurity.net> Date: Tue, 18 Aug 1998 20:24:42 -0500 From: lb To: freebsd-hackers@FreeBSD.ORG Subject: An odd crash Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i Organization: Molebat Heavy Industries Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi there. I've run FreeBSD a few years now, and it's been wonderfully stable (save when I was attacked a few times -- oh well :) ... But today it seemed to die "on its own" -- while I was using tin, doing *nothing* to provoke it as best I could tell... this is all I saw in my logs, before the box died: Aug 18 10:08:02 umgah /kernel: FIOASYNC Aug 18 10:11:18 umgah /kernel: FIOASYNC Aug 18 10:11:19 umgah /kernel: timeout flushing dbuf_out, chan 1 cnt 0xa44 4 flags 0x00000041 ... it locked up, but did not reboot... video froze, keyboard froze (I could not hit numlock to toggle my lights, etc) ... no network interactions did anything -- couldn't ping it. Someone suggested I mail this here, and that perhaps someone could explain to me what this means/what might cause it. Incidental information: this is a 2.2.6-RELEASE box with luigi's pnp mods. (Soon to be upgraded, don't smack me :) lb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message