From owner-freebsd-current@FreeBSD.ORG Sat Nov 13 19:45:41 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DB2A516A4CE for ; Sat, 13 Nov 2004 19:45:41 +0000 (GMT) Received: from mail2000-2.so-net.net.tw (mail2000-2.so-net.net.tw [61.64.127.18]) by mx1.FreeBSD.org (Postfix) with SMTP id EE16D43D3F for ; Sat, 13 Nov 2004 19:45:40 +0000 (GMT) (envelope-from yongjhen@alqualonde.org) Received: from 61.62.136.104V3.20S(94435:2:AUTH_RELAY) (envelope-from ); Sun, 14 Nov 2004 03:45:12 +0800 (CST) Message-ID: <41966447.1010903@alqualonde.org> Date: Sun, 14 Nov 2004 03:45:11 +0800 From: Yong-Jhen Hong User-Agent: Mozilla Thunderbird 0.9 (Macintosh/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Godwin Stewart References: <20041110001055.5548c227.gstewart@bonivet.net> In-Reply-To: <20041110001055.5548c227.gstewart@bonivet.net> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: 5.3-RELEASE: WARNING - WRITE_DMA interrupt timout - what does it mean? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Nov 2004 19:45:42 -0000 Godwin Stewart wrote: > On Tue, 9 Nov 2004 15:01:41 -0800, "Zoltan Frombach" > wrote: > >>I just upgraded to 5.3-RELEASE a few days ago. This morning this line got >>into my system log file: >>Nov 9 06:14:03 www kernel: ad0: WARNING - WRITE_DMA interrupt was seen >>but timeout fired LBA=2491143 >> >>I've never seen this message before. Can someone please explain what it >>means? With Thanks, > > Looks like you may have a hard disk about to die. I'd start doing backups if > I were you and then consider replacing the HD. > I can easily reproduce this warning message with 'pkg-config xxx', xxx is anything can not be found in 'pkg-config --list-all'. My system has nearly no response (console, network, etc.) after that. From that I find 'gnome-config' is symbolic-linked to 'pkg-config' on my system(!). When 'pkg-config' can't find anything about 'xxx', it calls 'gnome-config', and 'gnome-config'('pkg-config') calls 'gnome-config'('pkg-config') calls...:) 65751 v1 S+ 0:00.01 pkg-config xxx 65752 v1 S+ 0:00.01 sh -c gnome-config --libs xxx > /dev/null 2>&1 65753 v1 S+ 0:00.01 gnome-config --libs xxx (pkg-config) 65754 v1 S+ 0:00.01 sh -c gnome-config --libs xxx > /dev/null 2>&1 65755 v1 S+ 0:00.01 gnome-config --libs xxx (pkg-config) 65756 v1 S+ 0:00.01 sh -c gnome-config --libs xxx > /dev/null 2>&1 65757 v1 S+ 0:00.01 gnome-config --libs xxx (pkg-config) 65758 v1 S+ 0:00.01 sh -c gnome-config --libs xxx > /dev/null 2>&1 65759 v1 S+ 0:00.01 gnome-config --libs xxx (pkg-config) ...