[660] in arla-drinkers

home help back first fref pref prev next nref lref last post

Re: arla-0.22 + netbsd-current (19990301, i386, 1.3J) == crash

daemon@ATHENA.MIT.EDU (assar@stacken.kth.se)
Wed Mar 3 19:26:06 1999

From owner-arla-drinkers@stacken.kth.se Thu Mar 04 00:26:04 1999
Return-Path: <owner-arla-drinkers@stacken.kth.se>
Delivered-To: arla-drinkers-mtg@bloom-picayune.mit.edu
Received: (qmail 5536 invoked from network); 4 Mar 1999 00:26:03 -0000
Received: from unknown (HELO sundance.stacken.kth.se) (130.237.234.41)
  by bloom-picayune.mit.edu with SMTP; 4 Mar 1999 00:26:03 -0000
Received: (from majordom@localhost)
	by sundance.stacken.kth.se (8.8.8/8.8.8) id BAA02977
	for arla-drinkers-list; Thu, 4 Mar 1999 01:20:25 +0100 (MET)
Received: from dyn02.trafford.dementia.org (dyn02.trafford.dementia.org [204.29.154.130])
	by sundance.stacken.kth.se (8.8.8/8.8.8) with ESMTP id BAA02971
	for <arla-drinkers@stacken.kth.se>; Thu, 4 Mar 1999 01:20:19 +0100 (MET)
Received: (from assar@localhost) by dyn02.trafford.dementia.org (8.9.1/8.7.3) id BAA66078; Thu, 4 Mar 1999 01:22:44 +0100 (CET)
From: assar@stacken.kth.se
To: Johan Ihren <johani@pdc.kth.se>
Cc: arla-drinkers@stacken.kth.se
Subject: Re: arla-0.22 + netbsd-current (19990301, i386, 1.3J) == crash
References: <199903040013.BAA00198@wanda.pdc.kth.se>
Mime-Version: 1.0 (generated by tm-edit 7.68)
Content-Type: text/plain; charset=US-ASCII
Date: 04 Mar 1999 01:22:37 +0100
In-Reply-To: Johan Ihren's message of "Thu, 4 Mar 1999 01:13:27 +0100 (CET)"
Message-ID: <5lr9r66r3m.fsf@mg.trafford.dementia.org>
Lines: 22
X-Mailer: Gnus v5.5/Emacs 19.34
Sender: owner-arla-drinkers@stacken.kth.se
Precedence: bulk

Johan Ihren <johani@pdc.kth.se> writes:
> Doing just the modload in console mode gave the following info that I
> didn't see before because of X11:
> 
> uvm_fault(<addr>, 0, 0, 1) -> 1
> kernel: page fault trap, code=0
> Stopped in modload at _vfs_opv_init+09:         cmpl    $0,0(%edi)

Can you print out %edi ?  I would also be interested in a backtrace.

> Doing a ps in ddb just shows all the expected processes (including
> the modload process). Is there anything in particular you are interested in?

Given the above, it's not interesting.  But if the machine would just
hang I would be interested in if there are any processes with a wait
channel of "xfs".

> For some strange reason I cannot just paste the complete output in ;-)

:-)

/assar

home help back first fref pref prev next nref lref last post